Trying to dual-boot Fedora 38 and Windows 10.
During the installation the error popped up:
"The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?
Failed to set new efi boot target. This is most likely a kernel or firmware bug."
There have been cases where there was so many entries that you could no longer add another entry. Some UEFI implmentation will aggressively remove boot entries which refers to non-existing files in the ESP. A lot does not do so.
This seems that boot0000, boot0001 and boot002 are accessing the ESP (efi file system) on partition 4, 5, 2 respectively. I would expect them to refer to the same partition.
It appears that you are trying to boot Fedora from the wrong place in the ESP it should be /boot/efi for Fedora to be able to boot using Grub2.
You also do have another Linux booting from \EFI\Boot\.
There are times when the flash ram that the Bios is residing on (usually two chips it seems) can fill up with items, not just boot entries and prevent the addition of another OS, even Windows. To clean it up you do need to mount the system. I haven’t tried this on a dual boot system, but had to do it on my Lenovo E530 when trying to switch it from Windows to Silverblue, or Guix.
In your case I would strongly recommend trying to reinstall Fedora with the installation media or if this is WS there should be the ability to select Repair an Installed System from the installation media at the beginning of the process.
Mine looks like this …
As you can see the mount point needed by Fedora is /boot/efi
Hi, WS (Work Station) so not the variants like Silverblue etc… Remnants of your previous install are showing what you posted above as I noted. The Live Image I believe is also able to provide recovery, but since I haven’t had to use it recently, I cannot say for certain. So If I was doing the install myself, and intending to dual boot Windows with Linux, I would mount my efi partition with possibly the live image and delete manually the EFI/Boot dir and create a /boot/efi dir. Then I would unmount it and restart the Fedora installation. If it fails at the same point, I would look at what the specific failure was (ie it has no space to install the bootloader, or the ESP is not laid out as Fedora expects.) To see the failure you will need to do it while in the installation (don’t answer the dialog and use a terminal), or mount the Fedora root of your install to see what is in /tmp since there should be a file holding the pertinent debug info. The reason it failed. Without the specific reason, no one here can give you any more detailed answers to help recover. Note that it is important that the ESP partition is mounted as /boot/efi for Fedora to boot correctly.
First, if you are not comfortable with what I suggested, please don’t start removing anything. So the anaconda.log file should have the results of the installation process to review. You’ll want to look at the part that shows writing the bootloader to see the actual error.
Sorry, but that is not correct. The file names here are relative to the mountpoint, that is, when the full path name is /boot/efi/EFI/fedora/shim.efi and the mount point is /boot/efi/ the file path name as seen from the UEFI firmware will be /EFI/fedora/shim.efi and as it wants backslashes, \EFI\fedora\shim.efi. Think of it, the UEFI firmware doesn’t care how you mount the ESP file system, or if you mount it at all.
