Failed to open \EFi\fedora\ - Not Found

oduda · June 1, 2025, 2:51pm

This occurs since F41 mainly, even in LiveCD boot. No entry in BIOS boot menu solve this.
I have an old Asus M5A99X EVO motherboard and Phenom II X6 1100t processor.
*Running in dualboot F42 (sdb) and Windows 10 LTSC (sda) but i just invert this and the same issue.
*Boot animation fail too, appears 3 points at left region of a gray screen.
Is possible to detect the problem with:

efibootmgr

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0008,0000,0007,0006,0009,0003
Boot0000* Windows Boot Manager HD(1,GPT,bf03947b-7891-4582-910c-5e17d01e8faa,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000065000100000010000000040000007fff0400
Boot0001* Fedora HD(1,GPT,98629386-3a53-4483-90bf-d69ec3222707,0x800,0x12c000)/\EFI\fedora\shimx64.efi
Boot0003* Fedora HD(1,GPT,98629386-3a53-4483-90bf-d69ec3222707,0x800,0x12c000)/\EFI\FEDORA\shimx64.efi
Boot0006* UEFI OS HD(1,GPT,98629386-3a53-4483-90bf-d69ec3222707,0x800,0x12c000)/\EFI\BOOT\BOOTX64.EFI
Boot0007* Lenovo E660 SSD-2.5-512G BBS(HD,0x0)AMBO
Boot0008* Lenovo E660 SSD-2.5-512G BBS(HD,0x0)AMBO
Boot0009* KINGSTON SA400S37240G BBS(HD,0x0)AMBO

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 476,9G 0 disk
├─sda1 8:1 0 100M 0 part
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 476,3G 0 part
└─sda4 8:4 0 509M 0 part
sdb 8:16 0 476,9G 0 disk
├─sdb1 8:17 0 600M 0 part /boot/efi
├─sdb2 8:18 0 1G 0 part /boot
└─sdb3 8:19 0 475,4G 0 part /home
/
sdc 8:32 0 223,6G 0 disk
└─sdc1 8:33 0 223,6G 0 part

Thank you!

computersavvy · June 1, 2025, 2:59pm

lsblk -f would provide more usable information.

What is meant by Cannot find EFI file at boot? Is this an error message? or something else? The information from sdb seems to indicate that efi is available and mounted.

Details about what is happening are critical for finding a solution.

pg-tips · June 1, 2025, 3:41pm

Also, what is the result of sudo ls /boot/efi/EFI/fedora ?

vekruse · June 1, 2025, 4:20pm

lsblk -f -o +PARTUUID would be better as it will show the partition UUID that you will also see in the efibootmgr listing. For any other purpose lsblk -f is better.

oduda · June 1, 2025, 4:31pm

Thank you!

lsblk -f -o +PARTUUID
NAME   FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda                                                                                            
├─sda1 vfat   FAT32            5247-4A5F                                                       bf03947b-7891-4582-910c-5e17d01e8faa
├─sda2                                                                                         8b65e114-3b53-4504-b5f6-61f53e06939b
├─sda3 ntfs         Local Disk CCE64AA8E64A931E                                                7f448f40-1457-48ad-8242-32242795a473
└─sda4 ntfs                    E89E98649E982CD6                                                f4b00271-ff71-46bf-991d-f5858d332e58
sdb                                                                                            
├─sdb1 vfat   FAT32            931C-9DB6                             579,5M     3% /boot/efi   98629386-3a53-4483-90bf-d69ec3222707
├─sdb2 ext4   1.0              7b9790ae-dcb8-4aed-ad08-ac9066da1c48  637,3M    28% /boot       897c9e8c-a26e-43ee-9ea9-3a109fb45f52
└─sdb3 btrfs        fedora     26788c94-87ce-43b0-a99c-90ed1c9768e8  467,3G     1% /home       5009ceb8-50c7-4a96-b1d3-7eb0cb8a9c3b
                                                                                   /           
sdc                                                                                            
└─sdc1 ntfs         Local Disk 6F5C6C1C0381370C                                                d1d0a0bc-01

oduda · June 1, 2025, 4:33pm

sudo ls /boot/efi/EFI/fedora
BOOTIA32.CSV gcdia32.efi grub.cfg grubx64.efi mmx64.efi shimia32.efi
BOOTX64.CSV gcdx64.efi grubia32.efi mmia32.efi shim.efi shimx64.efi

pg-tips · June 1, 2025, 4:48pm

Thanks - no obvious problem there!

oduda · June 1, 2025, 5:17pm

This message appears when booting, before the Grub menu is loaded.

And when Fedora is selected from Grub menu appears this (not the loading animation with Fedora logo)

vekruse · June 1, 2025, 6:25pm

This so far looks fine.

Boot number 0000 refers to the ESP in /dev/sda1 and should be bootable.

Boot number 0001 and number 0003 both refers to the ESP in /dev/sdb1 and should boot be able to boot the Fedora system.

This occurs sometimes and it may not look nice but should not prevent the system from booting.

I am not sure what boot menu you refer to. The UEFI boot menu should show both Windows and Fedora. Sometimes it is just easier to use the UEFI boot menu for multi-booting instead of trying to make it work with grub.

You get this message when you boot which UEFI boot entry? If you select a boot entry which doesn’t work, UEFI will usually try the next one in the boot order.

oduda · June 1, 2025, 7:15pm

Sorry, yes, after select any option in BIOS boot menu, before GRUB menu…
*Boot0000 option is Windows, and no message or error occurs.

And Setup disks is this

Thanks Villy Kruse, i used Fedora since the 16a. version, and a so powerful and beautiful OS
needs care of user to maintain yours qualities

I’m very sad that I can’t do it, because I don’t know EFI/UEFI deeply enough to solve it

computersavvy · June 1, 2025, 11:37pm

I edited the output from your lsblk -f command above and added the preformatted text tags (available by highlighting the text then click the </> button on the tool bar) so it appears exactly as seen on your screen.
Please try to post text that you copy and paste that way so it retains the on-screen formatting.

I note that you seem to have the boot order from efibootmgr showing a strange sequence. Mostly I see fedora - fedora - windows - something else in the boot order.

Your 2 fedora entries are 0001 and 0003 with windows as 0000, but your boot order is

I wonder if having the 0007 & 0008 entries are possibly preventing the system from reaching the windows boot since it searches in order. 0001, 0008, 0000.

Possibly simply changing the boot order to something like 0001, 0003, 0000, … might allow the sudo grub2-mkconfig -o /boot/grub2/grub.cfg command to locate and add windows to your boot list. It appears that windows is on sda and fedora is on sdb and that each has its own efi boot partition.

oduda · June 2, 2025, 5:01pm

Thank you Jeff V
Sorry for the unformatted post.
I have always used Linux on the sda disk, now I have changed it to the sdb disk to test if it would resolve the error. But unfortunately it did not. I would like to remind you that Windows is booting normally. What appears is the error message before the BIOS menu, before Grub. Afterwards, when I select any entry in the Grub menu (Linux or Windows), everything is correct.
Greetings…

vekruse · June 2, 2025, 5:56pm

That has already been concluded. Boot0000 boots Windows from the ESP in sda1 and Boot0001 boots grub2 from the ESP in sdb1. Boot0003 is a duplicate of Boot0001.

jrredho · June 2, 2025, 9:03pm

A couple of quick thoughts/questions:

Have you updated your BIOS firmware recently?
Have you had a Windows update recently? If so, would it be possible that that update mucked with your sda EFI partition?
I wonder if it’s possible that your UEFI Boot Manager is looking for a fedora directory in your sda EFI partition?

oduda · June 2, 2025, 9:58pm

Thanks, these are the results of commands suggested:

lsblk -o PATH,PARTTYPE,FSTYPE
PATH      PARTTYPE                             FSTYPE
/dev/sda                                       
/dev/sda1 c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat
/dev/sda2 e3c9e316-0b5c-4db8-817d-f92df00215ae 
/dev/sda3 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs
/dev/sda4 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs
/dev/sdb                                       
/dev/sdb1 c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat
/dev/sdb2 bc13c2ff-59e6-4262-a352-b275fd6f7172 ext4
/dev/sdb3 0fc63daf-8483-4772-8e79-3d69d8477de4 btrfs
------------------------------------------------------------------------------------
bootctl status
systemd-boot not installed in ESP.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-0-rescue.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-0-rescue.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-0-rescue.conf:8: Unknown line 'grub_class', ignoring.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf:8: Unknown line 'grub_class', ignoring.
System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (unsupported)
  TPM2 Support: no
  Measured UKI: no
  Boot into FW: not supported

Current Boot Loader:
      Product: GRUB 2.12
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Enroll SecureBoot keys
               ✗ Retain SHIM protocols
               ✗ Menu can be disabled
               ✗ Multi-Profile UKIs are supported
               ✓ Boot loader set partition information
    Partition: /dev/disk/by-partuuid/98629386-3a53-4483-90bf-d69ec3222707

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/98629386-3a53-4483-90bf-d69ec3222707)
         File: ├─/EFI/BOOT/BOOTIA32.EFI
               ├─/EFI/BOOT/BOOTX64.EFI
               ├─/EFI/BOOT/fbia32.efi
               └─/EFI/BOOT/fbx64.efi

