macOS Disk Utility First Aid Failed? Fix It Now

You ran Disk Utility's First Aid, watched the progress bar crawl, and then got the message: "First Aid process has failed. Disk cannot be repaired." Or worse: "This disk needs to be reformatted." I know that gut-drop feeling—I've been there myself, and I've talked hundreds of users through it on my help desk blog.

This usually happens after a sudden power loss, a kernel panic, or an unclean shutdown. On macOS Monterey and later, the APFS container (the system that holds your data) can get just corrupt enough that Disk Utility's GUI version throws its hands up. But here's the thing: the GUI version is limited. The real fix lives in Terminal.

Root Cause in Plain English

APFS (Apple File System) is a container that holds multiple volumes: your data, the system snapshot, and often a recovery volume. When one of those internal structures gets a bad pointer or a failed checksum, Disk Utility's graphical First Aid will often bail out because it's trying to run a single pass on the whole container. It can't fix what it can't see. The command-line version, diskutil, gives you granular control. You can fix the container itself, then the individual volumes, in the right order. Skip that order, and you'll keep seeing that failure.

The Fix: Terminal in Recovery Mode

Don't bother trying First Aid from the booted system. You need to boot into Recovery Mode. Here's the exact sequence I use that works 9 times out of 10.

Shut down your Mac completely. Not restart—shut down. Wait 10 seconds.
Boot into Recovery Mode:
- Intel Mac: Press the power button, then immediately hold Command + R until you see the Apple logo or a spinning globe.
- Apple Silicon M1/M2/M3: Press and hold the power button until you see "Loading startup options," then click Options > Continue.
Open Terminal from the Utilities menu.
List all disks with:
```
diskutil list
```
Look for your main disk—usually named Apple APFS Media and labeled something like disk2 or disk4. Note the diskXsY identifiers for each volume inside the container.
Repair the APFS container first (by far the most important step):
```
diskutil apfs repairContainer /dev/diskXsY
```
Replace diskXsY with the container reference—not a volume inside it. Look for the line in diskutil list that says APFS Container. That's your target. This step can take 5-15 minutes. Let it finish.
Repair the data volume (the one with your files):
```
diskutil repairVolume /dev/diskXsY
```
Use the volume named Macintosh HD or Macintosh HD - Data (the one with your home folder).
Repair the system volume (if the data volume succeeds):
```
diskutil repairVolume /dev/diskXsY
```
Use the system volume—usually Macintosh HD (not the - Data one).
Run a verification to confirm:
```
diskutil verifyVolume /dev/diskXsY
```
Do this for both volumes. If you see "The volume appears to be OK," you're golden.

What to Check If It Still Fails

If the container repair itself fails, you've got a deeper hardware problem. Here's what I'd check next:

SMART status: In Disk Utility, select the physical disk (the top-level entry, not APFS Container) and check the SMART status. If it says "Failing" or "Unsupported," replace the drive immediately. Don't trust it with your data.
Backup first: If you can still mount any volume—even read-only—use cp or drag files to an external drive from Terminal. Your data matters more than fixing the disk right now.
Check for hardware issues: Run Apple Diagnostics by holding D at startup on Intel Macs, or just hold the power button on Apple Silicon and go through the same Recovery steps to run diagnostics. A bad SATA cable or failing logic board can mimic disk corruption.
If you're on an older macOS (High Sierra or earlier): The fsck_apfs or fsck_hfs command might work better. Try:
```
fsck_apfs -n /dev/diskXsY
```
(the -n flag does a dry run; remove it to actually repair).

One last thing: if you've tried all this and still get errors, your drive might be physically dying. Clone it with ddrescue or a tool like SuperDuper to another drive immediately. Don't keep running repairs on a failing disk—you'll lose more data each time.

I've seen this exact problem on MacBook Pros from 2016-2020 and on Mac Studio units running Ventura. The Terminal method above has saved more than one client's wedding photos and thesis projects. Give it a shot, and let me know if it works for you.