Never mind what I wrote. I was seeing so many differences in the boot
load that I went ahead and wiped the drive clean, set the zero fill
option, reset the MBR and reformatted as ext4. Grab the up to date ISO,
and re-installed 20.04 LTS. I let the install run as a normal full
install, and the partitions that completed were as first noticed. sda1
vfat, sda2 extended, sda5 ext4. So that IS the default installer
locations. Had never seen that arrangement on Ubuntu ever, so I assumed
the arrangement were based on a previous Win10 partition. I was
incorrect and apologize for the bug tracker. I guess the real answer
here is to not run boot repair on a new install, as it will put the boot
files in the wrong place and effect booting. In closing, as stated above
"the reporter is confused".
Can we know why this partition arrangement was needed?
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/690540
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876733
Title:
GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr
partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876733/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
