- Joined
- Nov 24, 2012
- Messages
- 32
- Motherboard
- GA-Z77X-UD5H
- CPU
- i5-3570K
- Graphics
- HD 4000
- Mac
- Classic Mac
- Mobile Phone
I am running Mavericks 10.9.0 on a Gigabyte GA-Z77X-UD5H motherboard with pretty standard hardware. I built this hack with Mountain Lion about a year and a half ago and haven't had any issues upgrading.
Today I decided to upgrade to 10.9.2 so I downloaded the standalone installer and repaired permissions as per Stork's instructions at http://www.tonymacx86.com/407-os-x-10-9-2-update.html. Diskutil found a bunch of issues, so I restarted before moving ahead with the update. On that restart, disaster struck: refused to reboot -- I don't even reach the bootloader.
So here's where I am stuck:
My next step will be to recreate the Unibeat USB drive in an attempt to get that to work and hopefully use that to identify the problem and repair the bootloader.
Thanks for the help!
Today I decided to upgrade to 10.9.2 so I downloaded the standalone installer and repaired permissions as per Stork's instructions at http://www.tonymacx86.com/407-os-x-10-9-2-update.html. Diskutil found a bunch of issues, so I restarted before moving ahead with the update. On that restart, disaster struck: refused to reboot -- I don't even reach the bootloader.
So here's where I am stuck:
- When I let it boot to the default drive (P0: 128 GB Samsung 830 SSD), immediately after the motherboard splash screen it goes to a black screen with the spinning ASCII characters in the very top left, though they only spin for a second before freezing, either with an underlined \ or |.
- Naturally, my first thought was to boot from my Unibeast USB drive. No dice -- exact same behavior. I am not sure how to tell if that is because it is hitting the same issue on the second drive, or if that it is not finding a bootloader on the USB drive so it is just reverting to my primary SSD.
- I can enter the BIOS and force it to boot to my secondary SSD (P1: 64 GB Samsung 830 SSD), which happily boots up Windows. Joy.
My next step will be to recreate the Unibeat USB drive in an attempt to get that to work and hopefully use that to identify the problem and repair the bootloader.
- Have any of you encountered an issue like this? Did I cause it by repairing permissions?
- Is there any way to get more information about exactly what is causing the issue before I reach the bootloader?
Thanks for the help!