Boot Loaders Listed in EFI Variables:
        Title: Fedora
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/98629386-3a53-4483-90bf-d69ec3222707
         File: └─/EFI/fedora/shimx64.efi

        Title: Windows Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/bf03947b-7891-4582-910c-5e17d01e8faa
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

        Title: UEFI OS
           ID: 0x0006
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/98629386-3a53-4483-90bf-d69ec3222707
         File: └─/EFI/BOOT/BOOTX64.EFI

        Title: Fedora
           ID: 0x0003
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/98629386-3a53-4483-90bf-d69ec3222707
         File: └─/EFI/FEDORA/shimx64.efi

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/897c9e8c-a26e-43ee-9ea9-3a109fb45f52)
        token: fedora

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Fedora Linux (6.14.9-300.fc42.x86_64) 42 (Workstation Edition)
           id: d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf
       source: /boot//loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf (on the Extended Boot Loader Part>
      version: 6.14.9-300.fc42.x86_64
        linux: /boot//vmlinuz-6.14.9-300.fc42.x86_64
       initrd: /boot//initramfs-6.14.9-300.fc42.x86_64.img $tuned_initrd (No such file or directory)
      options: root=UUID=26788c94-87ce-43b0-a99c-90ed1c9768e8 ro rootflags=subvol=root rhgb quiet $tuned_params

