The dreaded stop sign, Yosemite 10.10 Install on GA-Z68X-UD3H-B3

[boxofmochi]

Hello,

My build is:
MB: GA-Z68X-UD3H-B3
Processor: Intel i7

I am using: Clover Bootloader
I am attempting to install: Yosemite 10.10
I am upgrading from originally: Lion OS X 10.7.5 (not sure if that matters since I wiped the startup drive for this to install Yosemite)


I followed the following guide to the tee:
http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html

And came up with the dreaded stop sign error.

Attempt 1:

Since I'm using Clover, I attempted to add the following code block to my config.plist file (as per several tutorials I've found online):


<key>KextsToPatch</key>
<array>
<dict>
<key>Name</key>
<string>IOAHCIBlockStorage</string>
<key>Find</key>
<data>
AEFQUExFIFNTRAA=
</data>
<key>Replace</key>
<data>
AAAAAAAAAAAAAAA=
</data>
<key>Comment</key>
<string>TRIM Enabler</string>
</dict>
</array>

I added the above code just before the last 2 lines of the file which are:

</dict>
</plist>

Attempt 2:

I also attempted to edit Clover Settings per another post I found:
Enable USB Injection and USB ownership from clover and retry.

But this didn't work either.

Attempt 3:
Changed the boot drive between USB 2.0 ports and USB 3.0 ports.
No change in results.
Note: my bootloader USB is a USB 3.0 drive, would that be a problem?

Photos of Error:
I've attached some pictures of the resulting error after I attempt to boot via the USB > boot the installed Yosemite Startup Disk:


Any assistance or ideas as to what direction I might go would really help.
I've combed through the instructions several times, including reinstalling OS X onto the Startup Disk, with no change in results.

Thank you for reading.

 

[Jithin.C.V]

Note: my bootloader USB is a USB 3.0 drive, would that be a problem?

It can be. Try with USB 2.0 device and USB 2.0 port.

Is the BIOS running with latest firmware??

What are the states of the options which related to USB on your BIOS??

Is the Vt-d Disabled (If it present/supported) ??

 

[boxofmochi]

The dreaded stop sign "Still waiting for root device", Yosemite 10.10 Install on GA-Z68X-UD3H-B3

Hi there!

Thank you for your response.
First off, it seems that the main error is in reading my USB Bootloader.
The other error (or not an error, but an issue?) may be in my 2nd note (below).

It can be. Try with USB 2.0 device and USB 2.0 port. - Next attempt (will take some time because I have to set up Lion OS X on a separate SSD again to install this, as my copy of Yosemite is on the same computer)

Is the BIOS running with latest firmware?? - Currently running F11i, in order to install F12 I'll need to install Lion again (same as above). Will have an update in a few hours.

What are the states of the options which related to USB on your BIOS?? - Please see attached pic.

Is the Vt-d Disabled (If it present/supported) ?? - Yes, I just disabled it. Didn't work though.

Some notes:
1. On first restart, it says to boot ""Boot OS X Install from OS X Install OS X Yosemite"" again to complete the installation.
Specifically, it should complete the following:
""The system will boot into the new drive, create the recovery partition, and complete the installation. Upon completion, system will restart a 2nd time.""
However, every time I've done this, it seems like it's just doing a full installation all over again.
It doesn't look like it's completing the initial install.
Is there something I missed? I'm thinking it may be related to #2 below:

2. Odd thing I noticed is:
- When I change the hdd's to AHCI mode, my SSD's are not recognized by Clover Bootloader. But they ARE recognized by Disk Utility (Clover > Boot Install OS X > Disk Utility)
- And vice versa: when I change the BIOS config of the hdd's to IDE mode, my SSD's ARE recognized by Clover Bootloader, but are NOT recognized by Disk Utility.
Is this normal?"

 

[Jithin.C.V]

Load default settings on BIOS and try again.

 

[boxofmochi]

Load default settings on BIOS and try again.

This does not fix the issue.

But I found a fix elsewhere, thanks.