From owner-freebsd-scsi  Wed Sep 24 12:17:39 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA19678
          for freebsd-scsi-outgoing; Wed, 24 Sep 1997 12:17:39 -0700 (PDT)
Received: from dev-null.aero.und.edu (dev-null.aero.und.edu [134.129.214.74])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19670
          for <freebsd-scsi@freebsd.org>; Wed, 24 Sep 1997 12:17:36 -0700 (PDT)
Received: (from rand@localhost)
	by dev-null.aero.und.edu (8.8.5/8.8.7) id OAA02649;
	Wed, 24 Sep 1997 14:17:27 -0500 (CDT)
Date: Wed, 24 Sep 1997 14:17:27 -0500 (CDT)
Message-Id: <199709241917.OAA02649@dev-null.aero.und.edu>
From: "Douglas K. Rand" <rand@aero.und.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-scsi@freebsd.org
Subject: Target Busy errors w/XP34300W & AH2940
X-Mailer: VM 6.22 under 19.15 XEmacs Lucid
X-Face: $L%T~#'9fAQ])o]A][d7EH`V;"_;2K;TEPQB=v]rDf_2s%<d5}=?&`PeE)<@]
 fT6ejN-VVK,Fej'k6570?"R$}bLKm84G-S?"!F8vaZ*8h}mM;@Xs%\I@8p8Rc
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've been getting some reoccuring errors with Quantum XP34300W disk
drives on an Adaptec 2940 controller under 2.2.2-RELEASE. It started
on one disk, so I called Quantum and returned it. 2 days after
shipping it, the other disk in the machine started reporting the same
errors. The replacement drive came in earlier this week and
immediately started with the same problems. 

After scanning the archives folks said that heat could be the cause as
well as bad SCSI cables. I'm on my third cable, and with the new drive
it displayed the problem as soon as I got the system booted. I also
don't think its the drives, not with three showing the exact same
problems. 

The error usually manifests itself with dumps of the file system, but
fsck can also cause it. As can iozone. Using "iozone raw=/dev/sd0a"
(or on any other partition) immediately causes the errors, where as
iozone to a file or fsck or dump only sometimes cause the problem.

Here are the errors:

sd0(ahc0:0:0): Target Busy
sd0(ahc0:0:0): SCB 0x2 - timed out in datain phase, SCSISIGI == 0x44
SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
sd0(ahc0:0:0): abort message in message buffer
sd0(ahc0:0:0): SCB 0x1 - timed out in datain phase, SCSISIGI == 0x54
SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2
ahc0: Issued Channel A Bus Reset. 2 SCBs aborted
Clearing bus reset
Clearing 'in-reset' flag
sd0(ahc0:0:0): no longer in timeout
ahc0: target 0 using 16Bit transfers
sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 , retries:3
ahc0: target 0 synchronous at 10.0MHz, offset = 0x8

-- 
Douglas K. Rand                                              rand@aero.und.edu
System/Network Administrator      Scientific Computing Center -- UND Aerospace
Office: +1 701 777 2801                             University of North Dakota
FAX:    +1 701 777 2940                   Box 9022, Grand Forks ND  58202-9022
 echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc