ERROR: No free space in /boot/efi for new kernel

[non_space]

Indeed, for the most part I agree, on my TW system booted right now I have:

# df -h /boot/efi/
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  350M  8.7M  342M   3% /boot/efi

But on my Gaz15 running Pop/COSMIC I just checked it yesterday because of this thread; they put the kernels in that directory, or they did and I have the /boot/efi partitioin set to 512 MB and GParted shows 474.09 MB used!! The system had 4 kernels installed, I used Mainline to remove the three older kernels, which used to free up space . . . after doing that 474.09 MB remains as being used!!!???

[shundhammer]

I posted this here just a few days ago: 5.8 MiB total on the ESP (/boot/efi) with a single Tumbleweed installation with grub2-efi.

[karlmistelberger]

5700g:~ # find /boot/efi/
/boot/efi/
/boot/efi/EFI
/boot/efi/EFI/5700g
/boot/efi/EFI/5700g/grubx64.efi
5700g:~ # 

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” - Antoine de Saint Exupéry, Airman’s Odyssey

[moniaqua]

@LaQuirrELL

So, my boot/efi partition needs to be 2 - 4 GB.
Are there any other recommendations to improve the partitioning? The SSD is 232.28 GB with efi/boot, swap and root on it. The other SSD is split equally for home and other data storage.

As quite normal user, doing some office tasks, some music and some graphics right now, my partitioning layout looks like this:

userathost: path # lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 931.5G  0 disk 
├─nvme0n1p1 259:1    0  39.1G  0 part 
├─nvme0n1p2 259:2    0  39.1G  0 part 
├─nvme0n1p3 259:3    0     1K  0 part 
├─nvme0n1p5 259:4    0   9.8G  0 part 
├─nvme0n1p6 259:5    0  48.8G  0 part 
└─nvme0n1p7 259:6    0 794.8G  0 part /run/media/someuser/home
nvme1n1     259:7    0 476.9G  0 disk 
├─nvme1n1p1 259:8    0     1G  0 part /boot/efi
├─nvme1n1p2 259:9    0  58.6G  0 part /
├─nvme1n1p3 259:10   0  58.6G  0 part /var
└─nvme1n1p4 259:11   0 358.8G  0 part /home

The second home because I just got Tumbleweed when throwing out windows as I accessed that partition anyways only for updating windows any more. So I want to take the chance and re-organize my whole setup. Still meditating about how I will do it I am on ext4, worked fine for me the last decades.

@shundhammer

The problem is that the new default bootloader for new Tumbleweed / Slowroll installation is now grub-bls which wants to store all kernels and all initrds on the EFI System Partition (/boot/efi).

Gosh. Good that you mention this. I was just wondering why on earth my /boot/efi, that I already enlarged from one cylinder or so to 1G because I thought “Oh, make it bigger, so I can become fancy and put some nice graphics in there.” was so clogged now after the installation of Tumbleweed (I will keep on doing multiboots, but the other systems have the kernels not in /boot/efi).

@malcolmlewis

So I have a Tumbleweed setup using grub-bls dual booting with Windows 11, I just hit the BIOS boot key (F12) and select Windows Boot Manager if want to use, seems like grub-efi which still requires keyboard interaction?

The keyboard interaction I usually need on a multiboot with grub_efi is arrow down and enter. That’s all. Since I installed Tumbleweed yesterday I have to enter bios (hit the right key at the right time), take the mouse to get boot order right, hit Fxy to save and I think also an enter to finally get the right system running (ok, could wait some seconds, too). For me that’s a bit more complicated than just select the right item in a nice menu. I’ll straighten this up asap.

[malcolmlewis]

@moniaqua I use ext4 here on my primary desktop running Tumbleweed, but I have other disks for data and then just use softlinks as required to /data. Then /data is just rsynced over ssh to another system and disk for backup…

lsblk -f
 
NAME        FSTYPE          FSVER  LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda         isw_raid_member 1.1.00                                                              
├─md126     xfs                    DATA     004ea158-d650-479b-a985-54d658914683  157.7G    65% /data
└─md127                                                                                         
sdb         isw_raid_member 1.1.00                                                              
├─md126     xfs                    DATA     004ea158-d650-479b-a985-54d658914683  157.7G    65% /data
└─md127                                                                                         
sdc                                                                                             
└─sdc1      xfs                    BUILD    06b2cbce-999f-42f0-8e96-531640104eab   25.5G    77% /build
sr0                                                                                             
zram0       swap            1      zram0    1ad771cf-8aa3-4691-89c1-84146a019bb0                [SWAP]
nvme0n1                                                                                         
├─nvme0n1p1 vfat            FAT32  ESP      44D1-83D0                                 4G     0% /boot/efi
└─nvme0n1p2 ext4            1.0    TW111824 1ab675ed-aba2-4593-9ebc-1c893015b607  622.7G    28% /

[moniaqua]

@malcolmlewis

I use ext4 here on my primary desktop running Tumbleweed, but I have other disks for data and then just use softlinks as required to /data. Then /data is just rsynced over ssh to another system and disk for backup…

So you have a normal /home (in /) and symlink from there? Sounds quite reasonable to me, I had the idea to do something pretty equal. Thank you

[malcolmlewis]

@moniaqua yes, so directories are on /data and then just for example ln -s /data/Documents ~/Documents as part of my user setup script those are created as required.

Since I have multiple systems and setups as I make changes, these are documented in either a system or user setup bash script and enabled via options.

I really need to move to the Agama Installer and profiles…