Jump to content

Boot0 error without 4k drive


1 post in this topic

Recommended Posts

I’ve got a really strange issue that I can’t seem to find a solution for. I’ve got Mavericks successfully installed using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] (this was the case with Mountain Lion too). I install [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and reboot, so everything is working great. However, when I go to reboot the system again, I get a blinking underscore for a while and then a boot0: error. No boot0: GPT or repeated message, just the one.



When I reboot the system from a [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] drive, I can see the installer, but not the boot drive I just created. When I go into disk utility on the installer, the partition that I was booting from is greyed out (I can’t verify/repair the drive or the partition) and it has lost its name (reverted from ‘Boot’ to ‘disk0s1’)



My initial thought was to use the boot0 error guide, but as far as I can tell, I’m not using a 4k drive. My setup is as follows:



CPU: i7 3770k

Motherboard: Gigabyte B75M-D3H

Drives: Samsung 840 (Boot), Western Digital Blue 2.5” (1tb), 2* Western Digital Green 3.5 (3tb) - in a RAID 1 Mirror

GPU: GTX660ti



The strange thing is that I had a completely working Mountain Lion system for several months before this and the error started occurring with no hardware change at all. Chimera, [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], and OS upgrades clearly didn't help with anything.



Basically, I’m down to always booting from a [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] drive and then selecting the proper drive to start the OS, so it sounds like something in the BIOS/Bootloader is screwy. I’ve been pulling my hair out over this for months, so if someone could help me out, I’d be so grateful. I’d be happy to post any logs or anything that would be helpful.


When I try performing the normal boot0 fix (as outlined in the guide) it says that the drive was already unmounted. I ran the fix (0+2 in, 0+2 out), but when I went back to Disk Utility, it was unmountable. Now it's doing it every time I boot and it's driving me up the wall. Someone please help.

Link to comment
Share on other sites


  • Create New...