Contribute
Register

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

Status
Not open for further replies.
I had the same problem on a Hackintosh with a Gigabyte H110M-S2HP. The setup on this Hackintosh is extremely simple, only one SSD with only macOS Sierra and matching recovery partition. And yet, I was still getting new entries.

After spending a few hours on this, trying a lot of the suggestions from this and other threads, the solution turned out to be relatively straight-forward.
  1. Boot into Clover.
  2. In Clover Boot Options choose Add Clover boot options for all entries.
  3. From Clover enter the UEFI shell and remove all unneeded options using bcfg boot rm XX as described elsewhere in this thread. (See below for details on which option to keep.)
  4. Boot into macOS.
  5. Mount the EFI partition.
  6. Rename the folder EFI/BOOT into EFI/BOOT-XXX. Of course, it is also possible to delete this folder rather than renaming it. The important thing is that the BIOS can't find anything at \EFI\BOOT\BOOTX64.efi.
  7. Reboot.
Regarding step 3, I only kept option 00, which is the one that was created by Clover. Option 04 did reappear later but that seems harmless as it only gets created once.

IMG_0474.jpg


In my case it was not necessary to disable scanning in Clover as suggested elsewhere. It was also unnecessary to create a custom boot entry in Clover's config.

It is likely that if I ever reset the CMOS then the computer won't be able to boot from the SSD because on its own the BIOS won't find the Clover bootloader, which is at \EFI\CLOVER\CLOVERX64.efi, and the one it would find, ie. \EFI\BOOT\BOOTX64.efi, isn't there anymore. In that case I'll have to boot from a USB stick once and use Clover to create the boot options from there.

Hope this helps.
 
Last edited:
This might sound completelly unnecessary but I am completely noob and I dont wanna fak something up.

Can i instead of pulling out drives just disable them in bios?

What could go wrong if I dont pull out drive with data? Right now I am in Efi shell and i disabled drive with data in Bios.
 
Last edited:
bruno03 said:
This might sound completelly unnecessary but I am completely noob and I dont wanna fak something up.

Can i instead of pulling out drives just disable them in bios?

What could go wrong if I dont pull out drive with data? Right now I am in Efi shell and i disabled drive with data in Bios.
Click to expand...
NO.
You cannot pull a running drive unless hot swap is supported and turned on in the bios, and still it is not a good idea, or practice.
Disabling the drives in the bios does not cure this ridiculous problem. Any time a drive is connected to the machine the offending drive creating the extra bios ghost entries adds another entry. It is not other drives that are the problem for extra creation, it is typically the Mac boot drive with the Clover bootloader that has extra entries. Even connection of a Iphone through USB will add the entries unless one of the many fix options are used to either stop the entries or manually remove them, periodically as they are created.
 
Ok it might not be completelly unnecessary. So how to exit efi shell before bcfg boot dump?
 
I did "exit". Pulled off drive. And re again. Now its fixed. I am noob at this and dont understand half of shiit. So when you come up with answers that are not completly understandable like posts before I get picky.
 
bruno03 said:
I did "exit". Pulled off drive. And re again. Now its fixed. I am noob at this and dont understand half of shiit. So when you come up with answers that are not completly understandable like posts before I get picky.
Click to expand...

1. I did not write the post with the answer you are quoting above, but if you do not understand terminal don't enter it. You can cause more damage than benefit. Typing exit, and then closing Terminal is the documented way of closing a session in Terminal.
2. The problem here is a poorly written bios but a number of Bios Manufacturers bios code writers for not just Gigabyte boards and it only effects Skylake, at this point.
3. The problem does not occur unless you use the Clover boot-workloader and have multiple drives attached to an affected machine. Newer versions of the bios that support Kaby Lake for this boards do not have the problem. The problem cannot be reproduced on a Windows only machine.
4. It is not fixed, it will come back. Unless you renamed the folder. Further, as soon as you move to another permutation of the OS, you will not be able to boot, unless you make another fix. Read carefully.
5. It really means nothing to me, that you will not take the time to read everything and understand and process it. This is how this forum works, and I have been long time, and I am not a moderator. I do not love how questions are resolved here, but this is way it is. I had to learn the hard way. Your expected to learn, by reading, making sure no one has asked the same question previously. or do not expect any answers Noob or not. Answers to new problems are developed over time, as any time hardware that was not designed to work vanilla is used with a new OS version, new problems will arise, with every change. The Clover boot-loader is constantly changing, to accommodate hardware changes and OS changes. Tony-mac's current tool to install Clover uses the version of Clover that the tool has coded into it. Each tool version is written for a specific OS version. The current version of Clover is 2.4k revision 4097 which I believe was released today. I do not think the current T.M. tool (Multibeast) has the latest version embeded. Clover can be installed clean from its own installer, from Multibeast, and updated from Clover Configurator. It is recommended that the Configurator be updated before updating a non current Clover version.
 
6. Further,
when the Apple new file system APFS is released to the public, more problems will be created.
 
OK, so I did the steps (OP) above on my Sierra / Win 10 dual boot. Have done this previously El Capitan and it was fine, but this time I think I accidentally deleted the Windows drive entry. Any way to restore it or do I have to start installing both OSs from scratch?

The windows drive and files are there in OS X and clover, but is not available as a boot drive in BIOS. Any pointers are appreciated. I have one physical SSDs each for the respective OS (i.e. two SSDs).
 
McEntosh said:
OK, so I did the steps (OP) above on my Sierra / Win 10 dual boot. Have done this previously El Capitan and it was fine, but this time I think I accidentally deleted the Windows drive entry. Any way to restore it or do I have to start installing both OSs from scratch?

The windows drive and files are there in OS X and clover, but is not available as a boot drive in BIOS. Any pointers are appreciated. I have one physical SSDs each for the respective OS (i.e. two SSDs).
Click to expand...
EasyUEFI can add entries from the Windows side. You can boot from Windows independently of Clover and install Easy UEFI as a trial and add the entry you lost. Someone else will have to answer how to do this from Clover.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top