WARNING: default boot entry is broken
------------------------------------------------------------------------------------
find /boot -ls
        2      4 dr-xr-xr-x   6 root     root         4096 jun  1 11:25 /boot
       11     16 drwx------   2 root     root        16384 mai 29 12:11 /boot/lost+found
       18  11364 -rw-r--r--   1 root     root     11633538 mai 28 21:00 /boot/System.map-6.14.9-300.fc42.x86_64
       31  55568 -rw-------   1 root     root     56900484 jun  1 10:56 /boot/initramfs-6.14.9-300.fc42.x86_64.img
     8194      4 drwxr-xr-x   3 root     root         4096 mai 29 12:15 /boot/loader
       14      4 drwx------   2 root     root         4096 jun  1 11:25 /boot/loader/entries
       29      4 -rw-r--r--   1 root     root          417 mai 29 12:18 /boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-0-rescue.conf
       24      4 -rw-r--r--   1 root     root          368 jun  1 10:56 /boot/loader/entries/d6aed2ea408b4c58b7a5447296b1e4b4-6.14.9-300.fc42.x86_64.conf
       22      0 lrwxrwxrwx   1 root     root           46 jun  1 10:55 /boot/symvers-6.14.9-300.fc42.x86_64.xz -> /lib/modules/6.14.9-300.fc42.x86_64/symvers.xz
       19    280 -rw-r--r--   1 root     root       285842 mai 28 21:00 /boot/config-6.14.9-300.fc42.x86_64
       17  16848 -rwxr-xr-x   1 root     root     17250664 mai 28 21:00 /boot/vmlinuz-6.14.9-300.fc42.x86_64
       28 172028 -rw-------   1 root     root     176153064 mai 29 12:17 /boot/initramfs-0-rescue-d6aed2ea408b4c58b7a5447296b1e4b4.img
        1      4 drwx------   4 root     root          4096 dez 31  1969 /boot/efi
        3      4 drwx------   4 root     root          4096 mar 13 21:00 /boot/efi/EFI
      117      4 drwx------   2 root     root          4096 mar 13 21:00 /boot/efi/EFI/BOOT
      122    732 -rwx------   1 root     root        747681 mai 29 15:14 /boot/efi/EFI/BOOT/BOOTIA32.EFI
      123    928 -rwx------   1 root     root        949424 mai 29 15:14 /boot/efi/EFI/BOOT/BOOTX64.EFI
      124     72 -rwx------   1 root     root         70360 mai 29 15:14 /boot/efi/EFI/BOOT/fbia32.efi
      125     88 -rwx------   1 root     root         87816 mai 29 15:14 /boot/efi/EFI/BOOT/fbx64.efi
      126      4 drwx------   2 root     root          4096 mar 13 21:00 /boot/efi/EFI/fedora
      139      4 -rwx------   1 root     root           144 mai 29 15:18 /boot/efi/EFI/fedora/grub.cfg
      140      4 -rwx------   1 root     root           112 mai 29 15:14 /boot/efi/EFI/fedora/BOOTIA32.CSV
      141      4 -rwx------   1 root     root           110 mai 29 15:14 /boot/efi/EFI/fedora/BOOTX64.CSV
      142   2952 -rwx------   1 root     root       3022144 mai 29 15:14 /boot/efi/EFI/fedora/gcdia32.efi
      143   3944 -rwx------   1 root     root       4037952 mai 29 15:14 /boot/efi/EFI/fedora/gcdx64.efi
      144   2952 -rwx------   1 root     root       3022144 mai 29 15:14 /boot/efi/EFI/fedora/grubia32.efi
      145   3944 -rwx------   1 root     root       4037952 mai 29 15:14 /boot/efi/EFI/fedora/grubx64.efi
      146    660 -rwx------   1 root     root        673992 mai 29 15:14 /boot/efi/EFI/fedora/mmia32.efi
      147    832 -rwx------   1 root     root        848080 mai 29 15:15 /boot/efi/EFI/fedora/mmx64.efi
      148    928 -rwx------   1 root     root        949424 mai 29 15:15 /boot/efi/EFI/fedora/shim.efi
      149    732 -rwx------   1 root     root        747681 mai 29 15:15 /boot/efi/EFI/fedora/shimia32.efi
      150    928 -rwx------   1 root     root        949424 mai 29 15:15 /boot/efi/EFI/fedora/shimx64.efi
      151      4 drwx------   3 root     root          4096 mai 29 15:14 /boot/efi/System
      153      4 drwx------   3 root     root          4096 mai 29 15:14 /boot/efi/System/Library
      155      4 drwx------   2 root     root          4096 mai 29 15:15 /boot/efi/System/Library/CoreServices
      157      4 -rwx------   1 root     root           384 mai 29 15:15 /boot/efi/System/Library/CoreServices/SystemVersion.plist
      158      4 -rwx------   1 root     root            34 mai 29 15:14 /boot/efi/mach_kernel
       20      4 -rw-r--r--   1 root     root           161 mai 28 21:00 /boot/.vmlinuz-6.14.9-300.fc42.x86_64.hmac
       27  16572 -rwxr-xr-x   1 root     root      16968040 mai 29 12:16 /boot/vmlinuz-0-rescue-d6aed2ea408b4c58b7a5447296b1e4b4
     8193      4 drwx------   3 root     root          4096 jun  2 18:45 /boot/grub2
       15      4 drwx------   2 root     root          4096 abr  9 09:05 /boot/grub2/fonts
       23   2340 -rwx------   1 root     root       2394108 mar 26 21:00 /boot/grub2/fonts/unicode.pf2
       25      8 -rw-------   1 root     root          7882 mai 29 12:18 /boot/grub2/grub.cfg
       16      4 -rw-------   1 root     root          1024 jun  2 18:45 /boot/grub2/grubenv
       21      4 -rw-rw-r--   1 root     root           141 abr  9 09:18 /boot/grub2/earlyboot.cfg

