RAID Battery Failed

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?
Thanks

Sounds 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.

Similar Messages

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

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

G5 Pro - RAID Battery failed

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?
Thanks

Hi 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

RAID card battery conditioning - "Battery failed (other than expired)"

OK, so if you log-in using the GUI, you get a warning telling you that battery conditioning is happening and that you shouldn't the server.
However, if you log-in over SSH, as you might, for instance, with a headless Xserve, you don't get that warning. And then, if you restart more than a certain number of times, for instance because you're installing all the software updates that the server has missed while it hasn't been switched on, you end up in the following state:
$ raidutil list status
Apple raidutil version: 1.2.0
General Status: Issues Found
Battery fault. See Battery Status below.
Battery Status: Battery failed (other than expired)
Controller #1: Hardware Version 2.00/Firmware E-1.3.2.0
Write Cache disabled
Plainly this is undesirable.
Does anyone know how to reset the battery state, preferably without having to pull the server out of its rack and disconnect the RAID card battery?
Also, since when was it in any way reasonable to tell a user that they can't shut their machine down for 24 hours? Even with a server, that's ridiculous - sometimes you just have to reboot.
Kind regards,
Alastair.

FWIW, I just filed rdar://7653429 about the fact that terminal users don't get any warning of this, and rdar://7653468 about the fact that battery conditioning shouldn't force sysadmins to keep their machine running for the next 24 hours (since they might really need to shut it down, right now).

