In the partitioner, it thinks you need to install on RAID before there is a partition on the Array. When it does finished an installation, you can manually shrink that partition and add the bios_grub partition back in. And if you add it manually outside of it, it is back at square one. It automatically adds a 512MB ?boot/efi partition. You can say 5mb, unformatted, and unmounted. But most of it isn't that far from the norm.Īll it will let you add as the first partition on a new GPT disk on UEFI is the /boot/efi partition. I know I don't end up doing normal things for testing. I always figured if you went into advanced settings, with would be a custom install, you "should" be able to 'do things' without having to hack it and use work-arounds. Then later go back to move things to allow for a dual boot rescue scenario. To retest on the same disk, I had to delete all and start fresh. In the old, you could customize many settings. and when you try to go them, it will give you warnings that it is a "bad idea." (In those words exact words. There of those partitions were marked as RAID.Įven when doing something standard, options are greyed out. Besides not recognizing the partition flags, it will not recognize partition labels, filesystems (correctly), nor filesystem labels. The installer for "Something Else" really falls short in many ways. The 18.04 and 20.04 Desktop partitioner does. So even though it had been a dual-boot UEFI and BIOS bootable disk, that could be pulled out and put into anything, and all the partition flags where there, the new partitioner does not recognize them. LOLIf you delete them all, then it will let you select the disk to boot from it.
It will let you delete "All" the partitions, but is labeled in it's menu's as "Reformat", of the disk popup menu, then when selected, says it's going to delete all the partitions on the disk. If you try to delete any partitions the message is: "Cannot delete partition of local disk- Cannot delete a single partition of a disk that already has partitions." The option stays greyed out and you cannot go on from there.
#Without LVMEven first going into it, with nothing selected, it will not let you select any disk as the boot disk. Sda2 is EFI 500MB, fat32 (marked as ESF and Bootable) Sda1 is marked as bios_grub 5MB, unformatted
0 kommentar(er)