And so doctors?

oduda · June 2, 2025, 10:02pm

No I do not made firmware update recently. My motherboard is an old one, 2012 */-, and since that had updates anymore.

oduda · June 2, 2025, 10:08pm

Sorry, I do not believe this… To complete the information - I had reset many times the BIOS by removing the battery. But the “problem” remains…

oduda · June 2, 2025, 10:37pm

Talk about change with in Fedora shell? Because I can’t edit BIOS entry, nor?

computersavvy · June 3, 2025, 12:34am

Having multiple disks with an ESP is fully functional (or even multiple ESPs on a single disk). The limitation is that the UEFI BIOS can only be configured to use one ESP for booting.
The various ESP partitions can usually be selected from the bios boot menu or the bios setup config, but only one can actually be used at a time.

Generally a fedora installation can identify and configure the windows boot entry in grub even when it is on a different drive (as long as that drive is attached and functional when grub is configured).

vekruse · June 3, 2025, 5:47am

It is up to UEFI to what it would accept. In Tianocore, aka edk2-ovmf, the UEFI system is able to load the efi boot loader from any vfat or fat file system. It doesn’t even need to be marked as ESP. What real hardware does or doesn’t accept, that can vary quite a lot.

When selecting to boot from a particular disk unit, the system is looking for an ESP marked partition and looks for the file \EFI\BOOT\BOOTX64.EFI and load that. That is primarily used to boot a removable boot device such as a USB memory stick with an install image.

Topic		Replies	Views
Error booting Fedora 40 after installation Ask Fedora efibootmgr , uefi , f40	12	2240	May 20, 2024
Error booting Fedora 42 after Installation Ask Fedora	4	59	June 2, 2025
Issue with Fedora 42 UEFI Bootable USB – “\EFI\BOOT\ - Not Found” (and Post-Install “\EFI\fedora\ - Not Found”) Ask Fedora	5	272	June 5, 2025
Fedora 38 Bootloader install error Ask Fedora f38 , uefi , dual-boot , windows	29	4676	June 2, 2023
GRUB Fails to boot Fedora, boots Windows instead Ask Fedora f34 , uefi , dual-boot , grub , nvidia	7	1055	March 1, 2023

Failed to open \EFi\fedora\ - Not Found

efibootmgr

lsblk

Related topics