From owner-freebsd-questions@FreeBSD.ORG Fri May 16 20:29:07 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA526106566B for ; Fri, 16 May 2008 20:29:07 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 8C6FF8FC13 for ; Fri, 16 May 2008 20:29:07 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.2) with ESMTP id m4GKT5dr072914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 16 May 2008 15:29:05 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.2/Submit) id m4GKT5QG072910; Fri, 16 May 2008 15:29:05 -0500 (CDT) (envelope-from dan) Date: Fri, 16 May 2008 15:29:05 -0500 From: Dan Nelson To: Robert Jesacher Message-ID: <20080516202904.GJ4461@dan.emsphone.com> References: <4820B502.8000009@smartt.com> <20080506200245.GA4083@sandvine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.0-STABLE User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Chris St Denis , freebsd-questions@freebsd.org Subject: Re: AAC driver. No kernel error messages for failed raid5? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 20:29:07 -0000 In the last episode (May 16), Robert Jesacher said: > On 06.05.2008, at 22:02, Ed Maste wrote: >> On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: >>> I pulled out one of the raid5 drives to test the functionality and >>> noticed that FreeBSD didn't seem to notice the disk failure at all. >>> I was expecting kernel messages about it, but got nothing. >> >> This is missing functionality in the aac(4) driver. For now about >> the best you can do is regularly poll the status using Adaptec's CLI >> tool "arcconf." >> >> -ED > > The tool you need to look into is: sysutils/aaccli . I think arctool > is only for arcmsr-devices. unfortunately aaccli doesn't provide the > possibility to use it with parameters, so you probably need to use it > with an expect-script. aaccli is most definitely scriptable: $ aaccli "open /readonly aac0 : enclosure show status : disk show smart : container list /full" -- Dan Nelson dnelson@allantgroup.com