Apple RAID A1009 used on Linux VM

While planning expansion of my production mail server I'm hoping to use an Apple RAID array. The system in question is as follow:
- Dell Poweredge 2950
- host OS is CentOS 5
- VM runs Ubuntu 6.0.6
- mail server is Zimbra
From initial research I think one of the QLogic fiber channel cards will be my best bet, bang for the buck, etc.
Will this RAID array handle a 4GB fiber channel interface or am I limited to 2GB?
Does CentOS 5 support any of the QLogic cards?
This isn't an Apple system per se, but I haven't worked with Apple RAID arrays very much.

Thanks for your help William. I'm a bit of a novice with RAID, so please excuse the simple questions.
With fiber channel PCIe cards, if the card is rated for 4GB, does that mean 2GB per interface? Or is this something that is dependent on the model of card?
The Linux distro in question is CentOS 5. I've already posted into the forums on centos.org so if you aren't that familiar with this distro, don't sweat it.

Similar Messages

  • Access MP motherboard SATA ports when using Apple RAID card

    I asked this question in another topic and thought I'd have better luck in a separate topic.
    I will soon be the proud owner of an early 2008 3.2 G Mac Pro with the Apple RAID card. I have been given a lot of great advice by the regulars to this topic area who gave me an idea that I wanted to confirm would work.
    Since the internal HDs are connected through the RAID card, that leaves the iPass connector free to connect 4 more SATA drives to the motherboard. The suggestion was made to use an iPass to 4 x SATA cable to gain access. But where to attach and mount the drives? If not the optical bay, the only alternative is outboard, but what to do with the cable? I also learned here that there are two more SATA ports on the motherboard, and Newer Technology makes a cable that attaches to both and mounts in an empty PCI slot hole. Very neat.
    So why not combine the two? I am not certain, but it appears that the connector genders are such that you could combine an iPass to 3 x SATA cable attached to the motherboard to a pair of the Newer Tech cables, then mount them to the PCI doors enabling the user to attach 4 more SATA drives with suitable for another RAID, boot Camp or whatever. Does this seem a reasonable solution? Would love some feedcak on this. Thanks.

    This:
    > But, when I install Mavericks to 512GB SSD in PCIe slot, installation finishes without problem, but the system NEVER boot up with that drive.
    It is not uncommon to have trouble installing, cloning, or booting from a PCIe card - though the Sonnet Tempo Pro SSD is one of the reliable ones, still, you should install the OS first on SATA II normally, then move the SSD to its new home.
    The fact the SSD works on the ODD port - have you asked or looked for firmware update or anything from Sonnet and what they have to say?
    With three PCIe cards to contend with, they may interact - not unheard of - and the USB3 may need drivers first to work?

  • Apple Raid Card panic on Mac Pro Early 2008 after installing SSD as an enhanced JBOD.

    I recently installed a SSD drive in my Mac Pro to replace an aging, original boot drive.  I have an Apple raid card with 3 other hds attached - all in an enhanced JBOD configuration.  After installing the SSD from OWC (3G Electra SATA II Compatible) everything appeared to work fine.  But after 36 hours I received a apple raid card kernel panic alert.  See below for diagnostic crash log.  OWC support says that their drive should work fine - now I am not so sure.  Anyone out there with suggestions/solutions is most welcomed.
    Anonymous UUID:       83ADF2C8-4D41-D2EE-58C2-0CC4344DB0B4
    Sun Jan  5 21:18:46 2014
    panic(cpu 3 caller 0xffffff7f98b1441e): "AppleRAIDCard controller panic"@/SourceCache/AppleHWRaidDriver/AppleHWRaidDriver-401/Driver/Driver/Apple RAIDCard.cp:1018
    Backtrace (CPU 3), Frame : Return Address
    0xffffff8221563e30 : 0xffffff8017622f69
    0xffffff8221563eb0 : 0xffffff7f98b1441e
    0xffffff8221563ef0 : 0xffffff8017aada80
    0xffffff8221563f30 : 0xffffff8017aac522
    0xffffff8221563f80 : 0xffffff8017aac5f7
    0xffffff8221563fb0 : 0xffffff80176d6aa7
          Kernel Extensions in backtrace:
             com.apple.driver.AppleRAIDCard(401.0)[06045EA1-0404-36C3-9BE6-FE217DCD420C]@0xf fffff7f98b11000->0xffffff7f98b26fff
                dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(3.6.0)[657BB360-C3EA-3D01-934E-12DBD6 0BBBF5]@0xffffff7f97f80000
                dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f97cba000
                dependency: com.apple.iokit.IOSCSIParallelFamily(3.0.0)[B6D80E76-647D-3BAE-823A-85871E9BAC7 2]@0xffffff7f97ca9000
                dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(3.6.0)[76253A22-A1DB-3BF4-A972-E6 94A37CD09A]@0xffffff7f97c78000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    13B42
    Kernel version:
    Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
    Kernel slide:     0x0000000017400000
    Kernel text base: 0xffffff8017600000
    System model name: MacPro3,1 (Mac-F42C88C8)
    System uptime in nanoseconds: 91308918786320
    last loaded kext at 89490169308794: com.apple.filesystems.smbfs          2.0.0 (addr 0xffffff7f99714000, size 335872)
    last unloaded kext at 1120636252260: com.apple.driver.StorageLynx          3.3.5 (addr 0xffffff7f99714000, size 8192)
    loaded kexts:
    com.apple.filesystems.smbfs          2.0.0
    com.apple.driver.AudioAUUC          1.60
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleBluetoothMultitouch          80.14
    com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
    com.apple.driver.AppleUpstreamUserClient          3.5.13
    com.apple.driver.AppleMCCSControl          1.1.12
    com.apple.kext.AMDFramebuffer          1.1.4
    com.apple.iokit.CSRBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.AMDRadeonX3000          1.1.4
    com.apple.driver.AppleUSBDisplays          360.8.14
    com.apple.driver.AppleHDA          2.5.3fc1
    com.apple.driver.AppleMCEDriver          1.1.9
    com.apple.kext.AMD5000Controller          1.1.4
    com.apple.driver.AppleLPC          1.7.0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AppleHWAccess          1
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.XsanFilter          404
    com.apple.driver.Oxford_Semi          3.3.5
    com.apple.iokit.SCSITaskUserClient          3.6.0
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          35
    com.apple.driver.AppleIntel8254XEthernet          3.1.3b1
    com.apple.driver.AppleRAIDCard          401
    com.apple.driver.AppleUSBHub          650.4.4
    com.apple.driver.AppleAHCIPort          2.9.5
    com.apple.driver.AppleIntelPIIXATA          2.5.1
    com.apple.driver.AppleFWOHCI          4.9.9
    com.apple.driver.AppleUSBEHCI          650.4.1
    com.apple.driver.AppleUSBUHCI          650.4.0
    com.apple.driver.AppleACPIButtons          2.0
    com.apple.driver.AppleRTC          2.0
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          2.0
    com.apple.driver.AppleACPIEC          2.0
    com.apple.driver.AppleAPIC          1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
    com.apple.nke.applicationfirewall          153
    com.apple.security.quarantine          3
    com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
    com.apple.kext.triggers          1.0
    com.apple.driver.IOBluetoothHIDDriver          4.2.0f6
    com.apple.driver.AppleMultitouchDriver          245.13
    com.apple.iokit.IOSerialFamily          10.0.7
    com.apple.driver.AppleSMBusController          1.0.11d1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.iokit.IOAcceleratorFamily          98.7.1
    com.apple.driver.DspFuncLib          2.5.3fc1
    com.apple.vecLib.kext          1.0.0
    com.apple.iokit.IOAudioFamily          1.9.4fc11
    com.apple.kext.OSvKernDSPLib          1.14
    com.apple.iokit.IONDRVSupport          2.3.6
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.kext.AMDSupport          1.1.4
    com.apple.AppleGraphicsDeviceControl          3.4.12
    com.apple.iokit.IOSurface          91
    com.apple.iokit.IOBluetoothFamily          4.2.0f6
    com.apple.driver.AppleHDAController          2.5.3fc1
    com.apple.iokit.IOGraphicsFamily          2.3.6
    com.apple.iokit.IOHDAFamily          2.5.3fc1
    com.apple.driver.AppleSMC          3.1.6d1
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.5.1d27
    com.apple.driver.AppleUSBHIDMouse          180.9
    com.apple.driver.AppleHIDMouse          180.9
    com.apple.driver.AppleUSBHIDKeyboard          170.15
    com.apple.driver.AppleHIDKeyboard          170.15
    com.apple.iokit.IOUSBHIDDriver          650.4.4
    com.apple.driver.AppleUSBMergeNub          650.4.0
    com.apple.driver.AppleUSBComposite          650.4.0
    com.apple.iokit.IOFireWireSerialBusProtocolTransport          2.5.1
    com.apple.iokit.IOFireWireSBP2          4.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.0
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOATAPIProtocolTransport          3.5.0
    com.apple.iokit.IONetworkingFamily          3.2
    com.apple.iokit.IOSCSIParallelFamily          3.0.0
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
    com.apple.iokit.IOUSBUserClient          650.4.4
    com.apple.iokit.IOAHCIFamily          2.6.0
    com.apple.iokit.IOATAFamily          2.5.2
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOUSBFamily          650.4.4
    com.apple.driver.AppleEFINVRAM          2.0
    com.apple.iokit.IOHIDFamily          2.0.0
    com.apple.driver.AppleEFIRuntime          2.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          278.10
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.AppleKeyStore          2
    com.apple.driver.DiskImages          371.1
    com.apple.iokit.IOStorageFamily          1.9
    com.apple.iokit.IOReportFamily          21
    com.apple.driver.AppleFDEKeyStore          28.30
    com.apple.driver.AppleACPIPlatform          2.0
    com.apple.iokit.IOPCIFamily          2.8
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    com.apple.kec.pthread          1
    System Profile:
    Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 18 GB, SMC 1.25f4
    Graphics: ATI Radeon HD 5870, ATI Radeon HD 5870, PCIe, 1024 MB
    Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x80AD, 0x48594D5035313241373243503844332D5335
    Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x80AD, 0x48594D5035313241373243503844332D5335
    Memory Module: DIMM Riser B/DIMM 3, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353142363445363830304600
    Memory Module: DIMM Riser B/DIMM 4, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353142363445363830304600
    Memory Module: DIMM Riser A/DIMM 3, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Memory Module: DIMM Riser A/DIMM 4, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Bluetooth: Version 4.2.0f6 12982, 3 services, 22 devices, 1 incoming serial ports
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: ATI Radeon HD 5870, Display Controller, Slot-1
    PCI Card: ATI Radeon HD 5870, ATY,LangurParent, Slot-1
    PCI Card: Apple RAID Card, RAID Controller, Slot-4
    Parallel ATA Device: PIONEER DVD-RW  DVR-112D
    USB Device: Hub
    USB Device: Keyboard Hub
    USB Device: Apple Optical USB Mouse
    USB Device: Apple Keyboard
    USB Device: XD-0405-U
    USB Device: Apple Cinema HD Display
    USB Device: USB2.0 Printer (Hi-speed)
    USB Device: Bluetooth USB Host Controller
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    FireWire Device: unknown_device, Iomage HDD, Up to 800 Mb/sec
    FireWire Device: unknown_device, Unknown
    Thunderbolt Bus:

    RE: Mac Pro Replacement Graphics cards
    1) Apple brand cards,
    2) "sold in the Apple store" cards, and
    3) "Mac Edition" cards ...
    ... show all the screens, including Boot up screens, Safe Mode, Installer, Recovery, debug screens, and Alt/Option boot screens. At this writing, these choices include:
    1) Apple brand cards:
    • Apple-firmware 5770, about US$250** works near full speed in every model Mac Pro, Drivers in 10.6.5
    • Apple-firmware 5870, about US$450
    2) "sold in the Apple store" cards
    • NVIDIA Quadro 4000, about US$1200
    • NVIDIA Quadro 5000, about US$2500
    3) "Mac Edition" cards -- REQUIRE 10.8.3 or later:
    • SAPPHIRE HD 7950 3GB GDDR5 MAC Edition, about US$480** Vendor recommends Mac Pro 4,1
    • EVGA GTX 680 Mac Edition, about US$600
    The cards above require no more than the provided two 6-pin aux power connectors provided in the Mac Pro through 2012 model. Aux cables may not be provided for third-party cards, but are readily available.
    If you are Meet ALL of these:
    • running 10.8.3 or later AND
    • don't care about "no boot screens" etc AND
    • can re-wire or otherwise "work out" the power cabling, THEN:
    You can use many more cards, even most "PC-only cards"

  • Windows 7 Thunderbolt Apple RAID crashes?

    So Wndows 7 started getting CACHE_MANAGER BSODs, yesterday. They go away if ther LaCie Thunderbolt SSD is unplugged; configured the SSD as 2 disks instead of an Apple RAID seems to get rid of the problem as well.
    Given that there doesn't seem to be a way to install Windows on the SSD, I'd be reasonably content to disable Thunderbolt entirely for the moment; however, disabling Thunderbolt in the Device Manager does nothing.
    So any help disabling Thunderbolt or fixing the real problem would be appreciated.
    Thanks.

    Thunderbolt ports and displays: Frequently asked questions (FAQ)
    https://support.apple.com/kb/HT5219
    https://www.apple.com/thunderbolt/
    rMBP, Bootcamp off thunderbolt drive - MORE COMPLETE SOLUTION
    http://forums.macrumors.com/showthread.php?t=1414769
    https://discussions.apple.com/thread/4232557
    Boot Camp: FireWire devices may affect Windows 7 responsiveness if connected to an Apple Thunderbolt display
    http://support.apple.com/kb/TS4190
    This looks promising:
    http://www.macwindows.com/bootcamp5.html
    Thunderbolt problems with Windows 8
    TIP: Fix for Thunderbolt problem with Windows 8 in Boot Camp
    Boot Camp users who updated Windows 7 to Windows 8 may find that a Mac booted with Windows 8 does not recognize Thunderbolt . According to a new Apple tech article, the problem is an incompatibility with the Windows 8 Fast Boot feature (also called Fast Startup). The workaround is to disable Fast Boot using the Windows Control Panel.
    Here's how:
    In Windows 8, open the Control Panel. (You can move the mouse to the upper-right corner to activate the Charms bar, click the Settings icon, and then select Control Panel.) 
    Select Hardware and Sound. 
    Under Power Options, choose Change What the Power Buttons Do. 
    Under Shutdown Settings, uncheck the Turn On Fast Startup. Checkbox. 
    Click Save and then restart the Mac back into Windows.
    After restart, Windows 8 will recognize Thunderbolt devices attached to the Mac.

  • Windows and Mac Pro w/ Apple RAID card

    It happened i have a need to run Windows natively on Mac Pro with Apple RAID card installed.
    I know there is no Windows driver for that card, but i had a hope to bypass RAID card via connecting of internal SATA drive directly to iPass(SSF-8087) connector of Mac Pro's motherboard and using of that drive for Windows.
    So, i've connected SATA drive this way and it works fine with OS X.
    But i can't even try it with Windows because Mac Pro doesn't boot up from Windows installation CD if Apple RAID card installed
    Empty black text console is all that i've got after selecting of Windows installation CD in EFI boot menu.
    I need a suggestion how to bypass my problem, or generally speaking, how to install Windows onto Mac Pro with Apple RAID card.

    I've tried that.
    Installation and booting of WinXP passed OK if RAID card removed.
    But i've got black screen again trying to boot WinXP after RAID card re-installed.

  • How do I determine what needs attention on my Apple RAID card?

    Every time I turn on the computer, I get a message that says," The Apple RAID Card installed in your system requires your attention."
    This is what I have: RAID 065-7214 Mac Pro RAID Card
    Why do I keep getting this message? I am not sure what needs to be done to rectify any error. If there is no error and the warning is just due to battery charging, then I would like the warning to stop appearing--or do I just have to continuously click "Ignore"? Any insight into this?
    When I open RAID Utility it says: RAID set R0-1 has been mounted with indeterminate data loss. ( Is this just due to improper shutdown?)
    Also: Controller reports RAID system 72-hour battery reserve unavailable-System is configured to run without battery.
    Message was edited by: Darlyne

    I have had the exact same error message. When you open Raid Utility (that is where you can read what "attention" is needed you will see under the "Status" section what happened, and under the "Tasks" you will see the raid card "initializing" your RAID set. The first time I saw this I freaked, thinking that my drives were being reformatted, and my data would be lost. This is not the case. If you look down on the left side, you will (hopefully) see green lights next to your drives. The initialization seems to be a verification of the raid structure -- basically checking to make sure everything is redundant.
    So, back to the original question: it seems from my poking around that you SHOULD NEVER TURN OFF your Mac Pro with an Apple Raid Card installed. The firmware is not able to spin down the drives correctly, so when you turn your machine back on, you get the error message we have been discussing.
    I would recommend you get a good battery backup (UPS, like an APC) and just power off your monitor when not using your machine. I did not see this in the documentation, I am not 100% sure, but this is what I will be doing. In my case it takes many hours for the Raid Util to initialize my Raid again.
    Hope this helps.
    Theo

  • Apple RAID card II - will it work in single CPU Mac Pro 4,1?

    Will the Apple RAID card work in a quad core 2009 Mac Pro?  I'm refurbing a used Mac Pro I got at a great price and just wondering if I can put in this card (which was "thrown in" with a used 8 core I also bought) with the idea of doing a RAID 10 to experiment with getting top disk read/write performance. I know most do not like the Apple RAID card II but it might be a cost effective way to max out performance on the single CPU, quad core Mac Pro. Ultimately I want to falsh the firmware to 5,1 and upgrade the CPU to a W3690 hex core. I plan to use this box for photography, light video and possibly sound editing. If my plan will result in high benchmarks and provide some fault tolerance I'm comfortable with using the card. I have heard from other users that the new card is much better than the first version and that it actually works pretty well. Any insights appreciated.

    Heck!
    Im about to win an eBay auction for a blue Apple RAID card together with a pair or SAS 300gb cheetah 15.5k discs for 75 bucks *happy*. Would have been healthy fast upgrade for small investment I thought?!
    Guess it probably would have been if the thing worked!?
    Why doesnt it work? iPass cable or something like that?
    Suppose I still want to go the SAS route with those drives for performance. Any other cards not too expensive that will enable SAS in the Pro?
    I use my MP 4,1 as a photo edit workstation but I also keep it on 24/7 for home server, web server, nas, backup etc. So i like to use items that are made for round the clock usage.
    Or i just get inexpensive SATA drives and SoftRAID them. So RAID 0+1 is no problem in software RAID?
    Thank you guy for quick informed response

  • Suggestions for removing Apple RAID Card?

    After a year of dealing with problematic Apple RAID cards, and replacement batteries – we are ready to move on, without the RAID card.
    We have not yet used it as a RAID – all drives operate discretely, non-RAIDed.
    We propose to remove the RAID card to eliminate that point of common failure. Has anyone else faced this, done this? Any suggestions, warnings?
    TIA for your kind attention.

    Hi Michael,
    What issues are you having? I had an issue with a faulty battery on a new xserve but once that was swapped out it's been as good as gold. If the drives you have installed have not been raided then you could buy the SATA backplane for the Xserve and swap it out.. Takes about 10 mins to do.
    All the best
    Beatle

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

  • Simple Apple RAID question...

    New MacPro, Apple RAID Card, 4 1TB drives, all included in the RAID 5 array that has been created and initialized in RAID Utility booted from the OS install disk. All looks well ATM.
    I now want to partition this array into two partitions. One 300 GB for OS/Apps, the other 2.x TBs for data. Someone mentioned I should partition using the RAID Utility, but can't figure out how to do this. Should I just be using Disk Utility to create the partitions on my new 4 drive, RAID 5 set?
    Thank you!! The RAID Utility user manual has no mention of this, and finding this answer on the internet is difficult.

    That explains the RAID setup, which I have created and successfully initialized. I never had the manual, but looking at it now that's exactly how I did it.
    Now that it has completed, I have a 4 disk RAID 5 "set", that is 2.x TBs in size, which is perfect. All I wanted to do was partition this set into two separate "volumes", just like you can do with any other "drive". I went into Disk Utility (booted to the install disk, the same disk that contained the RAID Utility), and created the partition in 2 minutes. I don't want to create two RAID sets, more drives in a RAID 5 set the faster, and didn't want to lose the HD space that 0+1 entails.
    I'm just wondering if this was correct, if doing it this way creates issues, etc...
    THANK YOU both for your responses!

  • How can I force the Disk Cache on with Apple Raid Card?

    I have an apple raid card in my mac pro that has now had it's battery fail twice. I don't really want to keep putting money into this and would rather just force the disk cache on and hope my UPS works, I don't use this box for real work anymore anyway and it's all backed up.
    There used to be a force on button next to the Write Cahce Status section, but that seems to have gone away. Does anyone know how to force the cache on? Permanently if possible.

    OK, Command Line fun, use at your own risk:
    sudo raidutil modify controller -E

  • Apple raid ip address assignment...??

    I have an apple Xserve with ip address of ::
    ip address :: 192.168.1.xxx.
    subnet mask :: 255.255.255.0
    router :: 192.168.1.1
    It is connected on en0 port. I have then attached my apple RAID to the other ethernet port en1. In network pref on the server it shows up as active and self assigned. The Raid ethernet connection shows up with
    ip address :: 169.254..68.212
    subnet mask :: 255.255.0.0
    router :: NA
    I have read through other threads and it seems to use RAID admin I need to be on the same subnet mask. How do I do get the RAID on the correct subnet mask and give it an appropriate ip address.
    I need to keep the server on 192.168.1.xxx
    Much Thanks in advance

    Power off the the XServe Raid. Attach network cables to the Ethernet management ports on the controller(s). Plug the network cable(s) into a switch port(s), -obtain a switch if you don't have one, attach the switch to your network. Power on the XServe Raid. Read the manuals:
    http://manuals.info.apple.com/en/XserveRAID_UserGuide.pdf
    http://manuals.info.apple.com/en/XserveRAID_AdminDiskUtility.PDF
    http://docs.info.apple.com/article.html?artnum=51795

  • XServe Raid A1009 & Xserve Dual Core Compatibility

    We have a 2X2GHz Dual-Core Intel Xeon and are looking at an Apple xServe Raid A1009..
    the Xserve has 2 fibre channels available.
    Apple 2 Port 2Gbps Fibre Channel Card:
    Name: pci-bridge
    Type: PCI-to-PCI Bridge
    Driver Installed: Yes
    Bus: PCI
    Slot: Slot-1
    Vendor ID: 0x8086
    Device ID: 0x0340
    Revision ID: 0x0009
    Link Width: x4
    Link Speed: 2.5 GT/s
    1. are these units compatible?
    thanx
    TW

    +im lead to believe that i can put any old ATA/IDE drived up to 750GB as long as i run the latest firmware is that correct?+
    When 750 PATAs were plentiful peoples results were mixed. The simple version is if the RAID understands the SMART controller the drive would work. Mostly there were a few 750GB models "known good" so everyone went with those until they stopped making them. I have to disagree with the "any old" characterization. It's not as picky as the Xserves but certain models *do not* work. Search the old threads about people trying trying different drives with mixed results. As I said the Caviar 500GB are the only drives still being made that I know of to reported as "known working".
    On the larger issue I would very much hesitate to mix and match any drives in a RAID set-up due to reliability issues between drives. Whatever drives you settle on I would get them all the same models new at the same time.
    I like my Xserve RAID - the thing is a workhorse - but I'd look at the cost + the cost of 16 replacement drives and look at what you might get in a SATA housing since those drives are still current.
    My $.02,
    =Tod

  • How do I expand my apple raid

    I have an apple raid card in my Mac pro. I have set it up as a Raid 5 with Three internal 1.5 TB drives. I just replaced one with a 3tb drive. However the capacity did not increase. I looked at the manual and it tells me:
    Expanding a Volume
    You can use the command line to expand (add space to) an existing volume from the
    available space on the RAID set that hosts it. Expanding a volume doesn’t affect data
    already on the volume.
    To expand a volume:
    m Open Terminal and enter the following command:
    $ sudo raidutil modify volume --expand -n volume -s size
    where volume is the name of the volume as shown by the raidutil list volumeinfo
    command and size is the amount of space you want to add to the volume.
    For more information, see the raidutil man page.
    So I opened terminal and put in what it says. However terminal keeps getting stuck. below is what its saying. If anyone can tell me what I am doing wrong that would be awesome. I'm not sure why Apple put in such a round about expandtion any way.
    NYCretoucher-Remote:~ nisian$ sudo raidutil modify volume R1V1 --expand -n volume R1V1 -s size 700g
    Required argument missing: '--rewrite', or '--verify', '--move', '--expand'.
    usage: raidutil <global-options> modify volume <required-arguments> <optional-arguments>
        global-options:
            [--controller <ControllerType> | -c <ControllerType>]
            [--terse | -t]
            [--verbose | -v]
            [--version | -V]
        --expand | -e
            required arguments:
                --name <VolumeName> | -n <VolumeName>
                --size <SizeToExpandVolume> | -s <SizeToExpandVolume>
            optional arguments:
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
        --move | -m
            required arguments:
                --names <VolumeName> | -n <VolumeName>
                --targetraidset <TargetRAIDSetName> | -t <TargetRAIDSetName>
                --raidset <RAIDSetName> | -r <RAIDSetName>
            optional arguments:
                --waitfortask | -W
        --rewrite | -w
            required arguments:
                --name <VolumeName> | -n <VolumeName>
            optional arguments:
                --priority <ServicePriority> | -p <ServicePriority>
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
        --verify | -v
            required arguments:
                --name <VolumeName> | -n <VolumeName>
            optional arguments:
                --priority <ServicePriority> | -p <ServicePriority>
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
    NYCretoucher-Remote:~ nisian$ sudo raidutil modify volume R1V1 --expand
    Required argument missing: '--rewrite', or '--verify', '--move', '--expand'.
    usage: raidutil <global-options> modify volume <required-arguments> <optional-arguments>
        global-options:
            [--controller <ControllerType> | -c <ControllerType>]
            [--terse | -t]
            [--verbose | -v]
            [--version | -V]
        --expand | -e
            required arguments:
                --name <VolumeName> | -n <VolumeName>
                --size <SizeToExpandVolume> | -s <SizeToExpandVolume>
            optional arguments:
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
        --move | -m
            required arguments:
                --names <VolumeName> | -n <VolumeName>
                --targetraidset <TargetRAIDSetName> | -t <TargetRAIDSetName>
                --raidset <RAIDSetName> | -r <RAIDSetName>
            optional arguments:
                --waitfortask | -W
        --rewrite | -w
            required arguments:
                --name <VolumeName> | -n <VolumeName>
            optional arguments:
                --priority <ServicePriority> | -p <ServicePriority>
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
        --verify | -v
            required arguments:
                --name <VolumeName> | -n <VolumeName>
            optional arguments:
                --priority <ServicePriority> | -p <ServicePriority>
                --raidset <RAIDSetName> | -r <RAIDSetName>
                --waitfortask | -W
    NYCretoucher-Remote:~ nisian$

    Three problems with this:
    1. My understanding is that the Apple RAID card doesn't support drives larger than 2.2TB in size.
    2. RAID 5 requires all drives to be the same size in order for more space to be available, then the file system needs to be grown.
    3. The odds of an unrecoverable read error in the course of rebuilding a 3TB consumer SATA hard drive is actually rather high. 1 bit error in 1E14 is the most typical URE published by hard drive manufacturers for consumer SATA, and that translates to 11.4 TB, that is ever 11.4.TB of read, 1 bit error is expected. In the event of an unrecoverable read error, the reconstruction is halted. And a 3 disk RAID 5 means you're reading 6TB of data to rebuild the 3rd drive. So your statistical chance of failure is in the vicinity of 50/50. Not good odds. Therefore you already need to consider RAID 6, or RAID 10 (or RAID 1 + linear which is growable by adding 2 disks of the same size at a time, which can be different sizes than the disks already in the linear array).

  • Apple Raid 5 Lost?

    I have a macpro with a Apple raid card.  I have 4 Seagate drives in a raid level 5 config.  Randomly last week, the machine came up with a question mark on start up.  Upon further investigation, the raid apparently had failed completely and I have lost all of my data?  I hope that is not the case.  Upon start up with the raid utility admin tool, the card and the drives are online and the only option I see available is to rebuild the raid.  1.  Has anyone else had this problem?  2. Is there anything I can do to recover the data/raid?

    You haven't provided any useful information at all to go on. Have you read the RAID Utility User Guide? What's the status of the card, the individual drives, and what are the errors and events reported by the utility? Why, exactly, do you say the array has apparently completely failed? If you have two physically dead drives, or more, then for all practical purposes you have lost the data, although a professional data recovery service might have luck reconstructing it.
    RAID is not a backup. RAID 5 actually has a rather high chance of total array failure during rebuild after a single disk has failed; not merely due to the likelihood of a 2nd disk failing during rebuild, but the increasing likelihood of parity error or a sector read error occurring during rebuild.
    Proprietary RAID is much more difficult to recover data from in the event of an additional failure of an already degraded array.

Maybe you are looking for