Date: Mon, 9 Aug 1999 11:05:02 -0600 (MDT) From: "Kenneth D. Merry" <ken@kdm.org> To: mike@sentex.net (Mike Tancsa) Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? Message-ID: <199908091705.LAA29115@panzer.kdm.org> In-Reply-To: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> from Mike Tancsa at "Aug 9, 1999 02:14:07 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tancsa wrote... > > Hi, > I am running FreeBSD 2.2.8-STABLE #0: Thu Aug 5 box that ran into some > disk problems tonight. All of a sudden on my console, it was filled with > the following. > > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy > Aug 8 20:53:12 granite last message repeated 36 times > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Bu > Aug 8 20:53:12 granite /kernel: sy > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy > Aug 8 20:53:12 granite last message repeated 36 times [ ... ] > 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. You would probably do a lot better if you went to 3.x/CAM. The new CAM SCSI subsystem can generally handle unruly drives much better than the old SCSI subsystem. (In fact, we used Quantum Atlas II's with bogus firmware to test some of the error recovery code.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908091705.LAA29115>