Missing Kernel after Upgrade

Ask Fedora
, ,
1

I decided to take part in the KDE Plasma 6 Test days last week. I followed the directions as shown in the article. My Fedora 39 system was upgraded and everything was working fine. A few days later there was an upgrade, so I did it. That was when I realized, with some horror, that my system had been converted to Rawhide and updates were now coming from the Rawhide repository. Luckily, it was set to be branched on 13 February, so I thought it should be fine. But I noticed something curious…

None of the new fc40 kernels were getting installed.

rpm -q kernel-core
kernel-core-6.6.14-200.fc39.x86_64
kernel-core-6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64
kernel-core-6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64

dnf ran and everything appeared to be upgraded correctly, but the kernels were not there, yet my old fc39 kernels were being removed after each upgrade!

ls -al
total 188960
dr-xr-xr-x. 1 root root 630 Feb 11 10:21 .
dr-xr-xr-x. 1 root root 178 Feb 11 12:28 …
-rw-r–r–. 1 root root 266338 Jan 25 17:00 config-6.6.14-200.fc39.x86_64
drwx------. 7 root root 4096 Dec 31 1969 efi
drwx------. 1 root root 40 Feb 11 12:06 grub2
-rw-------. 1 root root 116527049 Sep 25 12:03 initramfs-0-rescue-7ff7800c3e854a338eaf8b0c72137151.img
-rw-------. 1 root root 38654894 Jan 28 14:33 initramfs-6.6.14-200.fc39.x86_64.img
drwxr-xr-x. 1 root root 14 Sep 25 12:03 loader
lrwxrwxrwx. 1 root root 46 Jan 28 14:33 symvers-6.6.14-200.fc39.x86_64.xz → /lib/modules/6.6.14-200.fc39.x86_64/symvers.xz
-rw-------. 1 root root 8786730 Jan 25 17:00 System.map-6.6.14-200.fc39.x86_64
-rwxr-xr-x. 1 root root 14537000 Sep 25 12:03 vmlinuz-0-rescue-7ff7800c3e854a338eaf8b0c72137151
-rwxr-xr-x. 1 root root 14678120 Jan 25 17:00 vmlinuz-6.6.14-200.fc39.x86_64
-rw-r–r–. 1 root root 161 Jan 25 17:00 .vmlinuz-6.6.14-200.fc39.x86_64.hmac

Where are the 2 new kernels that are shown to be installed? They are not in /boot and they do not show up on the grub boot menu at startup.

I just tried reinstalling kernel-core…fc40, but it still did not appear anywhere. I ran a search and it was not to be found. Then I noticed this message:

cp: error writing ‘/boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/initrd’: No space left on device
dracut: Creation of /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/initrd failed
/usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 1.
warning: %posttrans(kernel-core-6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64) scriptlet failed, exit status 1

Error in POSTTRANS scriptlet in rpm package kernel-core

Reinstalled:
kernel-core-6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64

But it didn’t get installed.

What is happening? Will my system automatically switch to the newly branched Fedora 40 repos on the 13th of February? Will the kernels then start appearing?

As a safeguard, I edited /etc/dnf/dnf.conf and set it to keep 6 kernels, just in case.

What do I do?

2

Probably not. Once it is branched then you will need to update to f40 instead of rawhide. At that point rawhide will become f41.

What is the space remaining on /boot? The command df -h should show the space used and remaining on each mounted file system.

When posting text copied from your screen please always use the preformatted text tags (the </> button on the toolbar) so what is displayed here remains formatted exactly as shown on your screen.

If there is no space remaining in /boot this will be totally ineffective. Nothing will be installed without adequate space. The space error must be addressed and resolved.

3

I’ve never known about the preformatted text tags. I will try them now. df -h shows:

Preformatted text/dev/nvme0n1p1 256M 256M 0 100% /boot/efiPreformatted text

