Time Machine backup will not mount deserves a clear, practical explanation. There is a particular sinking feeling that comes with double-clicking a Time Machine backup and watching macOS think about it for ninety seconds before telling you the disk image could not be opened. You did the responsible thing. You had a backup. And now the backup is the thing that needs recovering.
The short answer. Most unmountable Time Machine backups are sparsebundles with a damaged band or a stale lock file, and both are fixable without special software. Work through the free steps first. If the volume itself is failing or the catalog is genuinely corrupt, stop repairing and start extracting — every repair attempt on a failing disk costs you data.
Time Machine backup will not mount: Start with the boring fixes
- Unplug and replug. A surprising share of these are a USB enclosure that dropped off the bus, not a damaged backup.
- Try a different cable and a different port. Powered hubs are a common culprit with 2.5in drives.
- If it is a network backup on a NAS or Time Capsule, delete the .lock file inside the sparsebundle. A backup interrupted mid-write leaves one behind and macOS refuses to mount while it is there.
- Run First Aid on the physical volume, not on the sparsebundle, first.
Then try hdiutil
Terminal will tell you more than Finder will. Running hdiutil attach against the sparsebundle with the -readonly and -nomount flags gives you an actual error rather than a shrug. “No mountable file systems” points at the filesystem inside the image. “Resource temporarily unavailable” points at a lock or another process holding it. They need different fixes, and Finder tells you neither.
The point where you stop repairing
If First Aid fails twice, or the drive is making any noise it did not make last month, or the Mac hangs when the drive is connected — stop. Each repair attempt writes to the disk, and on a drive with failing sectors those writes are how a recoverable situation becomes an unrecoverable one.
The move at that point is to take an image of the whole drive onto a healthy disk, and do everything else against the image. It is slower and it feels like a detour, but it means you get exactly one pass at the failing hardware instead of twenty.
| Symptom | What it usually means | Next step |
|---|---|---|
| Mounts, then ejects itself | Enclosure or cable, not the data | New cable, new port, no hub |
| "No mountable file systems" | Filesystem inside the image is damaged | Read-only attach, then recover files out |
| First Aid fails repeatedly | Physical media problems | Image the drive, work from the image |
| Clicking or spin-up-spin-down | Mechanical failure | Power off. Software will not help here |
| Mounts but Time Machine sees no backups | Catalog or index damage | Browse the sparsebundle manually in Finder |
Getting files out without Time Machine
You do not need Time Machine to read a Time Machine backup. If the sparsebundle mounts read-only, the folder structure inside is plain readable directories, one per snapshot date, with your real files under them as hard links. Copy what you need straight out in Finder. Ignore the fact that Time Machine itself will not open it.
When the image will not attach at all
If macOS will not mount the sparsebundle even read-only, the container header is damaged and no amount of First Aid will change that. Stellar Data Recovery reads APFS and HFS+ structures directly out of the disk image and pulls files without needing the OS to attach it — which is the specific thing that is failing here.
Afterwards
One backup is not a backup. If this episode cost you a weekend, the lesson is not “Time Machine is unreliable” — it is that any single copy eventually fails. Add a second target: a cheap external that you rotate, or a cloud backup running alongside. Time Machine supports multiple destinations and alternates between them automatically.