Contribute
Register

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

Status
Not open for further replies.
Joined
Nov 16, 2014
Messages
131
Motherboard
Gigabyte Z97M-D3H (BIOS - F9b)
CPU
i7 4790K
Graphics
ASUS GTX 660 OC
Mac
  1. iMac
Mobile Phone
  1. iOS
I'm a little lost on how to identify a bogus entity. Testing
Code:
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 ?



IMG_2058.jpg
 
Joined
Aug 17, 2013
Messages
5
CPU
Intel Core i5 Skylake 6600
Graphics
GeForce GTX 970
Mac
  1. iMac
Mobile Phone
  1. iOS
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,
 
Joined
Nov 25, 2015
Messages
544
Motherboard
AsRock Fata1ity Z270 Gaming ITX
CPU
i5-7500
Graphics
WX5100
So if I don't fix this would it give me problems in the future?
 
Joined
Aug 17, 2013
Messages
5
CPU
Intel Core i5 Skylake 6600
Graphics
GeForce GTX 970
Mac
  1. iMac
Mobile Phone
  1. iOS
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.
 
Joined
Aug 23, 2012
Messages
51
Motherboard
Z170X-GAMING 5
CPU
I7 6700K
Graphics
EVGA GTX 980Ti ACX SC+
Mac
  1. MacBook Pro
Classic Mac
  1. 128K
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
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...
 
Joined
Jan 23, 2016
Messages
38
Motherboard
GA B150M D3H DDR4
CPU
i5 6500
Graphics
GTX 970
Mac
  1. iMac
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?

27ozpgu.jpg
 
Joined
Mar 3, 2014
Messages
1,335
Motherboard
Gigabyte Z390 I AORUS PRO WIFI
CPU
i9-9900K
Graphics
RX 580
Mac
  1. MacBook Air
Classic Mac
  1. Power Mac
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?
 
Last edited:
Joined
Dec 24, 2015
Messages
58
Motherboard
ASrock X99 Extreme4
CPU
i7-5820K
Graphics
GTX 960, R9 280X & RX 580
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
Classic Mac
  1. Apple
  2. Power Mac
Mobile Phone
  1. iOS
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.
 
Status
Not open for further replies.
Top