Seems grubby is not working properly

asked 2018-01-17 12:16:28 -0500

Peter76 gravatar image

updated 2018-01-25 12:14:45 -0500


A while ago I had this problem: ,

which was then solved.

Today I updated my system through the software app, which included kernel 4.14.13-300 .

After the update, I didn't see the new kernel in Grub's menu.

uname -r gives:

4.14.11-300.fc27.x86_64 , grubby --default-kernel also points there.

rpm -q kernel gives:

kernel-4.14.8-300.fc27.x86_64 kernel-4.14.11-300.fc27.x86_64 kernel-4.14.13-300.fc27.x86_64

So the new kernel is there.

After typing all this, I ran grub2-mkconfig -o /boot/grub2/grub.cfg, rebooted, and now everything is fine off course, but this should have been done by the update....

Anyone knows what's going on?

Regards, Peter

edit retag flag offensive close merge delete


The question should rather be "Why grubby is not working properly?"

Fedora is using grubby instead of grub2-mkconfig to reconfigure grub.cfg.

villykruse gravatar imagevillykruse ( 2018-01-18 01:48:44 -0500 )edit

Hi Peter, I recommend to manage all software installations and updates by using dnf exclusively ! :)

clnetbox gravatar imageclnetbox ( 2018-01-18 06:11:06 -0500 )edit

@ villykruse, ok, changed question:-)

@ clnetbox, will do, but for now that doesn't resolve the problem:-)

Peter76 gravatar imagePeter76 ( 2018-01-25 12:14:07 -0500 )edit

Do check if the grub packages are installed properly and not damaged.

rpm -Va 'grub*'

Important is that the symbolic link /etc/grub2.cfg points to ../boot/grub2/grub.cfg.

On UEFI system the symbolic link grub2-efi.cfg should point to ../boot/efi/EFI/fedora/grub.cfg.

villykruse gravatar imagevillykruse ( 2018-01-25 14:57:49 -0500 )edit

output of rpm -Va 'grub*' gives:

.M....... c /etc/default/grub

Actually quite baffled by that output,no idea what that means... :-)

Peter76 gravatar imagePeter76 ( 2018-01-25 16:36:42 -0500 )edit