[Bug 1969822] Re: failed storage configuration at install of ubuntu-22.04-server

[Dan Bungert]

Thanks for the report.

> However there is nothing I can do to select one! (the option to "Use
As Boot Device" is greyed out).

Up through that part sounds correct - there needs to be a little space
to setup for a boot disk and there isn't, so you made the right choice
to go backwards a bit and format the disks.

Would you attach the contents of the /var/log/installer directory?
If you're concerned about sharing information, the files I'm most interested in are /var/log/installer/subiquity-server-debug.log and /var/log/installer/block/probe-data.json.

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

Title:
  failed storage configuration at install of ubuntu-22.04-server

Status in subiquity:
  New
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  when booting a new VM using the ubuntu-22.04-live-server-amd64.iso
  file (VMWare), and following the installer options, I went for a
  "Custom storage layout", because I had 3 disks and wanted to use disk1
  (/dev/sda) as main disk (mounted in /), disk2 (/dev/sdb) mounted under
  /var/lib, and disk3 (/dev/sdc) mounted under /srv.

  After formatting all devices and specifying mount points, the system
  does not allow me to move on, saying "To continue you need to: Select
  a boot disk

  However there is nothing I can do to select one! (the option to "Use
  As Boot Device" is greyed out).

  If I start again fresh and choose the first disk (/dev/sda) and
  instead of "Format" I go for "Use As Boot Device", the system (again)
  does not allow me to move on, saying "To continue you need to: Mount a
  filesystem at /" (now the option "Stop Using As Boot Device" is greyed
  out).

  Hence, in summary, this is very confusing. It is not clear what the
  installer expects (e.g. how to do things right), and there are no
  hints provided.

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