Grub Menu not update after dnf upgrade --refresh kernel 6.8.10 not visible but installed

[sreyaz01 (Syed Reyaz)]

@computersavvy

grub2-editenv - list

as you told

┌ sreyaz@blueswitch  ~  | 3.061s                                                                             zsh 
└$ sudo grub2-editenv - unset menu_auto_hide

┌ sreyaz@blueswitch  ~  | 82ms                                                                               zsh 
└$ sudo grub2-editenv - unset blsdir

┌ sreyaz@blueswitch  ~  | 74ms                                                                               zsh 
└$ sudo grub2-editenv - list                
saved_entry=5f391706b7cf43a0ba83c55ca1e9fd9e-6.8.10-300.fc40.x86_64
boot_success=1
boot_indeterminate=0

[computersavvy (Jeff V)]

Excellent.
I think that another boot should show only one entry for each fedora kernel now

[sreyaz01 (Syed Reyaz)]

oh that thing fixed by just opening grub-customizer gui which auto updated the files but

so we know now that
blsdir=/root/boot/loader/entries

this one line causing the issue ?

[computersavvy (Jeff V)]

It has been some time since I had seen that thread you linked, and it reminded me of that fix.
Would have been a simple fix had I remembered that without the reminder.

Please mark the appropriate post as the solution if things are now working for you as expected.

[computersavvy (Jeff V)]

@sreyaz01

this one line causing the issue ?

It would appear that is correct

Grub customizer has caused some errors of various types at times.

[sreyaz01 (Syed Reyaz)]

well but that blsdir=/root/boot/loader/entries was also present after i successfully booted to 6.8.10 kernel. ref post#78

i am still not certain that removing that line fixed those issue or just

• rm /boot/grub2/grub.cfg /boot/efi/EFI/fedora/grub.cfg
• dnf reinstall grub2-* shim*

these commands fixed it , still i am going to mark that post#75 as solution

thanks alot

[computersavvy (Jeff V)]

Thanks for being patient with me as I tried to work through the several possible causes.

When I started with the grubenv file I should have immediately had you do the list command to see what was there before making any changes and the problem would have jumped out at me in that listing.

Glad we were able to reach a resolution.

I do disagree on the solution since hiding or not hiding the menu would not cause this. It may have been a combination of the reinstalling of the grub files as well as editing the grubenv file. (Reinstalling the grub2 packages after removing /boot/grub2/grub.cfg would have also corrected structure errors in the grubenv file)

It also may have been a slightly corrupt grubenv file since that file is a specific number of bytes and however that blscfg line was written there may have corrupted it. The grub2-editenv command is the only one designed to edit that file and not corrupt it.

[sreyaz01 (Syed Reyaz)]

@computersavvy

(Reinstalling the grub2 packages after removing /boot/grub2/grub.cfg would have also corrected structure errors in the grubenv file)

this is understandable.
so on a basic note our issue was a corrupted grubenv file,

i am glad I am running fedora again without any issue thanks to you and vekruse who also participated

[computersavvy (Jeff V)]

@sreyaz01

a corrupted grubenv file,

Either a corrupted file or having the erroneous “blscfg=” entry in it seems the cause.

[computersavvy (Jeff V)]

@computersavvy

I seem to have the updates-archive repo enabled so that is why I could reinstall that package.
Try again with the command as
dnf install kernel-6.8.9 --enablerepo updates-archive

BTW
I just checked to verify what I remembered, and found that the updates-archive repo can be installed and enabled through the gnome software app (hamburger menu in upper right corner then selecting repositories)

That was part of the discussion early on way back in post 22 of this thread.

[vekruse (Villy Kruse)]

@computersavvy

/proc, /sys, /dev, and /run are all bind mounted according to the commands I provided and he echoed.
for file in sys run proc dev ; do mount -o bind /$file /mnt/$file ; done done as root from the live system.

