From owner-freebsd-scsi Wed Jul 2 04:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA29527 for freebsd-scsi-outgoing; Wed, 2 Jul 1997 04:44:10 -0700 (PDT) Received: from weenix.guru.org (phantasma.bevc.blacksburg.va.us [198.82.200.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29511 for ; Wed, 2 Jul 1997 04:44:03 -0700 (PDT) Received: (from kmitch@localhost) by weenix.guru.org (8.8.5/8.8.5) id HAA00749 for scsi@freebsd.org; Wed, 2 Jul 1997 07:44:01 -0400 (EDT) From: Keith Mitchell Message-Id: <199707021144.HAA00749@weenix.guru.org> Subject: Archive Viper and 3940UW (bad Drive?) To: scsi@freebsd.org Date: Wed, 2 Jul 1997 07:44:01 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Lately I have been having trouble getting my tape drive to work at all. I get BUS resets everytime I try to access the drive. I have tried moving it to a different BUS. using different cables as well as trying every statement in the SCSI-Select software of my 3940UW card. I know the BUS is terminated correctly (I have tried allowing the last drive on the chain [a wide drive] terminate the BUS and I have also tried using a self-terminating cable [one that has the terminator moded in at the end of the cable]). The verbose probe message for the drive is: st0 at scbus2 target 4 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x13, 512-byte blocks, write-enabled and the BUS reset messages I get are: st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 st0: abort message in message buffer st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x94 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc1: Issued Channel A Bus Reset. 3 SCBs aborted Clearing bus reset Clearing 'in-reset' flag st0: no longer in timeout ahc1: target 0 using 16Bit transfers st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 st0: abort message in message buffer st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x94 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc1: Issued Channel A Bus Reset. 3 SCBs aborted Clearing bus reset Clearing 'in-reset' flag st0: no longer in timeout ahc1: target 0 using 16Bit transfers st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 st0: abort message in message buffer st0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x94 SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc1: Issued Channel A Bus Reset. 3 SCBs aborted Clearing bus reset Clearing 'in-reset' flag st0: no longer in timeout ahc1: target 0 using 16Bit transfers sd2: UNIT ATTENTION asc:29,0 sd2: Power on, reset, or bus device reset occurred , retries:1 ahc1: target 0 synchronous at 10.0MHz, offset = 0x8 My suspicion is that the drive has gone bad. It was working fine up until about the 6th of June and then this happened. Nothing has changed on the SCSI bus and I don't believe anything has changed in the SCSI code. I am running a -current system from around 6/25. Is this likely to be the drive or could it possibly be a cabling issue I forgot about?? BTW does anyone know how well a standard wide cable will work for ultra-wide devices?? -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved Unauthorized use or duplication prohibited