[1977] in linux-scsi channel archive
Re: SCSI problem with ASUS SC-200
daemon@ATHENA.MIT.EDU (Thomas Tongue)
Tue Jun 10 10:42:30 1997
Date: Tue, 10 Jun 1997 09:30:21 -0500 (CDT)
From: Thomas Tongue <ttongue@proteus.imagiware.com>
To: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.94.970606134818.24511I-100000@proteus.imagiware.com>
I've had further developments with the ASUS SC-200 board. First, someone
suggested that I should use the ncr53c8xx driver rather than the
ncr53c7xx,ncr53c8xx driver. When I try the straight ncr53c8xx, it detects
only two of the 3 hard drives (but detects the CD and Tape fine).
Its the 3rd drive (SCSI ID3) that is missing in action, and it is
identical in spec to the 2nd drive (They're the same model and
revision of drive).
I have heard some poor things about the Quantum Fireball on this mailing
list. Could this be the root of the problem? It just seems so flaky that
one driver reliably detects the drive, and the other does not.
Here's the background on the problem:
> I have a problem similar to others mentioned in this group. I am recieving
> on the console the following messages when trying to run a tape backup:
>
> scsi : aborting command due to timeout : pid 93469, scsi0, channel 0, id 2, lun 0 Write (6) 0d 00 5b 02 00
> scsi0 : DANGER : command running, can not abort.
> scsi : aborting command due to timeout : pid 93470, scsi0, channel 0, id 2, lun 0 Write (6) 0d 40 57 04 00
> scsi0 : found command 93470 in Linux issue queue
> scsi : aborting command due to timeout : pid 93471, scsi0, channel 0, id 2, lun 0 Write (6) 0d 40 5b 02 00
> scsi0 : found command 93471 in Linux issue queue
> scsi : aborting command due to timeout : pid 93466, scsi0, channel 0, id 0, lun 0 Write (6) 00 00 41 02 00
> scsi0 : DANGER : command running, can not abort.
> scsi : aborting command due to timeout : pid 93467, scsi0, channel 0, id 0, lun 0 Write (6) 00 00 49 02 00
> scsi0 : found command 93467 in Linux issue queue
>
> Note that this symptom does not crash the machine, and the tape backup
> appears to work fine. The also does not appear to be any damage to the
> disks (which are also SCSI).
>
> Heres the config info:
>
> Kernel: 2.0.30 (both with and without SMP enabled)
> Hardware: Dual Pentium Pro MB by ASUS (with 2 PPro200's)
> 128 MB RAM
> ASUS SC-200 SCSI adapter
> 3com 3c590 PCI ethernet
> ....
>
> Other system info:
>
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: QUANTUM Model: FIREBALL_TM1280S Rev: 300X
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: ARCHIVE Model: Python 25501-XXX Rev: 5.AC
> Type: Sequential-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: NEC Model: CD-ROM DRIVE:502 Rev: 2.2e
> Type: CD-ROM ANSI SCSI revision: 01
>
>
> As indicated above, this happens while the tape drive is running,
> but the id's singled out by the error messages are for the hard
> drives. Suggestions?
Thanks for your suggestions and help!
Thomas Tongue
ttongue@imagiware.com
http://imagiware.com/
