Why is rEFInd listed in efibootmgr?

After the GRUB Disaster, I am seriously considering switching to rEFInd, but I haven’t yet.

This is a clean install of the Artemis ISO. No more booting issues :smiley:

Why do these entries appear in the efibootmgr? Is it safe to delete the entries? Which file am I changing or do I have to use efibootmgr -o ?

Boot0005* Fedora HD(1,GPT,a37eab10-2ea8-4307-b501-6b080e8b0c13,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)

Boot0003* rEFInd Boot Manager HD(1,GPT,aaf28d10-ec03-7c41-b714-f2fd97eda185,0x800,0x96000)/File(\EFI\refind\refind_x64.efi)

The strange part is I have never downloaded, installed or booted from rEFInd.
I booted the EndeavourOS Artemis ISO through Ventoy, and there is a Fedora ISO on the USB key, So that may explain the Boot0005 entry, but it does not explain Boot0003.

It is Calamares BTRFS default install. /etc/fstab

Which file needs the boot order to be changed?

UUID=7200-CA65 /boot/efi vfat defaults,noatime 0 2
UUID=068e39a0-d042-44a0-a576-43603368da7e / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=068e39a0-d042-44a0-a576-43603368da7e /home btrfs subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=068e39a0-d042-44a0-a576-43603368da7e /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=068e39a0-d042-44a0-a576-43603368da7e /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=3cf15e8d-b58b-4fde-9523-2709b9b223c5 swap swap defaults 0 0

Here is the efibootmgr for completeness.

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,2001,2002,2003
Boot0002* HDD: Hitachi HTS547550A9E384	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,831052f6-afea-9641-bad5-499092120021,0x1000,0x96000)RC
Boot0003* rEFInd Boot Manager	HD(1,GPT,aaf28d10-ec03-7c41-b714-f2fd97eda185,0x800,0x96000)/File(\EFI\refind\refind_x64.efi)
Boot0004* endeavouros-8732	HD(1,GPT,11d41e04-780c-7041-8a47-74385c11ac8e,0x1000,0x96000)/File(\EFI\endeavouros-8732\grubx64.efi)
Boot0005* Fedora	HD(1,GPT,a37eab10-2ea8-4307-b501-6b080e8b0c13,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot0006* endeavouros-2573	HD(1,GPT,831052f6-afea-9641-bad5-499092120021,0x1000,0x96000)/File(\EFI\endeavouros-2573\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
│ vfat FAT32 NO_LABEL
│ 7200-CA65 298.8M 0% /boot/efi
├─sda2
│ btrfs 068e39a0-d042-44a0-a576-43603368da7e 424G 7% /home
│ /var/cache
│ /var/log
│ /
└─sda3
swap 1 swap 3cf15e8d-b58b-4fde-9523-2709b9b223c5 [SWAP]

EFI entries generally don’t get cleaned up. So that is a list of things that ever been installed in your EFI.

@HMS_Endeavour
When you install rEFInd it adds that entry to UEFI. Entries in UEFI don’t necessarily get removed just because you uninstalled it.

2 Likes

you can remove not needed EFI entries if they bother you.

for example you need to remove the rEFInd entry

Boot0003* rEFInd Boot Manager	HD(1,GPT,aaf28d10-ec03-7c41-b714-f2fd97eda185,0x800,0x96000)/File(\EFI\refind\refind_x64.efi)

it has boot number 0003

than you can remove it with the following command

sudo efibootmgr -b 0003 -B
2 Likes

A longer explanation on how to manage EFI boot entries manually with efibootmgr is here:

1 Like

But will that also physically remove the corresponding directory from the partition?

as I have read about it, this deletes the entry in the nvram. nvram is not in a partition, it is a component in the computer, in which data is stored e.g. the boot entries.

2 Likes

So then you also have to manually delete the corresponding directory

It’s an entry in NVRAM. It doesn’t get removed always from the entries in UEFI just because you uninstalled the package.

1 Like

you have to be careful that you delete the right entry. So only delete entries from deleted OS’s

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.