RAID Degraded on Mac: What to Do Right Now

Stop all disk writes immediately. That single action, taken the moment Disk Utility or Terminal reports a RAID Degraded status, is what separates a routine drive swap from a permanent data loss event. A degraded RAID on macOS means the array has lost redundancy, and every additional read or write cycle increases the odds that a second failure turns a recoverable situation into a genuine disaster.

Once writes have stopped, your roadmap is straightforward: confirm the array’s real status with diskutil checkraid, identify exactly which physical drive failed, and only attempt a rebuild after you’ve mapped drive identities and verified you have a current backup or forensic image. Skip any of those steps and you risk rebuilding the wrong assumption into a broken array.

A few things worth knowing before you touch a single command. APFS and legacy HFS+ containers behave differently once a member drive drops out. NVMe-based enclosures rebuild faster than spinning SATA drives but are far less forgiving of interrupted power. And whether you’re running RAID 0, RAID 1, or a vendor RAID 5 array, the underlying rule is the same: a degraded array is still a working array, but only for now.

• Do this first: stop writes, note the exact error text, and avoid clicking any “Rebuild,” “Erase,” or “Initialize” button until you’ve read the identification steps below.
• Do this second: run diskutil checkraid from a normal boot (not Recovery Mode) and record the Unique ID and member UUIDs.
• Do this third: confirm the failed drive physically before replacing anything.

Macwest Data Recovery has handled degraded and failed RAID arrays for Los Angeles clients since 2006, across everything from Mac Pro RAID cards to Thunderbolt enclosures running SoftRAID. Free diagnostics and a strict no recovery, no charge policy mean there’s no downside to getting a second opinion before you attempt a DIY rebuild on data you can’t afford to lose.

Key Takeaways

A degraded RAID on macOS still holds accessible data, but recovering it safely requires stopping writes immediately, correctly identifying the failed drive, and confirming backups before any rebuild attempt.

Point	Details
Stop writes first	Halt all reads and writes to the degraded array the moment you see the warning, including backups and indexing.
Confirm before you rebuild	Use diskutil checkraid and physical checks (LEDs, serial numbers) to identify the failed drive before removing anything.
Match tools to RAID type	Disk Utility handles RAID 0 and RAID 1; RAID 5, RAID 3, and advanced setups typically require SoftRAID or vendor tools.
Escalate on multiple failures	Call a professional lab if more than one drive has failed, metadata looks corrupted, or the data is business-critical.
Macwest offers a safety net	Macwest Data Recovery provides free diagnostics, no recovery no charge, and same-day appointments for RAID cases in West LA.

Table of Contents

• Immediate Precautions Before You Touch the RAID
• What Does “Degraded” Actually Mean for Your RAID?
• How Do You Check RAID Status on macOS?
• How Do You Identify Which Physical Drive Failed?
• Rebuilding a Degraded RAID 1 on Mac: Step by Step
• Why Is the Rebuild Button Greyed Out?
• When a Rebuild Won’t Work: Your Data Recovery Options
• When Should You Call a Professional RAID Recovery Service?
• What Actually Works vs. What Sounds Good in Theory
• Get Same-Day Help With a Degraded RAID in Los Angeles
• Sources
• FAQ

Immediate Precautions Before You Touch the RAID

The fastest way to destroy recoverable data on a degraded array is to “fix” it before you understand it. Every RAID recovery lab has a story about a client who ran a well-intentioned repair tool, an automated firmware update, or a reformat, and turned a single-drive failure into total data loss.

Do this:

• Stop all write activity to the volume immediately, including Time Machine backups pointed at the same array, Spotlight indexing, and any active file transfers.
• Unmount the RAID volume from Disk Utility rather than force-ejecting or pulling drives while mounted.
• Check physical connections first: reseat Thunderbolt or USB cables, confirm the enclosure’s power supply is stable, and look for status LEDs indicating which bay is flagged.
• Screenshot or copy every Terminal output before making any change, in case you need to hand it to a recovery technician later.
• Leave the array powered on but idle if you’re unsure of next steps. Sudden power loss during a degraded state is one of the more common causes of a second, unrelated drive dropping out.

Don’t do this:

