vega50
(Mike C)
July 11, 2025, 9:38pm
1
I’m experiencing a persistent boot issue on Fedora 42. I haven’t been able to boot into any kernels newer than 6.14.9. Whenever I try to boot with a more recent kernel (e.g., 6.14.11, 6.15.4, 6.15.5), the system drops into emergency mode. The 6.14.9 kernel still boots fine.
Any help or insights would be greatly appreciated!
It seems something is wrong with your disk.
The kernel is timing out looking for the root file system.
Can you boot your system from a live usb image?
If so you can investigate what is wrong.
vega50
(Mike C)
July 12, 2025, 10:45pm
3
I can boot to into kernel 6.14.9 without any issues and the system works perfectly fine with no disk problems. Any kernel I update to after 6.14.9 is when the time out occurs and dumps me into emergency mode. Not sure what would cause that.
I’ve been running Fedora on this system since 36 and never had any issues with updating kernels until now.
What does lsblk -f
report?
What does cat /proc/cmdline
show?
I am wondering is there is issue between kernel options and your partitions.
vega50
(Mike C)
July 13, 2025, 2:43pm
5
Here are the command outputs:
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 e246b8cd-f962-4af2-974b-5be35b01def1 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT16 1384-FFFC 171.9M 38% /boot/efi
├─nvme0n1p2 ext4 1.0 0cf10e99-dea7-4d3d-a563-0238c94d747a 543.6M 37% /boot
├─nvme0n1p3 ntfs OS FCD816DDD816964C
├─nvme0n1p4 ntfs WINRETOOLS B672D49A72D46123
├─nvme0n1p5 ntfs Image CE76D4B176D49B91
├─nvme0n1p6 ntfs DELLSUPPORT EC168A50168A1C28
└─nvme0n1p7 btrfs fedora_localhost-live 93a8adfa-36a2-4863-b54f-68ed36e1333c 118G 62% /home
/
cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.14.9-300.fc42.x86_64 root=UUID=93a8adfa-36a2-4863-b54f-68ed36e1333c ro rootflags=subvol=root rhgb quiet
Here is the /etc/fstab
UUID=93a8adfa-36a2-4863-b54f-68ed36e1333c / btrfs subvol=root 0 0
UUID=0cf10e99-dea7-4d3d-a563-0238c94d747a /boot ext4 defaults 1 2
UUID=1384-FFFC /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=93a8adfa-36a2-4863-b54f-68ed36e1333c /home btrfs subvol=home 0 0
That seems okay.
Check that the new kernel is using the same kernel command line as the working kernel.
vega50
(Mike C)
July 14, 2025, 9:09pm
7
I’ve got it working now. Thanks Barry for getting me steered in the right direction. Here is what I did to fix:
Updated to the most recent kernel 6.15.5
Rebuilt the grub config: grub2-mkconfig -o /boot/grub2/grub.cfg
Rebooted