Can’t boot after update

Ask Fedora
, , , , , , ,
1

I updated my Fedora Silverblue Rawhide install and now I am not able to boot anymore.

When I try to boot from the device Fedora is installed to, I get this loop:

Computer starts, but I can’t get into the boot menu (tried arrows and ESC). After a very short times the computer reboots again into BIOS. When I exit out of it, the loop starts again.

I really thought I was save using Rawhide with Silverblue, because I could just rebase to 40 whenever I have some issues. I guess I was wrong there.

I checked the disk and everything seems to be fine.

Has anyone an idea what I could do? I don’t even know where to start troubleshooting.

Please let me know what additional information you may need.

2

So you say not even GRUB is showing up?

3

Yes, it does not show up. Maybe it is there and is (re-)booting into BIOS directly, but I can’t make it show up and I don’t know how to find the cause for this.

4

Well, you cant give us much logs here, but more infos please

  • nvidia or other kernel modules
  • grub customized or something
  • what hardware, is the BIOS still supported, UEFI?
  • Secureboot? Custom keys setup or default ones?
  • legacy or EFI boot?
  • since when do you have your install?
  • did you ever do the fix for the outdated grub?
5
  • nvidia or other kernel modules → NO.
  • grub customized or something → NO, but using rpm-ostree kargs
  • what hardware, is the BIOS still supported, UEFI? → It’s a Sasmung 750XED
  • Secureboot? Custom keys setup or default ones? → Yes, default.
  • legacy or EFI boot? → EFI.
  • since when do you have your install? → Since about a year.
  • did you ever do the fix for the outdated grub? → YES, some weeks ago.
6

I have the same issue since yesterday. I don’t think I upgraded something, if I remember correctly I just added some new overlays and wanted to reboot the system to activate them. So maybe rpm-ostree did mess something up during the process.

Before the system reboots again, I get this for few milliseconds (I had to use the slow-mo mode of my phone to be able to record / read this):

error: ../../grub-core/fs/fshelp.c:257:file 'grub2/x86_64-efi/bli.mod' not found.

I tried to edit the grub.cfg / adding the bli.mod file manually, but no luck.

Tried to reconfigure grub from a live system, with no luck either:

1 Like
7

fyi, I opened an issue at the Silverblue issue tracker:

2 Likes
8

So, what kargs do you use?

Might want to do the research what type of BIOS that is, as “a Samsung” is not a BIOS :wink: helps us not waste time on duckduckgo-ing stuff for others

Good that you reported the issue. Strange, might be an issue with the newer GRUB.

You could try to revert the GRUB version through some live media.

And yes, atomic desktops are only as unbreakable as the bootloader or OSTree itself. If something here breaks, you may need a reinstall. Had that before.

9

Added atomic-desktops, boot, bootupd, f41, grub

10

Thanks to @haeckerfelix and everyone else in the GitHub issue for figuring this out! I tried out things that were suggested and distilled it down to some work-around instructions @ Unable to boot rawhide after latest deployment, missing bli.mod file · Issue #587 · fedora-silverblue/issue-tracker · GitHub

Basically, you have to boot into a live Fedora Workstation from a USB stick, mount your EFI partition from your disk, copy a specific grub file (grubx64.efi, from an RPM, which you can get in a toolbx container) to your EFI partition, reboot back into your installed OS, and rebase back to Fedora 40.

More details at my comment on GitHub, linked above.

11

I made the laptop work following this, but I think my hardware and configuration is not really important anymore as the issue is reproducible and now has a solution in the github issue.

1 Like
12

Added bug-reported