How to Run Disk Utility First Aid on Your Mac

Disk Utility First Aid is one of the older, more underrated tools in macOS. It checks your disk’s filesystem for inconsistencies and repairs what it can. Unlike many things on a Mac, it’s quick, low-risk, and occasionally turns up something genuinely worth knowing.

You don’t need to run it daily, weekly, or even monthly — that’s overkill. But running it once every few months as part of routine maintenance, or as a diagnostic step when something feels off, is a good habit. Here’s how, and how to read the results.

What First Aid actually checks

When you run First Aid on a volume, Disk Utility runs the modern equivalent of the classic Unix fsck (filesystem check) tool against it. Specifically, it:

• Verifies the integrity of the filesystem catalog (the directory of all files and folders)
• Checks that allocated blocks match what files claim
• Validates extended attributes
• Looks for orphaned blocks (storage marked in use but not referenced by any file)
• For APFS volumes (most modern Macs), checks snapshot integrity, container relationships, and some encryption state

If it finds inconsistencies, it tries to repair them. Most modern disks pass First Aid cleanly with no issues. When something’s wrong, you want to know.

How to run First Aid

The procedure is simple:

1. Open Disk Utility (Applications → Utilities → Disk Utility).
2. In the sidebar, select the volume you want to check. Usually this is Macintosh HD (your boot volume), but you can also check external drives.
3. Click First Aid at the top of the window.
4. Confirm you want to run it (a dialog appears).
5. Wait. It takes 30 seconds to a few minutes depending on disk size and contents.

When it finishes, you’ll see “Operation successful” if everything’s fine, or a description of what was found and whether it was repaired.

For checking your boot volume specifically, the Mac may temporarily lock other operations during the check — that’s normal.

What the results mean

“Operation successful. The volume appears to be OK.” — exactly what it sounds like. No issues found. Nothing to do.

“First Aid found problems and repaired them.” — Disk Utility found inconsistencies and fixed them. Common, harmless. The disk is now clean.

“First Aid found problems but couldn’t repair them.” — The repair couldn’t complete. This is the result that warrants attention. See “When repair fails” below.

“This disk needs to be repaired” / “The volume could not be unmounted.” — Sometimes for the boot volume, full repair isn’t possible while macOS is using it. You’ll need to boot into Recovery and run First Aid from there (see below).

Running First Aid from Recovery

For deeper repairs of the boot volume — especially if the regular First Aid says it can’t fully repair while the system is running — boot into Recovery:

Apple Silicon: Shut down. Press and hold the power button until “Loading startup options” appears. Click Options, then Continue. Sign in.

Intel: Shut down. Power on while holding Cmd-R. Release when you see the Apple logo or globe.

In Recovery, choose Disk Utility from the main menu. Run First Aid the same way. From here, the boot volume isn’t actively in use, so deeper repairs are possible.

When done, quit Disk Utility and choose Restart from the Apple Menu.

When to run First Aid

You don’t need to run it routinely, but it’s a worthwhile diagnostic step in these scenarios:

1. Slow boot or login. Filesystem issues can drag boot. First Aid catches them.
2. App crashes that don’t make sense. Some app crashes are caused by corrupted files in their support directories. If First Aid finds and fixes catalog issues, those crashes may stop.
3. “File X cannot be opened” errors for files you know exist.
4. Storage usage doesn’t match expectations. “I have 50 GB of files but Storage shows 80 GB used.” May indicate orphaned blocks.
5. After unexpected power loss. Hard shutdowns occasionally introduce filesystem inconsistencies. First Aid afterward is good hygiene.
6. As part of annual maintenance. Once a year, run it on your boot volume. Takes a minute, catches issues early.

You don’t need to run it weekly or after every restart. Modern APFS is robust; routine running mostly turns up “Operation successful” with no value.

Diagnose AND clean in one appSweep finds runaway processes, frees RAM, and clears caches in one place. Free download →

