Cannot boot after upgrading to kernel-6.17.12-300.fc43.x86_64

Hello,

After upgrading from kernel-6.17.11-300.fc43.x86_64 to kernel-6.17.12-300.fc43.x86_64, I’m unable to boot on the new kernel (the old one still works). I get the following error:
VFS: Unable to mount root fs on unknown-block(0,0)
I tried reinstalling the kernel and running
sudo /usr/bin/dracut --kver=6.17.12-300.fc43.x86_64 --force -v
But no luck. I’m using akmod-nvidia-580.119.02-1.fc43.x86_64 and Secure Boot is enabled with signed EFI, but not sure if this could be related (in particular when booting on the previous kernel still works).
Am I the only one having this issue with the latest kernel?

Thanks!

Try rebuilding the nvidia driver. I assume you have an nvidia gpu since you added the tag for nvidia. sudo akmods --rebuild --force

I don’t think the driver has anything to do with the inability to boot with that error, but it might help.

I already did that.

Did you check that the initramfs exists and the boot partition is not full?

Hi @gnwiii ,
The initramfs exists, I checked after the kernel installation and after running dracut. The /boot partition is not full.

Try https://kmadac.github.io/posts/Troubleshooting-initramfs.

@gnwiii the issue is related to the latest version of the kernel, I didn’t have any issue with previous kernel updates.

I recently did this update and it significantly worsened the performance of my video card.
GTX 1070ti

I’m using the same kernel, and everything is normal here, but after the kernel update, did you wait 5 minutes before rebooting?

Why should I wait 5 minutes when the update command returned to prompt?

Okay thanks for the tip but I don’t think it’s related as I have an error linked to a mountpoint.

This user had an issue where the GRUB parameters for 6.17.12 omitted the root.

In their case they fixed it with sudo grub2-mkconfig -o /boot/grub2/grub.cfg.

2 Likes

Because the kernel update completes.
After the kernel update completes the driver build starts so one must wait for that to complete before rebooting so the new driver version is ready.

Similarly if the driver is updated the same applies. Wait for the build to complete before rebooting.

I followed this topic but I don’t see any difference in the UUIDs/paths between the 2 grub entries.

index=0
kernel="/boot/vmlinuz-6.17.12-300.fc43.x86_64"
args="ro rootflags=subvol=root rd.md.uuid=986749fc:ac589679:e526a302:7a690672 rd.md.uuid=2529fbe2:7f94101d:a5b6e036:66f848a1 rhgb quiet nvidia-drm.modeset=1 nvidia-drm.fbdev=1 rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core"
root="UUID=213aecc6-237a-45eb-a276-cde36a65fa51"
initrd="/boot/initramfs-6.17.12-300.fc43.x86_64.img"
title="Fedora Linux (6.17.12-300.fc43.x86_64) 43 (KDE Plasma Desktop Edition)"
id="9c59d90599d34779b7d70b0a2bd1c879-6.17.12-300.fc43.x86_64"
index=1
kernel="/boot/vmlinuz-6.17.11-300.fc43.x86_64"
args="ro rootflags=subvol=root rd.md.uuid=986749fc:ac589679:e526a302:7a690672 rd.md.uuid=2529fbe2:7f94101d:a5b6e036:66f848a1 rhgb quiet nvidia-drm.modeset=1 nvidia-drm.fbdev=1 rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core"
root="UUID=213aecc6-237a-45eb-a276-cde36a65fa51"
initrd="/boot/initramfs-6.17.11-300.fc43.x86_64.img"
title="Fedora Linux (6.17.11-300.fc43.x86_64) 43 (KDE Plasma Desktop Edition)"
id="9c59d90599d34779b7d70b0a2bd1c879-6.17.11-300.fc43.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-9c59d90599d34779b7d70b0a2bd1c879"
args="ro rootflags=subvol=root rd.md.uuid=986749fc:ac589679:e526a302:7a690672 rd.md.uuid=2529fbe2:7f94101d:a5b6e036:66f848a1 rhgb quiet nvidia-drm.modeset=1 nvidia-drm.fbdev=1 rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core"
root="UUID=213aecc6-237a-45eb-a276-cde36a65fa51"
initrd="/boot/initramfs-0-rescue-9c59d90599d34779b7d70b0a2bd1c879.img"
title="Fedora Linux (0-rescue-9c59d90599d34779b7d70b0a2bd1c879) 43 (KDE Plasma Desktop Edition)"
id="9c59d90599d34779b7d70b0a2bd1c879-0-rescue"

Could it be related to an unsigned kernel or module? SecureBoot is enabled on the host.
Edit: I ran sudo grub2-mkconfig -o /boot/grub2/grub.cfg and after a reboot, it worked. That’s strange because I don’t see any difference when comparing grubby output before and after running the command.

Indeed. Looks like your issue must be different from that topic.

No, you got it right, thank you @pg-tips !

1 Like

Sometimes a non-printing character ends up in configuration files so you won’t see a difference that is causing an error. Do you have a backup with the previous /boot/grub2/grub.cfg so you can do a byte-level comparison?

I wonder if one or both of those arguments may be the fault for you.
Neither is necessary on my system and have not been for quite some time. Loading the nvidia driver into the kernel during boot performs those steps automatically.

$ sudo dmesg | grep -iE 'secure|nvidia|nouveau'
[    0.000000] Command line: BOOT_IMAGE=(hd5,gpt2)/vmlinuz-6.17.12-300.fc43.x86_64 root=/dev/mapper/fedora_root-root ro rd.lvm.lv=fedora_root/root rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core
[    0.000000] secureboot: Secure boot enabled
[    0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[    0.003600] secureboot: Secure boot enabled
[    0.034624] Kernel command line: BOOT_IMAGE=(hd5,gpt2)/vmlinuz-6.17.12-300.fc43.x86_64 root=/dev/mapper/fedora_root-root ro rd.lvm.lv=fedora_root/root rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core
[    7.098736] nvidia-nvlink: Nvlink Core is being initialized, major device number 234
[    7.104292] nvidia 0000:06:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[    7.151516] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.119.02  Release Build  (dvs-builder@U22-I3-B15-03-5)  Mon Dec  8 07:51:55 UTC 2025
[    7.219695] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  580.119.02  Release Build  (dvs-builder@U22-I3-B15-03-5)  Mon Dec  8 07:38:31 UTC 2025
[    7.235393] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input16
[    7.235778] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input17
[    7.236086] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input18
[    7.236173] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input19
[    7.244589] [drm] [nvidia-drm] [GPU ID 0x00000600] Loading driver
[    9.529718] [drm] Initialized nvidia-drm 0.0.0 for 0000:06:00.0 on minor 1
[    9.566748] nvidia 0000:06:00.0: vgaarb: deactivate vga console
[   10.013704] fbcon: nvidia-drmdrmfb (fb0) is primary device
[   10.143363] nvidia 0000:06:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

Note the lines at 7.219695 and the last 2 lines – as well as the kernel command line content.

No, check above, it’s now solved.
And as I previously said, it worked with the previous kernel (no grub option changes).