RAID Card reports ERROR: Battery failed (code 0x#0 = 18). Help!

Hi,
I have a MacPro computer that has 4 drives and Apple's Hardware RAID Card installed. It's been working great, but we first received notification via RAID Utility of the following error: 5/23/09:Battery failed (code 0x#0 = 18). We ignored it because we have a project in the works. Computer is degraded in performance, and we can tell. Restarted and got the notification: 5/24/09: Controller reports RAID System 72-hour battery reserve unavailable. System is configured to run without battery.
What shall we do to get this working again.
I reallly appreciate any and all pointers. Apples online help didn't appear to be operating correctly today, Sunday, May 25.
Thanks, and so long for now, TOM

Unfortunately, this is a widely known issue with Apple's raid card. I would get in touch with Apple as soon as possible; not online help, but actually call them.
http://forums.macrumors.com/showthread.php?t=439873
http://discussions.apple.com/thread.jspa?threadID=1405187&start=0&tstart=0

Apple Raid Card Battery Failed

Hey guys !
I have an early 2008 Mac Pro with a Raid Card and i get this message battery failure other than expired
actually i got this message again about an year or so back ... so yes it happened before ... Apple replaced my battery
Now im out of warranty coverage.
Questions are :
How does this affect my Raid Set ?
Can my Raid Set survive without the battery ?
If yes ... what are the downsides ?
What can i do to manage the situation without changing again the battery ?
Hope to get some advice soon on this matter
Thank you very much.
PS
Down below i pasted some specs for my machine
Mac Pro RAID Card:
PCI Slot:          Slot-4
Hardware Version:          1.00
Firmware Version:          M-2.0.5.5
Expansion ROM Version:          0018
Shutdown Status:          Normal shutdown
Write Cache Enabled:          No
Battery Info:
Firmware Revision:          1.0.2
First Installed:          1/1/01 2:16 AM
Last Date Conditioned:          2/24/12 3:47 PM
State:          Faulted Battery
Fault:          Battery failed (other than expired)
Status:
Charging:          No
Conditioning:          No
Connected:          Yes
Discharging:          No
Sufficient Charge:          No
Drives:
Bay 1:
Product ID:          ST3300655SS
Serial Number:          3LM35BGK00009827PBXY
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          RS1
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
Bay 2:
Product ID:          ST3300655SS
Serial Number:          3LM622YT00009923HP5Q
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          RS1
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
Bay 3:
Product ID:          ST3300655SS
Serial Number:          3LM2Y49T00009827PAZV
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          R0-3
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
RAID Sets:
R0-3:
RAID Level:          Enhanced JBOD
Capacity:          299.8 GB (299,798,364,160 bytes)
Available Capacity:          Zero KB
Drives:          Bay 3
Volumes:          Vol-R0-3
Status:          Viable (Good)
RS1:
RAID Level:          0
Capacity:          599.73 GB (599,730,946,048 bytes)
Available Capacity:          Zero KB
Drives:          Bay 1, Bay 2
Volumes:          R1V1
Status:          Viable (Good)
Volumes:
R1V1:
BSD Name:          disk1
Capacity:          599.73 GB (599,730,946,048 bytes)
Read Command Size:          2 MB
Read Ahead Margin:          16 MB
RAID Set:          RS1
Status:
Degraded:          No
Inited:          Yes
In Transition:          No
Viable:          Yes
Vol-R0-3:
BSD Name:          disk2
Capacity:          299.8 GB (299,798,364,160 bytes)
Read Command Size:          2 MB
Read Ahead Margin:          16 MB
RAID Set:          R0-3
Status:
Degraded:          No
Inited:          Yes
In Transition:          No
Viable:          Yes
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro3,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          3.2 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per processor):          12 MB
Memory:          8 GB
Bus Speed:          1.6 GHz
Boot ROM Version:          MP31.006C.B05

The RAID card battery backs up the memory buffers on the card. These are needed for calculating the checksum blocks used in RAID 5 and similar schemes.
If you are not running RAID 5 or similar, you do not need the battery. For that matter, you do not need the RAID card, either (unless you are running SAS drives).

Apple RAID Card - Battery failed (code 0x#0 = 18)

Hello,
Upon start up of the computer I get a message that says "The Apple RAID Card installed in your system requires your attention".
When I open up the RAID Utility I have messages like -
Battery failed (code 0x#0 = 18)
Write cache disabled due to insufficient Battery Charge
Can anyone explain what this means and what I should now do?
Do I need a new Battery and does this mean my RAID 5 isn't saving data correctly?
Thanks in advance for any assistance.
Kris

Hello
I have the same problem too:
Battery failed (code 0x#0 = 18)
or in my case, I am german: Die Batterie funktioniert nicht (Code 0x#0 = 18)
It happened the first time after one year and I replaced the battery. One year later it happened again and I replaced the battery. And one more year later again. This time I decided not to replace the battery.
I booted the system from the recovery media and started the the raid utility from there and it said: battery charging.
So I returned to my "normal" partition and it said: battery charging.
A few days later: Battery failed (code 0x#0 = 18)
I repeaded this several times, always with the same result.
I was quite sure that all the trouble resulted from a firmware bug.
So I did shut down my Mac, and removed my raid card. On the raid card I disconnected the battery and waited a few minutes and reconnected it. I reassembled all and started my Mac.
It is running now for more than a month without any further errors.

XServe Battery failed (code 0x#0=18)

Hi guys – I need help?
I recently purchased 3 XServes and I noticed that one on them displays this message “ (Battery failed (code 0x#0=18)” error messages in the RAID controller. I did find similar posting with no solution. I was just wondering if you have similar issue and can guide me on this?
Would you please reply?
Thanks and regards
jd

GSX says to try disconnecting and re-connecting the battery. Getting to the battery to remove it seems pretty difficult from the manual but can anybody confirm whether or not you need to remove the raid card, fans etc just to unplug it? I'd just as soon buy a new one and replace it once instead of having to shut down and dismantle it twice.

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).

Battery failed (code 0x

What should I do after getting the message "battery failed (other than expired)", from the Raid Utility? Is there a way to manually recondition the battery?

Please look there: https://discussions.apple.com/message/22401775#22401775

Mirrorred RAID Rebuild Failing

Hello,
I had a mirrored raid setup on 10.6.7, everything was working great for the last month, then today I went into disk utility and it said one drive failed. After checking the drive, there didn't seem to be any problem with its operation, so I can only assume it was a software/communication failure.
Clicking the rebuild button resulted in this error:
Rebuilding RAID set failed with the error:
POSIX reports: The operation couldn't be completed. Operation not permitted.
So I tried removing a disk, that also failed with the same error.
I then erased the failed drive which automatically removes it from the RAID configuration. Now when I try to add it back to the configuration I get the exact same error.
Has any experienced this issue and have any suggestions on how to get RAID back online?
Thanks in advance!
Michael

Thanks for your reply.
Yes, I am sure that the drives are working. I do not know what caused one of the drives to 'fail' as far as disk utility was concerned - but it was online when I checked it again.
I had issues while originally creating the RAID configuration, similar POSIX issues.
I have managed to get the configuration back online using the SoftRAID, but I am unable to create any new RAID configurations or modify existing ones using Disk Utility. Is it possible its an issue with POSIX and the drive USB drivers? Though I have tried with 3 or 4 different brand drives.
SoftRAID allows the drive set to be converted to a Disk Utility set after creating/repairing it - so thats what I have done for now.
I will try to setup/repair this all again once I have Lion installed and see if they fixed it in that version.
Any suggestions on how to get Disk Utility's RAID configuration on a Intel Core 2 Duo Mac Mini would be appreciated. I have filed a bug report with Apple as well. SoftRAID was a suggested alternative to a few other posts on the discussions for similar issues.
Michael

MBP 17" A1189 battery fail – please help access Apple Customer Support?

Seven Steps to a “Help Me, Please?” Plea for Assistance
[1] 2009 – Apple creates global, free-of-change, battery replacement program: ‘MacBook and MacBook Pro Battery Update 1.2’ Exchange and Repair Extension Program – for their design-flawed Apple A1189 battery’s dead-&-bloated failure mode. [kudos, respect due]
A typical design-flawed Apple A1189 battery in dead-&-bloated failure mode – swollen cells crack open the battery’s casing
[2] 2011 – My A1189 battery fails, dead-&-bloated: Apple replace it free-of-change, as per [1], and my MacBook Pro is up-&-running again in no time. [perfect Apple Customer Service, as usual]
[3] 2014 – My A1189 battery fails, dead-&-bloated (and takes down power adapter too): Apple now wants ME to pay THEM for the replacement parts needed to repair the damage caused by THEIR design-flawed A1189 battery failure to MY Macbook Pro!
Erm... surely some mistake? I think NOT: intolerable Apple[don’t]Care injustice is intolerable – “So, we bust your computer, eh? Fuggedabahdid! You give us money, we fix your computer, capiche?”
[4] Wed 28 May – My ‘Apple UK Complaint’ is tasked to Apple employee.
[5] Fri 06 Jun – After 12 emails over 9 days, our complaint resolution progress STILL EQUALS ZERO –
[6] Sat 07 Jun – ‘Help Me, Please?’ shout out goes out to the Apple Support community.
Many thanks in advance for your assistance,
Dalinian
[Loyal 6-Macs-over-21-years Apple customer, pining for the days of perfect Apple Customer Support]
<Personal Information Edited By Host>

Hi Melophage,
Happy, Happy Day! With only the opposite of help from Apple Inc., and in reality thanks to the assistance and encouragement of my BFF IRL and your good self, my grand old MacBook Pro Kallisti has risen from Hades once again, and sprung back to life – and this reply is coming at you from her very own keyboard and net connection.
My non-Apple replacement battery and a second-hand power adapter from TheBookYard.com in Liverpool arrived on Tuesday, and with the swapping in of an unblown 3A fuse, all is as well again as it was before Apple’s design-flawed A1189 battery killed Kallisti for the second time.
What I’ve neglected to mention so far is that in early 2014, the screen began to fail intermittently, then with increasing frequency, until only via a DVI-HTML cable to my 50-inch TV could I see what I was doing at all. Yesterday the screen was working again initially, but only for a couple of hours, before failing to black again.
Seems this is yet another well-known and well-documented fault with all the MacBook Pros that use the NVIDIA GeForce 8600M GT graphics processor – see, eg: Apple’s (also prematurely terminated) ‘MacBook Pro: Distorted video or no video issues’ » http://support.apple.com/kb/ts2377 . I’ve a shed load of reading up to do on this issue from all over the web, including what appear to be some possible DIY fixes. I’ll most likely not waste any more time or energy on expecting Apple to take any responsibility for yet another well-known and well-documented fault with their MacBook Pro, since I find their naked contempt policy for Mac owners who fail to buy a shiny new Mac when the old one breaks down to be utterly revolting (not to mention environmentally unethical and unnecessarily destructive).
Re: you yourself being of the Yanqui petite bourgeois persuasion – on the two occasions I’ve been fortunate enough to visit the USA, I’ve been genuinely impressed by the admirable attributes of the Americans I’ve met and stayed with: heartwarmingly generous with their time and attention, welcoming with an effusive hospitality, helpful, friendly, and compassionate. Yet there’s a world of difference between the esteem in which I can hold individual Americans, and the contempt in which I can hold the ruling class social institutions of any country, including especially the USA and my own, the UK: greed-centric corporations, brutally repressive police forces, mass-killing-focussed foreign policy initiatives, etc., &c. Rest assured, from what little I know of you, you’re certainly in my highly esteemed American individuals category.
I don’t know how useful my advice was, since it wasn’t sufficient to convince the store manager at the Regent Street Apple store to provide you with a replacement battery.
I’m pretty sure nothing short of physical torture (which is obviously and repellently obnoxious) would convince that heartless, hard-nosed SoB to break with Apple’s iron cast built-in obsolescence policy – listen up and listen good: your Mac’s so old it’s ‘vintage’, so screw you, buddy – if you ain’t gonna buy a new Mac, or buy from us the parts needed to repair the damage we did to your old Mac with our known-to-be-faulty components, you can can just get the **** out of our shiny, shiny Apple Store, coz respecting your fancy-schmantzy ‘UK statutory consumer rights’ is only gonna put a dent in our bottom line, and getting to be filthy rich off of the likes of youse is what Apple’s really all about these days, capiche? I have GOT TO End This Conversation NOW!
There’s plenty of free web-based help and advice on reporting dodgy traders like Apple to the Trading Standards authority, and pursuing reparations from such lawbreakers through the small claims track in the civil courts. So now I’ve Kallisti back up-&-running again (albeit with a dead screen), on which to document my anti-Apple legal research, I’m taking my time to ensure I’m following due process, and relishing the irony of developing a suitable regulatory/legal punishment for Apple on the very ‘vintage’ flagship MacBook Pro which their offending policy has all but written off as obsolete. Plus, since it turns out its “Super”drive won’t eject a freshly burned DVD-R, I’ve ordered an Ubuntu 14.04 LTS 32-bit DVD to do a fresh unibooting install on my 2001-design backup PC notebook, to add some non-Apple computer robustness to my resources, until such time as I’ve saved up enough for to buy a purpose-built touch screen Ubuntu 14.04 LTS notebook, such as the System76 Darter UltraTouch (» https://system76.com/laptops/model/daru4 ); and that leaves plenty of time ahead to compare the long-term customer support reputations of potential Ubuntu PC manufacturer companies, to ensure that I don’t get taken for a fool by another Apple-like mobster-type corporation.
Time to begin investigating coconutBattery, I think. Many thanks again, Melophage – with zero support from fellow Mac users, I’d most likely have given up and thrown in the towel some time ago, but you’ve helped me to find the self-motivation to persist in perusing a just solution, despite my beginning this process by being sunk in the depths of an episode of severe clinical depression. I must admit, I’d no idea that contending against Yanqui corporate fascism could be so therapeutic!

My Lacie 2big 6TB Raid just failed. Help!

Hi
My Lacie 2Tb Raid just failed and I am looking for any advice on fixing it.
When I turned on my computer, I noticed that my raid didnt pop up. When I opened Disk Utility, it shows that one of the drives have failed. The image is below.
Is there any possible way to fix or recover that drive?
The HD was backed up a week ago, but I am not 100% sure what was added since then.
Thanks

Call Lacie. If it's not under warranty, do yourself a favor and go buy something else.
I work in IT at a non-profit. We had 4 Lacie 2big units all fail within 12 months, all just out of warranty. They are pure junk. I won't touch them, ever again. One failure is one thing. drives fail. Everything fails eventually. But having 4 of them fail within that short a period of time is just inexcusable.

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
Subbu

Hi 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,

RAID Battery Failed

Similar Messages

Maybe you are looking for