Re: Kernel Panic on Install of Debian 3.1r0a for SPARC

[Blars Blarson <blarson@blars.org>]

In article <[🔎] 20051206194133.8183.qmail@web401.biz.mail.mud.yahoo.com> 
bruce@harrisononline.net writes:

>  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

This is normal and unrelated to the error.  It happens all the time on
my ultra 5.

>  RAMDISK: Couldn't find valid RAM disk image starting at 0.
>  
>  cramfs: wrong magic
>  Kernel panic: VFS: Unable to mount root fs on 00:00
>   Press L1-A to return to boot prom

This looks like the silo bug that hasn't been completly tracked down.
Changing your ram configuration may be a workaround.  Try removing a
pair if all slots are full, or move the pair to the other slots if you
only have one pair.

-- 
Blars Blarson			blarson@blars.org
				http://www.blars.org/blars.html
With Microsoft, failure is not an option.  It is a standard feature.