Data Recovery Case File · Mac & Apple Ecosystem · Ask About the Sources First

The Backup Drive That Will Not Mount

His enquiry described a failure with a particular sting to it. A 3TB drive "recognised in Disk Utility but will not mount. It is Mac formatted for Time Machine back-ups and has all our data back-ups on it." The technical position is good — recognised-but-unmounted means healthy hardware behind an unreadable filesystem, which is among the most recoverable situations there is. But before any of that, there is a question worth asking that changes the whole picture, and people in this position rarely think of it: a backup drive failing is not the same as data being lost. The machines it was backing up may still have everything on them.

The decode: the first question, then the technical picture

Ask what the backups were of. A Time Machine drive holds copies of material that lived somewhere else. If the Macs it was backing up are still working, then nothing has actually been lost — what has failed is the safety net, and the correct response is to get a new drive and start backing up again today rather than to commission a recovery. That sounds obvious written down, and it is routinely missed, because the failure of a backup drive feels like losing everything. It is worth establishing before spending anything. The exception is where the source machines have since been replaced, wiped or failed, or where older material was moved onto the backup and deleted from the source — in which case the backup genuinely is the only copy and this becomes urgent.

What "recognised but won't mount" establishes: a great deal, all good. For the drive to appear in Disk Utility it received power, spun up, identified itself, reported its capacity and responded to being addressed — which eliminates the seized, clicking, dead-board and unidentifiable categories entirely. What has failed is the filesystem, and macOS declines to mount structures it finds incoherent rather than mounting them and risking further damage. That refusal is protective, and the contents sit intact behind it.

Why a backup volume is harder to rebuild than an ordinary one: the part worth knowing before comparing quotations. Time Machine does not store plain copies. It keeps many point-in-time versions using extensive linking — a file unchanged across fifty backups exists once with fifty references to it — and on newer systems it uses volume snapshots layered on top of that. So reconstruction has to rebuild not only the filesystem but the relationships that make the versions meaningful. Done poorly, the result is a heap of files with no sense of which backup they belonged to. Done properly, the backup structure is restored so that content can be located by date and by source machine.

What must not happen: Disk Utility will offer First Aid, and on a volume with this much structural linkage a repair that writes decisions can do disproportionate damage. It will also offer to erase. Neither should be accepted, and the drive should not be left connected while it is considered.

On the bench

The status of the source machines was established before any work was proposed, since a backup drive failing while the originals survive calls for a new backup rather than a recovery. Where the backup was genuinely the only copy, the drive was imaged write-blocked before any repair was attempted — the discipline a repair utility cannot offer. On the image the volume structures were reconstructed together with the linking and snapshot records that give a backup its versions, so that content could be located by date and by source machine rather than returned as an undifferentiated heap. Restored content was verified by opening.

The outcome

The sources checked first, the drive imaged before any repair and the backup structure rebuilt so versions remained meaningful. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose backup drive has failed: ask what the backups were of first, because if the machines they came from still work, nothing has been lost and the answer is a new backup drive today rather than a recovery; recognised-but-not-mounting means healthy hardware behind an unreadable filesystem, and the refusal to mount is protective; but a backup volume is harder to rebuild than an ordinary one, because it stores many versions through extensive linking and snapshots, and a poor reconstruction returns files with no sense of which backup they belonged to.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.