[GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

[VirtualRecess]

I'm a little lost on how to identify a bogus entity. Testing

bcfg boot dump

I get the results seen in the pic below. I've got Three PciRoot's and Two HD entries. The Three PciRoots are physical disks, just not bootable as they are storage drives for OS X and Windows 7. The two HD entries are my Elcapitan install and Windows 7 Pro UFEI install.

Should i be removing the three storage drives from the boot dump ?

 

[leboucher10]

I've been studying this thread for a couple of days, and this one looks like the most promising. I'm about to give it a shot, but I wanted to know if there is anything else I should do prior to doing it, or anything I should do after. Does this method erase all the erroneous versions of my drive, or does it just prevent new erroneous ones from being created?

Hi Beestar,

With this solution you can delete all extra boot entries and after prevent the creation of new ones. Nothing to do more: just follow the protocol explain before.

Best,

 

[aztlan78]

So if I don't fix this would it give me problems in the future?

 

[leboucher10]

So if I don't fix this would it give me problems in the future?

Yes. At one moment you will have many boot entries in your motherboard and you can't start anymore.

 

[muffie8]

Hi Beestar,

With this solution you can delete all extra boot entries and after prevent the creation of new ones. Nothing to do more: just follow the protocol explain before.

Best,

Of course, assuming you have an UEFI installed version of Windows.
My windows was installed as legacy, so, I just can't run EasyUEFI...

 

[Roberbond]

So if I don't fix this would it give me problems in the future?

with the solution by tbjem0013 above you will fix it forever.

 

[Dinho22]

Anyone having the same problem in the motherboard BIOS?

I have a mobo GA B150M D3H DDR4 and i5 6500

- It seems that you walk to create new bot option alone. Now in October 22, i have a #53 "Boot Option". Time ago my computer crashed (i do not know if bacause of this). But I had to reset the BIOS and reinstall the El Capitan.
Has anyone heard of this?

 

[Rallyfan13]

I'm having the same problem but I've not seen anyone address it. Looking forward to an answer.

 

[wstrohm]

I have tried to follow the procedures for getting rid of the extra boot options, but have found that the Clover Shell format prohibits me from doing the steps. The "map" function lists "FS" numbers but not boot options. The "vol" function shows which FS numbers are which targets, but not boot options. The "bcfg boot dump" function lists boot options but not "FS" numbers, and is so confusing that I cannot figure out which boot options to delete. I can do the "bcfg boot add" and it works, but since I cannot know which "FS" number corresponds to which boot option, I can't complete the procedure. This is a problem with the Clover Shell windows which I cannot solve. Any help here?

 

[Jeckell]

I've been using this procedure for about a week and a half. I keep coming home from work and finding the machine back in Clover. These extra boot entries keep repopulating, and I keep deleting them. I reflashed the board and installed the latest update, but it keeps happening. I'm not an expert on the crash logs, but I don't see anything that tells me why the machine dumped out of the OS, and it's not frozen like I've seen with kernel panics on my real Macs.

I only have a single SATA SSD, no other drives, and the Recovery partition is the only other partition on the SSD.

This machine previously ran Ubuntu Linux, but every trace of that should've been wiped when I flashed the bios and completely formatted the drive during the Mac OS Sierra installation.

I'd really love your thoughts on how to make this better.