fknchino Posted August 6, 2015 Share Posted August 6, 2015 Not sure if this has been answered but I've got an annoying problem. Every so often I end up with a stack of "UEFI OS" options to click when I'm prompted to select my bootloader. I've noticed that for every restart it will create another and another, right up until my computer freezes, gets stuck at 'press del or f1' and doesn't even post. The worst part is that the only way to fix this is to do a CMOS reset, disconnect all the power cables that connect to my drives and pray for the best.Since I'm in the middle of another OSX installation I'm constantly restarting my PC and in turn getting these UEFI OS' options that don't even work when selected. It's giving me the sh*ts. 15 minutes ago, I tried booting Yosemite but it won't even show on boot selection and if I selected the dreaded UEFI OS, it would take me to a grey apple screen and an endless loading icon. Please help. Intel 4970k Devils Canyon (Haswell Refresh) Intel 4600 HD onboard graphics Asus H97m-e 1150 Mobo Asus Strix 970 Gpu G.Skill 16gb Ram Samsung 120gb 840 Evo Samsung 120gb 850 m.2 (Yosemite) Samsung 250gb 850 Pro (Windows 8.1) WD 4TB Green (Backup Drive) Link to comment Share on other sites More sharing options...
cq511npss1 Posted August 6, 2015 Share Posted August 6, 2015 Your firmware is scanning your drives and adding EFI boot loaders it finds e.g. /EFI/BOOT/BOOTX64.EFI to its boot manager If you can boot Clover, you should be able to launch the EFI shell. Try "help bcfg", you can list all your boot entries with "bcfg boot dump" and remove the ones you don't want with "bcfg boot rm X" where X is the order from dump. Make sure you are not mixing EFI and legacy bootloaders between OSs/drives. And you only need one EFI system partition per system where all your loaders and drivers can go. 3 Link to comment Share on other sites More sharing options...
fknchino Posted August 6, 2015 Author Share Posted August 6, 2015 Your firmware is scanning your drives and adding EFI boot loaders it finds e.g. /EFI/BOOT/BOOTX64.EFI to its boot manager If you can boot Clover, you should be able to launch the EFI shell. Try "help bcfg", you can list all your boot entries with "bcfg boot dump" and remove the ones you don't want with "bcfg boot rm X" where X is the order from dump. Make sure you are not mixing EFI and legacy bootloaders between OSs/drives. And you only need one EFI system partition per system where all your loaders and drivers can go. I'm a bit confused but I'll poke around in clover to see what I find. Since I'm planning to have both ML and Yosemite installed does that mean that I would have to boot from the one EFI shell? I would've thought with different config.plist and arguments it would be a nuisance Edit: Can you please explain in a little more detail? Sorry, I tried entering the "help bcfg" command but it wouldn't recognize it in the efi shell Link to comment Share on other sites More sharing options...
cq511npss1 Posted August 7, 2015 Share Posted August 7, 2015 For UEFI booting what you need is a single installation of Clover EFI to only one of your disks, installed for UEFI booting only, and Windows must also be installed from an EFI boot (not legacy/BIOS mode). The windows bootloader (BOOTMGFW.EFI) should be installed on the same ESP on same disk as Clover. Disable BIOS compatibility / legacy boot in your firmware settings to avoid any confusion. That way you have one volume your firmware is aware of that is bootable (it boots Clover) and Clover is then aware of your ML, Yosemite and Windows loaders (when it scans your disks) and you can choose from the GUI which to load. This is option B in the Clover wiki: clover-wiki.zetam.org/What-is-what www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ 2 Link to comment Share on other sites More sharing options...
tchitou Posted August 7, 2015 Share Posted August 7, 2015 For UEFI booting what you need is a single installation of Clover EFI to only one of your disks, installed for UEFI booting only, and Windows must also be installed from an EFI boot (not legacy/BIOS mode). The windows bootloader (BOOTMGFW.EFI) should be installed on the same ESP on same disk as Clover. Disable BIOS compatibility / legacy boot in your firmware settings to avoid any confusion. That way you have one volume your firmware is aware of that is bootable (it boots Clover) and Clover is then aware of your ML, Yosemite and Windows loaders (when it scans your disks) and you can choose from the GUI which to load. This is option B in the Clover wiki: clover-wiki.zetam.org/What-is-what www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ I happen to have an installed Clover EFI on the wrong disk (the partition is on the 2Tb drive I only use to make backups). I wanted to clone that EFI partition to my primary SSD EFI partition but as soon as I do that (or install clover on it), I can't boot my computer at all and can't even access the bios. Black screen.... Then the only way is to disconnect the SSD drive and boot on Windows. As soon as I format the EFI partition on the SSD, my system boots normaly.... but it's using that slow EFI partition of the not-so-safe backup disk.... Would you know what causes that? Thanks!!! Link to comment Share on other sites More sharing options...
cq511npss1 Posted August 9, 2015 Share Posted August 9, 2015 I happen to have an installed Clover EFI on the wrong disk (the partition is on the 2Tb drive I only use to make backups). I wanted to clone that EFI partition to my primary SSD EFI partition but as soon as I do that (or install clover on it), I can't boot my computer at all and can't even access the bios. Black screen.... Then the only way is to disconnect the SSD drive and boot on Windows. As soon as I format the EFI partition on the SSD, my system boots normaly.... but it's using that slow EFI partition of the not-so-safe backup disk.... Would you know what causes that? Thanks!!! Firmware-Firmware bootmanager->EFI executable Link to comment Share on other sites More sharing options...
tchitou Posted August 9, 2015 Share Posted August 9, 2015 I'm sorry, what firmware are you talking about? Thank you a lot! Link to comment Share on other sites More sharing options...
cq511npss1 Posted August 10, 2015 Share Posted August 10, 2015 The one on your GA-Z77-DS3H motherboard. This one: I can't boot my computer at all and can't even access the bios. Either your firmware's boot manager finds nothing to boot, or it boots something that isn't working (blank screen). Thanks. Link to comment Share on other sites More sharing options...
tarasis Posted September 15, 2015 Share Posted September 15, 2015 Ah, so I'm not alone. I ran into this problem last night as I used Clover for the first time to install El Cap on a spare HD, so I could set it up before upgrading my Yosemite (using Chimera/Chameleon) install. At a certain point (about 3am) I hit the issue that I could no longer boot and it hung on the "Press F2 or Del" to enter the bios (Mobo is Asus Z97-A). I tried reseting CMOS and such, but it had no effect, in the end I removed all but one SATA device and then I could boot again. By default the bios lists all the devices in the boot menu, however each time I rebooted the disk using Clover, a new "UEFI OS (disk size)" entry appeared in the Boot Menu, till the point were the only option was 12 "UEFI OS (disk size)" entries. The only way to get the original list back is remove the disk with Clover installed. Link to comment Share on other sites More sharing options...
tarasis Posted September 17, 2015 Share Posted September 17, 2015 Not sure if this has been answered but I've got an annoying problem. Every so often I end up with a stack of "UEFI OS" options to click when I'm prompted to select my bootloader. I've noticed that for every restart it will create another and another, right up until my computer freezes, gets stuck at 'press del or f1' and doesn't even post. The worst part is that the only way to fix this is to do a CMOS reset, disconnect all the power cables that connect to my drives and pray for the best. Since I'm in the middle of another OSX installation I'm constantly restarting my PC and in turn getting these UEFI OS' options that don't even work when selected. It's giving me the sh*ts. 15 minutes ago, I tried booting Yosemite but it won't even show on boot selection and if I selected the dreaded UEFI OS, it would take me to a grey apple screen and an endless loading icon. Please help. Did you ever find a solution to the Boot list filling up? It happened to me again this morning (only became a problem after I installed Clover, till then I'd been using OS X in Legacy, likewise Windows 7 and now Windows 10). Link to comment Share on other sites More sharing options...
qqcapcom Posted October 7, 2017 Share Posted October 7, 2017 Did you ever find a solution to the Boot list filling up? It happened to me again this morning (only became a problem after I installed Clover, till then I'd been using OS X in Legacy, likewise Windows 7 and now Windows 10). http://www.insanelymac.com/forum/topic/309280-too-many-random-boot-options-available-in-bios-boot-options-for-gigabyte-z170x-ud5-after-installation-of-elcapitan-10111/ Link to comment Share on other sites More sharing options...
westsurf Posted August 4, 2018 Share Posted August 4, 2018 In my Clover boot options, despite a completed Majave installation, I now have a various new boot options that include names including “preboot” ... will this method remove those leftover install options? Link to comment Share on other sites More sharing options...
bronxteck Posted August 4, 2018 Share Posted August 4, 2018 just add the names you dont want to see in GUI/hide volumes section of config like the words preboot, recovery, legacy etc... use cloverconfigurator app if you dont want to manually edit config Link to comment Share on other sites More sharing options...
Recommended Posts