Kernel 6.7.7 wrong booting arguments

Ask Fedora
1

Hi,
I just rebooted my pc and installed new system upgrades. Then it didn’t boot up. The kernel went into panic mode because it couldn’t open root device which was set to /dev/something . It couldn’t mount root fs on unknown. Then I remembered that it happened as well when I upgraded to Fedora 39. In grub menu I changed the booting arguments manually to what other kernels had which was root=UUID=some long id. + added initrd.

I don’t know if it can be influenced by these factors:
I use GrubCustomizer to have themed grub. I have dual boot windows. Which resides on /dev/something that kernel 6.7.7 wanted to mount root fs to.

My question is why did that happen and how to prevent it in the future?

Thanks

2

Maybe try removing grub customizer and see if the problem returns with the next kernel upgrade or not. The problem you report here and in your other thread seem to have a common factor and that is the non-standard grub customizer which does not come from a fedora repo.

3

Okay, will try

4

What is the contents of /etc/default/grub and /etc/kernel/cmdline?

5

/etc/default/grub

GRUB_TIMEOUT=60
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
#GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="nvidia-drm.modeset=1 rhgb quiet nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="false"
GRUB_THEME="/boot/grub2/themes/bigsur/theme.txt"

#GRUB_GFXMODE="saved"
GRUB_SAVEDEFAULT="true"
#GRUB_HIDDEN_TIMEOUT="0"
GRUB_TIMEOUT_STYLE="menu"
GRUB_DISABLE_LINUX_RECOVERY="true"

/etc/kernel/cmdline

root=UUID=5dcb1e38-f154-4177-84cc-2a83137831ef ro rootflags=subvol=root rhgb quiet nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau

This is the correct value that works but after updates it was not this.

6

You got GRUB_ENABLE_BLSCFG="false" which means that the grub menu is not automatically updated when installing a new kernel. You will have to run

grub2-mkconfig -o /boot/grub2/grub.cfg

every time you get a new kernel upgrade. New installations gets GRUB_ENABLE_BLSCFG=true and old installations were converted many releases ago.

Also, you got nvidia-drm.modeset=1 two times. Once should be enough.

7

Thanks, I changed GRUB_ENABLE_BLSCFG to true and removed second nvidia-drm.modeset=1
I hope changing the BLSCFG will prevent this error in the future.

8

You will have re-install the latest kernel to verify if it works.