From owner-freebsd-scsi@FreeBSD.ORG  Mon Nov 13 22:38:24 2006
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
X-Original-To: freebsd-scsi@freebsd.org
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3836B16A4AB
	for <freebsd-scsi@freebsd.org>; Mon, 13 Nov 2006 22:38:24 +0000 (UTC)
	(envelope-from jfruge4@lsu.edu)
Received: from gate012.lsu.edu (gate012.ocs.lsu.edu [130.39.184.214])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4CC1443E80
	for <freebsd-scsi@freebsd.org>; Mon, 13 Nov 2006 22:34:49 +0000 (GMT)
	(envelope-from jfruge4@lsu.edu)
Received: from [130.39.198.198] ([130.39.198.198])
	by gate012.lsu.edu (Lotus Domino Release 6.0.3)
	with ESMTP id 2006111316342835-5259 ;
	Mon, 13 Nov 2006 16:34:28 -0600 
From: Joshua =?ISO-8859-1?Q?Frug=E9?= <jfruge4@lsu.edu>
To: freebsd-scsi@freebsd.org
Date: Mon, 13 Nov 2006 16:34:28 -0600
Message-Id: <1163457268.15851.17.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Subject: problems with serverraid 8i on an ibm x260
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2006 22:38:24 -0000

Hello,

	I am running freebsd 6.1 (amd64) on an ibm x260 and getting these
errors:

dmesg:
g_vfs_done():aacd0s1a[WRITE(offset=3D16567468032, length=3D16384)]error =3D=
 5
aacd0: hard error cmd=3Dwrite 1673028351-1673028382

and in messages :
Nov 12 23:59:14 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT
AFTER 50189 SECONDS
Nov 12 23:59:34 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT
AFTER 50209 SECONDS
Nov 12 23:59:54 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT
AFTER 50229 SECONDS


The system will lock, and require a manual reboot. =20

Has anyone run into this before, or can point me in the right direction
to look for answers?

Thanks,
--=20
Joshua Frug=C3=A9
jfruge4@lsu.edu
Louisiana State University
Information Technology Services=20