Contribute
Register

[Solved] Extra boot option entires

Status
Not open for further replies.
Joined
Oct 12, 2017
Messages
93
Motherboard
GA-Z170N-WIFI
CPU
Core i7 6700k
Graphics
EVGA NVIDIA GeForce GTX 960
I was curious about what BIOS version I have and then I clicked on the peripherals tab... and my jaw dropped..
WHAT THE HECK!?

I have 81 boot options all pointing to the same 2 drives
every time I boot I get new partitions...

Please somebody explain what to do with this monstrosity?
how do I first of all, remove all of these boot options and secondly, prevent this in the future

IMG_3709.JPG
 
Joined
Oct 12, 2017
Messages
93
Motherboard
GA-Z170N-WIFI
CPU
Core i7 6700k
Graphics
EVGA NVIDIA GeForce GTX 960

I did exactly by the book and that makes no sense at all...
This is what I have left after looking through them all and none of them was a physical drive boot option,
IMG_3712.JPG
But regardless, his guide only has recommendations but there is no actual solution there... they keep showing up after I remove them There must be some thing else to this problem, I can't keep removing them in the UEFI shell forever.

Maybe it has something to do wth clover scanning for entries? maybe I need to turn off the LEAGCY option?
 

UtterDisbelief

Moderator
Joined
Feb 13, 2012
Messages
6,781
Motherboard
Gigabyte Z490i Aorus Ultra - OC 0.6.8
CPU
i5-10600K
Graphics
GT 1030
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. eMac
  2. iBook
Mobile Phone
  1. Android
I did exactly by the book and that makes no sense at all...
This is what I have left after looking through them all and none of them was a physical drive boot option,
View attachment 285304
But regardless, his guide only has recommendations but there is no actual solution there... they keep showing up after I remove them There must be some thing else to this problem, I can't keep removing them in the UEFI shell forever.

Maybe it has something to do wth clover scanning for entries? maybe I need to turn off the LEAGCY option?

Hi there,

Nope, no need to mess with Clover. To get started the easiest way to clear so many entries is just to refresh your BIOS with the current version etc. True, that has it's own risks but is one quick way to "reset the clock".

This problem was completely solved by Gigabyte with a quite big step change in BIOS's. They went from the peaceful Grey and White/Yellow in your screen-grab, to a stark Black and Red. With the jump the duplicate boot entry problem has gone. According to Gigabyte you can't reverse out of this BIOS upgrade like you could for previous ones, however this can be done quite easily using a flash utility if you need to (I tried it once but it was a bit buggy so can't recommend this).

Anyway, if you check the lists for BIOS's on Gigabyte's web-site you'll see what I mean. The new versions start with F20 (check which version your motherboard is - I'm guessing version 1.0 because v2.0 came with F20 as standard I think).

:)
 
Joined
Jul 24, 2015
Messages
2,265
Motherboard
MSI H81i
CPU
i5-4570
Graphics
RX 580
I did exactly by the book and that makes no sense at all...
This is what I have left after looking through them all and none of them was a physical drive boot option,
View attachment 285304
But regardless, his guide only has recommendations but there is no actual solution there... they keep showing up after I remove them There must be some thing else to this problem, I can't keep removing them in the UEFI shell forever.

Maybe it has something to do wth clover scanning for entries? maybe I need to turn off the LEAGCY option?
Your firmware is buggy. It is erroneously saving boot options for the /efi/boot/bootx64.efi file on those drives. You can use Easy UEFI for windows to remove the entries quickly and easily, add a proper entry to Clover at /efi/clover/cloverx64.efi and finally delete the file at boot/bootx64.efi to hopefully prevent these entries returning.
 
Joined
Oct 12, 2017
Messages
93
Motherboard
GA-Z170N-WIFI
CPU
Core i7 6700k
Graphics
EVGA NVIDIA GeForce GTX 960
Hi there,

Nope, no need to mess with Clover. To get started the easiest way to clear so many entries is just to refresh your BIOS with the current version etc. True, that has it's own risks but is one quick way to "reset the clock".

This problem was completely solved by Gigabyte with a quite big step change in BIOS's. They went from the peaceful Grey and White/Yellow in your screen-grab, to a stark Black and Red. With the jump the duplicate boot entry problem has gone. According to Gigabyte you can't reverse out of this BIOS upgrade like you could for previous ones, however this can be done quite easily using a flash utility if you need to (I tried it once but it was a bit buggy so can't recommend this).

Anyway, if you check the lists for BIOS's on Gigabyte's web-site you'll see what I mean. The new versions start with F20 (check which version your motherboard is - I'm guessing version 1.0 because v2.0 came with F20 as standard I think).

:)

Yes I can confirm the BIOS look black and red and cool and stuff lol.
 
