Apple Raid card fitted - expand command fails

Ladies and Gents,
Terminal and RAID n00b here.
4 x 750Gb drives in a Mac Pro with Raid card fitted.
Created R5 with 3 drives (messed up, expected 1.3Tb R5 - Got 698Gb + 670Gb spare space)..
Just wanted 1.3 Tb R5. Tried expand command from the user guide;
Terminal I/O below - any help please?
no-dns-yet:~ sn$ raidutil list volumeinfo
Volumes Status Raidset Type Size Comments
R3V1 Is Viable RS1 RAID 5 698.45GB Condition: Good
no-dns-yet:~ sn$ sudo raidutil modify volume --expand -n R3V1 -s 670.63GB
Unsupported by this version of the hardware/firmware.
Obliged for assistance please...
GUI screenshot here;
files.me.com/burtonboyz/2i0f74

Oops wrong forum - sorry

Similar Messages

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

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

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

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.

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

Repair Apple RAID card battery

I have an Apple RAID card Mac Pro (Early 2009) RAID Card (top picture) with a bad battery. Unfortunately these batteries usually die after a few years and the replacement is not cheap. Looking on ebay, I can only get them from the US, but I live in Europe and it will cost me at least $150.
From what I suspect reading the case, the battery is a 3.7 V Lithium battery, probably with built-in electronics that I can perhaps get for $5 from China. Any soldering work is not a problem. If I can replace the digitizer of an iPad mini, I can probably replace a battery too.
The case of the battery looks like a regular aluminum box and the lit is probably just glued onto the battery. It's seems quite sturdy and would require some force to open. Has anyone ever opened an Apple Raid Card battery? I'm reluctant to apply much heat to open the case, though external heat might be ok. Any ideas? I'm aware of the risks.

To summarise the 'end of days' issue with RAID5 the problem is that with the much bigger size of hard disks now available and being used e.g. 4TB or even bigger, it takes so long to rebuild a RAID5 array when replacing a faulty drive that the chance of another drive failing during the rebuild is becoming more and more likely. This is actually made worse by the fact that a RAID rebuild causes a lot of activity and therefore 'stress' on the hard disks in order to do the rebuild process. It can take more than 24 hours to do a complete RAID5 rebuild and during all that time you are vulnerable to a complete failure.
RAID6 is a partial solution in that you start off with redundancy provided by two drives rather than RAID5 which has just one so RAID6 can survive two drive failures. It however only reduces the chances of having a complete RAID failure during a rebuild it does not eliminate it.
Standard RAID5 or RAID6 therefore is being increasingly viewed as having reached a brick wall.
For Enterprises i.e. those with lots of money you can just throw more drives at the problem e.g. RAID10. For the rest of us the hope is on new alternatives to RAID5. The one I am particularly excited about is BTRFS, this is a combination of both a RAID layer and a file-system layer, it is able to use file checksums from the file-system layer to spot and fix RAID issues and this is orders of magnitude more efficient than having to do a complete RAID resync/rebuild. This approach has two advantages, firstly it protects a problem described as 'bit rot' whereby a byte or block in a file can become corrupted, the checksums allow this to be detected and automatically fixed, the second is that it can do a rebuild of actual real data whereas a normal RAID rebuild rebuilds all blocks on a drive even empty ones.
BTRFS is still pre-release especially its equivalent of RAID5 and RAID6 but it is getting closer. (RAID 0 and 1 for BTRFS are already considered ready for use.)
ZFS is a similar 'new' file-system to BTRFS and at one point there was talk that Apple were going to switch to using ZFS but this no longer looks like happening. ZFS was a solution being developed and 'owned' by Sun Microsystems who are now part of Oracle. BTRFS is free open-source.
I personally hope that Apple at some point implement BTRFS.
There are some NAS manufacturers already implementing BTRFS however they are currently 'cheating'. NetGear for example use BTRFS on their current ReadyNAS OS 6.x models but rather than using a 'pure' BTRFS approach have a implemented BTRFS on top of a standard RAID5 system created by mdraid. They did this because as I mentioned above the official BTRFS RAID5/6 solution is not yet ready for real-world use. As a result you get some of the benefits of BTRFS like being more easily able to expand the size of a file-system, but you don't get the full checksum derived protection of BTRFS because it is not integrated to the RAID level. Thecus I believe have gone the same approach as NetGear. Synology and QNAP are still waiting for BTRFS to be 'finished' before implementing it.