From man mount

      The bind mount call attaches only (part of) a single filesystem, not possible
       submounts. The entire file hierarchy including submounts can be attached a
       second place by using:

When you bind-mount /sys, you only mount this file system and not whatever files systems mounted on /sys. They need to be separately bind-mounted

You may want to use rbind instead of bind. See the man page.

[hmmsjan (h.janssen)]

I’ve just seen this long discussion and fortunately the system runs again.
But the original grub.cfg shown above is not normal and may be generated by grub-customizer. As far I know this does not support blscfg.
Indicators are /etc/grub.d/10_linux_proxy and /etc/grub.d/33_linux_proxy, missing /etc/grub.d/10_linux.

May be good to check whether grub-customizer is still installed or some files left over from old installation, in order to prevent the problem comes back at some update.

[vekruse (Villy Kruse)]

@computersavvy

Either a corrupted file or having the erroneous “blscfg=” entry in it seems the cause

More than that

• Using a non-Fedora version of grub2, i.e. linpus
• Fedore no longer update the boot menu unless GRUB_ENABLE_BLSCFG=true
• The linpus grub doesn’t understand GRUB_ENABLE_BLSCFG=true
• /boot/efi/EFI/fedora/grub.cfg was messed up
• Using grub-customizer

[hmmsjan (h.janssen)]

Just did a test install of grub-customizer in a F39 VM. Indeed it created /etc/grub.d/10_linux_proxy, the other one I’ve not seen. But it does not “own” the files in the rpm. It also installs grub2-pc which is not needed on EFI, and cannot be removed anymore.

Anyhow, the grub.cfg is generated on the right location now.

“rpm -e grub-customizer” does not restore the original configuration by post_install script, the /etc/grub.d/10_linux generating bls entries has been moved into backup, the proxy is left over.

All fiddling with system files is done in the program, and as far I have seen the “restore” button in the program does not fix it, despite the backups.

[sreyaz01 (Syed Reyaz)]

I do not understand the whole thing here but yes Grub-Customizer is Installed if that’s gonna create issue in future Then I’ll remove that. Or If any Info is needed Lemme know

[hmmsjan (h.janssen)]

If you want to use it, I assume you should set “GRUB_ENABLE_BLSCFG=false” in /etc/default/grub and let grub-customizer create the /boot/grub2/grub.cfg. Your original default/grub file showed GRUB_ENABLE_BLSCFG=true, so that might be the starting point of the problem. Could be caused by executing “/sbin/grub2-switch-to-blscfg” during update/upgrade at some point.

If you do not need grub-customizer, I would delete it with “rpm -e grub-customizer”,
but you have to manually delete /etc/grub.d/*proxy*. There are some backup directories installed there, they do not harm but can be deleted. Then repeat the procedure you did before which revived the system.

[vekruse (Villy Kruse)]

@hmmsjan

f you want to use it, I assume you should set “GRUB_ENABLE_BLSCFG=false” in /etc/default/grub and let grub-customizer create the /boot/grub2/grub.cfg.

Don’t.

GRUB_ENABLE_BLSCFG=false is an unsupported setting, and your kernel upgrades won’t work properly.

So Don’t.

[hmmsjan (h.janssen)]

Thanks, OK, good to know. But this means grub-customizer should not be supported anymore as long as it does not handle GRUB_ENABLE_BLSCFG=true properly.

[sreyaz01 (Syed Reyaz)]

So the best way to Uninstall Grub-Customizer
And repeate post#75 process.

@hmmsjan

manually delete /etc/grub.d/proxy. There are some backup directories installed there, they do not harm but can be deleted. Then repeat the procedure you did before which revived the system.

And I don’t know which proxy to delete. not that much familier how grub.cfg works

And I am trying to find out what actually this line do

GRUB_ENABLE_BLSCFG

[vekruse (Villy Kruse)]

It works now, so don’t touch it. This thread is long enough.