Apple Raid Card, multiple drives and volumes

Hallo,
my xserve (early-2008) has an Apple Raid Card and two 300GB SAS-drives installed (mirroring).
Is it possible to install a third disk (300GB SAS) and to use it as a separate Volume ?
Disk 1 (300GB SAS) - Apple Raid Card mirroring: Volume 1 (300GB)
Disk 2 (300GB SAS) - Apple Raid Card mirroring: Volume 1 (300GB)
Disk 3 (300GB SAS) - Volume 2 (300GB)
How do I have to set this up using Apple Raid Utility ?
Thanks for your help !

Is it possible to install a third disk (300GB SAS) and to use it as a separate Volume ?
Yes. Of course.
How do I have to set this up using Apple Raid Utility ?
No. A third drive should just appear on the desktop. You only need RAID utility if you want to add that drive to an array, which doesn't sound like the case here.

Similar Messages

  • Mac Pro with Apple Raid Card - 1 drive OSX (JBOD) + 1 drive Vista?

    Can anyone walk me through what I'd need to do to set up an early 2008 model Mac Pro with the Apple Raid Card pre-installed and 2 500 gig drives, so that I can have OSX on the first drive and Vista on the second?
    I know it defeats the purpose of the raid card, but...
    What I've done so far is:
    1. Removed drive #2
    2. Install and using Raid Utility, add the first drive as a JBOD set/volume
    3. After install, shut down the machine
    4. Re-add drive #2
    5. Restart
    6. Use disk utility to add drive #2
    I tried to use bootcamp, but it only wants to put windows on the first drive - which won't work because it is RAID.

    Run Vista off an ATA interface in the 2nd optical drive. There is an SATA 2 ATA adapter.
    I think you can boot Vista off some RAID controllers, check out Highpoint RocketRAIDs. Should be able to configure the RR.
    Boot Vista off USB is a stretch.

  • Apple RAID Card, All Drives RAID?

    For those of you who have the Apple RAID card, I was wondering if all the drives are configured into one RAID set? Or can you have say a single boot drive, a third data drive and then have the remaining two drives set up as a RAID 0?

    I was interested in using the RAID card for 2 drives only, for storing captured video.
    I don't want to use the RAID for my boot/data drive.

  • Apple RAID Card, 4 SAS drives, 1 bootable large striped volume?

    I have an Apple RAID card and 4 SAS 250GB drives. I did the migration when I set up the RAID to give me 1 drive for my bootable OSX volume and the other 3 combined into unused unpartitioned space.
    But I want all 4 drives combined and striped for one large bootable OSX volume. I'd prefer not to have to reinstall OSX to do this.
    Do I need to buy a utility? Can I use Disk Utility or the Apple RAID Utility? I've done searches and read all the help and can't find an answer.

    Is it possible to install a third disk (300GB SAS) and to use it as a separate Volume ?
    Yes. Of course.
    How do I have to set this up using Apple Raid Utility ?
    No. A third drive should just appear on the desktop. You only need RAID utility if you want to add that drive to an array, which doesn't sound like the case here.

  • Is there a firmware update for the Apple RAID Card [early 2009 Xserve] that will take it beyond the E-1.3.2.0 version and allow it to see 4TB drives?

    Is there a firmware update for the Apple RAID Card [early 2009 Xserve] that will take it beyond the E-1.3.2.0 version and allow it to see 4TB drives?

    I have a few of these RAID cards in a couple servers, and then I have an earlier version of the RAID card in a few different servers.
    The earlier servers are running non-apple 1.5 TB drives. It will be interesting to learn if this firmware update will indeed allow me to boost the capacity by installing non-apple drives, as the firmware previously has not.
    Ohh I'm excited to update and try! This will greatly help out if it does!

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

  • Apple RAID Card after System Disk Failure: Volume visible but not mountable

    Hi,
    Im running a Mac Pro with 10.5.8. Server has a workgroup server. The Mac Pro is equipped with a Apple RAID Card running three 1TB SATA Drives and a SAS drive for the System. The three 1TB drives are used by a RAID5 to store the data the SAS drive was used for the system. After a power failure the SAS drive was dead and I installed a new drive and reinstalled the system with the DVDs that were in the box. After that the RAID5 is not mounted by the system anymore although I can sea it in the RAID Utility but not with its volume name but with the name R2V1.
    What can I do to save the data on that RAID?
    Thanks
    Phil

    It's tough to find info on your specific model but the Raid card listed in the Apple Store (http://store.apple.com/us/product/MB845Z/A?mco=MTY3ODQ5OTY) states you must use all SAS drives or all SATA drives with the card. Are you sure that the drive that died was a SAS drive?

  • Apple Raid Card: Raid-1 volume degrading

    Hello,
    I have 2 Raid-1 volumes running on a late 2009 mac pro with an Apple raid card. The second Raid volume has degraded now 3 times in the last 2 1/2 weeks. Raid utility is saying that the drive is damaged but when I shutdown, pull the drive out of the bay and push it back in and then restart it says that the drive is good. After assigning it as a spare the Volume rebuilds and lasts about a week until the same thing starts all over again. Perhaps the drive is somehow damaged but it seems more like a connection problem. If this is a familar issue to anyone and someone has a suggestion it would be greatly appreciated.

    Maybe you need to do a full surface scan for bad or weak failing sectors.
    Next time it drops out (or whenever you decide to remove it manually).
    Use Disk Utility to Initialize with Write Zeroes option. This takes several hours.
    If it completes without any error messages at all, it should then be good to use.
    If Bad Blocks are found, they will generally be spared out by this process, and the drive can be good to use for a while, but is likely to fail within 6 months. You should consider moving it to light-duty or occasional use, such as backups.
    Sometimes the Initialization will fail. If the drive is still under warranty, return it to the manufacturer for a refund/replacement. Original Apple drives have a one-year warranty, same as your Mac. Manufacturer warranties are often (but not always) 3 years or more.

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

  • Non-Apple RAID card with internal drives possible on 2009 model ?

    Hello there,
    I have decided against the Apple Raid card, since it does not support any other drives than the ones sold through the Apple Store and it also only supports up to 1 TB drives.
    My goal is to have 3x 1.5 TB drives in a RAID 5 array.
    Does anybody know any hardware Raid 5 capable adapters, that can be used with internal 1.5 TB drives & the early 2009 Mac Pro model ?
    Cheers,
    Martin

    Once upon a time, in a land far far away, ATTO and LSI, and Adaptec mainly owned the storage market for Mac controllers, and even then in those happy times we heard there was Voodoo in the land, and a curse on what were the Rules of SCSI Voodoo, and one had to be careful that a drive really was certified and tested, and one had to insure which firmware version one was talking about, not just any which firmware - and controllers also had to be updated as well.
    Signal processing over SCSI with good active termination, cable length, and 160 pins (and cable strands) (and no noise or crosstalk, good insulation).
    If one did all of the above, and was careful, you were rewarded with a working storage controller and array and the best possible performance at the time.
    And sometimes you could venture off the reservation... a little, and some drivers could patch and work around bugs in firmware or other problems - just as bugs in cpu, boot firmware, and microcode can be patched by the OS kernel. And people would pay for retail drivers, or they would have to rely on the vendor's bundled driver (that may only work on their own drives and no others).
    Hard Disk Toolkit, Silverlining and others made name for themselves, amoung others that now have faded into oblivion for most.
    But it still exists when you venture beyond consumer and pro-consumer devices and venture to use FC-SCSI, SCSI, and SAS. And taking a chance when you try to use off the shelf SATA storage products and solutions. There are times when OEM drives really are OEM-only and a good thing; and times to avoid.
    And there is no list of any kind of successfully used non-Apple drives, though there is word-of-mouth of a few that definitely need to be avoided.

  • New drives help for APPLE RAID Card RAID Redo

    Hi,
    I've been happily using an Apple 3,1 MacPro with Apple RAID Card installed and connected to 4-500 GB Apple OEM drives. I'd like to redo my setup and replace the Apple drives with bigger drives. Someone said I could only use up to 2 TB drives - is this correct?
    Has anyone done this or anything like it using Seagate Drives that are not Apple OEM. Will that work OK or will the Apple RAID Card want to see Apple OEM drives? Apple sells 2TB Seagates, but they cost a lot compared to non-OEM drives, but will cheaper generic Seagate Barracuddas work OK in every way?
    Also, after accomplishing this upgrade, I'd like to upgrade this machine to the latest Lion and possibly even Moutain Lion System Software. Any issues perceived?
    To reiterate, I'd like to increase my storage to the max in my Early 2008 MacPro3,1 which has the Apple RAID Card utilizing a RAID5. This is spec'd at  "4 - 3.0 Gbps Serial ATA (SATA) controllers" but no mention is made of what the MAX Size drives that will be addressed by the RAID Card.
    Thanks, and so long for now, TOM

    I thought it was an oxymoron to be using Apple RAID card, and to be happy.
    It does not support drives larger than 2.2TB
    Seagate's just seem to be more trouble. Any enterprise drive should do.
    If you really really need RAID5 then maybe this card is useful, otherwise, no.,
    There is much less than 300MB/sec x 4 in bandwith, they are shared and not independent, but the total is more like 800MB/sec maximum. Less overhead and other factors comes in more like 700MB/sec total max. \
    SSDs have come a long way.
    Use a PCIe cards to manage 2 x SSDs of 500GB up to 1TB
    Use Disk Utility or SoftRAID 4 to manage 2-4 drive mirror or stripe arrays
    10.8.4 has a bug that interferes with using 3TB and larger drives, just introduced bug.
    This is the FIRST time there have been limits on drive size. And Apple RAID card. Seems the card is not getting updated firmware to address the need for larger drives. For those using SAS it is also a viable candidate.
    SSD on its own to hold the system. 4 x 2TB WD Black for data and media storage. 4 x SSDs for scratch and graphic catalogues and media... all depends what your goal and use and type of programs.
    No you do not need to use Apple's.
    I cannot vouche for or seen someone doing so but I would hope that WD RED series would be suitable.

  • RAID card or drive?

    My Mac Pro with Apple RAID card will not boot to external FW800 or original install DVD if drives 2, 3, 4 are installed at the same time in any of the bays (i.e. gray screen, no apple, nothing). If I remove or replace any one, or more, or remove all of drives 2, 3, 4 Mac Pro will boot to anything with an OS on it via Opt. key. I'm thinking if any one of drives 2, 3, 4 were bad and drawing too much power the same problem would present when drive 1 (J+ w/ OS) is substituted for any one of 2, 3, 4. Replaced battery on RAID card no effect on problem. Passed Hardware Diagnostic on original Installer DVD. I'm thinking this has to be a RAID card issue. Do they go bad? Any opinions would be greatly appreciated.

    Software RAID?
    No, I have an the Apple RAID card that came with the Mac Pro, factory installed. RAID set was created with Apple RAID Utility. About testing, D-Genius only does a random/sustained read/write. I like the looks of intech's suite, but just spent $$ on new, replacement SAS drive, they're still not cheap, even with the advent of SSDs. Anyway, I had saved a profile of the DG benchtest on the previous RAID volume. When I ran the new disk the results very closely parallel the previous profile very closely. Odd thing is that I'm not sure it was a hardware problem (bad disk). Once I introduced the new disk into the mix, I was able to also re-introduce the old suspected bad disk and it worked. Maybe a RAID fluke??? Maybe the disk was intermittently failing causing the RAID set to fall over? Maybe I'm just cursed....
    If you're really board you can check out all the associated posts from when this debacle began:
    http://discussions.apple.com/message.jspa?messageID=13165864#13165864
    Anyhow, thanks for your help!
    J.

  • MacPro Raid Card single drive size limit

    OK this is a follow up to a previous question about the upper size limit of a single HD that the Macpro Raid card can address.
    It was pointed out to me that "The Apple RAID card cannot address more than 2.2TB of a drive" by Mr. Grant Bennet-Alder. So I am assuming that a 2TB SAS will work.
    I plan to RMA the 4TB drive (that was not recognised), so my question is will this drive work instead?
    Seagate Constellation ES 2TB 6GB/S SAS 7200RPM 3.5in (ST2000NM0001) Hard Drive  -  setup as JBOD.
    It's not that I don't believe what Grant has said, it's just that I don't want to RMA this drive as well, using the old wood working philosophy of 'measure twice, cut once.'
    And I spent 2 hr looking for this info on Apple's support site without any luck.
    SYS INFO
    MacPro 5,1
    2 X 6 Core 2.93 GHz Xeon
    Mac Pro RAID Card
    Bay 1:  450GB Seagate Cheetah SAS -JBOD
    Bay 2:  450GB Seagate Cheetah SAS - Raid set 1
    Bay 3:  450GB Seagate Cheetah SAS - Raid set 1
    Bay 4:  2TB Seagate Constellation (potential drive) to be JBOD
    Raid set 1: Raid 0 - 900GB
    OWC Mercury Accelsior 240GB
    ATI Radeon HD 5870
    Mac OS X 10.6.8
    All software updates current and applied
    Thanks
    -Robert
    Previous thread:
    https://discussions.apple.com/message/21675625#21675625

    If a Disk Fails If a RAID set or volume becomes degraded because a disk has failed, you can use RAID Utility to identify the disk that needs to be replaced.
    Note: If your RAID setup includes a spare drive, it is automatically incorporated into the RAID set, and the set switches from degraded to good as soon as the recovery process finishes. If there is no spare, the set will remain degraded until you replace the failed drive, and if a second drive fails before you replace the first, you could lose data.
    To replace a failed disk:
    1  Open RAID Utility, select the RAID set or volume that is displaying a problem status indicator, and look for a drive bay with a red status indicator. The bay numbers in RAID Utility correspond to the numbered drive bays in your Mac Pro or Xserve.
    2  Replace the bad drive module.
    3  Use the Make Spare command to set up the new drive as a global spare. If no spare was available when the original drive failed, the RAID card uses the new spare immediately to rebuild the affected RAID set and volumes. If a spare was available at the time of the failure, it is already incorporated into the affected RAID set, and the new spare remains available until it is needed.
    https://manuals.info.apple.com/MANUALS/0/MA318/en_US/RAID_Utility_User_Guide.pdf

  • MacPro2009-Apple Raid Card-2.2TB limit

    Hello,
    I have a MacPro (early 2009) with an Apple Raid Card. Lion 10.7.4
    I just bought a 4 Tb Sata hard drive and there is no way to make it work on the Apple Raid Card. When it mount , it only show a capacity of 2,2 TB and Apple disk Utility is of no utility with it on the Raid Card.
    So I managed to hook it in the Optical Drive bay and I have now a 4 TB volume available for Network backup.
    Can you confirm the limit on the Apple raid card
    Version Matériel:          2,00
      Version du programme interne:          E-1.3.2.0
    Thanks,
    Marc LE BRET

    I have this same issue with a mid 2010 MacPro Server running 10.8.2/OS X Server (10.8) and the Apple RAID Card with 3 - 1TB drives and an added 4TB drive (in Bay 4) that is only being seen with the 2.2TB limit.  I even initialized it and tested it a bit with my MacPro1,1 and a NewerTech toaster on eSata.  Very nice to see a workaround with the optical bay... thank you for that suggestion!  I was going to go to another enclosure or hard drive "toaster" / dock that allows 4TB drives and use eSata or FW800 as a connection... the 2nd optical drive bay sounds great and will give it a try. 
    The only thing I can figure from all this and talking to Tier 2 AppleCare is that the RAID card is only 32 Bit addressing O.o  ... which seems crazy but makes the most sense.  They will more than likely respond with "The drive is unsupported, since it isnt an "Apple" HD."

Maybe you are looking for