From owner-aic7xxx@FreeBSD.ORG Fri Apr 15 13:23:50 2005 Return-Path: Delivered-To: aic7xxx@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E378016A4CE for ; Fri, 15 Apr 2005 13:23:49 +0000 (GMT) Received: from frodo.hserus.net (frodo.hserus.net [204.74.68.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC3D43D45 for ; Fri, 15 Apr 2005 13:23:49 +0000 (GMT) (envelope-from kiko@async.com.br) Received: from 200-171-140-32.dsl.telesp.net.br ([200.171.140.32]:41231 helo=anthem.async.com.br) by frodo.hserus.net with esmtps (Cipher TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 4.50 #1) id 1DMQnS-000Aam-08 for ; Fri, 15 Apr 2005 18:53:47 +0530 Received: from anthem.async.com.br (kiko@localhost.localdomain [127.0.0.1]) by anthem.async.com.br (8.12.3/8.12.3) with ESMTP id j3FDNbO1011891 for ; Fri, 15 Apr 2005 10:23:37 -0300 Received: (from kiko@localhost) by anthem.async.com.br (8.12.3/8.12.3/Debian-7.1) id j3FDNZem011889 for aic7xxx@freebsd.org; Fri, 15 Apr 2005 10:23:35 -0300 From: Christian Robottom Reis Date: Fri, 15 Apr 2005 10:23:35 -0300 To: AIC7xxx Mailing List Message-ID: <20050415132335.GA11591@www.async.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Async Open Source, Brazil User-Agent: Mutt/1.5.6+20040907i Subject: 2940A failing mt operations with Medium Error X-BeenThere: aic7xxx@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Adaptec Device Drivers in FreeBSD and Linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 13:23:50 -0000 Hello there, We're having a problem with our SDT-9000 DDS-3 tape drive, which is attached to a rather puny 2940A. We had it installed on a little Pentium MMX and it was working fine, but since moving it last week to a more modern machine, we've been getting error on all mt operations. The kernel complaint is below. This is what I'm running: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.3.9 aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs Vendor: SONY Model: SDT-9000 Rev: 0601 Type: Sequential-Access ANSI SCSI revision: 02 st: Version 20040102, bufsize 32768, max init. bufs 4, s/g segs 16 The messages below indicates a Medium Error/Cartidge fault, but no matter if I try with a new cartridge or old, the same error ensues. st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Cartridge fault scsi0: Recovery Initiated scsi0: Dumping Card State while idle, at SEQADDR 0x7 >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ACCUM = 0x4f, SINDEX = 0x47, DINDEX = 0x25, ARG_2 = 0x0 HCNT = 0x0 SCBPTR = 0x0 SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1] SCSISEQ[0x12] SBLKCTL[0x0] SCSIRATE[0x0] SEQCTL[0x10] SEQ_FLAGS[0xc0] SSTAT0[0x5] SSTAT1[0xa] SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x0] SIMODE1[0xa4] SXFRCTL0[0x80] DFCNTRL[0x0] DFSTATUS[0x2d] STACK: 0x0 0x164 0x1a5 0x3 SCB count = 5 Kernel NEXTQSCB = 4 Card NEXTQSCB = 4 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 0:3 QOUTFIFO entries: Sequencer Free SCB List: 1 2 Sequencer SCB Info: 0 SCB_CONTROL[0x44] SCB_SCSIID[0x47] SCB_LUN[0x0] SCB_TAG[0x3] 1 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] Pending list: 3 SCB_CONTROL[0x40] SCB_SCSIID[0x47] SCB_LUN[0x0] Kernel Free SCB list: 2 1 0 Untagged Q(4): 3 scsi0: Host Status: Failed(0) DevQ(0:4:0): 0 waiting <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (scsi0:A:4:0): SCB 0x3 - timed out sg[0] - Addr 0x298000 : Length 32768 (scsi0:A:4:0): Queuing a BDR SCB (scsi0:A:4:0): Bus Device Reset Message Sent Recovery SCB completes scsi0: Bus Device Reset on A:4. 1 SCBs aborted st0: Error 70000 (sugg. bt 0x0, driver bt 0x0, host bt 0x7). st0: Error 8 (sugg. bt 0x0, driver bt 0x0, host bt 0x0). st0: Error on write filemark. st0: Error 8 (sugg. bt 0x0, driver bt 0x0, host bt 0x0). Does it look like a busted drive, adapter, bad terminator, bad power supply or perhaps all at once? Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331