• Don’t click any “Initialize,” “Erase,” or “Reformat” prompt that macOS or a vendor utility offers, even if it looks like the fastest fix.
• Don’t attempt a rebuild before confirming which specific drive failed. Removing the wrong member from a mirror can strand your only good copy.
• Don’t run repeated remove and re-add cycles hoping something “sticks.” Each cycle rewrites RAID metadata and narrows your recovery window.

Green drive LEDs can mask a real problem. A degraded RAID array is often caused by a loose cable, a flaky power connection, or metadata corruption rather than an actual dead drive, so a physical connection check belongs before any software troubleshooting.

Pro Tip: If you’re at all uncertain whether the array is safe to touch, image the drives first with a tool like ddrescue before attempting any rebuild. An image preserves your recovery options even if the live rebuild goes wrong.

If you suspect physical damage or hear unusual clicking, grinding, or repeated spin-up noises from any drive in the array, power down immediately and contact a data recovery lab rather than attempting any further troubleshooting.

What Does “Degraded” Actually Mean for Your RAID?

Degraded means the array has lost redundancy, reduced performance, or both, while typically remaining accessible. It is not the same as failed. Data usually stays readable, but the array’s ability to survive a second problem is gone or severely weakened, which is why treating a degraded state as urgent, rather than cosmetic, matters so much.

The practical risk varies sharply by RAID type, and macOS users often assume more protection than they actually have:

RAID Type	What Degraded Means	Immediate Risk
RAID 0	There is no redundancy to lose. Any member failure means the array is effectively already gone.	Data loss is likely and often total.
RAID 1 (mirror)	One member has dropped; the surviving drive still holds a full, readable copy.	Redundancy is gone, but data remains accessible on the good member.
RAID 5	One drive has failed; parity across the rest can still reconstruct data.	A single failure is tolerable, but a second failure during rebuild is often catastrophic.
RAID 3 (less common on Mac)	Similar to RAID 5 with a dedicated parity disk; one failure is survivable.	Rebuild windows are longer, extending exposure to a second failure.

macOS Disk Utility natively creates and manages only RAID 0 and RAID 1 sets. If you’re running RAID 5, RAID 3, or more advanced configurations, you’re almost certainly using SoftRAID from OWC or a vendor-specific management utility rather than Apple’s built-in tools, and your rebuild path will run through that software instead of diskutil.

How Do You Check RAID Status on macOS?

Open Disk Utility first. Select the RAID set in the sidebar and look at the status field: Online means healthy, Degraded means a member has failed or dropped, and Missing means a member is unreachable but hasn’t been formally removed from the set. Run First Aid only on a healthy or degraded array, never on one showing Missing until you’ve identified the physical drive.

For a more precise read, drop into Terminal and run:

diskutil checkraid

A typical degraded RAID 1 output looks roughly like this:

AppleRAID set "Mirror" UUID: 12345678-ABCD-1234-ABCD-1234567890AB
Type:      Mirror
Status:    Degraded
Size:      4.0 TB (4000000000000 Bytes)

============================================================
#  Index  UUID                                  Status
0  0      87654321-DCBA-4321-DCBA-0987654321BA  Online
1  1      -                                     Missing

That “Missing” line under index 1 tells you exactly which member dropped. Follow up with:

diskutil appleraid list

to see every AppleRAID set on the system, and cross-reference the RAID Unique ID with diskutil list to find the corresponding physical device node.

If you’re on a Mac Pro with a hardware RAID card, use RAID Utility instead of Disk Utility. RAID Utility can show bay-level status directly and offers a “Make Spare” action to incorporate a replacement drive, automatically returning the set from degraded to good once the rebuild completes.

Copy down three identifiers before doing anything else: the RAID Unique ID, the device node (like disk4), and the member UUID of the failed drive. Run all of this from a normal boot, not Recovery Mode. Some diskutil appleraid operations behave unpredictably outside the standard macOS environment, and you want full logging available if something goes sideways.

How Do You Identify Which Physical Drive Failed?

Getting this step wrong is the single most common way people damage a recoverable array. Removing the working drive from a mirror because you guessed instead of confirmed is a mistake seen constantly in recovery lab intake calls.

