It’s important to note that if you experience this error on an iMac or MacBook Pro, this isn’t the method for you as you receive the error for a different reason. This is purely for Hackintosh users, Macintosh users should run repair disk from Disk Utility.

I was recently creating a hackintosh on a Toshiba laptop and I ran into an error which I haven’t had for a while, and because of this I’ve never posted on it. But since it came up, I decided to post because it could be useful for some people to know the answer. Basically, after installing a Mac OS X system on a PC, upon booting with the “-v” boot flag, I received an error which was as follows:

/dev/rdisk0s1: UNEXPECTED INCONSISTENCY: RUN fsck_hfs MANUALLY.
/dev/rdisk0s1 (hfs) EXITED WITH SIGNAL 8
** /dev/rdisk0s1
Can’t initialize disk cache
/dev/rdisk0s1 (hfs) EXITED WITH SIGNAL 8
fsck failed!
Kext loading now disabled.
Kext unloading now disabled.
Kext autounloading now disabled.
Kernel requests now disabled.
Can’t get kextd port.

continuing
syncing disks… Killing all processes done
CPU halted: It’s now safe to turn off your computer

After displaying this error for a split second, the laptop would then proceed to switch off completely, something which you had no control over. So, what causes this problem? Well, the answer is simple and bizarre. Too much RAM can cause this error, simply because it can’t be recognised properly by the host system without it being configured properly first. So, the obvious answer is to remove some RAM. Anything below 4GB should work just fine, and afterwards you can configure your Hackintosh to recognise the amount you wish to use, then you’re able to reinstall your original amount. It’s one of those solutions which nobody would think to try, purely because it’s so random, which is why I feel the need to post about it as there isn’t much documentation on it on the net already. The video below shows the effect the error can have, and then shows how simple it is to fix it. Give it a quick watch if you want to check out exactly how it’s done.

I guess this is one situation where having a machine packed full of RAM isn’t a good thing! If you receive this error and have under 4GB of RAM, then leave a post in the comments and we’ll see if we can work out what the problem is!

3 Responses so far.

  1. sergio says:

    Hi.. Just 2 days ago I got this message on my mac pro.. exited with signal 8.. my computer won’t boot completely. So there is no way I can go to disk utility to repair. I’ve also tried goin on safe mode, but it won’t let me either. Can you help me? I’d really appriciate any sort of help. Thank-you!!

    • ZackehSoul says:

      Unfortunately on a Mac this is more likely to be a hardware failure. Do you have the installation discs? Email me (zackehsoul@hotmail.co.uk) and I’ll try help you out.

    • Patrick says:

      Oddly enough, I just got done dealing with this same problem on my early 2012 mac book pro. I had upgraded to 8GB of RAM and a few months back I got the signal 8 error which could not be repaired. Best Buy swapped it out for me because I had had it less than a month. Now, on my new one 2 months later, I had the same problem. I could not fix the error and when I tried, sometimes the disk utility said it was fine and other times it was bad, purely random. Every attempt of my restore failed on that drive as well as a small spare drive I had. I tried the memory thing, pulling out my 8GB and putting in my original 4GB, and amazingly enough it restored and has been working all day. I am actually using it now. Strange I know, but you should give this a shot.


  • RSS
  • Facebook
  • Twitter
  • Youtube