Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Aug 1999 02:14:07 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        questions@freebsd.org
Cc:        scsi@freebsd.org
Subject:   AHC errors. Bad disk or bad firmware, or bug in driver ? 
Message-ID:  <4.1.19990808234210.03c6b2d0@granite.sentex.ca>

next in thread | raw e-mail | index | archive | help

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:12 granite /kernel: sd2(ahc0:2:0): Target
Aug  8 20:53:12 granite /kernel: Busy
Aug  8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:12 granite last message repeated 3 times
Aug  8 20:53:12 granite /kernel: ahc0:A:2: ahc_intr - referenced scb not
valid during seqint 0x71 scb(7)
Aug  8 20:53:12 granite /kernel: ahc0: WARNING no command for scb 7 (cmdcmplt)
Aug  8 20:53:12 granite /kernel: QOUTCNT == 1
Aug  8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:12 granite last message repeated 27 times
Aug  8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target 
Aug  8 20:53:12 granite /kernel: Busy
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): Targ
Aug  8 20:53:12 granite /kernel: et Busy
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): T
Aug  8 20:53:12 granite /kernel: arget Busy
Aug  8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:20 granite last message repeated 79 times
Aug  8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
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
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Aug  8 20:53:47 granite /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Abort Message Sent
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 13 - Abort Tag Completed.
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): no longer in timeout
Aug  8 20:53:47 granite /kernel: Ordered Tag sent
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:47 granite last message repeated 3 times
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0xc - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Aug  8 20:53:47 granite /kernel: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Aug  8 20:53:47 granite /kernel: Ordered Tag queued
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while
recovery in progress
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0xc - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Aug  8 20:53:47 granite /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Abort Message Sent
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 12 - Abort Tag Completed.
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): no longer in timeout
Aug  8 20:53:47 granite /kernel: Ordered Tag sent
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:47 granite last message repeated 3 times
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0x0 - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Aug  8 20:53:47 granite /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Aug  8 20:53:47 granite /kernel: Ordered Tag queued

Aug  8 20:53:47 granite /kernel: Ordered Tag sent
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Tar
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:47 granite last message repeated 36 times
Aug  8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Bu
Aug  8 20:53:47 granite /kernel: sy
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:48 granite last message repeated 36 times
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target
Aug  8 20:53:48 granite /kernel: Busy
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:48 granite last message repeated 11 times
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): SCB 0x0 - timed out while
idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Aug  8 20:53:48 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Abort Message Sent
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): SCB 0 - Abort Tag Completed.
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): no longer in timeout
Aug  8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy
Aug  8 20:53:48 granite last message repeated 14 times
Aug  8 20:53:48 granite /kernel: s


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"

Thanks,

	---Mike
**********************************************************************
Mike Tancsa, Network Admin        *  mike@sentex.net
Sentex Communications Corp,       *  http://www.sentex.net/mike
Cambridge, Ontario                *  01.519.651.3400
Canada                            *


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990808234210.03c6b2d0>