Unsolved

This post is more than 5 years old

2 Posts

344543

January 21st, 2011 06:00

BBU enabled/disabled errors

Hi Everyone,

 

I have a PE 2950 with a perc 5/i in it - running FreeBSD.About once a day I am getting messages like this in the system log:

Jan 20 16:45:44 sys kernel: mfi0: 7269 (348852232s/0x0008/1) - BBU disabled; changing WB virtual disks to WT
Jan 20 16:45:44 sys kernel: mfi0: 7270 (348852232s/0x0001/0) - Type 21: Policy change on VD 00/0 to [ID=00,dcp=01,ccp=00,ap=0,dc=0,dbgi=0] from
[ID=00,dcp=01,ccp=01,ap=0,dc=0,dbgi=0]
Jan 21 05:09:41 sys kernel: mfi0: 7271 (348896757s/0x0008/0) - BBU enabled; changing WT virtual disks to WB
Jan 21 05:09:41 sys kernel: mfi0: 7272 (348896757s/0x0001/0) - Type 21: Policy change on VD 00/0 to [ID=00,dcp=01,ccp=01,ap=0,dc=0,dbgi=0] from
[ID=00,dcp=01,ccp=00,ap=0,dc=0,dbgi=0]

I am assuming that the RAID is noticing that the BBU is not charged enough to support WB so it disables WB and moves the disk over to WT. Does this point to the battery needing to be replaced?

About 25 days ago the server rebooted and presented the error message of 'E1422 cpu machine chk'. I ran the diags off of the bootable CD at that point and everything came back as being fine so I am not sure if the two errors are unrelated or not.

Thanks for any insight.

 

 


9 Legend

 • 

16.3K Posts

January 21st, 2011 08:00

Probably not related.

The PERC 5/6 is programmed to completely discharge the battery - called a learning cycle - every 90 days.  If you have a way to pull the entire PERC log, it will probably say when the next scheduled cycle is.  That said, a dying battery is also not out of the question, just not as likely as the learning cycle.

Machine Chk errors and memory errors on the 2950 is VERY common for early BIOS revisions.  Seeing as how you have a PERC 5, I am going to assume that the BIOS has never been updated and is probably in dire need of an update. 

2 Posts

January 21st, 2011 11:00

I am getting these BBU disabled/enabled about once a day so I was assuming it wasn't part of the regular learning cycle. Would that be a correct assumption? I have seen what look to be regular learning cycles in the logs before at regular intervals and the driver would log when it was X number of days away from a relearn. I don't get any of that when these more frequent messages. So given that, I was leaning towards the battery needing to be replaced. Make sense?


Thanks for the help.

 

 

 

9 Legend

 • 

16.3K Posts

January 21st, 2011 12:00

That's a good assumption ... you should not be getting it every day.  One more thing I'd consider:

  • Reseating the RAID components (controller card and battery cable).
  • Updating system BIOS, ESM/BMC, and RAID firmware.  It is the RAID controller that manages the battery state, and the battery has a known issue that's complicating management, it could be corrected by an update.

Just a thought ... otherwise, replacing the battery has a 99% chance of correcting the problem (1% chance of the controller or connector being bad, as it is the controller that is responsible for charging the battery).

13 Posts

August 3rd, 2011 08:00

I too just got this error today.  Our server rebooted and it's our main file server, I then went into OpenManage and noticed that our 2nd drive (which is mirrored) has now become a foreign disk (both of them).  Problem now is there doesn't seem to be an option to put it back to normal

1 Message

February 1st, 2012 11:00

You'll need to reboot into the RAID manager (CTRL+R), press F2 and select 'Foreign Disks > Import'

Top