Contribute
Register

Boot0...yes I read the sticky guide and it failed!

Status
Not open for further replies.
Joined
Nov 6, 2010
Messages
125
Motherboard
GIGABYTE GA-X58A-UD3R LGA 1366 Intel X58
CPU
Intel Core i7-950 Bloomfield 3.06GHz LGA 1366
Graphics
GIGABYTE GV-N285UD-1GH GeForce GTX 285 1GB 512-Bit GDDR3
Mac
  1. Mac Pro
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hey folks! I need some help with this boot0 error. Before you say DiD YoU ReAD ThE PoST tHE AdMiN MaDe Or UsEd ThE SeArCH bAR??!!!!

yes I did that. Let me tell you how this all came about first. I moved from one apartment to another and I moved myself. My hack was working great at the old apartment. When I moved my hack would hang at DSMOS HAS Arrived. I researched that and basically, the system was booting but the GPU wasn’t connecting to the monitor, so I now have to boot with the argument -v GraphicsEnabler=Yes PCIRootUID=0 in order for me to even get to the desktop. So, I got to that point finally. I figured that maybe the hard drive is failing because something got corrupted. Have you, this is a a Crucial 256 GB SSD, not sure if they fail, but I bought a 500GB SK HYNIX SSD to clone what I have on my drive on to the bigger drive. I used Carbon Copy Clone to clone the drive. I learned that CCC did not copy over the EFI so I needed to use multibeast to be able to get the system “bootable”. I ran through multibeast and it worked well, except for now I run into boot0. I can boot into the O/S 10.10 Yosemite when I plug in my old SSD and boot from there, but that’s such an inconvenience instead of having the computer boot natively.

I searched for boot0 on the forums and I tried that DD command from terminal and it didn’t work out. It said something along the lines of operation failed/not allowed. As suggested, I booted into my sort of working OS, the Crucial SSD (I say it’s sort of working because I have to always use the boot argument), so, I booted into the old working copy, installed multibeast, then targeted the new install, detached the old ssd and now I still come back to boot0.

Any help is appreciated.
Thank you!
4EE82ADA-8F36-4B1E-A2F5-5A6B22446580.jpeg
 
Hey folks! I need some help with this boot0 error. Before you say DiD YoU ReAD ThE PoST tHE AdMiN MaDe Or UsEd ThE SeArCH bAR??!!!!

yes I did that. Let me tell you how this all came about first. I moved from one apartment to another and I moved myself. My hack was working great at the old apartment. When I moved my hack would hang at DSMOS HAS Arrived. I researched that and basically, the system was booting but the GPU wasn’t connecting to the monitor, so I now have to boot with the argument -v GraphicsEnabler=Yes PCIRootUID=0 in order for me to even get to the desktop. So, I got to that point finally. I figured that maybe the hard drive is failing because something got corrupted. Have you, this is a a Crucial 256 GB SSD, not sure if they fail, but I bought a 500GB SK HYNIX SSD to clone what I have on my drive on to the bigger drive. I used Carbon Copy Clone to clone the drive. I learned that CCC did not copy over the EFI so I needed to use multibeast to be able to get the system “bootable”. I ran through multibeast and it worked well, except for now I run into boot0. I can boot into the O/S 10.10 Yosemite when I plug in my old SSD and boot from there, but that’s such an inconvenience instead of having the computer boot natively.

I searched for boot0 on the forums and I tried that DD command from terminal and it didn’t work out. It said something along the lines of operation failed/not allowed. As suggested, I booted into my sort of working OS, the Crucial SSD (I say it’s sort of working because I have to always use the boot argument), so, I booted into the old working copy, installed multibeast, then targeted the new install, detached the old ssd and now I still come back to boot0.

Any help is appreciated.
Thank you!View attachment 511032
not sure how reliable the SK HYNIX SSD are on a hackintosh, have seen other with issues on those drives
 
Thanks for the reply. The SSD from SK Hynix works well, or I would have much bigger issues than what’s here. At least I can boot into the O/S but it gets cumbersome when you want to just turn on your computer and then you have to do several steps just to get into it.

SK HYNIX is a great brand if you look up where they came from.
 
I went ahead and plugged my Sata connector to Port0 to see if that would help to no avail. I have no other Sata connections other than the SSD. I removed my DVD drive because no everything is USB!
 
I wouldn’t quite rule that out quite yet before any other solutions can be tried. Hell, my Crucial SSD some how corrupted because now I have to insert a boot argument that I never before needed to insert upon boot up.
 
I wouldn’t quite rule that out quite yet before any other solutions can be tried. Hell, my Crucial SSD some how corrupted because now I have to insert a boot argument that I never before needed to insert upon boot up.
your choice
 
If the SSD wasn’t supported, I wouldn’t be looking at my desktop right now. I would have gotten some sort of kernel panic of some sort.
AEA1D6E3-4E51-4DB0-A1F2-A4A772EED78B.jpeg
 
Status
Not open for further replies.
Back
Top