Jump to content
7 posts in this topic

Recommended Posts

I'm really not sure what the correct forum for this is, since it's not really a post-installation problem exactly, though I have successfully set up my hackintosh.

 

Quite simply the problem is that yesterday I booted my machine just fine without any problems at all, and now today my motherboard is refusing to recognise my system and secondary drives as being UEFI boot capable.

 

My motherboard's a Gigabyte GAQ87TN, and normally in the BIOS menu I can see entries for my drives looking something like:

P5 Samsung 840 EVO

Windows Boot Manager on P5 Samsung 840 EVO

UEFI: P5 Samsung 840 EVO

 

And the same again for my OCZ Vertex 2 SSD which I use mainly for running games from, but figured I should clone a spare EFI partition to for emergencies, but a fat lot of good it's done me.

 

 

I haven't changed anything about my configuration since yesterday, and like I say, it was running perfectly. Now suddenly I try to start up and neither drive is recognised as UEFI, so I'm unable to boot into Clover. I've managed to startup using another EFI copy I made for my Yosemite install USB (which I've kept around for situations like this) and I can boot my system just fine in this way, albeit with Clover taking a lot longer to load from the USB stick, but I don't want to rely on it as it's supposed to be for emergencies only.

 

However, nothing I've tried will fix the two internal drives; I've tried wiping the OCZ Vertex 2 entirely since it only contains games and isn't very big (so is easy to backup and restore), before re-installing Clover. I've also tried cloning the working Clover EFI from my USB stick onto the drive's EFI partition, but this doesn't seem to work.

 

I did manage to get my OCZ Vertex 2 to be recognised briefly using a vanilla Clover installation (install Clover with UEFI boot settings plus the mandatory drivers such as HFSPlus.efi) and while it boots into the Clover screen, it only reports the root device UUID then stops. I've tried recreating this but with the USB stick's Clover EFI folder, but it stops being recognised again.

 

Is there something I could be doing wrong? The motherboard is clearly still able to recognise UEFI drives, but I just can't get it to recognise these drives even when they have what should be a working Clover installation (because it's the same one I'm using right now).

 

For example, is there some particular method to cloning a working EFI installation? I've tried just copying the files in the Finder after mounting the EFI volume, and I've also tried using a command like:

dd bs=1024 if=/dev/rdisk3s1 of=/dev/rdisk1s1

To copy the EFI partition at the block level, but although this seems to work (I can mount the volume with any obvious errors or corruption) it still isn't recognised. Like I say, I have an EFI setup on my USB stick that works, so if there's a way I can copy it onto these drives I'd like to do it.

Have you tried reseting your BIOS to default settings (as in select Load Defaults from your BIOS), then setting them to what you need to boot into OS X?

 

This can clear out problems such as that

you are using dd command,  linux guy!

 

dangerous tool,  typing error,  wrong drive number,  will kill your hard drive.

 

Easy way is to check, all  important partitions are Ok.

 

A, boot pc up with OS X installation USB,  use disk utility to check partition type  and size.

B. if you can boot up with another window disk,   ( there exist free tools which will  allow you to read hfs data.)

     and use it to check your OS X partitions.

 

C. (i did a similar thing, many months ago).   use dos command line tool,  to delete incorrect EFI partition.  and reinstall loader.

 

google dos command for  delete  efi partition.

(i do not remember how to do it now)


You should boot up your PC with WIn8.1 installation DVD,

And Try to repair Win81 first.

Have you tried reseting your BIOS to default settings (as in select Load Defaults from your BIOS), then setting them to what you need to boot into OS X?

 

I hadn't, but unfortunately it hasn't helped.

 

 

The weird thing is that it's recognising the drive(s) as Microsoft boot loader capable when I copy across the /EFI/Microsoft folder, but it just isn't recognising it as a general UEFI disk anymore, which is what I need to select in order to boot Clover.

 

Easy way is to check, all  important partitions are Ok.

 

I tried running First Aid via Disk Utility when I first encountered the problem, and it found and repaired an issue with the partition map on my system volume, but even after clearing the EFI partition and restoring it from the working USB partition it wasn't recognised.

 

For my second SSD I just wiped the whole disk and recreated the partition map, installing Clover fresh, so there can't have been any partition related issues after that, but still it's not co-operating for some reason.

Some pc,  boot sequence has bug in the bios.

You may need to set hard drive  boot priority to windows hard drive first and f12 to start OS X.

or set OS X as first and f12 or boot loader select other.

 

if you have two clover installed hard drives, 

if  need to change clover's hard drive boot priority,  else it will boot the primary hd, no matter what you select in the boot loader.

something to try;

- Disable all internal AHCI / SATA disk in BIOS/UEFI but leave just one desired enable for your OSX & loader.

- Get a external backup (Carbon Copy Cloner) and boot loader (can be on another USB)  ready

- boot into working osx environment 

- Do a normal disk init via Disk Utility. Format as JHFS.

- Run Clover installer, make sure your config file is ok for your hardware, and also your .efi driver files.

- Clone system back, or run OSX installer.

One more thing to watch for.   Partition table.

cosole

diskutil list

 

something like this

 

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk0

   1:         Microsoft Reserved                         134.2 MB   disk0s1

   2: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC               314.6 MB   disk0s2

   3:                        EFI NO NAME                 104.9 MB   disk0s3

   4:       Microsoft Basic Data Acer-Win81              999.6 GB   disk0s4

/dev/disk1

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *320.1 GB   disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                  Apple_HFS Acer-Yosemite           319.7 GB   disk1s2

 

 

if partition table was corrupted,  ID will be incorrect, no EFI partition, no UEFI  boot.

×
×
  • Create New...