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

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

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.

Satellite Pro P100 - Battery fails to recharge

Hi.
I have an old Toshiba Satellite Pro P100, a refurbished model, which I got 2 years ago.
It has worked fine ever since I got it, but I went overseas for a month and left my laptop at home.
When I returned I found that the laptop battery won't recharge.
The battery power indicator on my desktop says 0% and it requires constant connection to the mains to work.
I've looked through the manuals, all they tell you is that a flashing orange light means low battery, but not what to do if it doesn't change.
I also looked online, but they don't help either.
What I want to know is whether there is a way to fix my battery or if I need to buy another.
Thanx

Hi
It looks like battery fault.
But check the battery connection firstly.
Remove the battery and after short time connect it again.
If this will not help then you should replace the battery and should test the notebook using new battery.
Greets

Mac Pro RAID Rechargeable Lithium Battery

I am trying to purchase a replacement Apple Mac Pro RAID Rechargeable Lithium Battery for a Mac Pro tower. It is an oblong battery about 3"x2"x0.25" (8.0 cms x 5 cms x 0.5 cms).
Mine no longer accepts a charge so the cache won't back up. The Mac Pro is less than 18 months old.
I have tried the Apple online store, the Apple Store in Covent Garden, Albion (an Apple Premium Reseller on the Strand in London) and even CTS (an Apple Premium Reseller in Paris while there this weekend).
No-one seems to know of it let alone stock it.
Can anyone tell me where I can find it?
I have to say Apple's support on this is useless.
All help appreciated.
Mike

Is there an "official" policy regarding the way one should treat a machine with a raid card. Some say never to switch off the machine, others say this is nonsense, as even if the MacPro is switched off, the battery should still be able to maintain it's charge. I have heard various Apple representatives say different things, but as far as I recall, I have never seen something in writing. Besides, my Raid Card lasted exactly one week before it needed replacement. I have now been sent a battery replacement after 4 months, and it failed (again) while keeping the machine on...so I am really confused.
Thanks in advance.

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

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

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

Mac Pro RAID Card and Western Digital drives

I'm having huge troubles with these items.
I first installed four WD7500AYYS (Raid Edition) to build a RAID 5 and install Leopard on it. At this point, one of the drives was probably DOA and didn't show up in the bay. I then reinstalled the Seagate that shipped with the machine, then proceeded to create another enhanced JBOD raid with one of the WD drives. After a couple of seconds, RAID utility reported an error (disk about to fail and such). I then tried with another one. The process ended with a kernel panic after two hours, while RAID utility was still marking the drive for enhanced JBOD. That disk never show up again, in any bay.
At this point, I'm left with two WD drives. I can't get past the creation of a RAID set with them, no matter what. Either RAID utility reports an error, or it says the disk has been ejected, or it keeps create the RAID for hours... The later usually ends with a "force quit", or a force shutdown. During these attemps, the RAID card went missing once, then it appeared again on the following reboot. The RAID battery, which was fully charged at first, is now being "repaired" (charging ?).
I then ran AHT to see whether there was something wrong. No errors reported.
Because all four drives were Raid Edition, I thought this could be the root of the problems. So I bought a Caviar SE16 (WD5000AAKS). To no avail. It fails too, in the very same way. And now it no longer appears in any bay.
The last step I took was to remove the RAID card (connecting the iPass connector to the motherboard). Out of the five WD drives, only two RE2 (the two that still show up with the RAID card) do appear in disk utility. But disk utility never ends "writing the partition map" or "preparing for initialization".
By now, I end up with five WD drives that appear to be just dead, as if they were killed by the RAID card trying to RAID them. The only drive that works, with or without the RAID card, in any bay, is the Seagate. I didn't try to fiddle with it though (I'm reluctant to format it just to see whether I can create an enhanced JBOD raid with it).
So the question is, are Western Digital drives compatible with this RAID card ? If they do, then how a RAID card can kill them in such a way while keeping the Seagate alive ?
I'm lost in conjectures. I don't even know if/how I can bring all the WD drives back to life. I'm not sure the RAID card is faulty, I've already lost a lot of time and money, I'm not willing to buy yet another drive to see it fail too, and my Mac Pro is kind of useless as I don't want to spend time on installing/configuring everything I need on a drive that is bound to be replaced by a larger RAID 5 array.
Any help is appreciated. Thank you.

Someone yesterday or Friday, had a system with 4 x 1TB drives and Pro RAID, but in their case, it was determined later Saturday that drive bay #1 was not functioning.
Hopefully these fully retail drives, not OEMs, and I would think they are fine. They are what I would use (Sonnet Tempo only supports RE of the WD drives). Someone else, Danish?, had 3 out of 4 WD drives were DOA.
I've never had trouble buying over a dozen from OWC, so it does seem odd.
If you have SoftRAID 3.6.6 I would use that to zero the first and last 100 sectors, or you can begin to zero the whole drive and cancel at any time, just to check the health of the drive and that it can zero and not produce I/O errors.
There are two other methods for accessing and managing Mac Pro RAID, ARD and CLI
http://docs.info.apple.com/article.html?artnum=306231
Originally, only Apple drives were supported. My understanding was that this changed. But the only article I found in KB dates back to Aug '07:
Question: What drives does Apple support with the Mac Pro RAID Card and the Xserve RAID Card?
Answer: +Only Apple drives are supported with the Mac Pro RAID Card and the Xserve RAID Card.+
My understanding that 3rd party retail drives such as WD RE2 750GB, Seagate, Hitachi were supported as well since the article was written - and I can't find where I read that, but sure that I did, as this was discussed in the past.
I'd like to find an official article. Even my friend Google was helpless

