SCSI madness

Net Llama! netllama
Thu Jan 13 13:50:39 PST 2005


I've been tearing my hair out for the past 4 days trying to deal with SCSI
errors on a box runnign FC3.

For the past week or so, whenever I boot up, see the following error on
the console:
sym0: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0

When the above error occurs, the box functions just fine, but i fear for
my data.  In fact, sometimes, i don't get the error above, and the
box boots up fine, and then as soon as the login prompt appears, i start
seeing SCSI reset/abort errors instead.  When the reset/abort errors show
up then i can't do anything, all input fails to register and the box can
only be reset.

FWIW, i'm using an old symbios 8951 SCSI controller.  I've replaced the
SCSI drive, the SCSI cable, and now the controller, and yet the fscking
error persists.

I'm at a loss as to how this error can persist when i've replaced every
component on the chain.

Anyone have any ideas?


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                                netllama at linux-sxs.org
Linux Step-by-step & TyGeMo                  http://netllama.ipfox.com


More information about the Linux-users mailing list