System Install .efiRC instead of .efi file grub2

Ask Fedora
,
1

I install fedora 41 on my acer aspire e15 as a only operating system. But the system wont boot after the installation using live media. I try to reinstall the grub2 according to grub2-bootloader , but nothing changed. After checking, i guess is due to the wrong version of efi file is installed. efiRC is installed instead of .efi file.

image
image955Ă—160 10.3 KB

The only option for me to boot the system is manually add a efi file at the uefi firmware which i dont think is a good idea. I am thinking to fixed the issues but dunno how. Anyone have idea on how to solve this correctly?

fyi, reinstall the fedore wont help as well. For now, manually adding a shim.efi file in the uefi firmware is the only way for me to boot into the system

2

This came up recently. See Fedora not detectable on boot options, but bootable through bootnext xxxx from live media - #9 by gnwiii

3

Thanks for point it out. But as i go through the discussion. I didnt see any useful solution. Does it means the problem is unsolvable for now?

4

You can use efibootmgr to remove a bad entry and replace it with the same entry after removing the trailing RC. What we don’t know is how these bad entries are being created, so the trailing RC may come back after being removed.

5

thanks, will try and see whether it works or not

6

unfortunately this didnt solve my problem, after removing the bad entry and reinstall the efi file, the file remain as efiRC after reboot. Currently the only way for me to enter the system is still manually adding the shrim64.efi file in the uefi firmware. Any other solution i can try?

7

Can you run efibootmgr -v? That will give some more information.

8

Result for efibootmgr -v is as below, boot 0000 is the efi file i add through uefi firmware which is the only way for me to boot into the fedora system on my acer aspire e15 laptop

efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* Fedora	PciRoot(0x0)/Pci(0x17,0x0)/Sata(0,0,0)/HD(1,GPT,852bf9c7-9064-4759-8509-7d334ba2519d,0x800,0x12c000)/\EFI\fedora\shimx64.efi4130312009ae
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 17 / 03 12 0a 00 00 00 00 00 00 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 c7 f9 2b 85 64 90 59 47 85 09 7d 33 4b a2 51 9d 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 41 30 31 20 09 ae
Boot0001* Unknown Device: 	HD(1,GPT,852bf9c7-9064-4759-8509-7d334ba2519d,0x800,0x12c000)/\EFI\fedora\shim.efiRC
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 c7 f9 2b 85 64 90 59 47 85 09 7d 33 4b a2 51 9d 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 52 43
Boot2001* EFI USB Device	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2002* EFI DVD/CDROM	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2003* EFI Network	RC
      dp: 7f ff 04 00
    data: 52 43
9

When entry Boot0000 works then keep on using it.

Looking at Boot0000 which is the currently booted entry we see

      dp: 02 01 0c 00 ...  00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

The last part is utf16 encoding of “\shimx64.efi” and “7f ff 04 00” is an end marker.

The next part is

    data: 41 30 31 20 09 ae

which looks like the continuation of “\shimx64.efi”, bit it really isn’t

In Boot0001: entry the part

    data: 52 43

is the “RC” text that looks like the the continuation of the file name shim.efi. And here again, “RC” is not part of the file name.

In conclusion, “RC” is not the problem and “4130312009ae” isn’t either.

It is possible that your UEFI Firmware can’t find the hard disk without the explicit hardware address specified as “PciRoot(0x0)/Pci(0x17,0x0)/Sata(0,0,0)/”.

1 Like
10

[quote=“Villy Kruse, post:9, topic:138308, username:vekruse”]
It is possible that your UEFI Firmware can’t find the hard disk without the explicit hardware address specified as “PciRoot(0x0)/Pci(0x17,0x0)/Sata(0,0,0)/”.
[/quote]

Installing Linux Mint on Aspire E15 has:

  • (10) Re-enable secure boot(BOOT) & select UEFI file as trusted(MAIN). Select HDD0, SSD0 or eMMC0, then , then , then grubx64.efi the UEFI file. Enter grubx64.efi in the space provided if selecting it doesn’t automatically enter it. Save BIOS setting and exit.

I’m guessing UEFI translates the selected entry to the PciRoot(0x0)/Pci(0x17,0x0)/Sata(0,0,0)/HD(1,GPT,<UUD>... format.

11

Normally, the boot entry doesn’t specify the hardware address, but only any disk having a partition UUID matching what is given in the boot entry.

You can specify the option --full-dev-path to create an entry including the full hardware address of the disk unit.