Mac Pro RAID 5 disk goes offline frequently in a random way. What can be causing this odd behavior?

Hi dudes,
I installed recently two Mac Pro RAID cards inside their corresponding Mac Pro systems. Four 2 TB Hitachi SATA disks are contained inside each system, and configured as RAID 5. Yes, the operating system is installed on this RAID 5 volume in order to get the highest performance of the array, taking advantage of the RAID 5 protection (Autodesk Smoke runs in each system; this application works only with uncompressed video in real time). I already had tested both systems keeping separated the boot disk just for the operating system, and making the RAID 5 volume just with three 2 TB disks, but the performance was slow on both systems.
The performance is now very good, but unfortunately, in both systems happens that sometimes one of the disks goes offline with no apparent reason. The RAID Utility immediately reports the failure and it is mandatory to declare as spare the disk that went offline. Then the rebuild process begins, but in the meantime, the performance goes down in a noticeable way. Sometimes it is even worse, because the disk disappears completely. Then, it is mandatory to turn off the system, and boot it up again, in order to see in the RAID Utility the missing disk, which needs to be declared as spare in order to be reintegrated into the RAID 5 volume in a slow rebuilding process.
Some important remarks: this very new Mac Pro systems do not have the iPass cable (at least apparently; I already disassembled completely one of these systems). This cable is mentioned in one Mac RAID card manual that I found over the internet. The diagrams do not match exactly with the Mac Pro nor the Mac Pro RAID board. I did not find a proper iPass connector in any of the Mac Pro RAID cards (?!). So, my guess is that currently the communication between the system and its Mac Pro RAID card is just by means of the internal bus. I think that if the iPass connection were mandatory, the RAID Utility would report it with a noticeable error message. Please advise.
I think that these Mac Pro RAID cards need a firmware upgrade, in order to be able to work fine with big SATA drives. Again, please advise.
Thanks in advance from Mexico.
Sincerely,
Martin Ponce de Leon

Hi Grant,
Thank you for your prompt response. The manual is a PDF document issued by Apple and it seems OK, but no updated to the latest Mac Pro system and Mac Pro RAID. I do not find the link where I found this manual. The systems belong to one of our customers. As far as I remember, in the printed manual included with the boards, it is not mentioned anything about the iPass cable, just about the battery cable. Do you know where can I get a PDF manual of the latest Mac Pro RAID card and the latest Mac Pro system? This client is far from our offices. So, I would prefer a PDF copy of this manual.
The drives that have gone offline, once they are back, are reported in a good status in the RAID Utility. Besides that, I have tested them in another system in our facilites, and all of them work fine. So, my guess is that the high capacity drives are not yet supported by the Mac Pro RAID card, or it requires a firmware update.
They do need to have in the same volume OS and video storage because three disks do no provide a good performance (they need also RAID 5), but four disks work fine... excepting when one disk is missing. Please advise. Thank you.
Best Regards,
Martin

Sleep or Shut Down with Mac Pro RAID Card?

I'll be gone for a four-day weekend trip, which is longer than the 72 hours claimed for the Mac Pro RAID Card battery. If I shut down and come back four days later, the battery will presumably be discharged. What will happen when I restart?
Asked another way ... is 72 hours the maximum amount of time that the computer should be shut down or do I simply restart and wait for the battery to recharge and the write caches to be re-enabled?
The FAQ for the Mac Pro RAID Card http://support.apple.com/kb/HT1346 talks around this issue, but doesn't say whether it is a good or bad idea to allow the battery to discharge for "... any length of time." Please review the appended excerpt from the FAQ and advise on whether I should sleep or shut down.
Regards,
iPhoton
Question: Why does RAID Utility show a yellow light and report the status "Write cache disabled"?
Answer: The write cache is disabled automatically so data cannot be written to RAID volumes when the battery charge is not sufficient to back up cached data for 72 hours. This message is normally encountered when a RAID Card is used for the first time, when the battery enters a conditioning cycle once every three months, or when a computer with a RAID Card installed is shut down for any length of time.
If your RAID card's firmware is M-2.0.3.3 or later, or E-1.2.2.4 or later, you can use RAID Utility to force-enable the write cache while the battery conditions itself. Warning: If you enable the write caches before the battery is fully charged, you might lose some data if the power to your computer is interrupted.

Thanks to everyone who replied to my message. I did a proper backup and normal shut down on Wednesday night and restarted on Monday morning. That was over 100 hours later and certainly more than the battery is specified (72 hours).
When I restarted on Monday morning I noticed ... no change! The battery was fully charged according to the RAID Utility, I received no warning messages, there were no new events in the RAID Utility log ... it's as if the extended shutdown never occurred.
So, an extended shutdown appears not to be a problem and I won't worry about it again, not even on my next extended shutdown for three weeks at the end of the year.
Regards,
iPhoton

Disc Utility - warning if RAID HD fails ?

I would like to set up an external RAID1 in a Sonnet JBOD ( Fusion D400P ).
I just learnt, that if I set up this RAID1 with Apples Disc Utility, there will be no automatic warning if one of the drives is failing...
Is that true ?
Do I need to set up the RAID with SoftRaid to be on the safe side ?
Cheers - Steffen

http://discussions.apple.com/category.jspa?categoryID=194
What make and model drives? Not all work, or work well, and Samsung F1s have specifically been sited as not working with Apple Pro RAID.
http://www.apple.com/support/macpro/
http://support.apple.com/kb/HT1346
Other ideas:
http://discussions.apple.com/thread.jspa?messageID=8446960

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!

G5 Pro - RAID Battery failed

Similar Messages

Maybe you are looking for