macOS Disk Utility First Aid Stuck Running – Real Fixes That Work

The 30-Second Fix: Force Quit and Reboot

If Disk Utility First Aid has been stuck for more than 10 minutes with no progress bar moving, you're probably not looking at a deep repair. You're looking at a hang. Happened to a client last month on a 2019 MacBook Pro running Monterey. The fix was brutally simple.

1. Force quit Disk Utility: Apple menu > Force Quit (or press Command+Option+Escape), select Disk Utility, click Force Quit.
2. Shut down your Mac completely. Not restart. Shut down.
3. Wait 30 seconds. Then boot up normally.
4. Open Disk Utility again and run First Aid again — but this time, only on the top-level disk (e.g., "APPLE SSD"), not the individual volumes. The hang often happens when you try to repair a volume container while the system is writing to it.

If the same thing happens again, move to the next fix.

The 5-Minute Fix: Boot to Recovery and Use Terminal

When First Aid hangs in the normal OS, it's because macOS is actively using the drive. You can't fix a running system's drive reliably. I wrote about this back in 2022 for a client whose iMac Pro wouldn't boot past a stuck First Aid. Here's the real trick: use Terminal in Recovery mode.

1. Shut down your Mac.
2. Turn it on and immediately hold Command+R until you see the Apple logo or a startup options screen. This boots to macOS Recovery.
3. From the Utilities menu, select Terminal.
4. Type diskutil list and press Return. You'll see a list of all disks. Find your main disk – it's usually something like disk0 or disk1 and named something like "APPLE SSD AP0512M".
5. Now run First Aid directly via Terminal: diskutil verifyDisk disk0 (replace disk0 with your actual disk identifier). For APFS containers, use diskutil verifyVolume disk0s2 (check your diskutil list output for the actual volume ID).
6. If verify passes, try repair: diskutil repairDisk disk0 or diskutil repairVolume disk0s2.

This bypasses the GUI hang entirely. Had a client whose First Aid sat spinning for two hours. This command finished in under 60 seconds and found a bad block that the GUI hid.

The 15+ Minute Fix: Single User Mode fsck (Intel Macs) or Data Recovery

If Recovery mode Terminal also hangs, you've got a more serious problem. For Intel Macs, there's an ancient but effective tool: fsck in Single User Mode. Note: Apple Silicon Macs don't support Single User Mode, so this is Intel-only.

1. Shut down your Intel Mac.
2. Boot while holding Command+S. You'll see black text scrolling.
3. At the command prompt, type /sbin/fsck -fy and press Return.
4. Let it run. It may take 15-30 minutes on a large drive. It will print progress messages. If it says "FILE SYSTEM WAS MODIFIED", run it again until it says "The volume appears to be OK".
5. Type reboot to restart.

If fsck also hangs, or if you're on Apple Silicon and everything above fails, your drive likely has physical damage. At this point, stop running First Aid – every attempt can make data recovery harder. I've seen this three times in the last year: clients who ran First Aid 5+ times on a failing drive and ended up with a completely unreadable disk. When the drive has bad sectors, First Aid can wedge trying to read them.

Your next step is data recovery software (like Disk Drill or Data Rescue) or a professional recovery service if the data is critical. Backup your data before running any more repairs.

Bottom line: If Disk Utility First Aid hangs, don't just wait. Force quit, reboot to Recovery, use Terminal. If that fails, your drive is likely failing physically. Stop repairing, start recovering.