How to Fix APFS Exit Code 8 ('Disk Utility Can't Repair This Drive') in Recovery Terminal

Running Disk Utility First Aid and seeing a red alert reading File system check exit code is 8. Disk Utility can't repair this drive. Back up as much of your data as possible is one of the most terrifying warnings in macOS.

Most forums and Apple Store Genius Bar technicians will advise you to immediately wipe your internal SSD, erase your files, and reinstall macOS from scratch.

Do not wipe your drive. At our downtown Chicago repair bench, we see this error weekly. In the vast majority of cases, your drive hardware is physically healthy, and your live documents, photos, and applications are completely intact.

Below is the exact engineering breakdown of why Exit Code 8 happens and how to clear it using macOS Recovery Terminal in 10 minutes.

🔍 The Root Cause: The “Read-Only Snapshot” Glitch

To understand why Disk Utility fails, you have to understand how the Apple File System (APFS) operates:

1. Whenever your Mac runs an automatic macOS update, executes a Time Machine backup, or runs cloning software, macOS takes an instantaneous APFS Local Snapshot—a frozen, point-in-time image of your drive.
2. By security design, APFS snapshots are strictly read-only. Even macOS itself cannot modify or edit them once created.
3. When you click “Run First Aid,” Disk Utility verifies not just your current live files, but every single historical snapshot stored on the disk.
4. The Trap: If a single snapshot created 3 weeks ago has an invalid checksum, corrupted inode, or broken extent tree, Disk Utility tries to repair it. But because the snapshot is read-only, First Aid is forbidden from writing the fix. It panics, aborts the entire scan, and outputs Exit Code 8.

The solution is simple: Identify the damaged snapshot and delete it. Your live files are unaffected, and First Aid will instantly pass.

Step 1: Boot into macOS Recovery & Open Terminal

You cannot delete locked system snapshots while booted into normal macOS. You must run this from Recovery:

• Apple Silicon (M1/M2/M3/M4): Shut down. Press and hold the Power button until you see “Loading startup options.” Click Options → Continue, select your Admin user, and enter your password.
• Intel Macs: Shut down. Turn on the Mac and immediately press and hold Command (⌘) + R until the Apple logo appears.

Once the macOS Utilities window appears, look at the top menu bar, click Utilities → Terminal.

Step 2: Identify Your APFS Volume Identifier

In the Terminal window, type:

diskutil list

Press Return. Look through the list for your internal drive (usually labeled Macintosh HD or Macintosh HD - Data).

Note the disk identifier in the rightmost column (for example: disk3s1 or disk3s5).

Step 3: List All APFS Snapshots on the Drive

Now, inspect the snapshots attached to your data volume by running:

diskutil apfs listSnapshots /Volumes/"Macintosh HD - Data"

(If your drive is mounted simply as “Macintosh HD”, use /Volumes/"Macintosh HD" instead).

Terminal will print a list of every snapshot stored on your SSD. Each entry looks like this:

+-- Snapshot Name:   com.apple.TimeMachine.2026-10-18-142301.local
    Snapshot UUID:   E2B358A1-8C9B-4D12-9F12-A1B2C3D4E5F6

Step 4: Purge the Corrupted Snapshots

To clear the snapshot obstruction, you have two methods depending on what created the snapshot:

Method A: Delete Time Machine Local Snapshots (Most Common)

If the snapshots begin with com.apple.TimeMachine, run:

tmutil listlocalsnapshots /Volumes/"Macintosh HD - Data"

To delete the problematic snapshot, enter:

tmutil deletelocalsnapshots 2026-10-18-142301

(Replace the timestamp with the exact date string shown on your screen).

Method B: Delete System & Carbon Copy Cloner Snapshots via Diskutil

If the snapshot was created by an OS update or third-party backup tool, use the snapshot’s UUID:

diskutil apfs deleteSnapshot /Volumes/"Macintosh HD - Data" -uuid E2B358A1-8C9B-4D12-9F12-A1B2C3D4E5F6

Terminal will respond with: Deleted APFS Snapshot.

[!TIP] Can’t tell which snapshot is broken? You can safely delete all local snapshots. Local snapshots are merely temporary point-in-time restore points; deleting them does not delete any of your current desktop files, applications, or external Time Machine backup drives. In fact, deleting them will instantly free up 20GB to 80GB of hidden storage!

Step 5: Run Direct fsck_apfs File System Repair

Once the locked snapshots are removed, you can run the raw Unix file system checker directly on your disk container without Disk Utility’s graphic interface getting in the way:

fsck_apfs -y -x /dev/disk3s1

(Replace disk3s1 with your actual volume identifier from Step 2).

• -y: Automatically confirms repairs without pausing.
• -x: Mounts and checks extended attributes cleanly.

Watch Terminal verify the object map, check inode records, and inspect directory trees. When finished, Terminal will display:

The volume /dev/disk3s1 was found to be corrupt and was repaired.
** The volume Macintosh HD appears to be OK.
** File system check exit code is 0.

Exit code 0 means your file system is 100% repaired and healthy! Quit Terminal, click the Apple icon, restart your Mac, and you are back in business.

Bench Attribution & Educational Disclaimer

[!NOTE] Primary Authority & Community Thanks:
We gratefully acknowledge Howard Oakley at The Eclectic Light Company (eclecticlight.co) and Rich Trouton at Der Flounder (derflounder.wordpress.com). Their exhaustive forensic documentation of APFS B-tree structures, snapshot immutability, and Darwin diskutil binaries serves as the gold standard for independent Mac technicians worldwide.

At Arbor Mac Repair, our mission is to take these dense forensic terminal breakthroughs and translate them into practical, consumer-friendly recovery guides so everyday Mac owners can rescue their data without unnecessary panic or expense.