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

[fernanAguero]

Moreover, if I go to a shell and format the disks, when I go back to the
installer, and hit "Reset" the system recognizes the changes, and shows
the disks as "already formatted as ext4", with "partition 1 existing",
"not mounted", and with a message saying:

"To continue you need to: Mount a filesystem at /
Select a boot disk"

But there is now way to mount at / (option greyed out).

I've been able to work around this by selecting Mount -> Other and
ignoring the warning about this being dangerous. Both mounting at / and
/var/lib produced these warnings. Mounting at /srv did not.


** Attachment added: "screenshots of installer"
   https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1969822/+attachment/5582185/+files/MergedPDF%2C2.pdf

-- 
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