Should have been: * while parted does show it as well.
Out of curiosity, I gave a go to fedora server and it seems to work(
with one minor detail when it comes to partitioning).
Im going to alter title, as it is wrong.
General flaw seems to be LVM mixing drives/CC partition table onto another:
Possibly original tittle might be wrong. Ive reset physical connections and
BIOS, but could not reproduce ID switch. I might just have been tired and
imagined it. Nevertheless, installation still fail.
Through trial and error one thing is clear - plain HDD install( no LVM/Crypto)
does work like
** Package changed: ubuntu => subiquity (Ubuntu)
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929213
Title:
Ubuntu server fails to install if boot is not on sda1
To manage
Im thinkering with ubuntu server 20.10 from live USB.
I tried single drive install and it worked. Once it went live I tried minimal
setup on two SSDs( /boot, /boot/efi and encrypted LVM with rest on both). Not
sure if its relevant but I can see in crash report:
"adding partition 'partition-3'
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1929213
When reporting bugs in the future please use apport by using 'ubuntu-
Upon further investigation - it might be connected to BIOS screwing up
order. Part of installer see wrong order, but scripts most likely see it
differently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929213
Title:
Ubuntu server fails to install if boot is not on sda1
To manage notifications about this bug go
