[291] in linux-scsi channel archive
Re: scsi problems with debian
daemon@ATHENA.MIT.EDU (H.J. Lu)
Fri Jun 23 15:26:07 1995
From: hjl@nynexst.com (H.J. Lu)
To: berg@POOL.Informatik.RWTH-Aachen.DE (Stephen R. van den Berg)
Date: Fri, 23 Jun 95 14:18:30 EDT
Cc: ncr53c810@cs.colorado.edu (ncr53c810),
linux-scsi@vger.rutgers.edu (Linux SCSI)
In-Reply-To: <9506231410.AA27438@tabaqui>; from "Stephen R. van den Berg" at Jun 23, 95 4:10 pm
>
> Chris Tubutis <grogg@holly.ColoState.EDU> wrote:
> >> scsi : aborting command due to timeout: pid 13126,
> >> scsi0, id 0, lun 0, Write (6) 05 73 29 02 00
> >> scsi: DANGER: command in running list, can not abort
>
> Two things are happening here:
> 1. The current NCR driver can't deal with problems on the SCSI bus, if a
> problem occurs, it cannot recover.
> 2. The fact that problems occur at all, usually indicates that your
> cabling is bad, over- or underterminated.
>
I posted a note last week about my problem with NCR 53C810 SCSI card
and Quantum 2 GB SCSI-2 hard drive. Thanks to all who sent me
suggestions. What I did was I low level formatted my Quantum
drive under DOS, which was from a Mac mail-order vendor. It seems
to work ok now.
From what I have seen, I think
1. Always do a low level format on a new SCSI hard drive.
2. The error handling code in the generic/NCR 53C810 SCSI driver
may not work at all.
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