I even moved the Microsoft directory off the partition, as I don’t have any Microsoft OS installed, and tried reinstalling kernel-core, but it gave me the same error.

Can you think of anything I can remove from the /boot/efi partition? I have never had this issue before and the Microsoft directory was in place and I had numerous kernels installed. Something must be there that is taking up more space than before. I did read recently, if I recall correctly, that kernels are now getting so large that it is no longer possible to install from a CD, so this might also be affecting the /boot/efi partition.

Idea how I can easily remedy this without reinstalling system? And, once I do reinstall, what is the recommended size for /boot/efi nowadays?

4

The preformatting use the back quote character. Not sure what you did.
To preformat a bunch of lines do this:

```
line 1
line 2
etc
```

You can use a single back quotes for inline quoting as I did here.

5

df -h should have shown something similar to this and it would appear as shown if you used the button </> as I indicated.
paste the text, highlight it with your mouse, click the button. – done. (hovering the mouse over that button gives its name (Preformatted Text).

$ df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/fedora_raptor-root  458G   36G  399G   9% /
devtmpfs                        4.0M     0  4.0M   0% /dev
tmpfs                            16G  4.0K   16G   1% /dev/shm
efivarfs                        128K   41K   83K  33% /sys/firmware/efi/efivars
tmpfs                           6.3G  1.8M  6.3G   1% /run
/dev/nvme0n1p2                  974M  298M  609M  33% /boot
tmpfs                            16G  7.4M   16G   1% /tmp
/dev/nvme0n1p1                  1.3G   18M  1.3G   2% /boot/efi
/dev/mapper/fedora_raid-home    6.0T  4.4T  1.4T  77% /home
tmpfs                           3.2G   96K  3.2G   1% /run/user/42
tmpfs                           3.2G   84K  3.2G   1% /run/user/1000

As I said, we need to really see the full detail and not just part of a single line.

1 Like
6 
df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p6   30G   17G   14G  57% /
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           7.7G     0  7.7G   0% /dev/shm
efivarfs        268K  253K   11K  96% /sys/firmware/efi/efivars
tmpfs           3.1G  2.4M  3.1G   1% /run
/dev/nvme0n1p8  300G   39G  260G  13% /home/peter/Storage
/dev/nvme0n1p5   30G   19G   12G  62% /old
/dev/nvme0n1p7  500G  287G  213G  58% /home/peter/Documents
/dev/nvme0n1p1  256M  256M     0 100% /boot/efi
tmpfs           7.7G  116K  7.7G   1% /tmp
tmpfs           1.6G  176K  1.6G   1% /run/user/1000
7

To clarify: Storage and Documents are my personal data on separate partitions, to safeguard from destruction when doing ‘clean’ system installations. As I do a clean install about every second release, I always have an earlier release as a backup and it is mounted at /old (just in case I forgot to transfer something or if an install fails and I need to boot into a good system).

8

Ok, thanks for the additional info.

The only partition that is showing an issue is /boot/efi so we need to find out what is using all the space there. I have several systems and none are using more than about 20M in /boot/efi/

Please post the output of sudo du -ha /boot/efi

As far as your Storage and Documents are concerned you could probably just as easily have a single partition mounted at /home and achieve the same thing (maybe even better for some users)
You are only using about 230G of 800G in those 2 partitions which could allow additional space for / and /boot/efi if they were combined.

You said you removed windows partitions so there may also be free space on the drive. Please post the output of sudo fdisk -l as well.

9 
sudo du -ha /boot/efi
4.0K    /boot/efi/EFI/fedora/grub.cfg
4.0K    /boot/efi/EFI/fedora/BOOTIA32.CSV
4.0K    /boot/efi/EFI/fedora/BOOTX64.CSV
2.9M    /boot/efi/EFI/fedora/gcdia32.efi
3.8M    /boot/efi/EFI/fedora/gcdx64.efi
2.9M    /boot/efi/EFI/fedora/grubia32.efi
3.8M    /boot/efi/EFI/fedora/grubx64.efi
664K    /boot/efi/EFI/fedora/mmia32.efi
840K    /boot/efi/EFI/fedora/mmx64.efi
928K    /boot/efi/EFI/fedora/shim.efi
728K    /boot/efi/EFI/fedora/shimia32.efi
928K    /boot/efi/EFI/fedora/shimx64.efi
18M     /boot/efi/EFI/fedora
728K    /boot/efi/EFI/Boot/BOOTIA32.EFI
72K     /boot/efi/EFI/Boot/fbia32.efi
92K     /boot/efi/EFI/Boot/fbx64.efi
928K    /boot/efi/EFI/Boot/bootx64.efi
1.8M    /boot/efi/EFI/Boot
8.0K    /boot/efi/EFI/OEM/Boot/boot.stl
2.0M    /boot/efi/EFI/OEM/Boot/bootmgfw.efi
2.0M    /boot/efi/EFI/OEM/Boot/bootmgr.efi
56K     /boot/efi/EFI/OEM/Boot/kdnet_uart16550.dll
84K     /boot/efi/EFI/OEM/Boot/kdstub.dll
68K     /boot/efi/EFI/OEM/Boot/kd_02_10df.dll
428K    /boot/efi/EFI/OEM/Boot/kd_02_10ec.dll
64K     /boot/efi/EFI/OEM/Boot/kd_02_1137.dll
268K    /boot/efi/EFI/OEM/Boot/kd_02_14e4.dll
84K     /boot/efi/EFI/OEM/Boot/kd_02_15b3.dll
80K     /boot/efi/EFI/OEM/Boot/kd_02_1969.dll
68K     /boot/efi/EFI/OEM/Boot/kd_02_19a2.dll
60K     /boot/efi/EFI/OEM/Boot/kd_02_1af4.dll
324K    /boot/efi/EFI/OEM/Boot/kd_02_8086.dll
56K     /boot/efi/EFI/OEM/Boot/kd_07_1415.dll
84K     /boot/efi/EFI/OEM/Boot/kd_0C_8086.dll
1.7M    /boot/efi/EFI/OEM/Boot/memtest.efi
12K     /boot/efi/EFI/OEM/Boot/winsipolicy.p7b
64K     /boot/efi/EFI/OEM/Boot/BOOTSTAT.DAT
32K     /boot/efi/EFI/OEM/Boot/BCD
32K     /boot/efi/EFI/OEM/Boot/BCD.LOG
0       /boot/efi/EFI/OEM/Boot/BCD.LOG1
0       /boot/efi/EFI/OEM/Boot/BCD.LOG2
80K     /boot/efi/EFI/OEM/Boot/bg-BG/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/bg-BG/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/bg-BG
12K     /boot/efi/EFI/OEM/Boot/CIPolicies/Active/{5DAC656C-21AD-4A02-AB49-649917162E70}.cip
28K     /boot/efi/EFI/OEM/Boot/CIPolicies/Active/{82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
12K     /boot/efi/EFI/OEM/Boot/CIPolicies/Active/{CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip
56K     /boot/efi/EFI/OEM/Boot/CIPolicies/Active
60K     /boot/efi/EFI/OEM/Boot/CIPolicies
80K     /boot/efi/EFI/OEM/Boot/cs-CZ/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/cs-CZ/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/cs-CZ/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/cs-CZ
80K     /boot/efi/EFI/OEM/Boot/da-DK/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/da-DK/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/da-DK/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/da-DK
84K     /boot/efi/EFI/OEM/Boot/de-DE/bootmgfw.efi.mui
84K     /boot/efi/EFI/OEM/Boot/de-DE/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/de-DE/memtest.efi.mui
220K    /boot/efi/EFI/OEM/Boot/de-DE
84K     /boot/efi/EFI/OEM/Boot/el-GR/bootmgfw.efi.mui
84K     /boot/efi/EFI/OEM/Boot/el-GR/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/el-GR/memtest.efi.mui
220K    /boot/efi/EFI/OEM/Boot/el-GR
76K     /boot/efi/EFI/OEM/Boot/en-GB/bootmgfw.efi.mui
76K     /boot/efi/EFI/OEM/Boot/en-GB/bootmgr.efi.mui
156K    /boot/efi/EFI/OEM/Boot/en-GB
76K     /boot/efi/EFI/OEM/Boot/en-US/bootmgfw.efi.mui
76K     /boot/efi/EFI/OEM/Boot/en-US/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/en-US/memtest.efi.mui
200K    /boot/efi/EFI/OEM/Boot/en-US
80K     /boot/efi/EFI/OEM/Boot/es-ES/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/es-ES/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/es-ES/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/es-ES
80K     /boot/efi/EFI/OEM/Boot/es-MX/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/es-MX/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/es-MX
80K     /boot/efi/EFI/OEM/Boot/et-EE/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/et-EE/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/et-EE
80K     /boot/efi/EFI/OEM/Boot/fi-FI/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/fi-FI/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/fi-FI/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/fi-FI
84K     /boot/efi/EFI/OEM/Boot/fr-CA/bootmgfw.efi.mui
84K     /boot/efi/EFI/OEM/Boot/fr-CA/bootmgr.efi.mui
172K    /boot/efi/EFI/OEM/Boot/fr-CA
84K     /boot/efi/EFI/OEM/Boot/fr-FR/bootmgfw.efi.mui
84K     /boot/efi/EFI/OEM/Boot/fr-FR/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/fr-FR/memtest.efi.mui
220K    /boot/efi/EFI/OEM/Boot/fr-FR
80K     /boot/efi/EFI/OEM/Boot/hr-HR/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/hr-HR/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/hr-HR
84K     /boot/efi/EFI/OEM/Boot/hu-HU/bootmgfw.efi.mui
84K     /boot/efi/EFI/OEM/Boot/hu-HU/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/hu-HU/memtest.efi.mui
220K    /boot/efi/EFI/OEM/Boot/hu-HU
80K     /boot/efi/EFI/OEM/Boot/it-IT/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/it-IT/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/it-IT/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/it-IT
68K     /boot/efi/EFI/OEM/Boot/ja-JP/bootmgfw.efi.mui
68K     /boot/efi/EFI/OEM/Boot/ja-JP/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/ja-JP/memtest.efi.mui
184K    /boot/efi/EFI/OEM/Boot/ja-JP
68K     /boot/efi/EFI/OEM/Boot/ko-KR/bootmgfw.efi.mui
68K     /boot/efi/EFI/OEM/Boot/ko-KR/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/ko-KR/memtest.efi.mui
184K    /boot/efi/EFI/OEM/Boot/ko-KR
80K     /boot/efi/EFI/OEM/Boot/lt-LT/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/lt-LT/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/lt-LT
80K     /boot/efi/EFI/OEM/Boot/lv-LV/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/lv-LV/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/lv-LV
80K     /boot/efi/EFI/OEM/Boot/nb-NO/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/nb-NO/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/nb-NO/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/nb-NO
80K     /boot/efi/EFI/OEM/Boot/nl-NL/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/nl-NL/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/nl-NL/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/nl-NL
80K     /boot/efi/EFI/OEM/Boot/pl-PL/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/pl-PL/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/pl-PL/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/pl-PL
80K     /boot/efi/EFI/OEM/Boot/pt-BR/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/pt-BR/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/pt-BR/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/pt-BR
80K     /boot/efi/EFI/OEM/Boot/pt-PT/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/pt-PT/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/pt-PT/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/pt-PT
56K     /boot/efi/EFI/OEM/Boot/qps-ploc/memtest.efi.mui
60K     /boot/efi/EFI/OEM/Boot/qps-ploc
80K     /boot/efi/EFI/OEM/Boot/ro-RO/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/ro-RO/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/ro-RO
80K     /boot/efi/EFI/OEM/Boot/ru-RU/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/ru-RU/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/ru-RU/memtest.efi.mui
208K    /boot/efi/EFI/OEM/Boot/ru-RU
80K     /boot/efi/EFI/OEM/Boot/sk-SK/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/sk-SK/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/sk-SK
80K     /boot/efi/EFI/OEM/Boot/sl-SI/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/sl-SI/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/sl-SI
80K     /boot/efi/EFI/OEM/Boot/sr-Latn-RS/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/sr-Latn-RS/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/sr-Latn-RS
80K     /boot/efi/EFI/OEM/Boot/sv-SE/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/sv-SE/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/sv-SE/memtest.efi.mui
208K    /boot/efi/EFI/OEM/Boot/sv-SE
80K     /boot/efi/EFI/OEM/Boot/tr-TR/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/tr-TR/bootmgr.efi.mui
48K     /boot/efi/EFI/OEM/Boot/tr-TR/memtest.efi.mui
212K    /boot/efi/EFI/OEM/Boot/tr-TR
80K     /boot/efi/EFI/OEM/Boot/uk-UA/bootmgfw.efi.mui
80K     /boot/efi/EFI/OEM/Boot/uk-UA/bootmgr.efi.mui
164K    /boot/efi/EFI/OEM/Boot/uk-UA
64K     /boot/efi/EFI/OEM/Boot/zh-CN/bootmgfw.efi.mui
64K     /boot/efi/EFI/OEM/Boot/zh-CN/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/zh-CN/memtest.efi.mui
176K    /boot/efi/EFI/OEM/Boot/zh-CN
64K     /boot/efi/EFI/OEM/Boot/zh-TW/bootmgfw.efi.mui
64K     /boot/efi/EFI/OEM/Boot/zh-TW/bootmgr.efi.mui
44K     /boot/efi/EFI/OEM/Boot/zh-TW/memtest.efi.mui
176K    /boot/efi/EFI/OEM/Boot/zh-TW
3.6M    /boot/efi/EFI/OEM/Boot/Fonts/chs_boot.ttf
3.7M    /boot/efi/EFI/OEM/Boot/Fonts/cht_boot.ttf
1.9M    /boot/efi/EFI/OEM/Boot/Fonts/jpn_boot.ttf
2.3M    /boot/efi/EFI/OEM/Boot/Fonts/kor_boot.ttf
192K    /boot/efi/EFI/OEM/Boot/Fonts/malgunn_boot.ttf
192K    /boot/efi/EFI/OEM/Boot/Fonts/malgun_boot.ttf
160K    /boot/efi/EFI/OEM/Boot/Fonts/meiryon_boot.ttf
164K    /boot/efi/EFI/OEM/Boot/Fonts/meiryo_boot.ttf
180K    /boot/efi/EFI/OEM/Boot/Fonts/msjhn_boot.ttf
180K    /boot/efi/EFI/OEM/Boot/Fonts/msjh_boot.ttf
172K    /boot/efi/EFI/OEM/Boot/Fonts/msyhn_boot.ttf
172K    /boot/efi/EFI/OEM/Boot/Fonts/msyh_boot.ttf
44K     /boot/efi/EFI/OEM/Boot/Fonts/segmono_boot.ttf
100K    /boot/efi/EFI/OEM/Boot/Fonts/segoen_slboot.ttf
100K    /boot/efi/EFI/OEM/Boot/Fonts/segoe_slboot.ttf
48K     /boot/efi/EFI/OEM/Boot/Fonts/wgl4_boot.ttf
14M     /boot/efi/EFI/OEM/Boot/Fonts
172K    /boot/efi/EFI/OEM/Boot/Resources/bootres.dll
16K     /boot/efi/EFI/OEM/Boot/Resources/en-US/bootres.dll.mui
20K     /boot/efi/EFI/OEM/Boot/Resources/en-US
16K     /boot/efi/EFI/OEM/Boot/Resources/fr-FR/bootres.dll.mui
20K     /boot/efi/EFI/OEM/Boot/Resources/fr-FR
216K    /boot/efi/EFI/OEM/Boot/Resources
28M     /boot/efi/EFI/OEM/Boot
20K     /boot/efi/EFI/OEM/Recovery/BCD
32K     /boot/efi/EFI/OEM/Recovery/BCD.LOG
0       /boot/efi/EFI/OEM/Recovery/BCD.LOG1
0       /boot/efi/EFI/OEM/Recovery/BCD.LOG2
56K     /boot/efi/EFI/OEM/Recovery
28M     /boot/efi/EFI/OEM
47M     /boot/efi/EFI
4.0K    /boot/efi/System Volume Information/LightningSand.CFD
8.0K    /boot/efi/System Volume Information
4.0K    /boot/efi/System/Library/CoreServices/SystemVersion.plist
8.0K    /boot/efi/System/Library/CoreServices
12K     /boot/efi/System/Library
16K     /boot/efi/System
4.0K    /boot/efi/loader/entries/7ff7800c3e854a338eaf8b0c72137151-0-rescue.conf
8.0K    /boot/efi/loader/entries
4.0K    /boot/efi/loader/entries.srel
16K     /boot/efi/loader
4.0K    /boot/efi/mach_kernel
41M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64/initrd
2.3M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64/linux
43M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64
15M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/linux
153M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/initrd
168M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue
210M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151
256M    /boot/efi

sudo fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: WDC PC SN530 SDBPNPZ-1T00-1114          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A23A84A7-FA99-4E0F-8739-5DB03544D951

Device              Start        End    Sectors  Size Type
/dev/nvme0n1p1       2048     534527     532480  260M EFI System
/dev/nvme0n1p2     534528     567295      32768   16M Microsoft reserved
/dev/nvme0n1p3     567296   34121727   33554432   16G Linux swap
/dev/nvme0n1p4 1998311424 2000408575    2097152    1G Windows recovery environment
/dev/nvme0n1p5   34121728   97036287   62914560   30G Linux filesystem
/dev/nvme0n1p6   97036288  159950847   62914560   30G Linux filesystem
/dev/nvme0n1p7  159950848 1208526847 1048576000  500G Linux filesystem
/dev/nvme0n1p8 1208526848 1837672447  629145600  300G Linux filesystem
/dev/nvme0n1p9 1837672448 1998311423  160638976 76.6G Microsoft basic data

Partition table entries are not in disk order.


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
11

Anyway, I have been tinkering. It was risky, as I haven’t the slightest clue about this, but I decided to take the /boot/efi/EFI/OEM directory and move it to my Storage partition, just in case it is required. That freed up 10% of space on /boot/efi.

Next, I reinstalled kernel-core yet again. This time it did install (there was no error about insufficient space or anything else), but I don’t have a clue where it went. I see that now only 5% space remains. That seems a lot for a kernel that didn’t even go into /boot/efi at all, since it ends up in /boot (on my system, /boot/efi is a separate partition, if you recall).

Here are the renewed outputs of the 2 commands you asked for, given the changes just made:

du -ha /boot/efi
4.0K    /boot/efi/EFI/fedora/grub.cfg
4.0K    /boot/efi/EFI/fedora/BOOTIA32.CSV
4.0K    /boot/efi/EFI/fedora/BOOTX64.CSV
2.9M    /boot/efi/EFI/fedora/gcdia32.efi
3.8M    /boot/efi/EFI/fedora/gcdx64.efi
2.9M    /boot/efi/EFI/fedora/grubia32.efi
3.8M    /boot/efi/EFI/fedora/grubx64.efi
664K    /boot/efi/EFI/fedora/mmia32.efi
840K    /boot/efi/EFI/fedora/mmx64.efi
928K    /boot/efi/EFI/fedora/shim.efi
728K    /boot/efi/EFI/fedora/shimia32.efi
928K    /boot/efi/EFI/fedora/shimx64.efi
18M     /boot/efi/EFI/fedora
728K    /boot/efi/EFI/Boot/BOOTIA32.EFI
72K     /boot/efi/EFI/Boot/fbia32.efi
92K     /boot/efi/EFI/Boot/fbx64.efi
928K    /boot/efi/EFI/Boot/bootx64.efi
1.8M    /boot/efi/EFI/Boot
20M     /boot/efi/EFI
4.0K    /boot/efi/System Volume Information/LightningSand.CFD
8.0K    /boot/efi/System Volume Information
4.0K    /boot/efi/System/Library/CoreServices/SystemVersion.plist
8.0K    /boot/efi/System/Library/CoreServices
12K     /boot/efi/System/Library
16K     /boot/efi/System
4.0K    /boot/efi/loader/entries/7ff7800c3e854a338eaf8b0c72137151-0-rescue.conf
4.0K    /boot/efi/loader/entries/7ff7800c3e854a338eaf8b0c72137151-6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64.conf
12K     /boot/efi/loader/entries
4.0K    /boot/efi/loader/entries.srel
20K     /boot/efi/loader
4.0K    /boot/efi/mach_kernel
41M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64/initrd
15M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64/linux
55M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/6.8.0-0.rc3.20240209git1f719a2f3fa6.31.fc40.x86_64
15M     /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/linux
153M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue/initrd
168M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151/0-rescue
222M    /boot/efi/7ff7800c3e854a338eaf8b0c72137151
241M    /boot/efi

fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: WDC PC SN530 SDBPNPZ-1T00-1114          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A23A84A7-FA99-4E0F-8739-5DB03544D951

Device              Start        End    Sectors  Size Type
/dev/nvme0n1p1       2048     534527     532480  260M EFI System
/dev/nvme0n1p2     534528     567295      32768   16M Microsoft reserved
/dev/nvme0n1p3     567296   34121727   33554432   16G Linux swap
/dev/nvme0n1p4 1998311424 2000408575    2097152    1G Windows recovery environment
/dev/nvme0n1p5   34121728   97036287   62914560   30G Linux filesystem
/dev/nvme0n1p6   97036288  159950847   62914560   30G Linux filesystem
/dev/nvme0n1p7  159950848 1208526847 1048576000  500G Linux filesystem
/dev/nvme0n1p8 1208526848 1837672447  629145600  300G Linux filesystem
/dev/nvme0n1p9 1837672448 1998311423  160638976 76.6G Microsoft basic data

Partition table entries are not in disk order.


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
12

Sorry about being so slow to respond.

It wold appear that the directory you moved can be deleted. Its content showed that it was a left-over from windows. The directory /boot/efi/System Volume Informationalso seems to be a leftover from windows and could be removed.

There are also 3 partitions that are left from windows.
nvme0n1p2, p4, and p9 are all windows remenants and could be removed.

Since you are using fedora the swap partition nvme0n1p3 is probably not needed. If you want to keep it it could be recreated at the very end of that device, using part of the space where p4 & 9 are currently located. Fedora uses zram for virtual swap instead of a physical swap space by default.

Once p2 & p3 are removed then p1 could be expanded to provide more room for /boot/efi.

It seems that you may be using sdboot, (or attempted to use sdboot) which explains why the kernel image files are now located under /boot/efi/loader and /boot/efi directly.

Is it actually using sdboot? If so then running uname -a should show one of the fc40 kernels booted.

Just as additional info, Fedora has for the last couple of releases by default created an efi partition of ~600M during installation in preparation for switching from grub to sdboot.

I think that if you are actually using sdboot then it becomes imperative that you enlarge the /boot/efi (nvme0n1p1) partition to at least 600M to allow space for all the files that were previously in /boot to now be placed into /boot/efi. You already have at least 2 kernels there.

If you did not intend to run sdboot, or if it is only partially switched over, then reversing the steps done and switching back to grub is still possible.

For managing disk partitions I think gparted will become your friend. The disks tool is not quite as user friendly.

13

I probably could remove the windows partitions, as I have no intention of installing the OS (I only kept the partitions with info intact, due to potential warranty issues), but nvme0n1p2 is the /boot/efi FAT-formatted partition that is required. Has this changed? Is /boot/efi no longer FAT?

Yes, I was keeping the swap partition just in case I should use suspend-to-disk. It doesn’t cost me any space worth mentioning.

If I am using sdboot, I am unaware of it. I have never heard of it. Perhaps it is something rawhide uses.

uname -r
6.6.14-200.fc39.x86_64

If Fedora is switching to sdboot, then I want my system to make the switch. Will this occur automatically, or do I have to take some steps, and if so, what do I need to do? I do not want to have outdated procedures on my computer.

I am quite adept at partitioning. I had hoped not to do a clean install until Fedora 41 in the fall, so that I don’t have to do any fiddling in good weather or even now, as I have put so much time into this unwitting upgrade to Rawhide. If at all possible, I would like to transition my perfectly running system from Fedora Rawhide to Fedora 40 on Tuesday, when branching is scheduled to occur.

I was not using sdboot, but perhaps Rawhide is. How would I know? And if those kernels are already installed, why don’t they show up in the grub menu at boot? There is no way for me to select them.

I just read some documentation that mentions sdubby. I know the upgrade to Rawhide replaced grubby with sdubby.

14

No, p2 is microsoft reserved. p1 is the efi partition.

It uses little space but prevents enlarging p1 beyond the 16M available by removing p2.
If you wish to keep a swap partition that is fine but you cannot enlarge p1 adequately until p3 has been removed and your swap space relocated.

If you look at the start & end sectors of each partition you can see that the order is
p1 - p2 - p3 - p5 -p6 - p7 - p8 - p9 - p4.

p2, p9 & p4 are all microsoft partitions. p3 prevents enlarging p1 beyond the space currently occupied by p2.
p9 & p4 could be removed. A new swap partition created there for suspend to disk, then p2 & p3 removed to allow proper expansion of p1.

That is simple and easy to do should you decide to follow that path.

1 Like
16

From the first post it seems there is a directory named /boot/efi/7ff7800c3e854a338eaf8b0c72137151.
It is a known problem that when this directory exist, the boot configuration is written into the /boot/efi instead of /boot. That directory needs to be removed and the kernel-core needs to be re-installed.

/boot/efi/7ff7800c3e854a338eaf8b0c72137151 is for systemd-boot if someone want to use that instead of grub2.

17

I have the impression that system-boot is the way Fedora is heading. Apparently, my system is already partially converted and I think it is best that I follow along.

18

Yes, resistance is yielding. I see where you are heading. I have deleted the 3 Microsoft partitions, grown /boot/efi to 600MiB and created a swap partition of 16GiB at the end. I have some free space after /boot/efi and before swap that I can deal with when I do a clean installation, either when Fedora 40 or 41 are released. In the meantime, I now have partitons set up as you indicate.

The problem now remaining is: how do I get my boot menu to show the new sdubby menu instead of the old grubby one?

19

Then you have to disable secure boot, unless you want to do some dirty tricks. It is still unclear how secure boot is supposed to be handled with systemd-boot.

20

Thanks for the heads-up. I want to do things correctly: no “dirty tricks”. Do you know how to do it? Are there instructions available?

21

I’m curious to know which instructions you followed.

22

If you intend to continue the switch to sdboot then the instructions are somewhat unclear to me but can be found at https://kowalski7cc.xyz/blog/systemd-boot-fedora-32/ and have been updated for F39. Note that for the present, as indicated by Villy, secure boot must be disabled.

If instead you wish to revert back to grub boot then remove the directory as indicated by Villy and reinstall kernel-core