[Bug 1929213] Re: Ubuntu server fails to install if boot is not on sda1

[Bartosz Baranowski]

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 a charm.
What I found odd about his is fact that installer, seems to see partitions cloned after restart, while parted does not( txt and img in ;single_drive_encr_lvm;). I'm fairly sure other iterations did produce similar duplication, but I just brushed it off as trash after last install - my bad?

Crash logs, with semi-descriptive dirs attached.

** Attachment added: "1929213.tar.gz"
   https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+attachment/5499657/+files/1929213.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1929213

Title:
  Ubuntu server fails to install if boot is not on sda1

Status in subiquity package in Ubuntu:
  New

Bug description:
  I've already sent crash report from installer, but since I'm not quite
  sure how it's handled, might as well follow up with this.

  I've been tinkering with ubuntu server and some old HW. Long story short, since I'm not used to CLI/text like install and missed that installer reverse order of HDDs I ended up with disk setup where /boot, /boot/efi along with LVM handling root were on /sdb
  To be precise:
  sdb:
  /boot
  /boot/efi
  /lvm/root

  sda:
  /lvm/root

  This failed at some point with message refering boot/grub could not be
  found on /dev/sda1:

  "could not get path to dev from kname sda1"

  If I set up everything on sda it works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+subscriptions