/boot/efi contains guid directory of 186M, what is normal?

Ask Fedora
1

My system has a directory /boot/efi/549a50985da741b4aad4b85dce99a8fc/ that contains 148M of data. I get warnings that /boot/efi is low on space.

# df /boot/efi
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/sda1         204580 196296      8284  96% /boot/efi

Why is there a /boot/efi/549a50985da741b4aad4b85dce99a8fc directory? In the grub version 2.06 boot menu, I see an entry: fedora 0-rescue-549a50985da741b4aad4b85dce99a8fc 30.

Inside the /boot/efi/549a50985da741b4aad4b85dce99a8fc directory are these files:

# find 549a50985da741b4aad4b85dce99a8fc
549a50985da741b4aad4b85dce99a8fc
549a50985da741b4aad4b85dce99a8fc/4.11.8-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.11.9-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.11.10-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.11.11-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.12.5-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.12.8-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.12.9-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.12.11-300.fc26.x86_64
549a50985da741b4aad4b85dce99a8fc/4.15.17-300.fc27.x86_64
549a50985da741b4aad4b85dce99a8fc/4.16.3-200.fc27.x86_64
549a50985da741b4aad4b85dce99a8fc/4.16.5-200.fc27.x86_64
549a50985da741b4aad4b85dce99a8fc/5.17.8-300.fc36.x86_64
549a50985da741b4aad4b85dce99a8fc/5.17.8-300.fc36.x86_64/initrd
549a50985da741b4aad4b85dce99a8fc/5.17.8-300.fc36.x86_64/linux
549a50985da741b4aad4b85dce99a8fc/0-rescue
549a50985da741b4aad4b85dce99a8fc/0-rescue/linux
549a50985da741b4aad4b85dce99a8fc/0-rescue/initrd
549a50985da741b4aad4b85dce99a8fc/5.17.6-300.fc36.x86_64
549a50985da741b4aad4b85dce99a8fc/5.17.6-300.fc36.x86_64/linux

Why are there all the very old kernels referenced?
The most space of /boot/efi is used in /boot/efi/549a50985da741b4aad4b85dce99a8fc/0-rescue/

# du -sh /boot/efi/549a50985da741b4aad4b85dce99a8fc/0-rescue/
116M	/boot/efi/549a50985da741b4aad4b85dce99a8fc/0-rescue/

What is the purpose of this /boot/efi/549a50985da741b4aad4b85dce99a8fc/0-rescue/ directory? Should it be there?

2

Yes and no. Either you use grub having software and kernels in /boot, and the UEFI software under /boot/efi , or you use systemd-boot as bootmanager having kernels and ramdisks below /boot/efi or /efi identified by the machine-id, the long uuid. During upgrades upto F36, sometimes the installation gets messed up. You have the choice to stay at grub, delete the uuid folder, and reinstall kernel, or switch to systemd-boot with bootctl and kernel reinstall… If you use grub and /boot is populated correctly, you can safely delete this uuid folder.

1 Like
3

It’s a bug,
https://bugzilla.redhat.com/show_bug.cgi?id=2071034

This comment has the workaround.

3 Likes
4

Duplicate of/reference: https://discussion.fedoraproject.org/t/f36-kernel-wont-install-due-to-running-out-of-space-in-boot-efi/73070

3 Likes