RAID Battery failed (other than expired)

Question

Level 1

12 points

RAID Battery failed (other than expired)

hello,
I've not even 1yr old Mac Pro with MB535PL/XXX/RAID,
Logs say in RAID logs that: `Battery failed (code 0x#0 = 18)', hard to imagine that it is battery fault.
I would like to know if there is any known solution because hw support wants me to send whole Mac to them.
Please check screenshot for more RAID Utility logs.
http://dl.dropbox.com/u/11758451/raid_bat.png

TIA
BRGRDS
LVJ

Mac Pro, Mac OS X (10.6.5)

Posted on Dec 15, 2010 3:54 AM

Reply

Answer 1

pi22-7__

Level 1

60 points

Feb 28, 2011 8:01 AM in response to lvj

Exactly the same issue here. Mac Pro is new as of Nov 2010. I will call Apple ( this is the second time the card has been an issue in less than 6 months) and see what they say. Will report back.

Reply

Answer 2

Feb 28, 2011 8:56 AM in response to pi22-7__

The RAID card reconditions its battery from time-to-time. During the interval when the battery is discharged, it may report that the RAID cache is disabled (and you are enduring longer writes because of that). It should charge up and start using the write cache again within a few hours.

The link above that says it is a log goes to the right site, but reports 404 not found. You can just paste your log (even a fairly long one) into a posting window.

Reply

Answer 3

pi22-7__

Level 1

60 points

Feb 28, 2011 10:18 AM in response to Grant Bennet-Alder

Grant Bennet-Alder wrote:
You can just paste your log (even a fairly long one) into a posting window.

Here is my exported report

Monday, February 28, 2011 10:13:40 AM PT Write cache disabled due to insufficient battery charge informational
Sunday, February 27, 2011 3:55:50 PM PT Battery failed (code 0x#0 = 18) critical
Sunday, February 27, 2011 3:56:03 PM PT Write cache disabled due to insufficient battery charge informational
Monday, December 20, 2010 4:12:54 AM PT Battery finished conditioning informational
Sunday, December 19, 2010 9:35:12 PM PT Battery started conditioning cycle (write cache disabled) informational
Sunday, December 19, 2010 9:23:37 PM PT Battery started conditioning cycle (write cache disabled) informational
Saturday, December 18, 2010 1:17:10 AM PT Battery finished conditioning informational
Friday, December 17, 2010 7:30:07 PM PT Battery started scheduled conditioning cycle (write cache disabled) informational
Sunday, December 31, 2000 5:16:41 PM PT Write cache disabled due to insufficient battery charge informational

Reply

Answer 4

lvj Author

Level 1

12 points

May 5, 2011 11:39 PM in response to Grant Bennet-Alder

Hi, this is my whole log since attaching the card.

Thursday, April 28, 2011 8:23:47 AM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, April 18, 2011 12:17:09 PM Poland Time Write cache disabled due to insufficient battery charge informational

Friday, April 15, 2011 12:31:04 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, March 28, 2011 8:52:28 PM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, March 27, 2011 1:40:53 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, March 14, 2011 11:24:20 AM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, March 13, 2011 5:41:10 PM Poland Time Battery failed (code 0x#0 = 18) critical

Sunday, March 13, 2011 5:41:22 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, March 7, 2011 4:34:36 PM Poland Time Battery finished conditioning informational

Monday, March 7, 2011 9:33:31 AM Poland Time Battery started scheduled conditioning cycle (write cache disabled) informational

Monday, March 7, 2011 8:14:19 AM Poland Time Write cache disabled due to insufficient battery charge informational

Saturday, March 5, 2011 8:44:39 AM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, February 27, 2011 7:48:08 PM Poland Time Write cache disabled due to insufficient battery charge informational

Wednesday, February 23, 2011 3:23:56 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, February 14, 2011 12:50:45 PM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, February 13, 2011 8:44:28 AM Poland Time Write cache disabled due to insufficient battery charge informational

Tuesday, February 8, 2011 11:23:02 PM Poland Time Write cache disabled due to insufficient battery charge informational

Friday, January 28, 2011 5:33:49 PM Poland Time Battery failed (code 0x#0 = 18) critical

Friday, January 28, 2011 5:33:48 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, January 24, 2011 10:50:30 AM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, January 17, 2011 11:59:31 AM Poland Time Write cache disabled due to insufficient battery charge informational

Thursday, January 6, 2011 4:11:33 PM Poland Time Write cache disabled due to insufficient battery charge informational

Wednesday, January 5, 2011 3:16:53 AM Poland Time Battery failed (code 0x#0 = 18) critical

Wednesday, January 5, 2011 3:17:02 AM Poland Time Write cache disabled due to insufficient battery charge informational

Friday, December 31, 2010 2:37:30 PM Poland Time Write cache disabled due to insufficient battery charge informational

Monday, December 20, 2010 4:03:06 PM Poland Time Write cache disabled due to insufficient battery charge informational

Wednesday, December 15, 2010 1:00:33 PM Poland Time Write cache set to battery detect informational

Wednesday, December 15, 2010 1:00:20 PM Poland Time Write cache temporarily enabled informational

Saturday, December 11, 2010 7:00:11 AM Poland Time Battery failed (code 0x#0 = 18) critical

Saturday, December 11, 2010 7:00:12 AM Poland Time Write cache disabled due to insufficient battery charge informational

Wednesday, December 1, 2010 11:17:34 PM Poland Time Battery finished conditioning informational

Wednesday, December 1, 2010 4:46:07 PM Poland Time Battery started conditioning cycle (write cache disabled) informational

Wednesday, December 1, 2010 4:22:20 PM Poland Time Battery started conditioning cycle (write cache disabled) informational

Tuesday, November 2, 2010 5:40:07 PM Poland Time Write cache disabled due to insufficient battery charge informational

Friday, October 29, 2010 9:35:08 AM Poland Time Controller detected disorderly shutdown without battery backup critical

Tuesday, November 2, 2010 5:19:11 PM Poland Time Write cache disabled due to insufficient battery charge informational

Friday, October 29, 2010 9:36:14 AM Poland Time Write cache disabled due to insufficient battery charge informational

Tuesday, October 19, 2010 12:58:09 PM Poland Time Write cache disabled due to insufficient battery charge informational

Tuesday, August 24, 2010 12:17:16 AM Poland Time Battery finished conditioning informational

Monday, August 23, 2010 5:11:50 PM Poland Time Battery started scheduled conditioning cycle (write cache disabled) informational

Wednesday, August 18, 2010 5:27:59 PM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, August 15, 2010 4:08:23 PM Poland Time Write cache disabled due to insufficient battery charge informational

Thursday, June 17, 2010 2:34:45 PM Poland Time Write cache disabled due to insufficient battery charge informational

Sunday, June 6, 2010 4:56:42 PM Poland Time Write cache disabled due to insufficient battery charge informational

Tuesday, May 25, 2010 5:11:29 PM Poland Time Battery finished conditioning informational

Tuesday, May 25, 2010 9:55:53 AM Poland Time Battery started conditioning cycle (write cache disabled) informational

Tuesday, February 23, 2010 1:04:33 PM Poland Time Battery finished conditioning informational

Tuesday, February 23, 2010 5:43:31 AM Poland Time Battery started scheduled conditioning cycle (write cache disabled) informational

Wednesday, November 25, 2009 5:43:30 AM Poland Time Battery finished conditioning informational

Tuesday, November 24, 2009 8:36:37 PM Poland Time Write cache set to battery detect informational

Tuesday, November 24, 2009 8:36:33 PM Poland Time Write cache temporarily enabled informational

Tuesday, November 24, 2009 8:36:30 PM Poland Time Write cache set to battery detect informational

Tuesday, November 24, 2009 8:36:18 PM Poland Time Write cache temporarily enabled informational

Tuesday, November 24, 2009 8:31:34 PM Poland Time Created volume “R1V1” on RAID set “RS1” informational

Tuesday, November 24, 2009 8:27:41 PM Poland Time Created RAID set “RS1” (RAID 0) informational

Tuesday, November 24, 2009 8:27:33 PM Poland Time Deleted RAID set “JBODSet1” informational

Tuesday, November 24, 2009 8:27:13 PM Poland Time Deleted RAID set “JBODSet2” informational

Tuesday, November 24, 2009 5:44:10 PM Poland Time Battery started conditioning cycle (write cache disabled) informational

Tuesday, November 24, 2009 1:38:34 PM Poland Time Battery started conditioning cycle (write cache disabled) informational

Reply

Answer 5

Sep 24, 2012 6:59 PM in response to lvj

same issue, i got 2 raid cards from support. never resolved. i gave up. been running this way on a 2 x 3.2 Quad core Xeon for years.

sad but true

Now i see my serial # does not even show....

Reply

Answer 6

norec

Level 1

0 points

Nov 28, 2012 9:41 PM in response to lvj

Same issue here too! So does "Battery failed (other than explained)" mean that the battery is dead??

The Xserve also has the.warden's issue where the serial # is no longer being shown.

Can anyone help, or is the server getting ready to explode! =P

Reply

Answer 7

herka

Level 1

0 points

Apr 9, 2013 3:32 AM in response to lvj

i cant believe noone has nothing to say about this as i can see internet full of this problem and ppl still trying to find a solution.

i have this issue on 6 different mac pro's. Getting the same error over and over again. We tried changing hard drives, batterys few times but still the same issue.

anyone with a solving post about this issue?

Reply

Answer 8

lvj Author

Level 1

12 points

Apr 9, 2013 1:50 PM in response to herka

@herka,

I had mine card replaced, unfortunetly it wasn't warranty replacement, but since then I have no problems with it.

Reply