Xserve RAID card reconditioning battery

Hello,
Does anyone know if there is a LaunchDaemon or script where i can schedule my battery reconditioning ?
It is always starting in the middle of a working day and the performance is then very slow.
Or did anyone tried to disconnect the battery cable an put write cache on ?
Tnx,
Harry

Seems to me to be a hardware design fault…
It has a mind of it's own –literarily– it's own internal control logic determines when this happens
– I have not seen any way to 'control it'
– Personally I consider this to be a major design fault…
– Would be OK if could control it
– OR if it had two batteries and could swap between them
– Neither of which seems to be the case…
I could be wrong – but I've never found a way to control it
– Seems to have a habit of choosing the most in-opportune times to recondition it's battery
– if it works at all…

Similar Messages

  • How to change xserve raid-card battery?

    how to change xserve raid-card battery?

    Xserve RAID Card Battery Replacement Instructions:
    http://manuals.info.apple.com/MANUALS/0/MA277/en_US/Xserve_RAID_Card_Battery_DIY Instructions.pdf

  • Xserve raid card failing? 3 x 1Tb drives

    Hi all
    I've had an xserve running for the last month or two now, it has been subject to frequent crashes...
    I have applied the latest 10.5.5 update and haven't had a crash for some time now.
    This morning I happened to have a look at the server monitor, and there was an error...
    I'm a little confused... especially when the xserve is also connected to an APC UPS unit.
    Should I be worried about this... is something lurking around the corner?
    *Any help/suggestions appreciated.*
    http://smam.net/xserve/raid-card.jpg
    Az

    This is covered in the RAID Utility User's Guide on page 12.
    Every 3 months the RAID card will discharge and recharge the battery. During this process, you will see the message.
    Regards,
    Eric Miller

  • Xserve RAID Card: Is setup kept when reinstalling OS?

    Hi everyone,
    I have a new Xserve with 3x 1 TB and the RAID Card. The default setup is JBOD and of course I'd like to change that by booting from the DVD and setting it up. I know that I can convert JBOD to RAID while keeping the already installed OS. But since I plan to reinstall the OS anyway I was wondering if my chosen RAID setup will be preserved this way?
    I believe this is a real Hardware-RAID so this should work, right?
    Thanks
    Björn

    Thanks,
    since the RAID can't be reconfigured while booted off one of the internal drives and since this can't be accomplished remotely using Server Assistant I need to reconfigure it with another (external) system. Is that true?
    I suppose it could also be done directly at the Xserve, but I do not have a Mini Display Port Adapter at hand, so this is currently no option. It seems to work with an external FW drive running OS X 10.5.7 (Client) which has the RAID Utility on it...

  • 4Gb Xserve Raid Card to 2Gb Xraid Fiber Channel

    Greetings All,
    Does anyone know if a 2x4Gb Fiber channel card will auto-negotiate down to the 2Gb level of my Xraid?
    Thanks,
    -dave

    Yes it does. I've done it and the newest Xserve is plug and play with the old Xserve RAID.
    =Tod

  • Kernel panics whenever RAID card conditions battery

    I have an early 2008 Mac Pro running 10.5.8, with an Apple RAID card with M-2.0.5.5 firmware. This has two Seagate Barracuda drives attached, formatted as RAID 0, and this RAID 0 is the OS drive.
    Periodically, the RAID card conditions the battery. In the past I've been able to work while this was happening but, about three weeks ago, the conditioning started and the computer became completely unusable: there were kernel panics every minute or two and, on restarting, the report showed "AppleRAIDCard Controller Panic...". I eventually gave up and left it alone until the conditioning finished, and it's worked fine since.
    This situation has just started again. It's only three weeks since the last conditioning; the gap was 6 weeks last time; and 12 weeks the time before that. Is the battery failing? Does that explain the constant AppleRAIDCard Controller-initiated kernel panics?
    I didn't set up this computer and could happily live without RAID but this OS drive now has lots of software installed, much of which needed to be authorised by challenges/responses and explanations to software manufacturers as to why it was being reinstalled etc. Reformatting and reinstalling everything again would be a major PITA.
    Is it possible to move the drives to a software RAID 0 without reformatting them? Is this likely to be less problematic than the Apple RAID card?
    Thanks in advance,
    Steve = : ^ )

    I'd just like someone to comment on whether they think the battery alone could be responsible for unending KPs whenever the controller is conditioning the battery, or whether the card might be faulty.
    I wonder about both points.
    Did some searching, and there are several reports of other users with battery problems.
    For some, the battery fixed the problem, for others, no remedy.
    One example:
    http://forums.macrumors.com/showthread.php?t=439873
    For troubleshooting, identifying the source through eliminating causes related to the symptoms would be a reasonable approach.
    Since the KP's occur only during battery conditioning, it places the most suspicion on the battery.
    Personally, I see this as most telling.
    Since you can't run without the battery, a replacement is the only way that I can think of to test the battery.
    Other possibilities could be firmware related.
    Is the card and the MP running the most current firmware?
    If the firmware of the card and the MP are up to date, the battery, again, comes to the top of the suspect list.
    And, of course, there is always the possibility that a component on card has failed.
    Unfortunately, as with the battery, a replacement is needed to test.
    I wouldn't move on this point until the battery theory were tested.
    Not to dismiss the potential for software involvement, I'm wondering what are the OS X kexts that are involved with the processes leading to the KP's?
    Logs in Console may provide some information.
    Portions of the KP report immediately after the word "backtrace" also provide the best information.

  • Xserve raid Card

    We buy a Xserve 2.66 8CX/6x2G/1TB/1TB/1TB/ SSD/SD whithout Raid Card.
    Is possible install now in the Xserve a Raid Card?

    Alberto
    This is the wrong place to ask.
    Try here:
    http://discussions.apple.com/forum.jspa?forumID=832&start=0
    Peter

  • Why do Xserve RAID cards take so long to ship?

    I have ordered three RAID cards (I need two and I was advised to get an extra for a backup) for our early 2006 Xserve. The cards are due to ship in just less than a month, why so long?

    It's probably an issue of supply vs. demand - in this case, the demand for such cards isn't high, so there aren't many in the supply chain.
    Typically even the manufacturer doesn't keep a local stock of low-demand items, instead running periodic production runs when there's sufficient demand. So some of the delay may be in waiting for the orders to queue up to a level that warrants a production run.
    Even if there is a stock, some manufacturers have minimum order values (e.g. they won't fulfill and order for less than $x, or y units), or offer significant discounts for large orders (thereby making one-off orders cost prohibitive), so the delay may be in Apple queuing up the orders until there's sufficient quantity to make it worthwhile.
    Either way there isn't much you can do unless you can find another reseller who has one in stock, or go used.

  • Xserve Raid Card battery conditioning

    Good afternoon, I have observed that the raid controller on my Xserve run conditioning cycle the batery every 3 months... is that normal?
    I appreciate a clarification on this.
    Thanks.
    Hipolito Lopes

    Hi Hipolito,
    3 months is normal. It's a shame you can't choose the time of day it does this but it's generally around the 6hour mark for the conditioning to take place.
    Hope that helps
    Beatle

  • Battery backed raid card

    Hi,
    I've been trying to determine whether there are any hardware raid cards with battery backed cache that are supported by Solaris 10 and offer online management and diagnostic utilities. The LSI Logic 320-2x (which is repackaged by Sun) is now supported by the lsimega driver, but there is little to no documentation for it (+broken links on sun.com).
    Cards like this usually offer both BIOS-based configuration as well as online utilities. Some cards and the corresponding drivers may be managed using raidctl, but I cannot determine which cards and drivers.
    If any body has links to documentation or personal experience that will enlighten me, it would be much appreciated.
    Regards,
    Michael

    I was going to respond with my personal view, but this wikipedia page describes it adequately.
    From http://en.wikipedia.org/wiki/Redundant_array_of_independent_disks:
    "With a software implementation, the operating system manages the disks of the array through the normal drive controller (IDE, SCSI, Fibre Channel or any other). With present CPU speeds, software RAID can be faster than hardware RAID, though at the cost of using CPU power which might be best used for other tasks. One major exception is where the hardware implementation of RAID incorporates a battery backed-up write cache and an application, like a database server. In this case, the hardware RAID implementation flushes the write cache to a secure storage to preserve data at a known point if there is a crash. The hardware approach is faster and limited instead by RAM speeds, the amount of cache and how fast it can flush the cache to disk. For this reason, battery-backed caching disk controllers are often recommended for high transaction rate database servers. In the same situation, the software solution is limited to no more flushes than the number of rotations or seeks per second of the drives. Another disadvantage of a pure software RAID is that, depending on the disk that fails and the boot arrangements in use, the computer may not be able to be rebooted until the array has been rebuilt."

  • MacPro RAID card - best drives?

    Hey, anybody have any experience they'd like to share on a good set of drives to go with the Apple RAID card? I want to get 4 and I'm looking for maximum speed, but I can't break the bank, so no Raptors.
    cheers,
    -r

    Well, save your $$ and just DON'T! get the Apple RAID card, then you could afford some decent drives.
    600GB 10K VRs $279 x 2
    OWC SSD 100GB x 2
    As for what drives, bare in mind -
    If you read the Apple Support Mac Pro link to RAID card FAQ:
    Question: *Which drives does Apple support for the Mac Pro RAID Card and the Xserve RAID Card?*
    Answer: Only Apple SATA drives and Promise 450GB SAS Drive modules sold through the Apple Store are supported for use with the Mac Pro RAID Card (Early 2009) and the Xserve RAID Card (Early 2009). Apple 300GB SAS Drive modules are supported with the Mac Pro RAID Card (Late 2007) and Xserve RAID Card (Early 2007). Drives must be either all Serial ATA (SATA) or all Serial Attached SCSI (SAS) drives. SSD drive modules are not recommended for the Apple RAID Card because these drives use their own on-disk cache and cannot take advantage of the protection provided by the battery-backed cache on the RAID card.
    http://support.apple.com/kb/HT1346#faq8
    People do try and use retail SATA drives, with mixed results. I have never seen anyone mix SAS and SATA.

  • Long beeping  on  the  raid  card

    having problem  with  my  xserver  g5  i  just  brought  i disconnent  the  raid  card   to  test  a  next  xserver   that  was beeping  and  when  i  reinstall  it  in the  next one  it  started   to  beep loud    can  anyone  can  tell  me  what  i  do  wrong  please

    I came into the office this morning and the RAID Utility reports the Battery Status as "Charged" and now the Overall Status is "Good".
    I don't know when it changed from Conditioning to Charged, but it has now been approx 19 hours since the install of the RAID card and battery so the charge time is definitely less than 72 hours.
    Makes me think my interpretation of the FAQ page may have been correct.
    If so it would be nice if the FAQ page answered the question about how long it takes to charge the battery. Where does one submit FAQ page improvement suggestions?

  • 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

  • Apple RAID Card and 3TB Drives only show 2.2 TB

    I tried a 3TB Seagate Barracuda XT drive in the July 2010 Mac Pro (and a Jan 2008 Mac Pro) on the RAID Card that came with the machines (so one is the RAID Card now shipping) and both show a maximum of 2.2 TB with a 3TB drive.
    I'm curious if anyone else has tried this with different results. Any luck in getting the RAID Card to see the full 3TB in the drives?
    By the way, without the RAID Card, the Mac (OS 10.6.4) sees the full 3TB, but not with it.
    Anyone else seeing this?

    Okay. Seems Apple didn't plan for or certify 3TB.
    However, Apple doesn't support using 3rd party drives. Some do, and in some situations, drives you would think work don't, or they work but only briefly.
    When I said read FAQ I was thinking of all the points like this:
    Question: *Which drives does Apple support for the Mac Pro RAID Card and the Xserve RAID Card?*
    Answer: Only Apple SATA drives and Promise 450GB SAS Drive modules sold through the Apple Store are supported for use with the Mac Pro RAID Card (Early 2009) and the Xserve RAID Card (Early 2009).
    Apple 300GB SAS Drive modules are supported with the Mac Pro RAID Card (Late 2007) and Xserve RAID Card (Early 2007).
    Drives must be either all Serial ATA (SATA) or all Serial Attached SCSI (SAS) drives. SSD drive modules are not recommended for the Apple RAID Card because these drives use their own on-disk cache and cannot take advantage of the protection provided by the battery-backed cache on the RAID card.
    http://support.apple.com/kb/HT1346#faq8
    http://www.apple.com/support/macpro/
    Apple Knowledge Base: recent changes:
    http://support.apple.com/kb/index?page=articles

  • 2010 Mac Pro with Apple RAID card - "Drive carrier 00:03 removed"

    I've got a 2010 Mac Pro with the Apple RAID card and 4 internal identical Seagate ST32000641AS 2TB drives inside.
    I've never had a problem with the RAID card (either battery or in operation) except for one thing:
    Almost every time I shut the machine down (which I try to do as rarely as possible), it keeps losing Drive 3, the spare.
    (See RAID Utility event log snippet below.)
    [I wish I could understand why this Apple RAID card keeps losing the spare across power-cycles/reboots, but I digress.]
    So I just adopted it as the spare and it spawns the rebuild and many hours later, everything's fine again.
    ... until the last time I rebooted (Jan. 2nd).
    After the usual "I lost the spare" message upon login, it began the rebuild.
    But this time, about 11 1/2 hours later the rebuild stopped and RAID Utility reported "Drive carrier 00:03 removed".
    Bay 3 is now missing in the Controller view.
    I powered off the system last night, and left it off overnight.  Today I took all the drives out, blew the dust off and reseated them.
    Same thing.  Drive 3 is still missing, and now the rebuild task aborted.
    The drive bay location shouldn't matter, right?  Can I swap the Bay 3 drive with the Bay 4 drive?
    I figure one of two things would happen:
    (1) It will report Bay 3 as being there but Bay 4 as being missing, same situation as is now.  Meaning the problem is in the Bay 3 spare drive.
    (2) It will report Bay 3 as being missing (despite a 'good' drive being present) and Bay 4 will be the (unattached) spare, and the RAID set will be unviable.  Meaning the problem is with the drive bay itself, not whatever drive is plugged into it.
    If "Drive carrier removed" is trying to tell me the disk is bad, why do I not see any log messages about it?  I suppose a spare that never gets used could go bad from lack of use, but ... no messages at all?
    Hesitant to plunk down $160 on a new spare disk if the present one isn't actually dead ...
    % sudo raidutil list raidsetinfo
                                         Total     Avail
    Raidsets      Type       Drives       Size      Size  Comments
    RS1           RAID 5     1,2,4      5.23TB    0.00MB  Rebuild: 0% complete            
    % sudo raidutil list driveinfo
    Drives  Raidset       Size      Flags
    Bay #1  RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
    Bay #2  RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
    Bay #4  RS1             2.00TB   IsMemberOfRAIDSet:RS1 IsReliable
    Event log snippet:
    Saturday, January 11, 2014 8:15:19 AM PT
    Background task aborted: Task=Rebuild,Scope=DRVGRP,Group=RS1
    informational
    Friday, January 3, 2014 3:50:28 AM PT
    Drive carrier 00:03 removed
    informational
    Thursday, January 2, 2014 4:29:37 PM PT
    Marked drive in bay 3 as a global spare
    informational
    Thursday, January 2, 2014 4:29:28 PM PT
    Adopted drive in bay 3
    informational
    Thursday, January 2, 2014 4:28:34 PM PT
    Degraded RAID set RS1 - No spare available for rebuild
    critical
    Saturday, December 7, 2013 5:35:17 PM PT
    Marked drive in bay 3 as a global spare
    informational
    Saturday, December 7, 2013 5:35:08 PM PT
    Adopted drive in bay 3
    informational
    Saturday, December 7, 2013 5:34:11 PM PT
    The "RedundancyScrub" command could not be executed. (Invalid request or invalid parameter in the request.)
    warning
    Saturday, December 7, 2013 5:34:03 PM PT
    Degraded RAID set RS1 - No spare available for rebuild
    critical
    Friday, December 6, 2013 4:56:47 AM PT
    Battery finished conditioning
    informational
    Thursday, December 5, 2013 9:53:44 PM PT
    Battery started scheduled conditioning cycle (write cache disabled)
    informational
    Friday, September 6, 2013 10:53:11 PM PT
    Battery finished conditioning
    informational
    Friday, September 6, 2013 3:41:33 PM PT
    Battery started scheduled conditioning cycle (write cache disabled)
    informational
    Saturday, June 8, 2013 3:41:35 PM PT
    Battery finished conditioning
    informational
    Saturday, June 8, 2013 8:37:49 AM PT
    Battery started scheduled conditioning cycle (write cache disabled)
    informational
    Thursday, May 30, 2013 4:09:51 PM PT
    Marked drive in bay 3 as a global spare
    informational
    Thursday, May 30, 2013 4:09:42 PM PT
    Adopted drive in bay 3
    informational
    Thursday, May 30, 2013 4:08:59 PM PT
    Degraded RAID set RS1 - No spare available for rebuild
    critical
    Thursday, May 30, 2013 3:32:29 PM PT
    Degraded RAID set RS1
    warning

    Power Pig wrote:
    "Hesitant to plunk down $160 on a new spare disk if the present one isn't actually dead ...
    % sudo raidutil list raidsetinfo
                                         Total     Avail
    Raidsets      Type       Drives       Size      Size  Comments
    RS1           RAID 5     1,2,4      5.23TB    0.00MB  Rebuild: 0% complete     
    I was talking about this.
    This looks like a RAID 5 setup without the parity to me. I would said it basically a RAID 0.
    Also you metioned "I guess that previous spare must really have gone 'bad', despite having never been used! "
    I wiped everything out, I selected the 3 disks and clicked on "Create RAID Set" with RAID5 selected and the "Use unassigned drives as spares" option checked.  The 3rd disk has always been marked as the spare ever since then.  You do not have a choice to create a "RAID5 setup without the parity".  If I wanted a RAID0 I would have chosen a RAID0!  raidutil now says
    % sudo raidutil list raidsetinfo
                                         Total     Avail
    Raidsets      Type       Drives       Size      Size  Comments
    RS1           RAID 5     1,2,3,4    5.23TB    0.00MB  No tasks running
    Every time the system would 'lose' Drive 3 on boot, I would just keep rebooting until it was 'found', and then manually re-assign the now-'floating' drive as the spare - and the RAID would rebuild.
    There was never a problem until the day that prompted this post - when it would not find Drive 3 no matter what I did.  I turned the Mac Pro off for several hours until the drives had all cooled down and it still did not find the drive.  I left the machine on but unmounted the degraded volume until I got the new replacement drive.
    I really don't understand what you are getting at. It's like you are trying to tell me I set it up as a 4-drive RAID5 with no parity(!) and that I was in grave danger because one of the disks was gone.  The actual RAID contents (spread across Drives 1, 2 and 4) were never in danger, unless a 2nd disk had failed while the spare was not seen by the Apple RAID card.  I wasn't too worried about that happening.

Maybe you are looking for