rEFInd adds boot entries for non existent OSes/Loaders

[Noorez Kassam]

I have installed rEFInd on a machine that only contains centos. The boot partition is on an xfs filesystem. To get the kernel stub loader to be found, I copied the xfs driver.

This allowed the kernel (vmlinuz) to be found, however, it also mysteriously caused the MacOSX and a few windows loaders to be added to the boot menu. None of which obviously work since the actual efi files don't exist (\System\CoreService..).

Is this a potential bug?

[Roderick W. Smith]

It could be a rEFInd bug, but it could also be that the files do exist somewhere on your computer -- perhaps even in another partition. Check the complete descriptions on the rEFInd menu for the non-functional entries; for most, they should provide complete paths and volume names or descriptions. (OS X is an exception; but its boot loader is in /System/Library/CoreServices/boot.efi, so you can look for that file.)

I haven't been doing as much with Fedora or CentOS recently as in the past, but I'm pretty sure that they install now GRUB to the OS X boot loader name on a dedicated HFS+ partition, at least on Macs. Thus, if you're using a Mac, or if there's a bug in the CentOS installer code that's causing it to think it's on a Mac, it might be putting GRUB there and rEFInd would then detect GRUB as OS X.

You can filter such entries with dont_scan_files, dont_scan_dirs, or dont_scan_volumes; or you can delete the unwanted boot loader files, if you're sure you never want to use them.