1. Run diskutil checkraid and note the UUID marked “Missing” or “Failed.”
2. Run diskutil list and match that UUID against the physical device nodes shown (disk0, disk1, disk2, and so on).
3. Check the enclosure’s bay numbering against the vendor documentation. Most Thunderbolt RAID enclosures label bays 1 through 4 physically, which should correspond to the device order in diskutil list.
4. Look for LED indicators. Solid red or blinking amber on a specific bay usually confirms the failed drive; solid green across all bays despite a degraded status often points to a connection or metadata issue instead.
5. If the enclosure supports safe hot-swap, disconnect the suspected drive and re-run diskutil checkraid. If the array status is unchanged, you’ve confirmed the right drive.
6. Record the serial number and model of the drive you’re about to remove before pulling it, in case you need this for a warranty claim or a recovery lab intake.

Never hot-swap a drive unless the enclosure’s documentation explicitly supports it. Some consumer enclosures require a full power-down before a member drive can be safely removed, and hot-swapping an unsupported unit can corrupt the RAID metadata on the remaining good drive. If you’re unsure, power down, document the bay layout with photos, and treat the situation as one for a recovery lab.

Rebuilding a Degraded RAID 1 on Mac: Step by Step

Before touching a single command, confirm three things: you have a current backup or forensic image of the data, you’ve stopped all writes, and the Mac won’t sleep during the rebuild. Open System Settings and disable sleep under Energy Saver, and disconnect any unrelated external drives to reduce the chance of diskutil misidentifying a device node mid-process.

1. Run diskutil checkraid and note the RAID Unique ID and the UUID of the failed member.
2. Remove the failed member from the set: diskutil appleraid remove <failed-UUID> <device-node>. This tells macOS to formally drop the bad drive from the array’s metadata rather than leaving it in limbo.
3. Physically replace the failed drive with a new one of equal or greater capacity.
4. Run diskutil list again to find the device node assigned to the new drive (it will often get a new identifier like disk5).
5. Add the replacement to the array: diskutil addtoRAID member <new-device> <RAID-Unique-ID>. macOS begins rebuilding immediately once this command completes.
6. Monitor progress periodically with diskutil checkraid, watching the “Rebuild” percentage climb from 0% toward 100% and the status field move from Degraded through Rebuilding to Online.

This sequence, including the exact checkraid, appleraid remove, and addtoRAID member commands, mirrors the Terminal-led workflow documented by Seagate/LaCie for rebuilding a RAID 1 mirror on macOS.

Rebuild duration depends heavily on drive capacity, connection speed, and whether the array is under any load during the process. A 4TB mirror rebuild can reasonably take 24 hours or more, and leaving the device powered continuously through that window, with sleep disabled, is standard practice. Interrupting a rebuild partway through, whether by a power blip or a forced sleep cycle, can force the process to restart from zero.

Why Is the Rebuild Button Greyed Out?

A greyed-out rebuild option is one of the most common frustrations in degraded RAID troubleshooting, and it almost always traces back to one of a handful of causes.

• The replacement drive isn’t initialized correctly. macOS sometimes needs the new drive formatted with a compatible partition scheme before it will accept it as a RAID member, even though the format will be wiped during the rebuild anyway.
• RAID metadata is corrupted, not just missing a member. This is the trickiest scenario, because Disk Utility and diskutil may not clearly say so; the UI will simply refuse to offer a rebuild path.
• The new drive’s capacity doesn’t match the array’s requirements. RAID 1 mirrors typically need the replacement to be equal to or larger than the original member.
• Device node mapping is wrong. If you’re targeting the wrong disk identifier in your addtoRAID command, the operation will silently fail or produce a confusing error.
• Cable, port, or firmware issues on the enclosure. Older Thunderbolt bridges and outdated enclosure firmware can prevent macOS from recognizing a new member cleanly.

When Disk Utility’s UI won’t cooperate, try the same operation directly through Terminal with diskutil addtoRAID member, since command-line tools sometimes succeed where the graphical interface stalls. On vendor NAS and enclosure systems, a common workaround is configuring the new drive explicitly as a spare rather than a direct rebuild target, which often triggers the rebuild automatically once the spare is recognized. If you’re managing anything beyond RAID 0 or RAID 1, this is also where SoftRAID or your enclosure’s own management utility takes over from Apple’s native tools entirely.

