Couldn't Unmount Disk (-69888) on Mac? 5 Safe Fixes for disk0 and External Drives

If your Mac shows “Couldn't unmount disk. (-69888)”, Disk Utility or the diskutil command could not detach the target disk or volume from macOS before repairing, erasing, partitioning, or otherwise changing it. The most common reason is that the disk is still in use. If the message mentions disk0, the target may be the current startup disk, which generally must be handled from macOS Recovery rather than from the running system.

The safest fix depends on whether the affected storage is an external drive or the startup disk. This guide starts with non-destructive checks, protects your files before repair or erase, and uses Terminal force-unmount only after simpler options fail.

Part 1. What “Couldn't Unmount Disk (-69888)” Means

The message is an unmount failure, not a diagnosis of one specific type of disk corruption. Understanding what macOS was trying to do when the error appeared is the fastest way to choose a safe fix.

Why Error -69888 Happens

Error -69888 usually appears when Disk Utility or diskutil needs exclusive access to a disk but macOS cannot release it. That can happen during erase, partition, repair, or other maintenance operations.

• The disk is still in use: A Finder window, app, backup process, Terminal session, indexing process, or another service may still be accessing the volume.
• You are targeting the current startup disk: The system cannot normally unmount the volume it is actively running from. This is a common reason for messages such as “The volume on disk0 couldn't be unmounted.”
• The file system needs repair: Directory or formatting errors can interfere with a normal unmount and may require First Aid.
• The drive or connection is unstable: An external HDD, SSD, cable, enclosure, port, or power source can cause repeated disconnects or failed maintenance operations.
• The disk is physically failing: If the drive clicks, disappears repeatedly, is intermittently detected, or cannot be seen reliably in Disk Utility, continued repair attempts can make data recovery harder.

Key distinction: a busy external disk can usually be released inside normal macOS, while the active startup disk requires a different boot environment (macOS Recovery).

External Disk vs. disk0: Choose the Right Path

Before running commands or clicking Erase, identify which disk is affected and what you were trying to do. The table below provides a safer starting point.

Part 2. Protect Your Data Before Fixing the Disk

Unmount errors often appear while users are preparing to repair, partition, or erase a drive. Those actions can change the source disk, so data protection should come before increasingly aggressive troubleshooting.

When to Back Up or Recover Files First

If the drive still opens and your files are readable, copy the important files to another healthy device before running First Aid, force-unmounting, repartitioning, or erasing. Apple likewise recommends having a current backup before repairing a storage device with Disk Utility.

If the error is on an external device and files have already become inaccessible, the dedicated external hard drive recovery on Mac guide explains the recovery-first path before you format or rebuild the disk.

Wondershare Recoverit

Your Safe & Reliable Data Recovery Expert

Download DownloadDownload

Easily recover deleted or lost files in 500+ data loss situations, such as deletion, formatting, and disk corruption. The software confidently retrieves all data types, regardless of how they went missing.

Part 3. How to Fix Couldn't Unmount Disk 69888 on Mac

Work through the fixes in order. The first two methods are the least disruptive. Terminal force-unmount comes later because the force option is less friendly to open files, while erase is deliberately kept last because it destroys data.

Method 1. Close Disk-Using Apps and Retry Unmount

For an external disk, begin by removing the most common reason macOS refuses to unmount it: an open app, Finder window, or active task that is still using the volume.

Step 1. Save your work and close apps that may be reading from or writing to the affected drive. Also close Finder windows that are displaying folders on that disk.

Tip: If Finder itself is holding the disk, relaunch it: hold Option, right-click the Finder icon in the Dock, and choose Relaunch. Then retry the unmount.

Step 2. If a Terminal window is currently working inside a folder on the external drive, change to your home directory with cd ~ or close that Terminal window.

Step 3. Open Disk Utility, choose View > Show All Devices, select the affected external volume or disk, and click Unmount.

Step 4. If the disk unmounts successfully, retry the repair, partition, or erase operation you originally intended. If it immediately remounts or the same error returns, restart the Mac and continue to Method 2.

Apple's current Disk Utility unmount guidance confirms that Disk Utility can unmount storage when maintenance requires the disk to be offline.

Method 2. Run First Aid in Disk Utility

If a normal unmount still fails, the next step is to check the file-system structure. First Aid can repair some formatting and directory problems, but you should already have a backup because repair operations can expose damaged files.

Step 1. Open Disk Utility and choose View > Show All Devices.

Step 2. In the sidebar, start with the last volume on the affected device. Click First Aid, then Run.

Step 3. Move upward through the storage hierarchy, running First Aid on each remaining volume, then any volume group, then the container, and finally the physical device itself.

Step 4. When First Aid finishes, quit Disk Utility and retry the operation that previously returned error -69888.

Apple's current Disk Utility First Aid instructions use this bottom-up order and recommend backing up before repair. If the affected item is your startup disk, do not keep retrying First Aid in normal macOS; continue to Method 4 and run it from Recovery.

Method 3. Force Unmount an External Disk With Terminal

If the affected external disk is still detected and your important files are already safe, Terminal can request a forced unmount. Use this only on the correct external disk identifier and only after closing apps that may be using it.

