Recover files from an APFS drive that macOS won’t mount
APFS keeps several layers of bookkeeping: checkpoints, an object map, file-system trees and snapshots. When one of them is damaged, macOS refuses to mount the whole volume, even though almost all of your files are still on the disk.
A volume that won’t mount is usually a damaged index, not lost files. Retrova reads the newest usable checkpoint directly, tolerates damaged trees, can browse older snapshots, and copies everything off without writing to the drive.
Why APFS volumes stop mounting
Common causes are a drive unplugged while it was writing, a power cut, a flaky USB bridge, or worn flash returning bad data. Any of these can leave one of APFS’s internal trees inconsistent. macOS is strict: if the checks fail, it won’t mount the volume, and First Aid may stop with an error such as “fsck_apfs exited with error code 8”.
The good news is that APFS never overwrites data in place. It writes new copies and keeps older checkpoints around, so a reader that is more forgiving than macOS can usually still reach your files.
How Retrova reads a damaged APFS volume
- It looks for the newest checkpoint that still holds together and reads the object map and file-system tree from there.
- It works around damaged parts of the catalog instead of giving up on the whole volume. Files it can’t read are listed in the log; everything else is copied.
- It can browse snapshots. If today’s state of the volume is damaged, an older snapshot may still be intact.
- It understands APFS-compressed files, and you see the real folder tree with original names and dates.
Step by step
- Plug the drive in and open Retrova. On the home screen choose A drive won’t open. Retrova lists every drive and partition it can see, with the file system it detected and a health check where the drive reports one.
- Pick the drive or partition. Reading a drive directly needs administrator rights, so Retrova asks for your password at this point and only uses it to read.
- Browse and choose what you want back. You see the original folders and file names. Select whole folders or single files, and preview photos, videos, PDFs and text before copying.
- Choose where the copies go. Always pick a different drive with enough free space. Retrova never saves onto the drive it’s rescuing, and it pauses by itself if the destination runs low on space.
- Copy, then verify. Files are written as temporary parts and renamed only when complete, so a half-copied file never looks finished. Anything unreadable is logged and the copy carries on. When it’s done, run Verify to compare every copied file with the original, byte for byte.
Retrova started as exactly this tool: a script written to rescue a portable SSD whose APFS volume macOS refused to mount. Read how that went.
About encryption
If the volume was encrypted with FileVault or an APFS password, Retrova tells you so when it scans the drive. Deep scan can’t find files inside an encrypted volume, because the content is scrambled without the key.
Get Retrova
Free and open source for macOS 11+ and Windows 10/11. No account, no recovery limit, and it never writes to the drive you’re rescuing.
Download RetrovaFree for Mac and WindowsQuestions
Should I run First Aid before recovering?
Once is fine on a healthy drive. If it fails, or the drive is slow, noisy or disconnecting, stop and copy your files off first. Repairs write to the disk.
Does this work on Apple silicon and Intel Macs?
Yes. Retrova has separate downloads for Apple silicon (M1 and later) and Intel Macs, on macOS 11 Big Sur or later.
Can I recover from a disk image instead of the drive?
Yes. Open a .img or .dmg-style raw image the same way as a drive. That’s the safest way to work with a failing disk: image it once, then recover from the image.