Hi;
First time Bazzite attempter here. I’ve created a ≈500gb partition as the attached screenshot. But when I reboot into the live installer, I get as far choosing language and keyboard, date and time, and then to the installation method screen…
I click “change destination”, select the NVME witb Windows on, choose “share disk with other operating systems” (leaving reclaim space and encrypt data off) and on the following screen I get:
“Warning: your /boot/efi partition is less than 500MiB which is lower than recommended for a normal Bazzite install. Click Next again to proceed despite this warning”.
So I’m guessing it’s trying to install into the 500Mb Recovery Partition instead of the 500gb empty parition. How do I get it to choose the right one?
Thanks for any (noob-friendly) guidance!
boot/efi partition is where boot info/startup logic goes, but windows makes a very small partition (only 100mb) on setup, so between windows and bazzite data, there is not enough space.
It will install the system in the 500gb partition, but will not boot without the proper data in the boot/efi partition. The installer is warning you of this situation, and the install will probably “work” but most likely be unbootable, or if it does work, cause problems later during bazzite updates.
There are partition management programs that can boot into a temporary environment and move/resize existing partitions so you can grow the existing EFI partition, but there is no tool built into windows for such a maneuver.
Thank you. Can I increase the size of the partition using the Live ISO somehow? Or do I need to do that in Windows?
No the boot partition is too small (Linux will install it’s boot program there) I had a 1GB boot partition that Mint kept filling up with various kernels and have to go through and delete the old ones, lesson learned I’m going 2GB for the boot partition next time
I’m not sure what will happen if you don’t install on the boot partition?
Doesn’t apt autoremove clear out old kernels and free up space on Debian based distros?
Ah… no is it the FIRST partition that’s the issue?



