[Bug 2137004] Re: Not possible install Ubuntu Server on prepared ssd with /boot , / and /home , requires a total wipe

Alecz20 2137004 at bugs.launchpad.net
Mon Dec 29 22:45:10 UTC 2025


I am able to reproduce this issue. I have a single disk on which I am
struggling to install Ubuntu Mate 24.04.3 LTS

On the 1st attempt, I created 3 partitions:
* sda1 /boot/efi (automatically created when I chose the disk as bootloader location)
* sda2 / root for OS
* sda3 "leave unformatted"

The installation crashed with some weird error that I could not report
from the installer (nothing happens when trying to report)

When rebooting, there was no user, just the guest login, so I decided to
re-install.

On the second attempt, I was not allowed to reuse the two partitions
creating by the 1st attempt, I could not select them and continue, I had
to erase the disk and create a new partition table.

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

Title:
  Not possible install Ubuntu Server on prepared ssd with /boot , / and
  /home , requires a total wipe

Status in subiquity package in Ubuntu:
  Confirmed

Bug description:
  Hardware Asus Maximus IV Gene-Z, Z68-system , 1 *120 GB SSD connected , partioned for a new install it is prepared with 512 m boot , 
  30 GB  for /root and the rest for /home, 

  I got stuck on the partitions tool to boot, no matter how i did , Subiquity didnt take other argument than wipe the whole disk.
  A really unlogical and lack of information UI with Subiquity, using debian is like a river compared to this slow backwards stream.

  Detailed issues:

                The "Done" Button Deadlock: Even with /boot, /, and
  /home correctly assigned, the "Done" button remained greyed out.

                 Boot Device Selection: The installer demanded a "boot disk" selection, but the "Use as boot device" option was greyed out      
                 for  the SSD, despite it having a dedicated boot partition.

                 Forced Data Loss: There was no logical path to preserve the existing /home partition. The only way to activate the "Done"            
                 button was to select "Use entire disk," which is unacceptable when preserving user data.
                 
                 Lack of Guidance: The UI provided no information on why the configuration was considered invalid (e.g., missing flags or           
                 specific partition types like "BIOS Boot").
                  

  Conclusion:
              
  I had to abandon my manual setup and wipe the entire drive to proceed. This is a critical failure in a "user-friendly" installer.

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




More information about the foundations-bugs mailing list