Pro Tip: If metadata looks corrupted, resist the urge to keep cycling through remove and re-add attempts. Each attempt rewrites more of the array’s descriptor data. Image the drives with a tool like ddrescue first, then consult a recovery specialist before trying anything else.

When a Rebuild Won’t Work: Your Data Recovery Options

Sometimes the rebuild simply won’t take, whether because a second drive has also degraded, the RAID metadata is too corrupted for diskutil to parse, or the array was never healthy enough to begin with. At that point, the priority shifts entirely from “fix the array” to “preserve what’s left.”

Do this:

• Stop all writes to every drive in the set, not just the one you suspect failed.
• Create sector-level images of each member drive using ddrescue or a commercial imaging tool, working from the healthiest drive first.
• Document the current state thoroughly: screenshots of Disk Utility, full diskutil checkraid output, and photos of the physical enclosure and bay layout.
• Note every action already attempted, including any commands run, in the order you ran them.

Don’t do this:

• Don’t initialize, erase, or reformat any member drive, even one that seems to be “just” showing as missing.
• Don’t keep reconfiguring the array hoping a different combination of remove and add commands will work. Each attempt narrows the recovery window.
• Don’t assume a drive that spins up and shows a device node is mechanically healthy. Controller-level and firmware issues can look identical to physical failure from the outside.

DIY imaging of a multi-terabyte array member can take anywhere from several hours to a full day or more, depending on drive health and read speed. When a drive is failing, every additional read attempt increases wear on already stressed sectors, which is part of why professional recovery timelines vary so widely: straightforward metadata reconstruction might turn around diagnostics the same day, while physically damaged drives or multi-member failures can mean several days of lab work. When you do reach out to a lab, bring your Terminal output, drive serial numbers, and enclosure model. That information alone often cuts hours off the intake process.

When Should You Call a Professional RAID Recovery Service?

Certain warning signs mean the DIY path has run out of runway, and continuing to experiment yourself only shrinks your options.

• More than one drive in the array shows failed or missing status.
• Any drive is making clicking, grinding, or repeated spin-up and spin-down noises.
• You suspect logic-board or controller failure on the enclosure itself, not just a single disk.
• The array remains degraded or worse after one or more rebuild attempts have already been tried.
• The data on the array is business-critical, irreplaceable, or tied to client deliverables where downtime has real cost.

A qualified recovery lab approaches a degraded or failed macOS RAID very differently than a DIY attempt. Work typically starts with forensic imaging of every member drive, followed by metadata reconstruction to rebuild the array’s structure logically rather than on the live hardware. From there, technicians perform controlled rebuilds in a lab environment, isolated from the risk of a second live failure. When the problem traces back to drive electronics or a failing logic board, that repair happens at the component level before any data extraction begins. On modern NVMe and SSD-based arrays running APFS, the recovery process also has to account for encryption states and APFS snapshot structures that didn’t exist in older HFS+ volumes.

Bring three things to your first call: your diskutil checkraid output (or screenshots of Disk Utility’s status screen), the drive and enclosure serial and model numbers, and a clear account of what you’ve already attempted. That last part matters more than most people realize. A lab that knows exactly which commands you already ran can often narrow down what’s salvageable much faster than starting from a blind diagnostic.

Macwest Data Recovery has managed exactly these scenarios for Los Angeles clients since 2006, offering free diagnostics and a strict no recovery, no charge policy on every case. If your array involves a Mac Pro RAID card, a Thunderbolt enclosure, or a SoftRAID-managed set that won’t rebuild cleanly, same-day appointments are typically available, and the first call is simply to assess what state the drives are actually in.

What Actually Works vs. What Sounds Good in Theory

Most RAID troubleshooting guides treat DIY rebuilds and professional recovery as an either-or decision. That framing misses the more useful question, which is sequencing. The reality is that almost every degraded RAID on macOS benefits from the same first three steps, whether you ultimately fix it yourself or hand it to a lab: stop writes, identify the failed member correctly, and confirm you have a backup or image before changing anything.

