Hi,
l did a fresh Tumbleweed 20260510 install last night, with guided partitioning given free reign on the whole disk. It suggested a 1GiB EFI partition, but at the end of the install process the boot-loader failed to install with an error of not enough disk space, then the machine booted to a borked state.
No biggie, I just went though the loop again, and dropped to expert partitioning giving EFI 4GiB this time and everything worked fine – just flagging as it might not be a good first impression for some users, or may even be too high a barrier to entry for some, so perhaps the defaults could be re-visited.
I’m not sure if driver sizing impacts whats written to EFI, but this was on a Beelink S12 Mini, with Non OSS repos enabled during the install flow.
@jedimasterjonny Hi and welcome to the Forum 
I suspect you were using YaST, the newer Agama installer accepts, actually defaults to 1GB for /boot/efi if just a single boot setup should be fine, but my manual setup is always 4GB…
Thank-you! 
Yeah - that was the problem, it defaulted to 1GiB, which wasn’t big enough for a standard Tumbleweed install.
Essentially I just clicked through, accepted the defaults, allowed it to take the whole disk, and the installer errored with out of space installing the bootloader. This left the machine unbootable.
I’m Linux veteran, but new to SUSE, so was surprised the default install path led to a bad outcome, and wonder if the default 1 GiB in the installer should be raised?
So just upon fresh install, you already have more than 1Gb of data on your ESP?
I find this puzzling. On my Tumbleweed install, the ESP is 512Mb (for historical reasons) and still works, even though it gets tight during system updates… And this is with snapper snapshots and 2/3 kernel versions present at a given time…
@jedimasterjonny It has been for me… Is this a multiboot setup? Also I’m only using ext4 (Hyprland), so no snapshots…
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 6767-0208 966.8M 5% /boot/efi
└─nvme0n1p2 ext4 1.0 964c5751-aca1-42e5-a10f-9ff5ee925b25 100.9G 8% /
Hello,
very surprised with theses sizes. On Leap, ext4 so no snapshots, my /boot/efi partitions are close to 20Mo and that’s yet not full.
Why Tumbleweed needs so much space ?
Tumbleweed now uses systemd-boot by default, so kernel and initrd are stored on the ESP; that typically makes some 40-50 MB for each kernel installed and more for kept snapshots.
1 Like
PEBCAK 
I played the issue back in my head to give you all more details, and realised as I did it booted to a (borked) Windows boot-loader, which obviously meant it hadn’t formatted the ESP, and systemd-boot had to tried to co-exist with what was already there.
It’s frustrating, this was the first boot of a freshly unboxed NUC… why can’t they just leave the drive empty? 
I thought I gave the guided partitioner instruction to delete the partition, but clearly not 
Thanks for all piling in to help so quickly!
Ah, that makes sense. Thanks for reply!