Last edited:
Joined
Oct 12, 2017
Messages
93
Motherboard
GA-Z170N-WIFI
CPU
Core i7 6700k
Graphics
EVGA NVIDIA GeForce GTX 960
Your firmware is buggy. It is erroneously saving boot options for the /efi/boot/bootx64.efi file on those drives. You can use Easy UEFI for windows to remove the entries quickly and easily, add a proper entry to Clover at /efi/clover/cloverx64.efi and finally delete the file at boot/bootx64.efi to hopefully prevent these entries returning.

I don't have any access to Windows mate, is there any other way?

By the way the BIOS update to F20d seems like it solved the issue visually, but now when I generate a log in clover configurator I get this:
I now have only 1 m.2 SSD instilled in the system, no other HDDs or SSDs

Code:
0:916  0:013  === [ ScanVolumes ] =======================================
0:916  0:000  Found 7 volumes with blockIO
0:916  0:000  - [00]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)
0:917  0:000  - [01]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,3A716BF3-3D55-4707-A01F-D5B10FC70F8B,0x28,0x64000)
0:918  0:000          Result of bootcode detection: bootable unknown (legacy)
0:919  0:001          This is SelfVolume !!
0:919  0:000  - [02]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7F9F77F2-2F73-436D-92A0-B998037D4A77,0x64028,0xDF30B60)
0:920  0:000          Result of bootcode detection: bootable unknown (legacy)
0:920  0:000  - [03]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7F9F77F2-2F73-436D-92A0-B998037D4A77,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,0E7EF20B9F7DAF4389970B17655FCAB1)
0:920  0:000  - [04]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7F9F77F2-2F73-436D-92A0-B998037D4A77,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,B495AE36CF58DF45B94F28D3DE86D766)
0:920  0:000  - [05]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7F9F77F2-2F73-436D-92A0-B998037D4A77,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,1499677AE2BCE141B2CE98E22CA287E9)
0:920  0:000  - [06]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,7F9F77F2-2F73-436D-92A0-B998037D4A77,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,099F406EB75A244194C9E614C828F88F)

While when I go to Shell and type bcfg boot dump I get this:

IMG_3731.JPG

which seems to be correct except this BBS Hard Drive thing, what is that?
And why does clover configurator tell me I have 7 boot entires in the boot.log? I don't see them in Shell or in BIOS.
 
Last edited:
Joined
Jul 24, 2015
Messages
2,265
Motherboard
MSI H81i
CPU
i5-4570
Graphics
RX 580
which seems to be correct except this BBS Hard Drive thing, what is that?
BIOS Boot Specification EFI device path, used by CSM to retrieve the data for that hard drive for legacy boot on that disk.
And why does clover configurator tell me I have 7 boot entires in the boot.log? I don't see them in Shell or in BIOS.
It is scanning the partitions, Clover boot entries are not directly-derived from the firmware boot entries (in your case you have no real entries in firmware, only the fallback UEFI path /efi/boot/boot.efi path is present, + the legacy BBS path), Clover actively searches for known Windows, macOS loader paths etc.
 
Joined
Oct 12, 2017
Messages
93
Motherboard
GA-Z170N-WIFI
CPU
Core i7 6700k
Graphics
EVGA NVIDIA GeForce GTX 960
BIOS Boot Specification EFI device path, used by CSM to retrieve the data for that hard drive for legacy boot on that disk.It is scanning the partitions, Clover boot entries are not directly-derived from the firmware boot entries (in your case you have no real entries in firmware, only the fallback UEFI path /efi/boot/boot.efi path is present, + the legacy BBS path), Clover actively searches for known Windows, macOS loader paths etc.

I have no real entires in my firmware? is that an issue that needs to be fixed?
And what is the legacy BBS path used for?

Excuse my noobnes, im very much learning at this stage.
I just finally figured out how to properly configure my memory in SMBIOS,
ive had it show 4 slots, 2 empty from the very start of my CustoMac build until now for at least like 6 versions of MacOS
The documentation is not noob friendly and very very hard to read, there are no simple explanations so im asking a lot of questions that seem very basic.
 
Joined
Jul 24, 2015
Messages
2,265
Motherboard
MSI H81i
CPU
i5-4570
Graphics
RX 580
I have no real entires in my firmware? is that an issue that needs to be fixed?
And what is the legacy BBS path used for?

Excuse my noobnes, im very much learning at this stage.
I just finally figured out how to properly configure my memory in SMBIOS,
ive had it show 4 slots, 2 empty from the very start of my CustoMac build until now for at least like 6 versions of MacOS
The documentation is not noob friendly and very very hard to read, there are no simple explanations so im asking a lot of questions that seem very basic.
The BBS path is used by your firmware for booting the old MBR way, you can ignore it. And you can add a permanent entry for Clover in EFI shell
Code:
fs0:
cd efi
cd clover
bcfg boot add 0 cloverx64.efi "Clover"
Then in your firmware options screens you will see "Clover" in the boot order interface rather than UEFI OS:SomeHardDrive, which is auto-generated e.g. for removable devices
 
Last edited:
Status
Not open for further replies.
Top