Subject: Re: SDLT 320 Tape Drive on -current
To: Duncan McEwan <duncan@mcs.vuw.ac.nz>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: current-users
Date: 09/11/2003 21:48:13
On Tue, Sep 09, 2003 at 05:58:01PM +1200, Duncan McEwan wrote:
> [...]
> 
> st0(ahc0:0:6:0):  Check Condition on CDB: 0x00 00 00 00 00 00
>     SENSE KEY:  Hardware Error
>      ASC/ASCQ:  Diagnostic Failure on Component 0x84

The hardware vendor can probably tell you more about this.
If the drive is still under waranty, I would call the vendor and tell them
about this one, at last.

> 
> st0(ahc0:0:6:0):  Check Condition on CDB: 0x11 01 00 00 46 00
>     SENSE KEY:  Media Error
>    INFO FIELD:  15
>  COMMAND INFO:  163931 (0x2805b)
>      ASC/ASCQ:  Recorded Entity Not Found
> 
> st0(ahc0:0:6:0):  Check Condition on CDB: 0x08 00 00 02 00 00
>     SENSE KEY:  Media Error
>    INFO FIELD:  512
>  COMMAND INFO:  163931 (0x2805b)
>      ASC/ASCQ:  Positioning Error Detected By Read of Medium
> 
> Perhaps some of these could have been caused by previous write operations
> failing and so the data on the tape is incorrect (ie: no end of tape marker,
> etc).
> 
> As well we also now occasionally get a different error that causes the kernel
> to generate a scsi card register dump and causes the program that was accessing
> the tape drive to block in the kernel in an unkillable state.  We actually
> have to power cycle the machine in order to get the scsi controller working
> again.  The register dump is 103 lines long so I won't include it in this 
> message, but if you want to see it you can get it from 
> 
> 	http://www.mcs.vuw.ac.nz/~duncan/ahc-dump.txt

This is probably caused by the drive misbehaving too (which causes the command
to timeout)

> 
> So at this stage I'm still not sure whether we are looking at a (second)
> faulty tape drive (or scsi controller) or whether there are perhaps problems
> with the NetBSD ahc or st drivers.  Any advice would be gratefully accepted!

This really looks like as a hardware problem on the drive side again
I can't see how a faulty driver could cause such coherent SCSI sense messages.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--