If I touched any of the "phantom" items in the boot priority list, the BIOS would freeze and I would have to start over. Resetting the CMOS, I was just able to boot Clover and fix the problem. My Z97 board certainly did degenerate into an unusable state. Since then, however, sleep is working properly. My current computer did not wake the display from sleep this morning, requiring a reset. I will post the results of my efforts when (if) I get them. When I have time (and buy a new cheap case to house it) I will try to resurrect it. I have put that aside for now, as I originally thought it was broken. It actually might be the solution to the freeze issue, but that other post was with my Gigabyte Z68 board.
#REMOVE DUPLICATE WINDOWS BOOTLOADER KEYGEN#
Trivial issues aside, I think that your statement that Clover Z97 systems may " degenerate to an unusable state" is an important one. In my case, I had a genuine Apple /EFI/BOOT folder (containing a "firmware" file), on one of my backup disks, and I promptly removed it.Ĭlover's "bcfg dump" lists all disks, even ones I have disabled under BIOS Boot Priority. On the EFI boot loader issue: all Disk Utility-formatted disks have an (empty) EFI partition, which, I guess, does not cause BIOS trouble, unless a bootloader resides there. I was hoping that this Clover bcfg procedure was the elusive fix for the freeze you mentioned in your other thread. Eventually (as happened before) it would "lock" the BIOS requiring me to go through the "reset CMOS" and then delete the extra entries. If I had kept everything connected on my system, it would have just kept adding another "UEFI OS(238475MB)" to the system every time I rebooted. Now the system is happy again and back to its stable state. This time there was no physical drive listed with bcfg boot dump, so I deleted all entries and restarted. After boot, here is what the relevant parts of the BIOS looked like:Īfter the first attempt to remove the offending items, it looked like this: Since it is about to be removed anyway when I get the chance, I disconnected the SATA and power connectors to the 2TB drive at the same time (it is blank at the moment anyway, and I do not need the storage space). So I removed the Samsung SSD from sata1, and put it back in its external case.
"UEFI OS(238475MB)" is not a physical disk. After messing about with this, I noticed that the entries that I had on the above screen shots did not all look like physical disks. I'll try to figure this out - the part about physical removal, I don't like at all. (The 2TB drive is about to be removed and the Samsung at sata1 normally sits in an external case now.) The other "boot" entry is a blank MS-DOS formatted 8GB flash drive that the BIOS thinks for some reason is bootable - this does go away when it is removed. The only real boot drive is my M.2 Samsung. Here is what my BIOS looked like after doing this. You shouldn't have a problem with either method.
Or, you could put the drives in an external USB 2.0 or 3.0 case with the boot loaders intact and connect them only when you need them. This probably means saving the data elsewhere, reformatting the disks and then restoring the data (probably other methods, but I am no expert on this). To make it stick, you need to remove the boot loaders from the other disks before you connect them back to your system. If you still have entries there other than your hard disk, then remove them. Then you need to look at your boot list in the BIOS. To make this work, you need to physically disconnect the drives, leaving only one drive with a boot loader connected to the system. You do not disable all of the internal hard drives except one in the BIOS. What am I doing wrong? How can one make this stick? retry "bcfg" in Clover, and the entries are back! you reboot, enter BIOS and sure enough they are disabled under Clover, you remove the entries, as per Anachronaut's advice you select "Disabled" under "Boot Priority" for all, except the boot disk
Can't claim expertise on this subject, but what I found is that:
0 kommentar(er)
