macOS 'The disk couldn't be mounted' error fix

Cause #1: Corrupted volume or file system errors

This is the most common reason. The drive has a small file system error that stops macOS from mounting it. It happens a lot after a crash, a power outage, or just yanking out a USB drive without ejecting it first.

What you'll see: You plug in the drive, it shows up in Disk Utility but has a grayed-out volume name. When you try to mount it from Disk Utility, you get the error: "The disk couldn't be mounted. com.apple.DiskManagement.disenter-119930068."

Fix it with Disk Utility First Aid.

1. Open Disk Utility (Finder > Applications > Utilities > Disk Utility).
2. In the left sidebar, click View and choose Show All Devices. You want to see the physical disk, not just the volume name.
3. Select the physical disk (the topmost item, usually like "WD My Passport Media" or "APPLE SSD"). This is important—don't pick the volume name below it.
4. Click First Aid in the toolbar, then click Run. macOS will start checking the disk. Expect it to take anywhere from 30 seconds to 10 minutes, depending on drive size and how bad the corruption is.
5. When it finishes, you'll see a green checkmark that says "Operation successful." If it found and fixed errors, you'll see a line like "File system check exit code is 0" or "Volume repaired successfully."
6. Now try mounting the volume. Click the volume name (the indented one below the physical disk) and click the Mount button in the toolbar. If it mounts, you're good. If not, reboot your Mac and try again.

If First Aid fails or says "The volume is damaged and needs to be reformatted," don't panic. Move to Cause #2 below. If the drive is encrypted with FileVault or a third-party tool, skip to Cause #3.

Cause #2: APFS container corruption (macOS High Sierra and later)

Starting with macOS High Sierra, Apple switched to APFS for SSDs and some external drives. APFS has a different structure, and sometimes the container itself gets messed up. The volume won't mount because the container is corrupt.

How to spot this: In Disk Utility, the physical disk shows up but the volume doesn't appear at all. Or you see a container with a red exclamation point. Terminal commands will confirm it.

The fix: Use the terminal to check and repair the APFS container.

1. Open Terminal (Finder > Applications > Utilities > Terminal).
2. Type diskutil list and press Enter. You'll see a list of all disks. Look for your external drive—it's usually something like /dev/disk2 or /dev/disk3. The physical disk will show a line like /dev/disk2 (external, physical). Write down that disk identifier.
3. Now run diskutil apfs list. This shows the APFS containers. Find your disk's container—it'll be listed under the physical disk. Look for a line like Container: disk2s1 or Container: disk3s2. That's your container identifier.
4. Run this command: diskutil apfs verifyContainer /dev/diskX (replace X with your container number, like disk2s1). It will scan the container. If it finds corruption, it'll tell you.
5. If it reports issues, run: diskutil apfs repairContainer /dev/diskX. This fixes APFS container damage. It can take 5–15 minutes. Keep an eye on the terminal—it will print progress lines.
6. After repair, run diskutil mount /dev/diskXsY (replace with your volume identifier, like disk2s2). If it mounts, you're done. If it still fails, try Cause #3.

Important: If the terminal says "The container is corrupt and cannot be repaired," your drive is likely dead or needs professional data recovery. Back up anything you can before it dies completely.

Cause #3: Encryption keys or permissions blocking mount

Sometimes the disk mounts fine, but macOS blocks it due to permissions or encryption issues. This happens with FileVault-encrypted drives, Time Machine backups, or drives that were used on another Mac with different user accounts.

How to spot this: The drive appears in Disk Utility but when you try to mount it, a dialog asks for a password but won't accept it. Or you see "The disk couldn't be mounted because the volume is locked."

Fix it by unlocking with the terminal.

1. Open Terminal.
2. Type diskutil list and find your encrypted volume. It'll usually have a name like disk2s2 and show "APFS Volume" with an "Encrypted" label.
3. Run diskutil apfs unlockVolume /dev/diskXsY (replace with your volume identifier). The terminal will ask for the volume's encryption password. Type it (nothing shows on screen—that's normal) and press Enter.
4. If the password is correct, the volume mounts immediately. If it says "Password incorrect," try again. If you've forgotten it, you're out of luck—no shortcut here.
5. For non-encrypted drives with permission issues, try: sudo diskutil mount /dev/diskXsY. Enter your admin password when asked. This forces the mount with admin privileges.

If none of these work, the drive might be physically failing. Run a quick check with smartctl (install via Homebrew) or listen for clicking noises—that means the drive is toast.

Quick-reference summary table

Start with Cause #1—it fixes 70% of cases. If that doesn't work, move to Cause #2. If your drive is encrypted, jump straight to Cause #3. And if nothing works, the drive may be dying—back up what you can and replace it.