Data Recovery Case File · Portable Drives · The Effect Exceeds the Explanation
An Interrupted Write Damages a Filesystem, Not a Device
His enquiry offers a cause and describes an effect that does not follow from it. A drive "disconnected mid transfer from a computer as some video files were being transferred. After that, the device isn't recognised by any laptop." Pulling a drive during a write leaves the filing structures inconsistent — and a volume that will not mount is a very different thing from a device that will not introduce itself at all.
| Media | 1TB external hard drive — disconnected during an active write; not enumerating on any host subsequently |
| Reported situation | Video files being transferred to the drive · drive disconnected during the transfer · device not recognised by any laptop since · contents required |
| Fault class | Failure to enumerate following an interrupted write — device-level fault exceeding what interruption alone accounts for; enclosure and drive both outstanding |
| Equipment used | Reported cause weighed against the observed symptom before any conclusion · drive removed from the enclosure and assessed on a native connection · current draw measured on a controlled bench supply · readiness sequence read under strict timeouts |
The decode: what an interruption can and cannot cause
What an interrupted write actually damages: the filesystem. Structures that were being updated are left half-written, so the volume describes a state that was never completed and the system declines to mount it. That is a logical fault and it is common.
What it leaves untouched: the device. The controller, the bridge board, the motor and the heads are all unaffected by a cable being pulled — they lose power, which they are designed to survive, and they behave normally on the next connection.
So what a drive with filesystem damage looks like: it appears. The device enumerates, the system sees a disk of the right size, and the volume either fails to mount or prompts to be formatted. Everything above the filesystem is broken and everything below it works.
Why his symptom is bigger than that: nothing recognises the device at all. That is a failure at a level an interrupted write does not reach, so the disconnection is unlikely to be a complete explanation on its own.
What that leaves, and there are two plausible readings. The first is coincidence — the drive was failing, and the transfer was heavy sustained work that brought it to the point of failing completely. Faults surface under load, and a large video transfer is the heaviest demand most drives meet.
The second is the disconnection itself: if the cable was pulled physically rather than ejected, the connector may have been damaged. A drive disconnected by force is a drive whose port has taken a lateral load, and a fractured joint produces exactly this — no enumeration at all, on every host.
Why the distinction matters practically: a connector fault is an inexpensive repair with the memory untouched. A drive that failed under load is a different job, and separating them starts with removing the drive from its enclosure and connecting it directly.
Why that single step is the right next one: it eliminates the enclosure, its bridge board and its connector in one operation. If the drive presents natively, the fault was in the enclosure — which is the cheapest outcome and a common one after a physical disconnection.
What must stop: further connection attempts on more machines. Every host will report the same thing.
On the bench
The reported cause was weighed against the observed symptom before any conclusion — an interrupted write damaging filesystem structures while leaving the device unaffected, so such a fault presents as a drive that enumerates with a volume that will not mount, whereas complete failure to enumerate indicates a fault at a level interruption does not reach. The drive was removed from the enclosure and assessed on a native connection, eliminating enclosure, bridge and connector in one operation.
The outcome
The stated cause weighed against the symptom, the enclosure eliminated on a native connection, and draw measured on a controlled bench supply. 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 interrupted write damages a filesystem, not a device. That produces a drive that appears with a volume that will not mount — yours does not appear at all, which is a bigger symptom than the cause accounts for.
Drive pulled during a transfer that nothing now recognises
Take it out of its enclosure and connect the drive directly — that one step eliminates the enclosure, its bridge board and its connector together, and it's the likeliest explanation. An interrupted write damages the filesystem, leaving structures half-updated so the volume won't mount, but it doesn't touch the device: the controller, motor and heads simply lose power, which they're built to survive. So filesystem damage looks like a drive that appears normally with a volume that won't open. Yours not appearing at all is a bigger symptom than the interruption accounts for, and a cable pulled by force can fracture a connector joint.
Try it out of the enclosure — call Oxford Data Recovery on 01865 593000; cause weighed against symptom, drive assessed on a native connection, draw measured on a controlled bench supply.
Request a quote online →
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.