[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-megaraid-devel
Subject:    RE: Megaraid monitoring.
From:       "Joshua D Rusch" <jdrusch () avatartechnology ! com>
Date:       2001-12-17 17:13:01
[Download RAW message or body]

What I ended up doing was this:
I just use the megamon with the option to log to a file. I used strings
on the megasrv binary (or whatever its called) to extract all the
potential error messages, and I just have a script that greps the log
file for a list keywords/phrases every couple of minutes. Of course if
something sets off the alarm, I have to reset the log file...but if a
RAID alarm goes off, I'm gonna be checking the system anyway, so its not
that big of a deal.

Unfortunately, I never did get an answer to that one point you
mentioned. I've stayed on the list in the hopes that I might see that
question answered in another thread, and to know about any new
software/drivers which might have different monitoring capabilities.

Hope this helps,

josh

-----Original Message-----
From: linux-megaraid-devel-admin@dell.com
[mailto:linux-megaraid-devel-admin@dell.com] On Behalf Of David Barnes
Sent: Monday, December 17, 2001 5:58 PM
To: linux-megaraid-devel@dell.com
Cc: David Barnes
Subject: Megaraid monitoring.



Hi -

over the past few months, I've gained experience with the "aacraid"
variety of Perc controllers.  Just this week we have received our first
"megaraid" variety of controller (a Perc 3/DC for a PE2450), and I am
(so far) less than impressed with the monitoring capability.

On the aacraid cards, one can use the 'afacli' utility to assess the
state of the array/s, including information such as the % complete
rebuild/scrub, amongst other things.

However, I can't see anything anywhere, either in the BIOS, or provided
via "megamgr"/"dellmgr" which tells what basic state the arrays are 
in.  Whether they are rebuilding, scrubbing, deteriorated, etc etc.

I have examined the contents of /proc/megaraid/0/*, and tried using
megamon (provided on the Dell site), but neither yield any particularly
useful information as far as I can tell.  Megamon managed to tell me it
was starting up:

RAID Monitor Service Ver Linux ---2.6 May 02, 2001 started

Initial CheckConsistency Schedule 
EnableFlag: 1
Date: 12/18/2001
DayOfWeek: 0
HourOfDay: 0
Week(s): 1
ReportChkonProgInterval: 0 seconds(0 means report in-frequently)

but there is no info. anywhere on how I might change the report 
frequency, nor is the file /etc/megamonitor/monitor particularly useful,
containing right now:

Adapter 1 Channel 2 Target 6: Device Slot #6 SCSI ID #15 was INSERTED .
--On 12/18/2001

Back in August, Joshua Rusch noted that:

"the /etc/megamonitor/monitor file
 contains the contents of only the last email that root received. If a
hard drive fails, is it possible for that file to not have a warning or
failure message in there if say MegaServ does a successful temperature
check or something like that?"

But I haven't seen a response to this particular point.  Matt Domsch
suggested that the megamon RPM should contain what Josh needed, but
alas, the specific point above has not been addressed.

I see that a number of emails are coming through to root though. 
That's at least a start, but an archive in /etc/megamonitor/monitor or
even /var/log/messages would be a big improvement.

Can anyone advise, please?

thanks - David.

_______________________________________________
Linux-megaraid-devel mailing list
Linux-megaraid-devel@dell.com
http://lists.us.dell.com/mailman/listinfo/linux-megaraid-devel
Please read the FAQ at http://lists.us.dell.com/faq or search the list
archives at http://lists.us.dell.com/htdig/


[prev in list] [next in list] [prev in thread] [next in thread]