Fedora 33->34 : corrupted Grub menu

A faulty SATA cable has caused an annoying issue with my F34 boot process.
To be specific, 2 weeks ago I decided to upgrade my F33 to F34.
It seems that during the upgrade process something went wrong with the kernel installation and since then I cannot boot with the fresh installed F34 kernel.
Below you can see some screenshots from the boot process:


As a workaround, I am using the previous F33 kernel in order to boot the PC.
I was wondering if I can rebuild somehow the grub menu and the corresponding /boot filesystem.

1 Like

If you try reinstalling the new kernel, that should re-update your grub information also. have you given that a try?

Otherwise there’s lots of information on modifying grub etc. here:

https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/

Actually, I tried installing the latest kernel but in vain. I can boot ONLY with the F33 kernel.

The output of the lsblk command is the following:

NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda               8:0    0  1,8T  0 disk 
├─sda1            8:1    0  500M  0 part /boot
└─sda2            8:2    0  1,8T  0 part 
  ├─fedora-swap 253:0    0  3,9G  0 lvm  [SWAP]
  ├─fedora-root 253:1    0   50G  0 lvm  /
  └─fedora-home 253:2    0  1,8T  0 lvm  /home

According to the documentation you shared, do you think that the following commands would fix the issue?

grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-install /dev/sda

That screenshot looks like you have a grub theme installed/active. It is possible that a grub theme that works in F33 may have issues when booting with F34.

1 Like

Panagiotis

JV is right when he says this is a problem with a grub theme. Your grub is looking for ‘fireworks.png’ in the system theme, which seems very weird.

Check /etc/default/grub, which is where themes are specified. Look for a line GRUB_THEME= and comment it out by putting a # before it.

Then

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

That’ll remove references to the theme in the grub.cfg file - you can check before you overwite it that that’s the case.

Of course, this explains why simply reinstalling the Fedora 34 kernel won’t work. Why the 33 kernel doesn’t complain is a mystery!

1 Like