Jump to content
fknchino

Getting very frustrated. Disappearing Boot options. UEFI OS?

13 posts in this topic

Recommended Posts

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)

Share this post


Link to post
Share on other sites
Advertisement

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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/

Share this post


Link to post
Share on other sites

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!!!

Share this post


Link to post
Share on other sites

 

 

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

 

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).

Share this post


Link to post
Share on other sites

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/

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By macinsane
      Update: Now running Mojave! Thanks to mojave2core! Yeah   Still using C2D in 2019!
      Inserted a nice and cheap GT710 that is not relying on nVidias Webdrivers and runs OOB under Mojave.
       
      Nice, seeing High Sierra running on this old but capable system! It rocks with a new ASUS GT1030
       
      Config:
      Gigabyte EP43-DS3L
      Core2Quad Q9300
      6 GB DDR2 RAM
      Asus GT1030 2GB
      Sandisk SSD 128GB
      TP-Link AC1200 Wifi USB
      Inateck KT4006 USB 3.0 PCIe (No boot)
       
      SMBIOS: iMac14,1
      Clover: 4297  4360
       
      A good deal of DSDT editing was necessary to get this machine to boot High Sierra but finally it works flawlessly, even sleep and wake!
      You NEED to have the DSDT put in place for installation because otherwise macOS doesn't recognize the SATA ports.
      There are a few important BIOS settings: SATA hast to be set to AHCI and "native" and HPET has to be run "64-bit", I'd recommend to disable IDE and the serial and parallel port.
      For the GT1030 nVidia Webdrivers are needed, have to boot with nv_disable=1 until you have them installed.
      You have to install Clover in legacy mode because this old fella does not support UEFI.
       
      Only downside: The so often recommended Inateck USB-card isn't recognized by BIOS, so you cannot boot from it. It works perfectly within macOS though, have the ac-Wifi connected to it.
      config.plist.zip
      DSDT.aml.zip
    • By Surfman
      Ciao a tutti.
      dopo aver installato High Sierra il pc non può avviarsi dall'SSD mostrandomi la schermata nera che dice di scegliere il boot. facendo partire il pc con l'USB inserita, da dove ho installato il tutto, mi viene mostrata schermata di scelta dove posso effettivamente fare partire osx appena installato dal ssd ma con una lentezza mostruosa!. se provo con la chiavetta scollegata stessa schermata nera con la scelta del boot. inutile aggiungere che ho cercato di cambiare l'ordine di avvio dal BIOS, aggiornato il BIOS, ma senza successo. l'ssd funziona perché dopo ho installato da questo stesso anche linux o windows tranquillamente
      cosa posso fare? grazie a tutti

      MOBO: Gigabyte GA-B250M-DS3H
      CPU intel i5
      GPU NVIDIA MSI N750 Ti TF 2GD5 / OC  

    • By fagner_sbs
      Hello! Sorry for the way of writing in English, I'm using google translator.
      I am several days trying to make my Mojave hakintosh work perfectly. However, I have reached a point where I can no longer proceed without help.
      Almost all hardawares were installed and recognized (using the clover). However, still have a panic kernel (capture attached). Every time, when connecting the MAC it restarts 2 or 3 times to be able to show the dekstop and to function normal. I also think that having problem with video graphics sometimes freezes the entire display system if video appears on a web page.
      I've attached a file with used files: clover, bios capture, complete hardware information, error capture(https://1drv.ms/u/s!AvhW45_HBY8zgfsySZPWZ-SZXFiMfA). Can someone help me?
       
      Notebook:
      Mobile DualCore Intel Core i7-3537U, 2000 MHz (20 x 100), 4 threads
      Asus K46CB Series Notebook
      Intel Panther Point HM76, Intel Ivy Bridge-MB
      16269 MB  (DDR3 SDRAM)
      BIOS AMI (05/17/2013)
      Vídeo:
      Intel(R) HD Graphics 4000                         10.18.10.4358
      NVIDIA GeForce GT 740M                            25.21.14.1634
    • By MikixIT
      Salve ragazzi, io ho un pc con sopra Windows e Sierra(che ho installato grazie a questo fantastico forum)
      Recenetemte ho avuto problemi con gli aggiornamenti windows 10(Che uso urgentemente per lavoro)
      E girando per i forum di Windows, ho capito che il problema era dato da un "interferenza" di clover di quando windows faceva i soliti riavvi quando aggiorna.
       
      Io volevo chiedere se era possibile selezionare MOMENTANAMENTE Windows come avvio primario e quindi non su clover, una sorta di bypassare clover
      e quindi il pc avvia o riavvia e va subito ad avviare windows senza passare da clover, in modo da fare aggiornare Windows e poi "RIATTIVARE" Clover esattamente come prima
      Esiste un modo di fare ciò senza perdere clover o dati etc? 
      Grazie se risponderete, buona serata ragazzi!
×