OSX Boot hangs at bsd root: major 14, minor 1 when 2 Hard Drives

[cdouillard]

Hello,

I am facing a weird issue. My hackintosh would stop booting at the "BSD Root" line each time my 2d hard drive is connected. I have been searching the web but haven't seen any topic on that.
I am on Snow Leopard (10.6.7) and the Chameleon boot (2.0 RC5) is installed on the EFI partition.

It was working fine (booting with 2 HD) until recently, when I suddenly was not able to even boot Chameleon. I had to remove the 2d drive to be able to boot again, then upgraded from RC4 to RC5 and moved the Chameleon boot to EFI partition.
I am now a step further as Chameleon boots but I am stuck at the bsd root line.

Has anyone faced the same situation?

Thanks
Christophe


 

[Gringo Vermelho]

Use Chameleon 2.1.

Post how you are installing Chameleon (or install 2.1 manually using the guide in my signature)

Post your /Extra/org.chameleon.Boot.plist

(from the late versions of RC5 and up, /Extra/com.apple.Boot.plist is now org.chameleon.Boot.plist)

[cdouillard]

Thanks Gringo,

I installed Chameleon Manually from the terminal:
sudo fdisk -f boot0 -u -y /dev/rdisk0
sudo dd if=boot1h of=/dev/rdisk0s1
sudo cp boot /Volumes/EFI/
I copied my Extra directory to /volume/EFI/
I didn't change the com.apple.Boot.plist
I don't have any DST file

This has worked (Booting with 1 hard drive) so far ... until the graphics on the Hackintosh started to go all over the place. I stopped and restarted my hackintosh (with 2 disks this time) and got stuck the just after the DSB root line (the line starts with "dev" then a non blinking cursor and nothing.
I thought it was coming from the 2d hard drive, but I can't even boot with only 1 drive now.

I will try to access my hard drive from a Macbook and I will post the com.apple.Boot.plist

Thanks for your help
Christophe

[Gringo Vermelho]

As I said:

(from the late versions of RC5 and up, /Extra/com.apple.Boot.plist is now org.chameleon.Boot.plist)

If you installed Chameleon using the files from my guide and you didn't rename your com.apple.Boot.plist, you're in trouble..

[cdouillard]

I'm accessing the disk from a Macbook and I have the 2 following files
/Extra/org.chameleon.Boot.plist
/Extra/com.apple.Boot.plist

and here is the content:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs$
<plist version="1.0">
<dict>
        <key>GraphicsEnabler</key>
        <string>Yes</string>
        <key>Kernel</key>
        <string>mach_kernel</string>
        <key>Kernel Flags</key>
        <string>boot-uuid=E95F4A6E-0774-3A22-AAE9-792BA301499B</string>
        <key>device-properties</key>
        <string>9b0700000100000002000000c70300001500000002010c00d041030a0100000$
</dict>
</plist>

[cdouillard]

Hi Gringo,
I installed Chameleon 2.1 (as you recommended in you 1st response), I installed all 3 files in the EFI partition. I haven't changed any kext. (I installed on the Hard drive from a Macbook)

I now get the following message: "still waiting for root device"

Should I try to install it on the main partition and see if that works better?

Thanks for your support
Christophe

[Gringo Vermelho]

Try deleting the boot-uuid from kernel flags:

        <key>Kernel Flags</key>
        <string>boot-uuid=E95F4A6E-0774-3A22-AAE9-792BA301499B</string>

So that it looks like this:

Code: [Select]

        <key>Kernel Flags</key>
        <string></string>
If your previous Chameleon installation was on the main partition, then you should install the new Chameleon on the main partition as well.

Or, you can move your /extra folder to the EFI partition.

Still waiting for root device means that OS X can't see your hard drive controller. This is probably happening now because you didn't move your extensions to the new Chameleon installation on the EFI partition.

I don't know why you kept your com.apple.Boot.plist, I told you twice already that org.chameleon.Boot.plist replaces it.

[cdouillard]

Hi Gringo,
That's strange, my previous installation was on the EFI partition (including the extra folder) and has been working for some time.
Does it have something to do with the fact that I am updating my config on my hard drive from a Macbook, using the drive as an external disk?

I will delete the boot-uuid and let you know what happened.

Thanks again
Christophe

[Gringo Vermelho]

No, installing Chameleon to the drive from another computer shouldn't make any difference.

It is strange that it became worse after upgrading Chameleon, if anything, your situation should improve.

Still waiting for root device means that a driver is missing or that the BIOS settings for your drive controller are wrong, it doesn't have anything to do with Chameleon itself, that's why it's so strange that this is happening now.

[cdouillard]

Does the latest version of Chameleon require a DSDT.aml file?
I don't have any and it used to work with RC4 (and RC5 I guess)

[cdouillard]

I finally successfully booted.
I removed the Boot-uuid line from org.chameleon.Boot.plist
I also had to specify the booting drive "rd=disk0s1"

Thanks for your Help Gringo, very much appreciated
Christophe
 

[Gringo Vermelho]

You're welcome, glad you got it working. Can you boot with both drives connected now?

dsdt.aml is not required.

[cdouillard]

Hey Gringo,

Sorry for not coming back to you earlier.
I haven't had the time to try booting with the second drive.
I will try this WE.
Thanks
Christophe

[cdouillard]

I can now boot with both drives connected. I just need to enter rd=disk0s1 before booting Mac OS.
I'll find a way to automate it.
Thanks again Gringo 
Christophe