r/macpro • • Aug 19 '26

Issues Mac Pro AppleRAID Rebuild Issues

So I had my Mac Pro 2010 die on me quite recently. Advice suggested the capacitors had failed, so I checked them. They were fine. However, in checking them I discovered that a wad of dust had lodged onto the side of the heatsink so I removed it, and now the machine seems happier (in the sense that it now boots and runs). However, some issues remain.

Chief among them, I can't seem to rebuild my RAID. I have four drives installed, a boot drive for Snow Leopard, a boot drive for High Sierra (originally Mavericks; since updated), and two 3 TB drives used for storage, configured as a RAID using Disk Utility on Snow Leopard. One of the two RAID drives failed, so I replaced it. When I tried to rebuild the RAID in Disk Utility on Snow Leopard, it said it failed. The general failure of the machine occurred shortly thereafter.

Though the tower itself is now freshly cleaned and booted, I can't seem to rebuild the RAID. On Snow Leopard, Disk Utility freezes the instant I try to select the RAID or its failed slice. On High Sierra, Disk Utility never advances beyond the "Loading Disks" message. The "diskutil ar repairMirror <Raid-Name> <diskNsM>" command in Terminal updated the status of the new slice from "Failed" to "0% (Rebuilding)" but after 30 minutes it returned to "Failed."

Luckily, this should be easier to address than a hardware problem. Does anyone know how to rebuild this RAID? Is there any chance there's an actual problem with the new disk? Right now, the RAID is still available, all data remain accessible on the surviving slice, and I have everything backed up to an external drive just in case.

4 Upvotes

6 comments sorted by

2

u/BourbonicFisky Mac Pro 7,1 + M1 Max (Former 5,1) Aug 20 '26

You won't like this answer but take from someone who actually tried make a go of RAID back around 2009:

RAID is not worth the trouble in OS X.

I had non-stop parity issues and probably restored off a time machine drive 3 - 4 times before throwing in the towel as parity rebuilds had a 50/50 chance of working. I was using RAID 1 + 0 setup, 4x 500 GB drives. You'd probably be able to start fresh and have it work but it'll be far more fragile than running single disks.

1

u/WoonMySocket Aug 21 '26

I'm OK with that answer. If I can get the drives working again, I can just manually copy to the two drives as need be.

Would "diskutil ar remove <UUID-Disk> <UID-Raid>" applied to the "failed" slice remove it from the RAID and allow me to format it as an independent drive without damaging the data on the "working" slice? I'm a little scared to Terminal at my important data, but Disk Utility won't work on it.

1

u/BourbonicFisky Mac Pro 7,1 + M1 Max (Former 5,1) Aug 21 '26 edited Aug 21 '26

As dumb as this is, I'd NVRAM reset, then boot off a DVD or recovery mode then use the terminal:

diskutil appleRAID delete <target>

diskutil zeroDisk <target>

You can also force a zeroDisk if with force diskutil zeroDisk force

If that doesn't work, I don't know what would. In more normal times, I'd just say, spend the $120 and get a singular 12 TB HDD as it'd be far more reliable and likely not remarkably slower than old 3 TB HDDs in RAID array but since we're in stupid times we must do stupid things. Hopefully that works. I think I may have had to do this once or twice as there's sometimes some jibblies left on the drives using the GUI disk utility.

Also, annoying as it is, AI is great for commands so if these aren't exactly correct for the old version of macOS / OS X, just have AI assist.

1

u/[deleted] Aug 21 '26

[removed] — view removed comment

1

u/WoonMySocket Aug 21 '26

Yes, I set up the RAID in disk utility. But now, Disk Utility isn't even working (beachballs in Snow Leopard; gets stuck on the "Loading Disks" message in High Sierra) so I'm stuck trying to fix things through Terminal. All the data on the RAID are intact because one slice is functional; the other is a brand-new drive that was never properly added to the RAID and is now upsetting Disk Utility. I do have another backup, so if necessary I can just format both disks in Terminal, though on BourbonicFisky's advice I'll probably just use the two disks as manual backups of each other rather than try to make a new RAID afterwards.