What about external drives?

You can run First Aid on external drives the same way: connect the drive, select it in Disk Utility, click First Aid. Same procedure, same results.

For external drives that you suspect are dying physically (clicking sounds, intermittent disconnection, sudden errors), First Aid checks the filesystem but not the underlying hardware health. SMART data is a better indicator there:

1. With the drive connected, open Disk Utility.
2. Select the drive (the physical drive, not a volume on it).
3. Look at “S.M.A.R.T. status” near the bottom. “Verified” is good. “Failing” is bad.

For a drive showing SMART warnings, copy data off immediately. Don’t run First Aid hoping it’ll fix the issue — failing hardware doesn’t get fixed by software.

When repair fails

If First Aid finds problems but can’t repair them, the situation is more serious. Options:

1. Try Recovery mode. As noted above, the boot volume can’t be fully repaired while it’s in use. Recovery’s First Aid sometimes succeeds where the regular one fails.
2. Try fsck from Single User Mode (Intel only). Boot holding Cmd-S. At the prompt, run fsck -fy (the -f forces a check, -y answers “yes” to repairs). Apple Silicon doesn’t have a Single User Mode equivalent.
3. Backup, then erase and reinstall. If repairs continue to fail, the filesystem is meaningfully damaged. Backup what you can (Time Machine, Migration Assistant), erase the drive, reinstall macOS, restore from backup.
4. Hardware check. Persistent, unrepairable filesystem damage on the same disk is sometimes a sign of physical failure (more common on SSDs nearing end of life, or external drives). Apple Diagnostics or a third-party SMART checker can clarify.

If your Mac is under AppleCare or recent enough to be under warranty, this is a reasonable Genius Bar conversation. They have deeper diagnostic tools than what’s in Disk Utility.

What First Aid CAN’T fix

Important to be honest about the limits:

• Bad sectors on the physical drive. First Aid checks the filesystem, not the hardware. A failing SSD shows up differently.
• Corrupted user files. If a single document is corrupted, First Aid won’t repair the document — it’ll only ensure the filesystem entry is consistent.
• Performance issues unrelated to filesystem. Slow Mac due to runaway processes, full storage, or memory pressure isn’t a First Aid issue.
• Permissions problems. Apple removed “Repair Permissions” from Disk Utility in 2015. Modern macOS handles permissions automatically; if you have a real permissions issue, the fix is elsewhere.

If First Aid passes cleanly but you still have problems, the cause is somewhere else. Don’t keep running First Aid hoping for different results.

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds — and only removes what you OK. Download Sweep free →

How First Aid compares to old “Verify Disk”

In older versions of Disk Utility, there were separate “Verify Disk” and “Repair Disk” buttons. Verify checked without repairing; Repair fixed issues. Modern First Aid combines both — it checks, and if it finds something, it tries to fix. There’s no “verify only” option anymore.

This is mostly fine. The repair operations are conservative; they don’t try to do anything destructive. If you really want a non-modifying check, you can run fsck -n from Terminal (the -n answers no to all repair prompts), but for almost all users, the standard First Aid is what you want.

Backup first

Standard advice that bears repeating: before running First Aid on a volume that’s having issues, back up first if you can. Repair operations are conservative and almost always safe, but “almost always” isn’t “never.” If the volume is misbehaving badly and you don’t have a backup, attempt the backup first (even if it has to skip some files), then run First Aid.

For routine annual maintenance on a healthy disk, no special backup is needed — your usual Time Machine cadence is fine.

A realistic frequency

In summary: run First Aid on your boot volume once a year as part of annual maintenance, plus whenever you have a specific symptom that points to filesystem trouble. That’s it.

Running it weekly is overkill. Running it never is fine for most people. Once-a-year-plus-when-needed is the realistic middle.

The whole tool takes a minute, requires no decisions, and occasionally surfaces problems before they become serious. That’s a good return on a small time investment.