I’m trying to install Rocky Linux 8.10 on my PC alongside Windows 10, but I’ve encountered a problem during the installation process. I want to have both operating systems on my machine, and I also want to keep my data on a separate partition to avoid losing it in case of any issues with the operating system.
The installation seemed to be going well until I received the following error:
“Failed to set new EFI boot target. This is most likely a kernel or firmware bug.”
This occurred right after the manual partitioning setup. Here are the details of my configuration:
/home partition: 424.55 GiB (XFS)
Root / partition:70 GiB (XFS)
/boot/efi partition:600 MiB (FAT32)
Swap partition: 3.86 GiB
The system is in UEFI mode, and the EFI partition is correctly formatted as FAT32.
Secure Boot is disabled.
I’ve tried the following without success:
Verified that the EFI partition is properly configured and has enough free space.
Confirmed that my system is in UEFI mode and not in Legacy mode.
Attempted to disable Secure Boot in the BIOS/UEFI settings.
I’m not sure how to proceed from here. Has anyone faced this issue before or have any suggestions on how to resolve it? Any guidance would be greatly appreciated.
I think you are missing the /boot partition. Here’s a snippet from RHEL docs:
/boot partition - recommended size at least 1 GiB
The partition mounted on /boot contains the operating system kernel, which allows your system to boot Red Hat Enterprise Linux 8, along with files used during the bootstrap process. Due to the limitations of most firmwares, creating a small partition to hold these is recommended. In most scenarios, a 1 GiB boot partition is adequate. Unlike other mount points, using an LVM volume for /boot is not possible - /boot must be located on a separate disk partition.
UEFI loads GRUB from ESP (the EFI partition). GRUB loads kernel. Kernel mounts root.
For these to happen, the GRUB has to be able to read the kernel from a filesystem.
Firmware should not be an issue since it (UEFI) reads the ESP, not /boot.
GRUB cannot load from LVM. If the / that contains kernel in directory ‘boot’ is on LVM LV, then that fails.
However, “Failed to set new EFI boot target” does not sound like “you did not create ok place for kernel” error. It sounds like “writing to UEFI … failed”. During installation an entry is added to motherboard’s flash and it is made the default boot entry. That entry has the info to load Rcoky’s GRUB from ESP.