Date: Fri, 10 Oct 2003 04:36:06 -0600 From: "Aaron Wohl" <freebsd@soith.com> To: "Josh Brooks" <user@mail.econolodgetulsa.com>, "Scott Long" <scottl@freebsd.org> Cc: freebsd-scsi@freebsd.org Subject: Re: confusing aaccli output ... Message-ID: <20031010103606.415923B222@www.fastmail.fm> In-Reply-To: <20031005202453.B54619-100000@mail.econolodgetulsa.com> References: <20031005202453.B54619-100000@mail.econolodgetulsa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Does anyone have a script to run aaccli a few times a day and see if the raid is happy? It used to be easy with dptutil (previous control program from adaptec for the 3200s)... each status had "Optimal" which changed to Degraded or whatever. aaccli seems geared more twords doing things to the raid than providing status. Id like to know what all the possible failures are and how to check for them with aaccli. I have a cron job check the status every few hours... but with aaccli ive never been sure I checked for all the failure kinds.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031010103606.415923B222>