dolphin_oracle wrote: Thu Oct 10, 2019 12:34 pm
bpr323 wrote: Wed Oct 09, 2019 8:58 pm
d) as above, let's create
gpt partitions table (but no partitions) and format entire disk to Ext4 ->
FAIL
e) let's create a new gpt partitions table and
leave the disk unformatted -
SUCCESS
I would love to see /var/log/minstall.log files for those 2 install cases.
BTW, if you formated the whole disk, you actually just made 1 big partition, so partition was involved, just not multiple partitions. This is an important distiction for the debugging, and it makes the difference between d and e interesting.
Also, what options did you use to create your LUM usb device? "Full-Featured" or "dd" mode.
Sorry, I didn't keep the logs after the final try which ended with successful install - I was stoked it finally worked for me!
I assumed the "live" logs would have been blown away anyway. But it's really easy to replicate just following my use cases :)
For LUM I used full-featured + optionals ticked for force gpt and force ext4 even if it exists
I do have some photos I was taking of Gparted screen with (i)'s related to missing data in failed partitions - do you want them?
In essence, the only path that worked was to create a new gpt partitions table and leave it unformatted w/o creating any actual partitions.
I'm guessing you want to make Minstall to trap the errors and do some overriding steps to process them as exceptions?
The biggest problem is the use case where user installs side by side with to keep a Windows install - then my "whole-disk" workaround would be a disaster.
But I didn't try those scenarios with "custom" (manual partitioning) install - if I need Windows, I'll install it on a "free" VMware workstation Player/Pro.
I think it's a deathwish to try and install Linux side by side with Win on the same disk - unless you're a masochist, of course