Hi Fedora Community, I’m encountering two UEFI glitches with Fedora 42 on a motherboard without Secure Boot support.
When booting the live USB (created with Fedora Media Writer) in UEFI mode, I see:
Failed to open \EFI\BOOT\ – Not Found
After a few seconds this clears, GRUB appears, and I can boot the live session successfully.
After a full installation, on boot I get:
Failed to open \EFI\fedora\ – Not Found
Again it disappears, GRUB loads, and Fedora boots normally.
Also I had this error as long as I remember in both fedora 40 41 and now 42
The only way I didn’t get this error was booting using ventoy grub2 mode (same error will appear if i choose the normal mode)
But after successful installation again same error
Failed to open \EFI\fedora\ – Not Found
I only faced this errors in fedora
Everything’s worked fine with Ubuntu Linux mint arch + Grub2 and arch + systemd-boot
My questions are :
What causes these transient “not found” errors
Cuz the needed files exit in the right directory
Could these errors risk EFI-partition corruption or disrupt automated boot (e.g. after firmware updates)?
Are there recommended workarounds—shim tweaks, efibootmgr adjustments, manually copying EFI/BOOT/bootx64.efi, etc.—to eliminate these messages and ensure a clean UEFI boot?
Does your hardware support 64 bits? Have you executed fsck on your SSD to check for errors? Have you backed up important data? If so, you may wish to format the system partition and the OS partition before attempting a clean install.
Yes my hardware is 64bits and my SSD gives no error
My data aren’t in the same hard drive witch i install the OS in it
Also thanks for the post but i still don’t understand why this happens
When reporting issues you should try to provide enough detail to allow others with similar hardware to reproduce the issue. A good way to do that it is to post the output from running inxi -Fzxx in a terminal (as pre-formatted test using the </> button from the top line of the text entry panel).
You should make sure your UEFI/BIOS is fully updated. I suspect there may be an old or corrupt entry in your boot configuration. Please post the output from running efibootmgr in a terminal (also as pre-formatted text).