From owner-freebsd-questions Tue Aug 10 0: 1: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 60C0D14FC6; Tue, 10 Aug 1999 00:01:02 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id JAA23693; Tue, 10 Aug 1999 09:58:54 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id E1BFFCA; Tue, 10 Aug 1999 09:59:06 +0300 (EEST) Date: Tue, 10 Aug 1999 09:59:06 +0300 From: Vallo Kallaste To: "Kenneth D. Merry" Cc: Mike Tancsa , questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? Message-ID: <19990810095906.A2512@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> <199908091705.LAA29115@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908091705.LAA29115@panzer.kdm.org>; from Kenneth D. Merry on Mon, Aug 09, 1999 at 11:05:02AM -0600 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 09, 1999 at 11:05:02AM -0600, "Kenneth D. Merry" wrote: > > Aug 8 20:53:21 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 > > SSTAT1 = 0xa > > Aug 8 20:53:21 granite /kernel: Ordered Tag queued > > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while > > recovery in progress > > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xc timedout while > > recovery in progress > > Aug 8 20:53:26 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while > [ ... ] > > > > And then the target busy just keeps repeating itself over and over. I had > > to reboot the machine and unfortunately, it had a few errors, pretty well > > all of which we were able to recover. The drive in question is a Viking II > > > > (ahc0:2:0): "QUANTUM VIKING II 4.5WSE 4110" type 0 fixed SCSI 2 > > sd2(ahc0:2:0): Direct-Access 4350MB (8910423 512 byte sectors) > > ahc0: target 4 Tagged Queuing Device > > > > If it was simply a media error, would it not either recover or panic ? Why > > the seemingly endless loop of "Target Busy" > > It smells like bogus firmware, but it's kinda hard to say. You might check > to see whether there is new firmware available for that disk. Quantum has > firmware and firmware loaders on their ftp site. I do have two of these drives and upgraded the firmware quite a while ago, had problems with older firmware, possibly relative to my ncr based controller. For now I'm running with these about a year without any problems. For what it's worth, they have working 64 tags also. I'm satisfied :) da0 at ncr0 bus 0 target 5 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ncr0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message