Where I’d push back on common advice is the instinct to treat every degraded RAID 1 as a routine, low-stakes fix because “the data’s still there.” That’s true right up until it isn’t. RAID 1 gives you zero protection against a second failure, and the rebuild window, often 24 hours or more for larger drives, is exactly when a second, unrelated member is most likely to show its own age. I’ve seen more damage done by well-intentioned remove-and-readd cycling on corrupted metadata than by the original failure itself. If your diskutil checkraid output looks anything less than clean, that’s the moment to stop clicking and start imaging.

The best practices that actually hold up over time are unglamorous: run periodic SMART checks on every member drive, keep enclosure firmware current, verify backups actually restore rather than just assuming they exist, and match your RAID level to your real workload instead of defaulting to whatever configuration came preset. A video editor pushing large sequential writes has very different needs than a small office backing up shared documents, and the wrong RAID level for the job is often what turns a manageable failure into a painful one.

Macwest Data Recovery’s work across West LA, from Mac Pro RAID cards to Thunderbolt enclosures, backs up a simple point: the arrays that recover cleanly are almost always the ones where someone stopped writing to them the moment something looked wrong.

Get Same-Day Help With a Degraded RAID in Los Angeles

If you’ve worked through the diagnostic steps above and the array still won’t rebuild, or you’d rather not risk a DIY attempt on data you can’t replace, Macwest Data Recovery is the local alternative to shipping drives out of state and waiting weeks for answers. We’ve handled RAID recovery, sector-level imaging, APFS and NVMe recovery, and logic-board component repair for Mac Pro, MacBook, and iMac systems since 2006, right here in West LA.

Every case starts with a free diagnostic, and our policy is simple: no recovery, no charge. On the first call, expect a quick intake covering your symptoms, what you’ve already tried, and your enclosure or Mac model, followed by a realistic turnaround estimate. Same-day appointments are typically available for degraded RAID cases.

We’re centrally located at 12041 Wilshire Blvd, Ste 26, between the 405 and Santa Monica, near UCLA and the Getty Center, serving Brentwood, Westwood, Venice, Hollywood, and Culver City. Call 310-866-0828 now, or start with our hard drive and RAID recovery service page to see exactly what a lab-grade rebuild involves before your drives take another read cycle.

Sources

Before contacting Apple Support or a recovery lab, capture your exact Terminal output, screenshots of Disk Utility’s status screen, and your enclosure’s model and serial numbers. Having that on hand speeds up diagnosis considerably.

• RAID Utility User Guide
• How to Rebuild the RAID 1 in Mac OS 10.11 (El Capitan)
• My RAID is in degraded mode. What should I do?
• Degraded mode

FAQ

How do I fix a degraded RAID on Mac?

Stop all writes, run diskutil checkraid to identify the failed member, replace the physical drive, then use diskutil appleraid remove and diskutil addtoRAID member to rebuild it. If the rebuild option is greyed out or metadata looks corrupted, image the drives before attempting further fixes.

What does it mean when a RAID is degraded?

A degraded RAID has lost redundancy or performance because a member drive failed or dropped out, but the array typically remains accessible with data still readable. The risk depends heavily on RAID type: RAID 0 offers no protection at all, while RAID 1 and RAID 5 can tolerate one failure before becoming critical.

What happens when a RAID array is in degraded mode?

The array continues to function, often with reduced performance, while missing the redundancy that would protect it from a second failure. Many systems, including Apple’s RAID Utility, can automatically incorporate a spare drive to return the set to a healthy state once a rebuild completes.

Can you run RAID on a Mac?

Yes. macOS Disk Utility natively supports creating and managing RAID 0 and RAID 1 sets, while Mac Pro systems with RAID cards use Apple’s RAID Utility for hardware-level arrays. More advanced RAID levels like RAID 5 typically require third-party software such as SoftRAID.

When should I call a professional instead of attempting a DIY rebuild?

Call a professional if more than one drive has failed, you hear clicking or grinding noises, the rebuild option stays greyed out after basic troubleshooting, or the data is business-critical. Macwest Data Recovery offers free diagnostics and a no recovery, no charge policy for exactly these situations, with same-day appointments available in West LA.

Recommended

• Mac RAID Recovery Tutorial: Restore Your Data on macOS
• Examples of RAID Failures: Causes, Cases, and Fixes
• RAID Types for Businesses: Choose the Right Tier
• RAID Data Recovery: Expert Methods for Los Angeles Systems