Date: Fri, 16 May 2008 15:29:05 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Robert Jesacher <jessy@sicha.net> Cc: Chris St Denis <chris@smartt.com>, freebsd-questions@freebsd.org Subject: Re: AAC driver. No kernel error messages for failed raid5? Message-ID: <20080516202904.GJ4461@dan.emsphone.com> In-Reply-To: <AF4FF84A-5F14-4189-8D2C-1D7A5A5B7EC2@sicha.net> References: <4820B502.8000009@smartt.com> <20080506200245.GA4083@sandvine.com> <AF4FF84A-5F14-4189-8D2C-1D7A5A5B7EC2@sicha.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080516202904.GJ4461>