What's the difference in Apple RAID card battery error messages?

I have a Mac Pro with 2 quad core Intel Harpertown CPUs at 3.2GHz, and an Apple RAID card. RAID Utility shows that the battery failed but in my research, nobody explains the difference between "Battery failed (code 0x#0 = 17)" (which is what I have) and "Battery failed (code 0x#0 = 18)" or ""Battery failed (other than expired)" (the latter two are what everybody talks about) and what the code numbers mean. Speaking to a local AASP, they recommend that I just wait for a couple of days to see if it's doing the automatic 72-hour reconditioning operation since my Mac Pro is attached to a pretty hefty UPS (2200VA with nothing else attached) and power failures where I live are rare plus the write cache has been disabled so the RAID card is basically doing write-throughs at the moment. But curiosity about the various, different error codes and messages is getting the better of me. Thanks in advance.
Also, what's worrying me (since RAID Utility is so vague) is this entry I found under "Hardware RAID" in System Profiler:
Status:
Charging:          No
Conditioning:          No
Connected:          Yes
Discharging:          No
Sufficient Charge:          No

As an update to this, once I replaced the RAID card battery (which was an absolute nightmare--the writer of the instructions at Apple obviously had never done it for real nor seen it done since they omit a lot of important things), the problem went away. But I'm still intrigued about what the error codes mean.

Apple RAID Card (Early 2009) Firmware Update 1.1

The update is recommend for all Mac Pro (Early 2009) and Xserve (Early 2009) systems with the Apple RAID card.
This update provides several fixes, including:
Reliability improvements during boot and power fail recovery
Improves handling of hard drives with bad blocks
Improves RAID 1 read performance
Improves hard drive compatibility with non-Apple drives
Improves support for systems with 48GB or larger memory
Improves battery handling and reporting
This update requires Mac OS X v10.5.8 or Mac OS X Server v10.5.8 or later. You will need to restart your computer as part of the update process.
http://support.apple.com/kb/HT3831
After this update has successfully completed,
your RAID Firmware Version will be: E-1.3.2.0
The updater application will be installed in the /Applications/Utilities folder and will launch automatically. Please follow the instructions in the updater application to complete the update process.

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

Apple raid card enigma

I have two Mac pros, on both I've installed the Apple raid card. Recently I've noticed that my 2008 Mac Pro does not react to based commands anymore. For example if I try to boot the computer on single user mode it doesn't react, the same goes to any other basic combined like P. RAM reset or target disk mode or even booting from a CD by pressing the C key on boot.
Once I've discovered that, I went and checked it on my 2007 Mac Pro. To my surprise the same thing occurs! It looks to me there is some sort of a firmware issue involved with the Apple raid card, I've called Apple support and they were in the dark as much as I am, at least the first two levels of support I never got to an engineer .
I was wondering if there is anyone else experiencing the same issues that I have and if there is anyone who has a work around for a these issue?

I have had issues with both a 2007 and 2008 mac pro booting to commands, when i was using a dell key board. But when i plugged the apple keyboard in they both worked. I know that this is probably not your problem but i figured on the slight chance it is there you go.

Apple RAID Card help needed

OK, new Mac Pro with Apple RAID card and three drives. Discovered RAID 5 is not setup as shipped.
Thought I would need to run Disk Utility, told no it's RAID Admin, but found out it's a app called RAID Utility, so I set this up. Also found out I could "migrate" existing OS X Server volume on Drive 1 to the RAID 5 without reinstalling... but after migration, found one partition with the OS and another empty partition. Are there any tools to expand the existing Partition 1 to include space on Partition 2 with the OS, without destroying/reinstalling it? Thanks - Lewis

You could open Disk Utility and click the RAID volume. Under partitions, see if you can make it 1 partition and retain data.

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

Apple Raid card fitted - expand command fails

Similar Messages

Maybe you are looking for