🐛 [BUG] Installer won't create EFI partition, won't let me create it either, breaks system on empty hard disk

[ell1e]

Description

The installer has no guided partitioning option, which seems like a major flaw. Even worse, it seems like it neither will create an EFI partition if the user doesn't nor will it even warn about it, but apparently just silently fail to set up anything bootable. Even more worse, when I attempt to create an EFI partition myself, it seems to be impossible in the installer since I can't format it.

The result seems to be that with an empty hard disk to start with that is GPT rather than MBR, the result will always be that the installer produces some unbootable partitions that aren't really of any use without further modifications that the installer UI can't do.

Given the many bug reports regarding the installer, it seems like it's not just me. I apologize however if I did something obvious wrong.

Reproduction steps

1. Start the installer
2. Choose "Install BlissOS..."
3. On an empty disk, no partition will be present. Choose "Create partitions..."
4. You'll be dropped into cfdisk or cgdisk without zero guidance on what partitions BlissOS even expects. This seems like the first major flaw, it should ask whether to set up the default partitions instead.
5. In cfdisk or cgdisk you can create an EFI partition, but it won't have any filesystem inside and therefore be unusable. When you return later to the installer UI it seemingly won't let you do anything about it. This seems like the second major flaw.
6. If in cfdisk or cgdisk you just create a single Linux partition filling the entire hard disk, the install will happily resume but in case of a GPT disk, seemingly silently(!) fail to install grub in any bootable way. This seems like the third major flaw.
7. It's also not clear what setting up a "userdata" partition is as the second entry in the installer main menu, or whether this should be a separate second partition at all. I assume this is some Android-specific concept, but the Installer UI somehow just assumes I know what it should be. This should perhaps be revised as well.
8. When the installer later prompts to install grub, it doesn't say why I wouldn't want to install grub or what it'll do if I don't. I assume the reason to say 'no' here is for dualboot if grub is already present, but it could be misunderstood to mean that it'll use some other boot method if I say 'no' so the UI again could use some work here.

Screenshots

![DESCRIPTION](LINK.png)

Logs

No response

Category

Bootup

OS Version

15.x