RE: megaraid battery status questions

RE: megaraid battery status questions

[Mukker, Atul]

> I have been using the megaraid driver on a Dell system using 
> the PERC4 for
> several months now and have noticed that 
> /proc/megaraid/hba0/battery-status
> will report errors after reading it over time.  If I reboot 
> the system then
> the battery status errors go away until I poll again.  The 
> BIOS for the
> Megaraid doesn't report battery status errors in any of the 
> tests I have
> run.  The errors I see include "low voltage" and "charge fail".  In
> addition, I have seen the same "errors" across several 
> different systems so
> it isn't just a single adapter or system that is failing.

Can you provide your dmesg output and the information from *all* files from
the /proc/megaraid/hbaX/ directory


> 
> With my goal to poll raid status and battery status on a 
> periodic basis,
> does anyone have ideas on what mechanism I can use?  Ioctl?  
> Other programs?

If you have an application which issues the corresponding ioctl, the same
would work with 2.20.3.1 driver

RE: megaraid battery status questions

[Russell Johnson]

> > With my goal to poll raid status and battery status on a
> > periodic basis,
> > does anyone have ideas on what mechanism I can use?  Ioctl?  
> > Other programs?
> 
> If you have an application which issues the corresponding 
> ioctl, the same would work with 2.20.3.1 driver

I was able to get the 2.20.3.1 driver installed and it seems to work fine
now when the 350O firmware is installed.  Apparently the only working
combination is the 2.20.3.1 driver with the 350O firmware.  The older
firmware I had would report battery errors after a short while but this new
firmware hasn't reported an improper battery status yet.

Thanks for your help.

megaraid battery status questions

[Russell Johnson]

I have been using the megaraid driver on a Dell system using the PERC4 for
several months now and have noticed that /proc/megaraid/hba0/battery-status
will report errors after reading it over time.  If I reboot the system then
the battery status errors go away until I poll again.  The BIOS for the
Megaraid doesn't report battery status errors in any of the tests I have
run.  The errors I see include "low voltage" and "charge fail".  In
addition, I have seen the same "errors" across several different systems so
it isn't just a single adapter or system that is failing.

My goal is to poll for both battery status and raid status on a periodic
basis (every 5 minutes or so).  I have tried this on different kernels and
driver versions with the same result and I'm wondering if anyone else has
seen the same issue or found a solution.  I started with a 2.4.21 kernel and
tried a 2.10.x driver.  I'm currently running a 2.6.7 kernel with the 2.00.3
driver and the latest firmware I could find, dmesg reports "megaraid:
[350O:1.09]".  I have written some code similar to recent posts with the
title "megaraid megaraid2-2.10.7 causing kernel panic" and it is reporting
the same failure on all of the above setups that I have tried.  It seems
that the latest proper megaraid driver for kernel 2.6 versions might be the
2.20.3.1 version but it doesn't support the /proc files as the 2.0 and 2.10
drivers did.  I'm not sure if the new driver supports the same ioctl I'm
using or not.

With my goal to poll raid status and battery status on a periodic basis,
does anyone have ideas on what mechanism I can use?  Ioctl?  Other programs?

I have also noticed that it seems that the megaraid mailbox will not accept
new commands while the inquiry3 command is being executed.  Can anyone
verify that this is the case?  I can't find any information on the command
and its limitations.

Thanks for any help!

Russ Johnson