From owner-freebsd-scsi Wed Feb 12 0:58:37 2003 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 3D92B37B401 for ; Wed, 12 Feb 2003 00:58:35 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854C843F75 for ; Wed, 12 Feb 2003 00:58:34 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id h1C8wSD14954; Wed, 12 Feb 2003 00:58:28 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id AAA06488; Wed, 12 Feb 2003 00:58:17 -0800 (PST) Received: from btc.adaptec.com (hollin [10.100.253.56]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id BAA03242; Wed, 12 Feb 2003 01:58:14 -0700 (MST) Message-ID: <3E4A0C90.5000600@btc.adaptec.com> Date: Wed, 12 Feb 2003 01:57:52 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Brooks Cc: freebsd-scsi@freebsd.org Subject: Re: confusing aaccli output References: <20030212001508.U39971-100000@mail.econolodgetulsa.com> In-Reply-To: <20030212001508.U39971-100000@mail.econolodgetulsa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Josh Brooks wrote: > Hello, > > I am seeing this in aaccli: > > AAC0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 Mirror 34.1GB Open 0:01:0 64.0KB:34.1GB > /dev/aacd0 array01 0:00:0 64.0KB!34.1GB > > 1 Mirror 34.1GB Open 0:02:0 64.0KB:34.1GB > /dev/aacd1 array02 0:03:0 64.0KB:34.1GB > > > At first glance it looks fine. Two healthy containers. But what is that > exclamation point: > > 0:00:0 64.0KB!34.1GB > > Interesting. Now I look at /var/log/messages: > > > > Feb 9 17:26:36 system /kernel: aac0: **Monitor** Drive 0:0:0 returning > error > Feb 9 17:26:36 system /kernel: aac0: **Monitor** ID(0:00:0) - drive > failure (retries exhausted) > Feb 9 17:26:36 system /kernel: aac0: **Monitor** Mirror Container 0 Drive > 0:0:0 Failure > Feb 9 17:26:46 system /kernel: aac0: **Monitor** Mirror Failover > Container > 0 no failover assigned > > > > So what is going on here ? messages tell me I have a broken mirror, but > aaccli shows me a healthy one. As noted above, the card took scsi driver 0:0:0 offline due to errors, so the mirror is running in degraded mode. I admit that the output from aaccli isn't terribly obvious here... > > Iam afraid to run a: > > container set failover > > because aaccli shows it as already belonging to the container... Eh? 'container set failover' allows you to assign one or more drives as either global or dedicated spares. The firmware won't really let you add the failed drive as a spare (not without some tickery, at least), so you'll need to shove a new drive into the mix and assign it as the spare. You'll also need to enable automatic rebuilds, and then everything will be good to go. If you're really in a bind because you didn't budget for a spare drive (shame on you!), pull out the drive that was marked as failed, put it on a regular scsi controller, do a low-level format of it, then put it back on the aac controller and add it as the spare. There's a good chance, though, that if the drive failed once then it's going to fail again. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message