Hello.
Another common one to watch out for is setting the SCSI ID of one of the
devices on the chain the same as the ID of the controller card. This
usually yields "unpredictable" results.
Looking back at the log file snippets, I don't think this is really the case
here, but it's an easy one to check for all the same. At least it would be
one more possible cause eliminated.
Bye for now,
Stuart.
-----Original Message-----
From: mikus@bga.com [mailto:mikus@bga.com]
Sent: Tuesday, October 12, 2004 10:59 AM
To: suse-linux-e@suse.com
Subject: Re: [SLE] scsi problem
On Tue, 12 Oct 2004 09:39:58 -0500 Danny Sauer
SCSI parity errors are often indicative of improper SCSI termination, cable too long, or problems with a particular device. It is almost always a hardware problem.
SCSI FAQ entry #1:
q: I'm having a problem - any problem - with my SCSI devices. Why? a: Check termination, and maybe check cables.
--Danny, noting that nearly every problem traces back to termination :)
Pay attention to the messages shown on the console when you first boot your system. Typically, SCSI BIOSes will list their devices. If one or more SCSI devices do not show up, that is often a sign of improper SCSI termination or incorrect SCSI adapter settings. mikus