[Bug 1982516] Re: Ubuntu 22.04 installer doesn't work if more than 1 EFI partition present

Chris Guiver 1982516 at bugs.launchpad.net
Fri Jul 22 02:37:03 UTC 2022


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 1982516

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

(this should be done on the same session after the problem occurred;
allow details of the system to be gained; without this detail, it may
take longer (needing someone else to re-create it) before the issue can
be recognized)

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

Title:
  Ubuntu 22.04 installer doesn't work if more than 1 EFI partition
  present

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I actually had a very interesting evening installing ubuntu 22.04.

  For reasons (VM that used LVM as a raw disk) I had 2 EFI partitions on
  my machine - one in LVM, another on disk.

  While Ubuntu managed to identify that I actually want to install
  bootloader on disk, it still tried to mount second EFI partition (even
  though in advanced mode of an installer I explicitly said not to used
  it) and then failed.

  If installation fails, it suggested that I can "go back" or
  "continue".

  If I click continue - it hangs on "Removing conflicting operating
  system files" or something like that.

  If I click "Go back" - it hangs on a Ad screen about 1/2 of the time
  (no ongoing operations, but it doesn't actually send me back). For the
  second half of the time - it goes back, but installer hangs on
  partitioning (doesn't allow to scroll and stops reacting on any button
  presses).

  The only solution for the problem was to temporary change partition
  type to be something else.

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




More information about the foundations-bugs mailing list