Data Recovery Case File · Formatted & Logical Faults · Interrupted Between Hosts

A Transfer Cut Partway Leaves Structures Neither System Can Interpret

His enquiry pins the failure to a transition. A drive whose filesystem has become unreadable — reported as raw — which "stopped working while transferring data from one machine to another, and now it's unreadable by both." The moment of failure is the diagnosis: an interruption during a write leaves the structures describing the volume half-updated, and a half-updated structure is not readable by the system that was writing it or by any other.

The decode: why an unrecognised filesystem is a structure fault, not a media fault

What a system means by an unrecognised filesystem: it read the beginning of the volume and found nothing it could identify. It is not reporting an empty drive or a damaged one — it is reporting that the description of the arrangement did not make sense, so it declines to mount rather than guessing.

Why that message so often follows an interruption: writing files means updating the structures that record where they are. Those updates are not instantaneous, and a device losing power or connection partway leaves them half-applied — internally inconsistent, and therefore unidentifiable.

Why it is unreadable by both systems rather than one: the damage is in the data structure itself, not in either system's ability to read it. Neither is refusing out of incompatibility; both are finding the same nonsense — which usefully rules out a cross-platform format question that would otherwise be worth investigating.

Why the content is very likely intact: the structures occupy a small area at the start of the volume. The files were written before the transfer and sit where they were placed, entirely unaffected by a damaged description of their locations.

Why the low occupancy is genuinely favourable: around a tenth of the capacity is in use. Sparse content means files sit in large contiguous runs with plenty of unwritten space between them, which makes them easier to locate and reassemble than a nearly full drive would be.

What helps most in reconstruction: filesystems keep duplicate copies of their key structures elsewhere on the volume. Where the primary set was damaged at the moment of interruption, the duplicates frequently survive — and comparing the two often restores the arrangement outright.

What is done where that fails: the content is searched for directly. Photographs and documents begin with recognisable patterns that identify them without any structure to guide the search — so the material is found even where the map cannot be rebuilt.

Why the absence of physical damage matters: the drive still responds and can be read. This is a logical fault on healthy hardware, which is among the more recoverable situations there is, provided nothing writes to it.

What must not happen: no accepting an offer to format the drive, and no repair or checking tools run against it. Both systems will offer to prepare a volume they cannot identify, and a consistency check writes corrections that can discard references to intact content.

On the bench

Interruption during writing was identified as the mechanism rather than media failure — file writes requiring updates to the structures recording locations, so power or connection loss partway leaves those updates half-applied and internally inconsistent, which both systems then report as an unrecognised filesystem rather than declining on compatibility grounds. Primary and duplicate filesystem structures were compared, duplicates commonly surviving damage confined to the primary set, with carving targeted to image and document formats where reconstruction was not possible.

The outcome

The interruption identified as the mechanism, the drive imaged at the block level, and structures compared against their duplicates. 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: an unrecognised filesystem means the description of the arrangement stopped making sense, which is what an interrupted write produces. Both systems find the same nonsense, and your files sit untouched behind it.

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.