Raid battery refreshment
Does anybody know how I can initiate the battery refreshment manually. After an interrupted raid card battery refreshment procedure I get permanently an error message and the raid cache is disabled. I don’t like to wait 3 months until the battery refreshment procedure will start automatically. It seems that there is not an menu option to do this.
Oh yeh just thought I'd add a screen shot of the raid utility log.
Similar Messages
-
RAID BATTERY CONDITIONING, HELPFUL INFO.
Point of Information: It took my MPRO 6 hours and 30 minutes (exactly) to complete the battery conditioning process, from a status of completely charged. It may not take this long if, for example, your battery is partially discharged. I spoke with an Apple Product Specialist via telephone who advised that there is no documented time parameters with regard to the conditioning process. He did advise that cache size, as related to the individual drives is a correlative variable. The Product Specialist also advised that I could carry on all normal work tasks while the conditioning process was active. He did state that I might notice slightly inhibited overall system performance until the conditioning process was completed, and the related write caches were re-enabled. IT IS VERY IMPORTANT not to reboot or shutdown your system during this process. If you do, the conditioning process will start all over from the beginning. For some unknown reason, my MacPro insists on 2 cycles of the aforementioned conditioning process resulting in about 13 hours total time allocated. After the first conditioning cycle is complete (battery shows charged and not conditioning), I have to shut the MacPro down, wait a few minutes and start it again. At that point, after a few minutes, the RAID Utility enters into another conditioning cycle. If I don't intentionally allow for the second conditioning cycle, it will automatically enter into the second conditioning cycle the next time I start the computer resulting in write caches being disabled and a drop in system performance prohibitive to editing and post-production workflow processes in FCPro/Motion, etc...
The entire conditioning process can be monitored in more detail (in conjunction with the Raid Utility) using the OS's System Profiler utility. Open the System Profiler utility and select the "Hardware RAID" option on the left. From the System Profiler, you can monitor whether the battery is charging or discharging. The following information is displayed in Syst. Profiler:
Hardware RAID
Battery Info:
Firmware Revision: 1.0d19
First Installed: 3/8/07 3:10 AM
Last Date Conditioned: Unknown
State: Working battery
Fault: Normal battery operation
Status:
Charging: No
Conditioning: Yes
Connected: Yes
Discharging: Yes
Sufficient Charge: No
Here you can see that my RAID syst. is conditioning the battery; is currently discharging the battery, and there is not a sufficient charge. It is important to note that the system profiler does not automatically update it's own status real-time, i.e., you must refresh (command + R) the window to get the latest status.I found that, at the end of the conditioning cycle, if I allow the battery to continue charging for 9 hours after system profiler and the raid utility indicate a full charge, the computer does not enter into a subsequent, charging cycle. Accordingly, I can only deduce that either:
1. although both the system profiler and the raid utility indicated a full charge, the battery has not actually reached a full charge, and thus enters into a subsequent conditioning cycle upon the next restart / boot.
2. The raid card battery is bad, or on the way out (not even a year old).
Apple Product Specialists (APS) have been very helpful, overall, and have shipped me a new replacement battery. While there are no specific battery replacement instructions available to the public, the APS I spoke with excerpted replacement instructions from the Apple Technician training manual and emailed me these. I have these available if anybody needs them. I will be happy to email them to you as I don't think I can post them anywhere here. You can find an email address to reach me under my profile. -
F0531 error - RAID battery inoperable
I see these 2 errors in few of our blades after upgrading them to 2.1(3a).
F1237 - Health LED of server 1/1 shows error. Reason:RAID_BATT_FLT:Sensor Failure Asserted;
F0531 - RAID Battery on server 1/1 operability:inoperable. Reason:
Any inputs on these errors?
Thanks
SubbuHi Sye,
This error is most commonly seen when the battery needs to be replaced in a UCS B440.
Fault Code:F0531
Message
This fault occurs when the RAID battery voltage is below the normal operating range.
Recommended Action
Step 1 Replace the RAID battery.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
Here is the battery location:
Chris, -
Hi. I'm working through new disk subsystem issues (see links below for reference). It looks like I have a new issue to address - raid battery backup.
My current editing system uses a battery backup. Other than some issues lately, it's worked well. I'm getting a new Areca 1882ix raid controller soon. The question is, do I need a battery backup specifically for the raid controller? E.g. http://www.newegg.com/Product/Product.aspx?Item=N82E16816151111 Or is a system battery backup adequate?
Thanks,
Dan.
Related discussions:
http://forums.adobe.com/message/4587655#4587655
http://forums.adobe.com/message/4593660#4593660Harm,
Thanks. Fortunately we have pretty good power here. When we loose power, it's typically for just a few seconds maybe twice a month.
I have a small UPS hooked up now. It's good for about 20 minutes. But I'm a bit concerned that it will react fast enough for the raid controller. I think I'll get that Areca BBM. Cheap insurance.
Now if Areca will get their buns in gear and bring out the PCIe 3.0 version of the 1882ix...
Thanks and regards,
Dan. -
Raid battery keeps being reconditioned
After the last scheduled raid battery reconditioning, everytime my mac pro is switched on it starts reconditioning the battery again. Any ideas as to why and how to stop it? I'd like to be able to turn off my mac when I want and not after it's reconditioned and recharged the battery everyday! Could the battery be duff?
any thoughts appreciated
PaulHello Paul. Had a similar problem with my Apple Raid Card (battery) 6 months ago. Apple replaced both the Raid Card and the Battery under warranty. Haven't had a problem since (fingers crossed!). If you still have AppleCare I would ask for a new battery at least.
Regards,
George -
Raid Battery issues....
I keep getting a warning for my Raid battery...saying write cache temp. disabled due ti insufficient battery charge.....Restarting does nothinng...Leaving system on for 72hours does nothing......
Does this RAID enclosure have a Battery itself that needs replacing, or is it the Mac's Battery? Is there a UPS involved?
a hardware RAID controller may carry a dedicated battery-powered write-back cache of its own, thereby allowing for efficient operation that is also relatively safe. Fortunately, it is possible to avoid such problems with a software controller by constructing a RAID with safer components; for instance, each drive could have its own battery or capacitor on its own write-back cache, and the drive could implement atomicity in various ways, and the entire RAID or computing system could be powered by a UPS, etc.
http://en.wikipedia.org/wiki/RAID
Mac Pro Raid Card - Battery issues...
http://www.mac-forums.com/forums/other-hardware-peripherals/157895-mac-pro-raid- card-battery-issues.html
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.
https://discussions.apple.com/thread/2684029?start=0&tstart=0 -
Areca RAID Battery Backup Module Problem
From the advice on this forum, I decided to go for an Areca 1680ix-12 and I've had it for about a week. I now have a 6 disk RAID 3 running. However, the battery back up unit was delayed, so I have only been testing the RAID so far and haven't enabled the write cache. I received the battery unit today, and if I install it and boot the machine, I start getting the familiar Area beep sound that something is wrong. If I have a look in the log, I see an 'under voltage' error. Upon further examination, if I look in the hardware monitor, the 'CPU +1.2V' is running at less than 1.2 - somewhere around 1.08 (can't remember the exact number now). I assume this is where the error is coming from. If I unplug the batter backup and reboot, it stays consistent at 1.2 (or higher) with no voltage errors or beeping. Anybody seen this before? I'm thinking the battery unit is DOA, unless one of the gurus around here know how to fix this.
Thanks,
ClaytonHarm,
Thanks for the reply. I triple checked that the cable was properly seated on both the BBM and the 1680ix. It's just the single cable correct? No other power cables necessary? It currently says 'Charging(96%)', however when the BBM is connected all the hardware readings are normal except for the CPU 1.2V which is at 1.12V dropping down to 1.08. When it hits 1.088, that's when under voltage error appears, which is about every 5 minutes while I'm trying to get this battery charged.
Should I wait until the battery is charged to see if the voltage goes up a bit, close to your 1.184V? However, even if a charged battery fixed the situation, it doesn't seem right to me that you can't run the card without a fully charged battery. -
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
LVJHi, 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 -
RAID battery error (code0x#0=17)
Hello folks!
When I turn on my Mac Pro, the following error appears after log in:
+Battery failed (code 0x#0 = 17)+
What is the meaning of that error? How can I solve it?
Thanks for your attention.It would seem you have few choices here:
1. Call AppleCare.
2. Replace the battery.
The only other info I found is: Mac Pro RAID Card and Xserve RAID Card: Frequently Asked Questions (FAQ). -
Hi,
I have a RAID 5 with 4 HDDs.
I have an error in the RAID Utility :
"Battery #0 failed (code 0x1f = Daemon not updating)"
I already called the Apple Care Support and we changed the battery but 10 days later the problem appeared again.
However the battery seems to work normally, and this month again the battery went to be emptied and filled as it does normally each month.
Is there anyone who have an idea?
ThanksHi fmotot;
I think that you are mistaken about your hardware. I never heard of a G5 Pro. This information has to be correct before anyone can help you.
Allan -
Hi,
I have a RAID 5 with 4 HDDs.
I have an error in the RAID Utility :
"Battery #0 failed (code 0x1f = Daemon not updating)"
I already called the Apple Care Support and we changed the battery but 10 days later the problem appeared again.
However the battery seems to work normally, and this month again the battery went to be emptied and filled as it does normally each month.
Is there anyone who have an idea?
ThanksSounds more like the card is malfunctioning in that case, and not the battery itself.
Or the card and software isn't reporting the status of the battery properly. But I would see about getting the card replaced or see if a new card has the same problem.
They should, with a 2nd battery test fail, take it one step further, now that it seems you have ruled that out, and it is the daemon or card. -
I have macpro (2009) with the card raid but I need to change the battery because it has died, is possible? exist do spare parts? where to obtain it?
Thank youHello all, i'm having the same problems with my Raid card in my MP.
I switch my maschine off everyday, some times even for a couple of days, since it can't go to sleep mode, i have had all the above mentioned Raid utility warnings, and they now turned in to the severe error ( code 0x#0 = 18 ) with the red dot. In battery status it now says charching and cache writing disabled.
And i may add that the speed of the raid is down to less the a normal drive, i use a 3 disk raid 5 set up, and it is now down to 13,3 MB/s Write , and 88MB/s Read ( Kona System test ), thats not why i took the raid card now is it.
I'm starting to feel this card is not a smart choice if you don't leave the machine on 24/7 and use it like a server.
No sleep mode, no Bootcamp , and no added speeds with the card, i'm starting to think i made a very expensive and bad choice in taking the the card.
Hope we can get the battery problem fixed , maybe this will have some effect on the performace aswell.
PS why isn't the battery charger always on aslong as the machine is plugged in , that would solve this problem , or not ?
Message was edited by: DJ Data -
Warning <Hardware> RAID ALERT: (0x0008/1) - Battery removed' (attempt #0)
Please, help me to understand what it means. Server Ironport c350. Every restart I can see this event in system.current in /system_log/Hello Igor,
please open a service request with support, as your RAID battery (the battery on the RAID controller) requires a replacement here.
Thanks and regards,
Martin -
RAID ALERT: (0x0008/3) - Battery needs replacement - SOH Bad
I've installed a new C350 recently. After a few days, I receive a warning message from IronPort (RAID ALERT: (0x0008/3) - Battery needs replacement - SOH Bad). What does it mean? Is it a hardware failure?
This indicates that the RAID battery is fully discharged and cannot be charged. Essentially, a bad RAID battery. I would recommend getting in touch with Ironport support to get the appropriate RMA initiated.
-
Fairly new battery not charging after not being used for a while
My computer (Elitebook 2530p) has not been used for a while, perhaps a month or two. The battery used to hold for over 3 hours of light use.
Now, the battery won't charge with the message "0% available (plugged in, not charging)"
I can't find a battery refresh utility in the BIOS, or any way to interact with the battery. Is there something I'm missing? Should the battery just go dead after not being used for a while?
Update: fixed typoI've run the HP battery check and got the code REOOW. Battery is dead, and I am out of warranty. I can't think of any possible reason why this should have happened.
What does this code (REOOW) mean?
Maybe you are looking for
-
File sizes - Click through selection
How bout looking at the ballooning file sizes? I just got pissed off at how slow illustrator was (using the new cs4 version and "mistakenly" left a couple layers pallet open) and did a copy-paste into Freehand and finished the job. When done the free
-
Why not i can use an archor in-page when i open page with ff4.0.1?
as title. I can not use an archor in-page when i open page with ff4.0.1.
-
Can't remove saved passwords in Safari
Hello, have a problem with Safari. I can't remove saved passwords of websites. My steps: - Settings - Safari - Passwords & autofill - Saved passwords - I write 4-digit code - I click on "Edit", select all sites, then I click on Remove If I go to save
-
Veiwing mailbox sizes in exchange 2007
Is it me or is Exchange 2007 missing mailbox size? i cant anywhere to veiw the size of a users mailbox.
-
Trouble upgrading to 10.6.1
Hi all, I'm having trouble upgrading to iTunes 10.6.1. Earlier today, I opened iTunes, and received an error message that "iTunes Library.itl cannot be read because it was created by a newer version of iTunes." Still not sure why this happened. I f