Data Recovery Case File · Trust, Practice & Honest Limits · A Failed Restore Is Not an Empty Drive

Being Unable to Reinstate a System Says Nothing About Whether the Files Can Be Read

Her enquiry reaches a conclusion that is more pessimistic than the facts require. A drive used to back up a laptop, where after the internal drive was replaced "it proved impossible to reinstate the system" — although "other things saved separately on the drive are accessible" — with photographs and video of her late husband among what is wanted. A restore failing and a backup being unreadable are different things, and everything she reports points at the first.

The decode: why a failed restore is a narrower problem than it feels

What a system backup of this kind physically is: a container. Backups are stored inside a large structured file on the drive rather than as loose copies of every document.

What restoring involves: reading that container and writing its whole contents back. It is one long operation with many requirements, and a failure at any point stops all of it.

Why that is the fragile part: restoration is demanding. It needs the container intact, the destination prepared, the versions compatible and the process uninterrupted.

Why extracting files is far less demanding: it asks for one thing at a time. Reading individual files from the container needs only the parts holding those files, not the whole structure.

Why that difference matters so much here: she does not need a system. She needs photographs, and photographs are extracted from a container that could never be restored in full.

Why the accessible files on the same drive are strong evidence: the drive works. Content she can open proves the drive reads, the filesystem is sound and the connection is fine.

What that narrows the fault to: the container. The problem is inside the backup structure rather than anywhere in the drive that holds it.

Why the suggestion about a partition is plausible: backup containers present themselves as volumes. The container is mounted as a disc image when opened, and damage to its own descriptor prevents that while leaving the file itself present.

Why that particular damage is so recoverable: the descriptor is small. A container's own structures can be repaired or bypassed, and its contents read directly from an image.

What must not happen meanwhile: no further restore attempts and no repair offered by the backup software. Both write into the container, and it is currently the only copy of the photographs.

On the bench

Restore failure was distinguished from content loss before any recovery route was chosen — system backups being held inside a large structured container rather than as loose copies, so restoration reads that container and writes its entire contents back in one long operation that fails wholly at any point, while extracting individual files requires only the portions holding them. Accessible separate content establishes the drive and filesystem are sound. The container was mounted read-only from the image.

The outcome

Restore failure distinguished from content loss, the drive imaged before any interpretation, and content extracted file by file without performing a restoration. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: a restore is one long operation that fails completely at any point. Reading your photographs out needs only the parts of the backup that hold them.

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.