First Aid on a Mac, from the dimmed button to the exit code
What First Aid in Disk Utility really checks, the order Apple says to run it in, and what the failed, dimmed and cannot unmount messages mean.
By Chethan Kumar S N · Updated
Disk Utility has one button that does real work, and it is the one people are least sure about. First Aid reads the structure of a disk and repairs it if it can. It is not a cleaner, it does not free space, and it never looks at whether a document opens.
That is why the same button produces two completely different kinds of complaint. The first is a genuine question about damage: does this disk have a problem? The second is about the process itself: the button is dimmed, the check has been running for twenty minutes, or it stopped with the words could not be unmounted. Apple answers both, but in three different places, and the answers are specific enough to be worth having together.
Everything below comes from Apple’s Disk Utility documentation, its support articles, and the strings inside the Disk Utility app on this Mac, plus one read-only check run while writing this page. Nothing was erased or installed, and no setting was changed. The machine here is a 14-inch MacBook Pro with an M1 Pro, running macOS 27.0.1.
What First Aid is checking
Apple’s own summary of the button is one sentence: Disk Utility can check for and fix errors related to the formatting and directory structure of a Mac storage device.
That is narrower than most people assume, and the examples Apple gives for when to use it are all consequences of a damaged structure rather than causes. Its list is multiple apps quit unexpectedly, a file is corrupted, an external device doesn’t work properly, or your computer won’t start up. Then the sentence that keeps expectations honest, because it is the one people skip: Disk Utility can’t detect or repair all problems that a disk may have.
So a clean First Aid result means the disk’s own bookkeeping adds up. It means the catalog, the allocation records and the container metadata are consistent. It does not mean your files are good, your SSD is healthy, or your Mac will stop misbehaving. First Aid is a structural check, and everything it reports is about structure.
Worth saying plainly because it is the most common misunderstanding: First Aid does not make a Mac faster and does not free up space. Nothing in Apple’s description of the tool mentions either, and nothing it does touches your documents.
The order, and why it runs bottom to top
Apple has two descriptions of First Aid, and the support article is the more precise one. The user guide says to run First Aid on each volume and container on the storage device in turn, then run it on the storage device itself.
The support article explains the actual sequence, and it is not the order most people click in. For each device that you’re repairing, it says, start by selecting the last volume on that device. Then: after Disk Utility is done checking the volume, select the next item above it in the sidebar, then run First Aid again. And then: keep moving up the list, running First Aid for each volume and volume group on the device, then each container, then finally the device itself.
The reason is the shape of the sidebar. Disk Utility nests things. A physical disk holds one or more containers, a container holds volumes, and on a modern Mac those volumes are grouped: one for the system, one for your data. If you start at the top, you are asking the container to be verified while the volume inside it is still broken, and anything the container reports is a consequence of the volume rather than an independent fault. Working from the last volume upward means each level is checked after the level it sits on top of.
Two details from the same page are easy to miss and both matter. The first is View > Show All Devices, which Apple flags with the words if available, because it puts containers and the physical disk into the sidebar at all. The second is that if a volume sits inside a volume group, you may need to click the arrow next to the group’s name before the volumes appear, and on a Mac where macOS and your data are separate volumes you are meant to check both. Apple’s example names them: the startup volume, and then the data volume underneath it.
Here is what that nesting looks like on this machine, from diskutil list, which is the same hierarchy Disk Utility’s sidebar draws:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: Apple_APFS_ISC Container disk1 524.3 MB disk0s1
2: Apple_APFS Container disk3 994.7 GB disk0s2
3: Apple_APFS_Recovery Container disk2 5.4 GB disk0s3
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +994.7 GB disk3
Physical Store disk0s2
1: APFS Volume Macintosh HD 13.7 GB disk3s1
2: APFS Snapshot com.apple.os.update-... 13.7 GB disk3s1s1
3: APFS Volume Preboot 10.8 GB disk3s2
4: APFS Volume Recovery 1.5 GB disk3s3
5: APFS Volume Data 654.3 GB disk3s5
6: APFS Volume VM 7.5 GB disk3s6
One internal disk, three containers, and six items inside the big one. The disk people call Macintosh HD is one small volume in the middle of that list, and the 654 GB with your files in it is a different volume entirely. Running First Aid on only the item with the familiar name checks the smaller half.
The same check in Terminal, and what it prints
The button is a front end. Apple’s support article for Terminal users is the one that leaves a trace, and the equivalent of a check without repair is diskutil verifyVolume. Run against the Recovery volume on this Mac, it produced this:
$ diskutil verifyVolume disk3s3
Started file system verification on disk3s3 (Recovery)
Verifying file system
Volume could not be unmounted
Using live mode
Performing fsck_apfs -n -l -x /dev/rdisk3s3
Checking the container superblock
Checking the checkpoint with transaction ID 3193291
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the encryption key structures
Checking volume /dev/rdisk3s3
Checking the APFS volume superblock
The volume Recovery was formatted by newfs_apfs (3288.1.3) and last modified by apfs_kext (3288.1.3)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
Verifying allocated space
The volume /dev/rdisk3s3 with UUID A90280AC-0225-4A06-869F-C807FCD0A89A appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Finished file system verification on disk3s3 (Recovery)
Four things in that output are worth reading slowly, because they are the same four things the app is doing behind its progress window.
The checker is named. The button without the interface is diskutil verifyVolume, and it runs fsck_apfs, the APFS consistency checker. The number in the failure summary people quote is that check’s exit status, printed on the line above the end.
The flags explain what you are getting. -n means never attempt to repair any damage that is found, and -l means live verification mode, which the manual page describes as making it possible to check an APFS container which is currently mounted read-write, although no repairs can be made. That is the same trade the app makes when it cannot unmount a volume.
There is no progress bar, only phases. Container superblock, checkpoint, space manager, object map, volume superblock, snapshot metadata, fsroot tree, extent ref tree. Each one is a named structure, and each is a line in the log. A check that looks frozen is usually a check that has been on the same line for a while because that structure is large.
The whole thing is fast when the volume is small. This was a 1.5 GB volume and it finished in about twelve seconds, most of which was reading rather than thinking. The data volume on the same Mac holds 654 GB, and the reason the sidebar estimate goes from seconds to minutes is that the structures the checker walks grow with the number of files and snapshots, not just with the bytes.
If the button is dimmed
Apple documents this as a normal outcome. From the support article: if the button is dimmed and you can’t click it, skip this step for the disk, container or volume you selected. No warning, no fault, move on.
The button carries a tooltip for the same reason, and it reads detect and repair errors in the selected volume, container or device partition map. That is the scope statement: structure, in one of three levels, chosen by what you have selected.
There is a second, more explicit case, and the wording for it lives inside the app rather than on a web page. When the selection is a file system First Aid cannot work with, Disk Utility says this disk’s file system does not support First Aid. It is the difference between a button that is unavailable for this item and one that would do nothing useful if it were available, and either way nothing is wrong.
The greyed-out button people actually write about is usually the startup volume, and that is not a file system problem. It is the unmount problem wearing different clothes, and Apple’s route for it is macOS Recovery.
When it says the volume could not be unmounted
Repair needs the volume to itself. A volume with an app in the middle of writing to it can be read but not fixed, and Disk Utility says which of those situations you are in. Its own messages, read from the app on this Mac, cover the cases separately:
Failed to unmount “X” because it is currently in use. Failed to unmount “X” because one or more of its volumes is currently in use. Failed to unmount “X” because it is currently in use by “Y”.
The third one is the useful one, because it names the process holding on to the disk. If the answer comes back as Spotlight, a backup or a document you left open in the background, quitting that is faster than reading further.
The startup volume is a special case with its own wording, and it is worth quoting because it explains a whole category of confusion. Disk Utility says plainly that the startup volume can’t be unmounted from this Mac, and its own menu for erasing a disk repeats the point: a volume can’t be erased because the startup volume can’t be unmounted from this Mac. You are running from it. It cannot be taken away from under you.
The recovery path for that is documented rather than clever. Apple’s instruction is that if you’re checking your startup disk or startup volume, restart your computer in macOS Recovery, and then choose Disk Utility from the utilities window. On an Apple silicon Mac you get there by shutting down and holding the power button until the startup options appear; on an Intel Mac it is Command and R at startup. In Recovery the startup volume is not mounted as your system disk, so the usual objection disappears.
Two more messages from the same list are worth knowing, because they sound like the end of the world and are not. First Aid could not unmount the volume for repair, and First Aid could not unmount one of the other volumes in the volume’s container. The second one is informative: repairing a volume in a container can need the other volumes in that container to step aside too, so an app using any of them is enough to block a repair on the one you selected.
Stuck, or hours long
Apple warns about this before you start, which is more than most software does. Selecting First Aid on the startup volume while running from it brings up this string:
Verifying the startup volume will cause this computer to stop responding.
And if you go ahead, the status line says how far that goes:
This computer will stop responding while verifying the startup volume; this may last for several minutes or hours.
Then the instruction that solves it, from the same dialog:
This may last for several minutes or hours. To avoid this, you can run First Aid while in Recovery.
That is the whole answer to nearly every First Aid taking forever thread. If the volume being checked is the one you are working on, the machine is expected to stop responding, sometimes for hours on a laptop with a large data volume. In Recovery the same check runs against the same structures with nothing else competing for the disk, and the volume is not mounted as the system.
The other half of the answer is that the estimate is not proportional to the size printed in the sidebar. What the check walks is the structures that describe the volume, and those grow with the number of files and snapshots rather than with the bytes in them. Two drives of the same capacity, one holding three files and one holding a decade of snapshots, are not the same amount of work.
So the useful question is not how long is it taking but where is it. Click the disclosure in the progress window, or watch the log, and it will be naming a structure: checking the space manager, checking the fsroot tree, verifying allocated space. A check that is moving between named structures is working. A check that has been on one for an hour is a check you would normally have run in Recovery anyway.
When it fails
Apple’s failure message is one line long, and it is a priority order in disguise:
First Aid process has failed. If possible back up the data on this volume.
Read that as the order of operations: back up first, diagnose second. The support article’s version adds what to do after the backup, and it is a short ladder. If Disk Utility can’t repair your disk, or you receive a report that the First Aid process failed, try to repair the disk or partition again. If that doesn’t work, back up as much of your data as possible, reformat the disk, reinstall macOS, then restore your backed-up data.
Running it once more is a real step rather than wishful thinking. Some failures are a side effect of the volume being busy or of a checkpoint being mid-write, and a second attempt after a restart sometimes completes. What does not work is running it ten times and hoping.
There is one failure that has its own explanation, and it is the one that sounds most alarming. If Disk Utility reports overlapped extent allocation errors, Apple’s description is that two or more files occupy the same space on your disk, and at least one of them is likely to be corrupted. The repair here is not a repair, it is a decision about files: you check each file in the list of affected files, delete the ones you can replace or recreate, and open the ones you need to confirm the data is intact. Most of the files in that list have aliases in a DamagedFiles folder at the top level of the disk, which is how you find them. A disk with this problem needs the files dealt with rather than the volume blessed.
Two failure messages name Recovery specifically, and both are about the startup side of the machine. On the startup volume: First Aid found corruption that needs to be repaired, and to repair the startup volume, you run First Aid from Recovery. On a container that failed a partition operation: operation failed because corruption was found in the startup container or one of its volumes, run First Aid from Recovery to repair it, then try again. Repair of the system side of the disk only happens when the system is not running from it.
And one more, for an encrypted container: First Aid could not finish because the container has one or more encrypted volumes that are locked, which resolves by mounting the locked volumes first and trying again. That is the FileVault case, and it is a mounting problem, not a damage problem.
If the volume is simply shot, Apple does not dress it up. Its sentence about a disk that Disk Utility says is about to fail is to back up your data and replace the disk, because you cannot repair it. First Aid checks structure. It cannot make failing hardware good again.
The exit code question
First Aid failed with exit code 8 is one of the most common phrases in Mac troubleshooting threads, and it is worth knowing that Apple publishes no list that decodes it.
What is documented is the tool. On macOS 27, First Aid runs the check with fsck_apfs, and the only published scale is a single line in that tool’s manual page: fsck_apfs exits with 0 on success, and greater than 0 if an error occurs. That is the whole documented meaning of the number. It is a flag rather than a severity, which is why the same code can appear for two very different problems and different codes can appear for the same one.
What actually helps is the line above it. When the check fails, the log names the structure that failed before it prints the number: a tree it could not read, an object map that did not agree, a snapshot that would not verify. That sentence is the diagnosis. The number is just a receipt.
The practical ladder after any failure is the same one Apple gives, and it does not depend on decoding anything: make sure you have a current backup first, try the repair a second time, and if it fails again, treat the volume as one whose structure can no longer be trusted and rebuild it rather than arguing with it.
If the disk is not in the sidebar at all
This is the one case where no amount of clicking helps, and Apple’s instruction is a clean one. If your storage device doesn’t appear in the sidebar of Disk Utility, your Mac or the storage device may need service. Shut down, unplug all non-essential devices, then try again. For an external storage device, check its cable, connections and power.
There is a distinction worth drawing before you worry. A disk that is missing from Disk Utility but visible in System Information under the storage list is usually a mounting problem. A disk that is missing from both is the service case. It is also worth trying another port and, on a desktop, another cable before booking anything, because a bad USB connection behaves exactly like a dead drive.
Where window managers fit
Nothing here is a window problem, and no window manager is going to repair a disk. What is worth taking from this page is narrower and more useful: First Aid is a structural check with a specific order and a specific set of messages, and reading them correctly costs nothing, while guessing costs an afternoon.
If what brought you to Disk Utility was a Mac that feels slow rather than a disk that looks broken, the better first stop is the three numbers in Activity Monitor, and the running slow page takes them in order. If it was a storage number that refused to move, the arithmetic behind the storage figure is usually the answer, and it has nothing to do with disk damage.
And if you are in Disk Utility because the desktop itself has become unmanageable, with windows stacked until you cannot see the one you want, that is a different kind of problem with a different kind of fix. Ribbon keeps your windows open at full size on one scrolling strip instead of layering them, so getting to the window you meant is a swipe rather than a hunt, and nothing shrinks into the background. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can drive the strip in your browser before you install anything.
The short version
First Aid checks and repairs the formatting and directory structure of a disk, and Apple says outright that it cannot detect or repair everything. It is not a cleaner, a defragmenter or a health check for your files.
Run it from the bottom up. Apple’s own order is the last volume first, then each item above it in the sidebar, then each container, then the device itself, because each level sits on top of the one below. Turn on View > Show All Devices first, so the containers are even visible.
A dimmed button is expected, and Apple’s instruction is simply to skip that item. A volume that cannot be unmounted is in use, and the app names the process when it can. A startup volume can never be unmounted from the Mac it is running, which is why Apple’s route for that one is macOS Recovery, and why the same dialog warns that the machine will stop responding if you insist.
A failure message is a backup instruction before it is a diagnosis. And the exit code is a pass or fail flag: the checker behind the button says only that it exits with 0 on success and greater than 0 on error, so read the line above the number instead.
Questions
Why is the First Aid button greyed out in Disk Utility?
Because it is the wrong item for that button, not because something is broken. Apple's own instructions say it directly: if the button is dimmed and you can't click it, skip that step for the disk, container or volume you selected, and move to the next item in the list. There is a second case where the message is explicit rather than implied, and Disk Utility's own wording for it is that the disk's file system does not support First Aid. Neither of those is a fault report. The greyed-out button is most often the startup volume while you are running from it, which Apple's documentation says to check by restarting into macOS Recovery instead.
Why does First Aid say the volume could not be unmounted?
Because the volume is in use, and Disk Utility says so in its own messages. Its wording covers the three cases separately: failed to unmount because it is currently in use, failed to unmount because one of its volumes is currently in use, and failed to unmount because it is currently in use by a named app. Repair needs exclusive access, so a volume with an open document, an indexed backup or a running app behind it can be checked but not fixed. The startup volume is the special case, and Disk Utility is blunt about it: the startup volume can't be unmounted from this Mac, which is why Apple's route for checking the disk you booted from is macOS Recovery rather than Disk Utility in normal use.
What does First Aid failed with exit code 8 mean?
Apple publishes no table of these numbers, and that is the honest answer rather than a trick. What is documented is the tool behind the button. On a Mac running macOS 27, First Aid performs the check with fsck_apfs, and the only published scale for its exit status is one line in its own manual page: fsck_apfs exits with 0 on success, and greater than 0 if an error occurs. So the number is a pass or fail flag rather than a severity, and the useful line is the one printed above it, which names the structure that failed. The message Apple attaches to a failure is the one to act on, and it is short: First Aid process has failed, and if possible back up the data on that volume.
How long should First Aid take, and is it stuck?
Longer than people expect, and Apple warns about this before you start. For the startup volume in normal use, its own text says the computer will stop responding while verifying it and that this may last for several minutes or hours, with the note that you can run First Aid while in Recovery to avoid that. The work is proportional to the number of files and snapshots on the volume, not to the size printed in the sidebar, so a nearly empty 2 TB drive can finish in seconds while a full 500 GB one takes a quarter of an hour. There is no progress bar to watch, only a log that names each structure as it is checked, which is why a working check looks like a hung one.
Do I still need to repair disk permissions on a Mac?
There is nothing left to repair, and modern Disk Utility does not pretend otherwise. The Repair Disk Permissions step that people remember from older versions of macOS was removed years ago, and Disk Utility on this Mac confirms it in its own way: the app's string table, read on macOS 27, contains no repair-permissions entry at all, while every First Aid message is about the formatting and directory structure of the volume. Permission problems do exist, they just live somewhere else now, in the Finder's Get Info sharing settings and in the ownership of individual files, and no single button rebuilds them.
Ready? Buy Ribbon for $15, or read all the guides.