From your picture, I can see a few things:
- Your ESP contains a few unnecessary directories,
dev,proc, andsys, probably from some earlier rescue attempt. These aren’t problematic, but you can clean them up at some point if you want. /dev/nvme0n1p1/EFI/fedorahas the shim and GRUB2 binaries we need.- BootOrder has the Windows entry (Boot0004) listed in first place, then “Fedora” (Boot0002), followed by two entries for your NVMe disks (Boot0008: HD(1,…) and Boot0009: HD(4,…)) and one for your USB stick (Boot000A); the “ubuntu” entry (Boot0000) is inactive (no * next to it).
- The “Fedora” entry references the ESP on a different disk: HD(5,GPT,38ff…) vs. HD(1,GPT,f9f1d979-…) for the Windows entry. I don’t know the contents of that ESP but it would explain why the Fedora entry is not working if the disk, the ESP on that disk, or the binaries are missing. Note how the HD(5,…) path is different from the HD(1,…) and HD(4,…) path we see in Boot0008 and Boot0009, so I am not sure where this entry is coming from.
- The fstab is exactly what I assumed, a single root subvolume mounted at
/, and nvme0n1p1 mounted at/boot/efi
Let’s fix this:
- Delete the “ubuntu” and “Fedora” entries:
$ efibootmgr # !double-check that "ubuntu" is "Boot0000"!
$ sudo efibootmgr --bootnum 0 --delete-bootnum
$ efibootmgr # !double-check that "Fedora" is "Boot0002"!
$ sudo efibootmgr --bootnum 2 --delete-bootnum
- Create a new entry for Fedora; --create should automatically add it to BootOrder in the first spot:
$ sudo efibootmgr --create --disk /dev/nvme0n1 --loader '\EFI\fedora\shimx64.efi' --label Fedora
- Check in the output of the previous command that BootOrder has a new entry before Windows’ Boot0004 and that this new entry references the same ESP as the Windows entry: HD(1,GPT,f9f1d979-…).
- Reboot and hopefully end up in your Fedora installation.
