Here we go again

[Justin Bennett]

For those who helped with my HP vs80 drive problems, thanks, Hp
overnighted a replacement and it works. I have 2 existing DLT8000 Drives, 
On their own Adaptes 2940 card, ID 3 and 4, The one drive works fine (st0)
the other drive (st1) I get parity errors and the drive is unusable. This
another HP replacement scenario?


[root at coyote root]# tar -tvf /dev/st1 --blocking-factor 128
tar: /dev/st1: Cannot read: Input/output error
tar: At beginning of tape, quitting now
tar: Error is not recoverable: exiting now
[root at coyote root]#

(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x1b6)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x1b6)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x165)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x165)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x165)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x1b6)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x1b6)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x1b6)
SCSIRATE(0
x88)
(scsi0:A:4:0): parity error detected in Data-in phase. SEQADDR(0x165)
SCSIRATE(0
x88)
(scsi0:A:4:0): Unexpected busfree in Data-in phase
SEQADDR == 0x1b6
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).


Since the other drive works and this one doesn't I'm thinking HW problem.

But as usual any ideas are welcome.

Thanks
Justin


-- 
-------------------------------------------
Justin Bennett
Red Hat (Linux) Certified Engineer
Network Administrator
Dynabrade Inc.
8989 Sheridan Dr
Clarence, NY 14031
716-631-0100 ext 215