Hello,
On Thu, 2 Dec 2004, Nicolas Will wrote:
[skipped]
ide0 at 0x1fe02c00000-0x1fe02c00007,0x1fe02c0000a on irq 4,7e0
ide1 at 0x1fe02c00010-0x1fe02c00017,0x1fe02c0001a on irq 4,7e0
(shared with ide0
Partition check:
hda:end_request: I/O error, dev 03:00 (hda), sector 0
end_request: I/O error, dev 03:00 (hda), sector 2
end_request: I/O error, dev 03:00 (hda), sector 4
end_request: I/O error, dev 03:00 (hda), sector 6
end_request: I/O error, dev 03:00 (hda), sector 8
end_request: I/O error, dev 03:00 (hda), sector 10
end_request: I/O error, dev 03:00 (hda), sector 12
end_request: I/O error, dev 03:00 (hda), sector 14
end_request: I/O error, dev 03:00 (hda), sector 0
end_request: I/O error, dev 03:00 (hda), sector 2
end_request: I/O error, dev 03:00 (hda), sector 4
end_request: I/O error, dev 03:00 (hda), sector 6
end_request: I/O error, dev 03:00 (hda), sector 8
end_request: I/O error, dev 03:00 (hda), sector 10
end_request: I/O error, dev 03:00 (hda), sector 12
end_request: I/O error, dev 03:00 (hda), sector 14
unable to read partition table
[skipped]
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 2828k freed
cramfs: wrong magic
Kernel panic: VFS: Unable to mount root fs on 00:00
Press L1-A to return to the boot prom
Now, there are clearly two distinct problems here. One is the hard drive
problem, another one is the failure to load initrd into ramdisk. The
latter one is (IMO) more serious, since the initrd image is clearly loaded
into memory by silo, but later kernel fails to find it. I don't remember
having seen that kind of failure before.
Best regards,
Jurij Smakov [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
