When you install Mac OS X on a non-Apple hardware device called a Hackintosh, you are likely to face the problem of 'Still waiting for root device'. This is the message you get when you try to boot Mac OS X. This message illustrates that the disk containing the OS X image is not booting properly. This message keeps on repeating, and you cannot move forward till you find some solution for it. This article shows how to fix 'Still waiting for root device' on your Hackintosh.
- In Verbose mode it crashes half way, a 'no entry' icon pops up and the last text says 'Still waiting for root device'. I followed all the instructions one by one. I tried it in multiple USB drives and different ports; tried creating the installation drive with Unibeast and Terminal.
- The Mac Mini's HD will be mounted as an external HD in the non-corrupted computer. Find and save your valuable data. Afterwards, making a Clean Install is the usual and fastest way of solving this issue. 'Still waiting for root device' on a macbook pro mid 2009 with osx 10.11.6.
This solution works for people who have installed Leo4all v3 and received the message upon rebooting. The cause of the error is due to incompatible or incorrect configuration of the ATA controller.
What does 'Still waiting for root device' means? It means that a driver/kext for the source from which you are booting is not detected properly by the mac operating system (USB kext not detected or loaded) Mac OS released prebuilt with the latest drivers that supports SATA out of.
How to Fix Still waiting for root device
Boot your PC using LeoV3 DVD as if you are reinstalling Mac OS X again.
Select the Terminal from the installer's Utility menu.
Now, you have to copy all the kexts from the DVD to your hard drive.
For performing this task, you need to use the following command:
cp -pr /Volumes/Leo4allv3/System/Library/Extensions/*ATA* /Volumes/MacHD/System/Library/Extensions/.
You need to replace Leo4allv3 with the name of your DVD. Also replace the MacHD with the name of your hard drive volume.
Set the permissions for the kexts you have copied. For this purpose, you need to use the following command in the terminal:
chown -R root:wheel /Volumes/MacHD/System/Library/Extensions/*ATA*
chmod -R 755 /Volumes/MacHD/System/Library/Extensions/*ATA*
Still Waiting On Root
Now, you need to remove the kextcache by using the following command:
Still Waiting For Root Device Mac Os X
rm -rf /Volumes/MacHD/System/Library/Extensions.*
Now, reboot your PC. It is highly recommended to press F8 when your PC is booting and then enter '-f' as the boot option to force reloading of the kexts.
Macbook Air Still Waiting For Root Device
It is not completely sure that this strategy might work for your Hackintosh, but still this solution is the most feasible one as reported by many people who suffered from the 'Still waiting for root device' issue. You might try exploring more settings if your problem is not solved by using the technique mentioned in this article.
Nicholas_NYC
Member- Joined
- Nov 23, 2009
- Messages
- 13
- Reaction score
- 0
- Points
- 1
Still Waiting For Root Device Macbook
I have a PowerBook G4 15-inch, pre-Intel from late 2005. Until today it always worked and rarely hanged. All I've ever needed to do when in trouble was reboot. I've updated the Apple OSX software regularly and have never touched the hardware, except once 18 months ago to add memory. All I do with this machine is use it. It's been weeks since I installed any new software.
There were no warning signs before the problem started today.
FIRST SIGN OF TROUBLE: The machine was unusually slow, showing beach balls on every minor move. I powered down conventionally and later turned it on again. After a minute I got the 'Forbidden Sign' grey screen, which I had never seen before. So I rebooted, and got that again.
I turned to the only other available machine (very old PC, unfortunately) to browse for solutions, and have so far tried the following:
1) BOOT FROM INSTALLATION DISK: Forbidden Screen. After a couple of attempts I removed the disk (by clicking trackpad on power up). At some point, in desperation, I even tried Disc 2.
2) RESET PRAM (Command-Option-P-R on power up) : I got three chimes, then the grey screen. It stayed on the apple and gear for many minutes. At least it never went to the Forbidden Screen.
3) FILE SYSTEM CHECK (Option-S on power up) : After a few steps it shows error messages (see below) and starts repeating, 'Still waiting for root device,' over and over.
4) RESET NVRAM (Command-Option-O-F on power up) : I got a blue screen with text and was able to input 'reset-nvram' (response: OK) and then 'boot.' Result: Forbidden Screen.
5) SAFE START (Option on power up) : Forget it. Forbidden Screen. Same when I try it with 'C' as some sites recommend. Same with or without the Install Disk in the DVD driver.
6) POWER MANAGEMENT UNIT RESET (Shift-Control-Option-Power): Subsequent boot still produces Forbidden Screen.
*THE ERROR MESSAGES*
Here are some of the messages when I start up with Option-S:
CSRHIDTransitionDriver:robe booting in single user .. do not match
Extension 'com.apple.driver.AppleUSBTCKeyboard' has no kernel dependency.
Extension 'com.apple.driver.AppleUSBTCKeyEventDriver' has no kernel dependency.
Apple PMU::CLOCK RESET! PMU WAS PROBABLY RESET SOMEHOW!! +(Yes, I did that, but it wasn't showing this before I did, and it WAS showing all of the following.)+
Security auditing service present
BSM auditing present
disabled
rooting via boot-uuid from /chosen: +(I think the long code that follows is the serial number?)+
Waiting on IOProviderClassIOResourcesIOResourceMatchboot-uuid-media
PMUMS::start ERROR: failed to find IOATABlockStorageDriver
Still waiting for root device
Still waiting for root device
Still waiting for root device
+(etc. ad infinitum)+
*So now I'm begging anyone for answers to these questions
Am I doomed?
Does anyone know what the problem is?
This seems to be happening prior to disk access, as it happens with or without the Install Disk. So do I still have the hard drive working? Is my data on it?!
Was resetting the Power Management Unit a bad idea?
What can I do next?
THANK YOU THANK YOU THANK YOU!
Nicholas from NYC