[648] in linux-scsi channel archive
Re: AHA-1740 SCSI errors
daemon@ATHENA.MIT.EDU (Jon Lewis)
Mon Oct 2 02:45:38 1995
Date: Sun, 1 Oct 1995 21:05:17 -0400 (EDT)
From: Jon Lewis <jlewis@inorganic5.chem.ufl.edu>
To: Michael Weller <eowmob@exp-math.uni-essen.de>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.3.89.9510020109.A25546-0100000@hertha.exp-math.uni-essen.de>
On Mon, 2 Oct 1995, Michael Weller wrote:
> > Since the errors come from all the SCSI devices, I'm guessing it's either
> > a cabling or driver problem. I doubt both controllers are bad, but we
> > are using long cheap SCSI cables. Anyone have any ideas? I'm
> ===============
>
> Why are you posing questions and then answer them yourself? Might it even
Well...I didn't mean we were using totally crappy cables...just that they
are run of the mill 50-pin ribbon cable and one is a bit on the long
side...but case configuration requires it.
I should have included that all devices in each system are internal.
There are no external chains.
I read recently that many SCSI problems can be caused by cheap cables,
and wonder if perhaps investing in really high qaulity cables would be a
good move...or is there such a thing as top quality ribbon cable?
A third system (used for WWW service primary DNS and as an X workstation)
uses an NCR 53c810 and an identical cabling setup (2 internal HD's, no
other SCSI devices) seems to have no such problems. That system was
"upgraded" to the NCR board after having serious stability problems with
first a 2940 and then 1540.
------------------------------------------------------------------
Jon Lewis | Mime attachments are OK
jlewis@inorganic5.chem.ufl.edu | But please ask before sending
http://inorganic5.chem.ufl.edu | unsolicited huge files.
|
_____Finger jlewis@inorganic5.chem.ufl.edu for PGP public key_____