Re-installing - "nfs_boot_init_failed with 6\n"

[Moddy]

Right guys, I've installed iDeneb 1.4 (Mac OS X 10.5.6) before on this machine - but had to format my HD for another project. Now I need to go back to Mac OS X for some work related stuff, and until I can afford a macbook - I thought I'd just go back to hackintosh for a while!

 

Now by default it wasn't working at all - so I unplugged my 160gb SATA HDD, and tried it with only IDE drives. Now I specify "rd=disk0s1 -v" and I get a little bit further; but its "Still waiting for root device". Now I remember having this before but for the life of me can't remember how I managed to get around it. Whilst this is happening, *one of the drives* clicks and it sounds like its just.. given up?!

 

I've googled and googled but to no avail, and played around with both my BIOS and my physical hardware. Both of my drives are set to cable select - and I've tried the HD as Primary and the DVD-ROM as secondary, and vise versa. (Both are IDE)

 

AHCI support is enabled in the BIOS, and I have looked at other links and got my BIOS looking as it should. See, I know it works as I installed this way before - but I just can't remember for the life of me what I actually did.

 

rd=disk0s1: "Still waiting for root device..."

 

rd=disk1s1: "Got Boot Device" -> "nfs_boot_init_failed with 6\n"@Volumes/disk1s1/leo_xnu... nfs_vfsops.c:851

 

rd=disk1s2: Same as disk1s1; but with the additional "Runtime corruption detected" then a message about running fsck next reboot. (Dodgy media? I'll burn a new DVD..)

 

So from this, I'm guessing disk1s2 is the correct drive/partition. Now I will reburn the media - and see if that improves the situation at all. Any ideas guys?

 

Distro

iDeneb 1.4 (Mac OS X 10.5.6)

 

ASUS P5SD2-VM / Intel Celeron Dual Core E1400 / 2GB RAM / 80gb IDE HDD

[Equinoxx]

Bump. I have had a similar problem and this is the same type of errors I get. Before I could install any distro without ever going into verbose mode to fix anything, now I can't get past still waiting for root device, and mind you this was with a SATA drive. I thought maybe the drive was damaged or something so I bought a new HDD that is IDE and tried everything possible to get it past still waiting for root device to no avail. So right now I believe it could be some problem with the motherboard but how come it worked perfectly fine before.