From owner-freebsd-hardware Wed Jan 31 12:14:54 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D9B4937B69D for ; Wed, 31 Jan 2001 12:14:36 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0VKFCW00827; Wed, 31 Jan 2001 12:15:12 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101312015.f0VKFCW00827@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Corris Randall Cc: freebsd-hardware@freebsd.org Subject: Re: aac driver with Dell Perc 3si (scsi errors) In-reply-to: Your message of "Wed, 31 Jan 2001 08:39:44 PST." <20010131163944.14146.qmail@web11606.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Jan 2001 12:15:12 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hi all, > > I have a Dell Poweredge 2450 with the Dell PERC 3si > RAID controller and 5 36GB Quantum disks. Since the > aac isn't on the 4.2 cd, I assume it's not for that > release. I'm running 5.0-20010119-CURRENT. this is > the error I'm getting. is it bad? is it unsolvable? > should I return the perc3 and get an adaptec 2100s? > > aac0: ** ID(0:03:0); Unexpected Bus Free [command:0x28] > aac0: ** ID(0:03:0); Error Event [command:0x28] > aac0: ** ID(0:03:0); Unit Attention [k:0x6,c:0x29,q:0x86] > aac0: ** ID(0:03:0); Power On, Reset, or Bus Device Reset > aac0: ** SCSI Channel[0]: Timeout Detected On 1 Command(s) > aac0: ** ID(0:03:0); Aborted Command [command:0x2a] > aac0: ** ID(0:03:0); Unexpected Bus Free [command:0x28] > aac0: ** ID(0:03:0); Error Event [command:0x28] > aac0: ** ID(0:03:0); Unit Attention [k:0x6,c:0x29,q:0x86] > aac0: ** ID(0:03:0); Power On, Reset, or Bus Device Reset These are SCSI errors reported directly by the controller. The 'aac' manpage doesn't have a comprehensive DIAGNOSTICS section because many of the useful messages come to us preformatted by the controller - they're printed with the '**' leader so you can tell that. Your problem is cabling, termination or drive firmware, and swapping to another controller won't help. You might want to start by seeing if you can't get a firmware update for your drives from Quantum; you can also do all the usual cable checking, etc. In the sample above, at least, you're only getting errors on the drive at ID 3; if you never see these errors for any other drive, you can narrow your search somewhat. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message