![gparted create boot partition gparted create boot partition](https://howtoubuntu.org/assets/images/how-to-resize-partitions-with-the-ubuntu-or-gparted-live-cd/Screenshot-from-2012-06-04-195206.png)
#Gparted create boot partition install
The bug is if I install any Linux distribution UEFI it will boot fine unless I switch cables to another SSD, If I try to boot the MB will not even recognize the drive is present. There are no more bios updates available from Asus. It has a UEFI issue or bug in the firmware that I discovered when switching to Linux Distros 2 years ago as Win7 went EOL. One with Debian Buster, a couple of Manjaro’s, Linux Mint, Ubuntu 20.04 and Kubuntu 20.10. I’ve got two computers and three monitors. It just seems odd that calamares would behave in this manner. The root partition overwrote the btrfs with ext4 as I expected.įrom an operational standpoint it doesn’t seem to matter, the system boots just fine legacy and with a GPT disk.
![gparted create boot partition gparted create boot partition](https://i.stack.imgur.com/TfPYs.png)
It just left whatever was there previously. So it appeared that selecting unformatted is kind of a passive not active selection. When I booted for the first time and took a look, that partition was btrfs. That time the bios-grub partition was set up the same.
![gparted create boot partition gparted create boot partition](https://i.ytimg.com/vi/Lk6mvVU7GOU/mqdefault.jpg)
I had some issues with it not related to this post and decided to check out how Manjaro handles the GPT and legacy boot. It partitioned the disk MBR and formatted it btrfs. Previously on this same disk I was testing Garuda KDE. As I mentioned Ubuntu leaves it unformatted as intended. It’s quite clear about the bios-grub partition being unformatted. My question is about the prompt in calamares. I understand why the bios-grub partition is needed for GPT partitioning.