Fix Couldn’t Unmount Disk on Mac: Safe Steps

If your Mac says it couldn’t unmount a disk, first close anything using the drive, then try ejecting it again in Finder or Disk Utility. If that fails, identify the process or volume keeping it busy; force-unmounting can interrupt file transfers, so use it only after checking that no work is being written.

What “couldn’t unmount” means

Unmounting disconnects a mounted volume from macOS so the system and apps stop treating it as available storage. It is different from erasing or physically disconnecting the device. macOS may refuse an unmount because a file is open, a copy is underway, a backup or indexing task is active, or another volume depends on the one you are trying to remove.

The message can appear when ejecting an external drive, repartitioning or erasing a disk in Disk Utility, or running a repair. Check which item is selected: a physical device can contain several volumes, and an unmount failure for one volume is not necessarily a failure of the entire disk. Do not erase or repartition anything simply to make the warning disappear; those operations can destroy data.

Try these steps in order

Wait for activity to finish. If Finder is copying files, an app is exporting a project, or a backup is running, let it complete. Do not unplug the drive while a write is in progress.
Close files and apps using the drive. Close documents stored on it, quit apps that may be accessing them, and close Finder windows showing the volume. Eject again from the Finder sidebar or by selecting the volume and choosing File > Eject.
Check for a busy app. If you do not know what is using the disk, save your work and quit open apps one at a time, retrying the eject. A file can remain in use even when its window is not visible. Avoid force-quitting an app that may still be saving.
Use Disk Utility. Open Disk Utility (in Applications > Utilities, or find it with Spotlight), choose View > Show All Devices if needed, select the relevant volume in the sidebar, and click Unmount. Confirm that you have the right volume. If you are trying to erase or partition a drive, unmounting is a separate step from those destructive actions.
Restart and try again. If the disk is not actively being written to and you cannot find what is holding it, save work, shut down or restart the Mac, then reconnect the drive and try to eject it before opening apps that might use it. A restart often releases temporary file handles.

Find the process holding the disk

For a more specific diagnosis, Activity Monitor can show processes that may be accessing files. Open it from Applications > Utilities, search for a relevant app or process, and quit only an app you recognize and can safely close. System processes should not be stopped casually; quitting the wrong one can cause instability or interrupt work.

Experienced users can inspect open files from Terminal with the lsof command. For example, sudo lsof +D /Volumes/DriveName searches a mounted volume for open files; replace DriveName with the actual volume name, preserving spaces as needed. The search can take time on a large drive. Treat the output as diagnostic information, not an instruction to kill every listed process. Avoid copying a command that includes a process-killing option unless you understand exactly what it will stop.

When force unmounting is appropriate

Disk Utility may offer a force-unmount option in some situations. Force unmounting tells macOS to detach a volume even though something may still be using it. This can cause unsaved changes or incomplete transfers, and an interrupted write can leave files damaged or a filesystem needing repair. It is not a general-purpose fix for a disk that is failing.

Before forcing an unmount, verify that no copy, backup, download, or save operation is in progress. If you are unsure, cancel the operation if possible, wait, and restart the Mac instead. Never pull a drive during an active write just because the eject command is taking a long time. If the volume contains important data and the device is making unusual noises, repeatedly disconnecting or repairing it may make recovery harder; stop and consider professional data-recovery help.

If Disk Utility still cannot unmount it

First determine whether the issue is the volume, the device, or the connection. Try another cable or port if the external drive behaves inconsistently, and connect it directly to the Mac rather than through a hub when practical. A drive that disappears, reconnects repeatedly, or produces input/output errors may have a hardware, cable, power, or filesystem problem—not merely a busy file.

If the volume mounts and your data is accessible, copy important files to another location before running repairs or making changes. In Disk Utility, select the volume and use First Aid to check and repair filesystem issues; follow the displayed prompts. First Aid is not a substitute for a backup, and it cannot guarantee recovery from physical failure. If the disk will not mount or contains the only copy of important data, avoid erasing it or experimenting with partition changes.

For an internal startup disk, macOS may prevent normal unmounting because the system is using it. Do not try to force the active startup volume offline from the running system. If repair is needed, use macOS Recovery and Disk Utility, following Apple’s current instructions for the Mac’s processor and startup method. Make sure you understand which disk is selected before using erase, partition, or restore controls.

Common causes and misconceptions

Finder is still copying: wait for the progress indicator to finish, including any delayed file transfers.
An app has a file open: close the file and quit the app normally; a hidden window can still hold it.
Spotlight or backup activity: background indexing or backup work may temporarily access a volume. Give it time rather than interrupting an active operation.
The wrong item is selected: Disk Utility’s device, container, and volume entries are different levels. Select the intended volume and verify its name and capacity.
“Unmount” does not mean “erase”: unmounting disconnects a volume logically; erasing removes its contents. Do not choose erase as an eject workaround.

Frequently Asked Questions

How do I force eject a disk on a Mac?
Try closing apps and files, then use Finder’s eject control or Disk Utility’s Unmount command. If a force-unmount option is available, use it only after confirming that no data is being written and accepting the risk of interrupted work.

Why does my Mac say the disk is in use when nothing is open?
A background process, hidden app window, Finder preview, backup, or indexing task may still be accessing the volume. Wait, close likely apps, or restart and retry before considering a force unmount.

Can I unplug an external drive if it will not eject?
Do not unplug it while files are copying, saving, or backing up. If you cannot establish that activity has stopped, shut down or restart the Mac before disconnecting the device.

Will First Aid erase my disk?
First Aid is intended to check and repair filesystem problems, not erase the volume. Still, repair is not risk-free and cannot replace a backup; copy accessible important data before attempting repairs.

Why can’t I unmount my Mac’s startup disk?
The running system depends on its startup volume, so macOS may keep it mounted. For disk repair, start macOS Recovery and use Disk Utility rather than trying to detach the active startup disk.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →