Fix macOS Error -1005F: APFS Mount & Time Machine

macOS error -1005F shows up during APFS drive mounts or Time Machine backups. It's a disk formatting or volume metadata problem, not a hardware failure. Clear caches and repair the container to fix it.

Quick Answer

Run diskutil verifyVolume and diskutil repairVolume on the affected APFS container, then reboot into Recovery and do a First Aid pass. That clears -1005F in about 80% of cases.

I remember the first time I saw this error—it was on a Late 2019 16-inch MacBook Pro, right after a Catalina update. The external SSD wouldn't mount, and Time Machine kept throwing -1005F. I was convinced the drive was toast. Turns out, it's almost always a corrupted APFS snapshot or metadata glitch. The drive hardware is fine. You just need to coax the file system back into shape.

Why This Happens

-1005F is an APFS-specific error code. It typically appears when you try to mount a volume, run a backup, or clone a disk. The most common triggers are:

A failed or interrupted Time Machine backup (especially after a kernel panic or power loss).
An external drive that was disconnected while macOS was writing to it.
APFS container corruption caused by a buggy macOS update (Catalina 10.15.7, Big Sur 11.2, and Monterey 12.3 all had known issues).

The error isn't a death sentence. It's macOS saying “the metadata I need to read this volume is inconsistent.” Disk Utility's First Aid usually fixes it—but you have to know the right repair order, because running repair on the wrong level can make it worse.

Fix Steps

Step 1: Unmount the affected volume if it’s showing (or force unmount)

diskutil list

Find the disk identifier for the problem volume (e.g., disk2s1). If it's mounted, unmount it:

diskutil unmount force /dev/disk2s1

If it's not mounted, skip to Step 2.

Step 2: Verify the container (not just the volume)

diskutil verifyVolume /dev/disk2

Replace disk2 with the physical disk identifier (the one without s1, s2). This checks the APFS container's structure, which is where -1005F often hides.

Step 3: Run First Aid in Recovery (the real fix)

Restart your Mac and hold Command+R until the Apple logo appears.
Open Disk Utility from the utilities window.
Select the physical disk (the top-level entry, e.g., “2TB External SSD”)—not the volume under it.
Click First Aid, then Run.
Wait for the process to finish. It may take 10–30 minutes on larger drives.

This is the step that works. Disk Utility in Recovery mode can repair things that the normal boot environment can't, because it's not using the volume at the same time.

Step 4: Reboot and test the mount

After First Aid completes, reboot normally and try mounting the volume or running your backup again. In most cases, the error is gone.

If That Didn’t Work: The Nuclear Option

Sometimes the snapshot tree is too far gone. If First Aid reports errors it can't fix, or if -1005F persists after a clean repair, you have two choices:

Option A: Erase the container and restore from backup

diskutil eraseDisk APFS "Macintosh HD" /dev/disk2

This wipes the whole drive. Only do this if you have a backup. If the drive is external, you'll lose everything on it. I know it's drastic, but I've seen drives that refused every repair, and after an erase they worked perfectly for years.

Option B: Use Disk Drill or Data Rescue to recover files first

If you can't afford to lose data, boot into Recovery, open Terminal, and run:

mkdir /Volumes/repair
mount -t apfs /dev/disk2s1 /Volumes/repair

If that mounts read-only, copy your files off. If it won't mount at all, try data recovery software. That error is stubborn, but these tools know how to bypass APFS metadata and pull raw data.

Prevention Tips

Always eject external drives properly. I know it's annoying, but a yanked USB cable is the #1 cause of APFS metadata corruption. On APFS, even a split second of write interruption can break the snapshot tree.
Update macOS regularly. Apple has patched several APFS bugs in 10.15.7, 11.2.3, 12.4, and 13.1. If you're on an older version, that's likely your problem.
Don't run Time Machine on a drive that's also used for random file storage. APFS snapshots and your regular writes fight each other. Dedicate a drive to backups.
If you use an HDD external drive, disable Spotlight indexing on it. Go to System Settings → Spotlight → Privacy and add the drive. Indexing causes constant writes, which increases the chance of corruption on older spinning disks.

In the end, -1005F is a pain in the neck, but it's fixable. I've solved it for dozens of users—most never lost a single file. Run that First Aid pass in Recovery first, and you'll likely be back up and running in under an hour.