Step 1. Open Terminal from Applications > Utilities.

Step 2. List the disks connected to your Mac:

diskutil list

Step 3. Identify the whole external disk, such as /dev/disk4. Verify its size and partition layout before continuing so you do not target the wrong device.

Step 4. Find which process is holding the disk (optional but useful):

sudo fuser -c /dev/disk4  or  sudo lsof | grep disk4

Both commands return the PID(s) of processes using the disk. If the output lists a process you recognize (for example, fsck_hfs), you can quit it and retry the unmount.

Step 5. Force-unmount all volumes on that disk:

diskutil unmountDisk force /dev/disk4

Replace disk4 with the identifier shown on your Mac. The important correction is the space between force and /dev/disk4.

Step 6. If Terminal reports a successful unmount, return to Disk Utility and retry the intended maintenance operation.

The macOS diskutil manual documents unmountDisk [force] device and warns that force-unmount is less kind to open files. If the command still fails, do not repeat it — use Recovery for an internal startup disk or move to the hardware checks in Part 4.

Method 3.5: Rule Out Spotlight Indexing and Time Machine

Two background services can quietly hold a disk and cause error -69888: Spotlight indexing and Time Machine backups.

1. Exclude the disk from Spotlight: Go to Apple menu > System Settings > Spotlight > Privacy, add the external drive's folder, then retry the unmount.
2. Remove the disk from Time Machine: Open System Settings > Time Machine, right-click the backup disk, and choose Stop Using for Backups, then retry.
3. Retry the unmount or maintenance operation. If either service was the culprit, the disk should release now.

Method 4. Use macOS Recovery for disk0 or the Startup Disk

If the message says “The volume on disk0 couldn't be unmounted” while you are trying to repair or erase the Mac's startup storage, the core issue may simply be that macOS is running from the disk you are trying to take offline. Recovery gives Disk Utility a separate environment to work from.

Step 1. Shut down your Mac.

Step 2. On a Mac with Apple silicon, press and hold the power button until startup options appear, then choose Options > Continue. On an Intel Mac, turn it on and immediately hold Command + R until the Recovery screen appears.

Step 3. Select Disk Utility in Recovery and click Continue.

Step 4. Choose View > Show All Devices, then run First Aid on the startup storage using the volume-to-device order described in Method 2.

Step 5. Quit Disk Utility and restart the Mac when the repair is complete. If your original goal was to erase the startup disk, continue only after confirming that the data you need is safely backed up or recovered.

Apple's current macOS Recovery startup instructions distinguish Apple silicon from Intel Macs. For a longer walkthrough of the Recovery tools and startup paths, see the Recoverit guide to starting a Mac in Recovery Mode.

Method 5. Erase the Disk Only After Your Data Is Safe

If the disk cannot be repaired and your original goal is to reformat it, erase is the final software step. It permanently removes the existing data, so do not use this method as a generic way to “fix” -69888 when you still need files from the disk.

Step 1. Confirm that all important data has been backed up or recovered to a different healthy storage device.

Step 2. Open Disk Utility. For a startup disk, enter macOS Recovery first. For an external disk, Disk Utility can normally be opened from Applications > Utilities.

Step 3. Choose View > Show All Devices and select the correct physical storage device or the appropriate startup volume for your specific erase task.

Step 4. Click Erase. On an Apple silicon startup disk, Disk Utility may offer Erase Volume Group instead.

Step 5. Choose the required name, format, and partition scheme for your use case, then confirm the erase only after verifying the target disk one more time.

Apple's erase and reformat guidance explicitly states that erasing deletes everything on the storage device. If you are formatting an external disk rather than the Mac's startup storage, this Recoverit guide explains how to format an external hard drive on Mac and choose a suitable file system.

Part 4. What If the Disk Still Won't Unmount?

If all five paths fail, stop repeating force-unmount, First Aid, erase, or partition commands. At this point, the drive's behavior matters more than the original error code.

Know When to Stop Repair Attempts

Stop repeated software repair attempts when the evidence points toward an unstable connection or physical device problem rather than a simple mounted-volume conflict.

Apple notes that if Disk Utility cannot see or repair a storage device, the Mac or the storage device may need service. For an external drive, checking its cable, connections, and power is also part of the current troubleshooting path.

When Data Recovery Makes Sense

If the drive is still detected but important files are missing, deleted, formatted, or inaccessible, data recovery should come before erase or repartitioning. Keep writes to the affected storage to a minimum and save recovered files to a different healthy drive.

Recoverit for Mac can be considered when the source storage remains detectable and the issue is logical data loss rather than a physically failing device. No recovery software can guarantee files that have already been overwritten, and a disk that is not detected at the operating-system or recovery-environment level may require professional hardware-level recovery instead.

Conclusion

Couldn't unmount disk (-69888) means macOS could not release the target disk for the operation you requested. For an external disk, close apps and Finder windows first, retry the normal unmount, run First Aid, and use Terminal force-unmount only after your data is safe. If disk0 or the startup disk is involved, switch to macOS Recovery instead of trying to unmount the active system volume from normal macOS. Erase only when it is genuinely required and only after the files you need are backed up or recovered.