macOS Disk Utility First Aid Failed: Quick Terminal Fix

Yeah, that "First Aid process has failed" message is frustrating. You're staring at a disk that won't mount or a Mac that won't boot. I've seen this dozens of times. Here's the direct fix.

The Real Fix: Run fsck in Recovery Mode

Skip the GUI. Disk Utility's First Aid is just a wrapper around fsck, but it gives up too quickly. You need to run it directly.

Shut down your Mac.
Start up in Recovery Mode: Intel Mac — hold Command+R immediately on boot. Apple Silicon (M1/M2/M3) — press and hold the power button until you see "Loading startup options".
Open Terminal from the Utilities menu.
Type diskutil list and hit Enter. Find your main disk — it's usually disk0s2 for APFS or disk0s3 for older HFS+ systems. Note the identifier.
Run:
```
fsck_apfs -y -l /dev/disk0s2
```
(replace disk0s2 with your actual disk). For HFS+ (Mac OS Extended), use fsck_hfs -fy /dev/disk0s3.
Let it run. Could take 5-15 minutes. If it says "The volume was successfully repaired", you're golden.
Type reboot and press Enter.

One caveat: If you see "Filesystem check exit code 8", that means the disk is dirty but still needs a bootable system to verify. Reboot normally and run fsck_apfs -n /dev/disk0s2 from your main OS — the -n flag means read-only check. If it shows errors, boot back to Recovery and run the -y (force repair) version above.

Why This Fix Works

Disk Utility's First Aid is designed to be safe and conservative. If it even suspects a problem with the volume's journal or dirty bit, it bails with a generic failure. The -y flag in fsck forces the repair to proceed even when potential data loss is possible (though rare). The -l flag tells it to check for dirty bits that are often the root cause.

A dirty bit is just a flag that says "this volume wasn't unmounted cleanly". It gets set when you force reboot, lose power, or unplug an external drive without ejecting. The system won't fully trust the volume until it's cleared. fsck clears it.

"Disk Utility bails. fsck does the actual work."

Also — if you're on macOS Catalina (10.15) or newer, your drive is almost certainly APFS. Don't bother running fsck_hfs on an APFS volume. It won't work and you'll waste time.

Less Common Variations

The "Invalid B-tree node" Error

This one's trickier. It means a catalog file is corrupted. Run this in Recovery Terminal:

fsck_apfs -y -l -S /dev/disk0s2

The -S flag does a deep scan of the B-tree structure. If that doesn't fix it, you're looking at data recovery. Don't try to reformat — that nukes everything. Use Disk Drill or Data Rescue on another Mac first.

Snapshot Warnings on APFS

If you see "Snapshot is being used by Time Machine" or similar, First Aid will fail because APFS snapshots prevent writes. The fix: delete old snapshots using tmutil. Boot to Recovery, open Terminal, and run:

tmutil listlocalsnapshots /Volumes/YourDriveName

Then delete each one with:

tmutil deletelocalsnapshots /Volumes/YourDriveName 2023-11-15-123456

Replace the date with the snapshot date from the list. After they're gone, run the fsck command above.

Third-Party Encryption Software (FileVault, Veracrypt)

If you use FileVault or similar, fsck cannot repair the encrypted container. You need to decrypt first. In Recovery, run:

diskutil apfs unlock /dev/disk0s2

Enter your password when prompted. Then run fsck on the unlocked volume. FileVault encrypts at the block level, so fsck sees garbage without the decryption key.

Prevention

Three things that'll keep you from ever seeing this again:

Eject external drives properly. Drag them to Trash or right-click > Eject. Pulling USB drives without ejecting sets the dirty bit almost every time.
Don't force shut down. Hold the power button only when the machine is completely frozen. If you can, wait 5 minutes — sometimes the kernel just needs time to sort itself out.
Run periodic maintenance. Once a month, open Terminal and run sudo periodic daily weekly monthly. This runs cleanup scripts Apple built into macOS. It's old-school but still works.

If you're on a Mac with Apple Silicon, you'll also benefit from keeping macOS updated. The APFS driver in older versions (macOS 11.0-11.3) had bugs that could trigger dirty bits unnecessarily. macOS Ventura and later handle this much better.

That's it. You should be back up in 10 minutes. If none of this works, your disk might be physically failing — run the hardware diagnostic by holding D at boot (Intel) or pressing the power button on Apple Silicon until you see Options. If the diagnostic shows a yellow or red status, replace the drive.