Re: Disk screwed up with ybin

[Benjamin Cama <benoar@dolka.fr>]

Le mardi 19 avril 2011 à 16:46 -0700, johnny-crash a écrit :
> boot=/dev/hda2
> device=/pci@f4000000/ata-6@d/disk@0:
> partition=3
> root=/dev/hda3
> timeout=100
> install=/usr/lib/yaboot/yaboot
> magicboot=/usr/lib/yaboot/ofboot
> enablecdboot
> macosx=/dev/hda4
> defaultos=macosx
> 
> image=/boot/vmlinux
> label=Linux
> read-only
> initrd=/boot/initrd.img
> append="quiet splash"
> 
> My macosx is on /dev/hda3 (sure), linux on /dev/hda5 and 6 (not sure). The
> important stuff is on the two macosx partitions.

Well, there's a problem then: your conf says that macosx in on /dev/hda4
and your linux /boot on /dev/hda3…

> dmesg says:
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> ...
> hda: no DMA mode selected
> Dev hda: unable to read RDB block 0

Another idea if you think your drive is not faulty: maybe you didn't
plug the hard drive right? I had some problems with 2,5" IDE drives that
have hard to push connector. Maybe a shock caused it to move?

> How do I get the partition table? I did dir hd:\ in OF and it crashed
> imediately.

With mac-fdisk?

> Yes target mode is much better but I doubt that I'll be able to read
> anything ;-(

Why? You don't have any more access to any OS? What is exactly the
“white” screen you were talking about? When does it show up exactly?

benjamin