Can't Boot after MultiBeast

[huertas]

Issue: I am unable to boot from hard drive - locks at boot screen. I've re-installed at least 10 times and, while I can boot fine from Unibeast thumb drive, I cannot boot from Hard Drive.

Following is what a verbose boot looks like.


Any ideas of what I can try? I've almost given up...


Parts:

- Intel Core i5-3560K
- Gigabyte GA-Z77-DS3H Intel 7 Series Motherboard (F8 Bios)
- (2 for 16GB total) Kingston HyperX 8 GB DDR3 1600MHz Memory Module
- 2TB Seagate Hard Drive
- Ultra 10/100/1000 LAN PCIE X1 Card
- Gateway 19" monitor connected via VGA

Steps taken:
I have setup all BIOS settings per
Used UniBeast ML 1.5.3 to install ML 10.8.2
Used MultiBeast 5.1.3 to install Audio and DSDT

 

[Pakalolo]

One step to take is you need to update your bios to F9. http://www.gigabyte.us/products/product-page.aspx?pid=4147#bios

 

[Thor_HoG]

Issue: I am unable to boot from hard drive - locks at boot screen. I've re-installed at least 10 times and, while I can boot fine from Unibeast thumb drive, I cannot boot from Hard Drive.

Following is what a verbose boot looks like.
View attachment 39421

Any ideas of what I can try? I've almost given up...

I had similar problems. In fact, I think my system still hangs a bit something audio related, but I've been too busy to muck about with it, as it boots fine, albeit a bit slower than normal.

Not related to audio though, after using MB 5.1.2 or 5.0.2 it would fail a boot. I actually got a "fail" after installing the SYSTEM kexts. What I did was, after installing MB but before rebooting was:

[TYPE] sudo kextcache -system-cache
[TYPE] sudo kextcache -update-volume /

Updating the cache like this will verify links to required kexts (or something like that). It will give you a list of kexts that should be removed. In my case they were:
ACPISensors.kext
FintekF718x.kext
ITEIT87x.kext
NSCPC8739x.kext
NVClockX.kext
NuvotonNCT677.kext
RadeonX.kext (even though I have a Radeon card)
WinbondW835x.kext
X3100.kext (this was on a list somewhere, but not actually reported nor on my system)

Deleting these and rebuilding the cache worked. Now, what was *critical* for me was to also delete the OEMSMBIOS.kext file *before* rebooting after the previous commands. Even if I rebuilt the caches (which was still required) it would lock at the IOUSBController::CreateRootHubDevice error and I couldn't even boot into -s (safe) mode.

Hopefully this information will help.

t

 

[huertas]

This is finally working

Thanks for the feedback and suggestions.

After trying your suggestions, it still did not work.

The fix - Changed out the VGA cable to DVI cable. Worked perfectly.