Data Recovery Case File · Portable Drives · Salt Is the Problem
It Was Not Much Liquid and That Is Not the Measure
Her enquiry describes a small spill and a device that stopped. An external drive in a bag with lunch, where "the soup leaked on the drive. The cover was wet but my external drive didn't have much liquid on it. When I plugged it into my laptop, it is not recognised." Quantity is not what determines liquid damage — composition is, and soup is considerably worse than the same volume of water for reasons that keep working long after everything looks dry.
| Media | Portable external hard drive following ingress of salted liquid food — protective cover saturated; limited visible liquid on the device; not enumerating |
| Reported situation | Drive carried in a bag alongside liquid food · food leaking within the bag · protective cover wet · limited visible liquid on the drive itself · drive not recognised on connection · contents required |
| Fault class | Salted liquid ingress with active residue — conductive bridging and accelerated corrosion; visible quantity not indicative of internal exposure |
| Equipment used | No power applied before inspection · enclosure opened and board examined under magnification for residue and corrosion · board cleaned and dried under controlled conditions before any energisation · drive assessed on a native connection · imaged write-blocked on restored operation |
The decode: why composition beats quantity
What plain water does: conducts while present, evaporates, and leaves comparatively little behind. A device dried thoroughly before being powered frequently survives it, which is why the standard advice about water damage is about drying and waiting.
What salted liquid does instead: leaves salt. As the water evaporates the salt stays, and it is both conductive and hygroscopic — it draws moisture out of the air, so a board that appears bone dry can carry a damp conductive film indefinitely. Soup also contains fats and organic matter, which hold that residue against the board rather than letting it flake away.
Why that keeps working after drying: salt in contact with metal in the presence of moisture drives corrosion continuously, and the residue supplies both. The damage progresses on its own schedule rather than being an event that happened and finished.
Why "not much liquid" describes the outside: liquid wicks. It travels along cable entries, through seams, and under components by capillary action, and the visible quantity on a case has no relationship to what reached the board. A drop at a connector can be more consequential than a splash on a housing.
Why a bag makes it worse: the drive sat in a warm, enclosed, humid environment for however long it took to be discovered. That is close to ideal conditions for the residue to spread and to stay damp, and it removes the one thing that helps — air.
Why the drive not being recognised is consistent and not conclusive: a conductive film bridging contacts on the interface or the power path prevents the device presenting itself while leaving the mechanism and the platters entirely untouched. The commonest outcome here is a board that needs cleaning rather than a drive that has failed.
What must not happen, and it is the instinct: no further connection attempts. Applying voltage across a residue film is what turns a cleaning job into a component failure, and each attempt does it again.
What to do instead: leave it disconnected and get it opened and cleaned before it is energised. Rice does nothing, heat drives residue further under components, and time is not on anybody's side with salt involved.
On the bench
No power was applied before inspection — voltage across a conductive residue film converting a cleaning task into component failure. The enclosure was opened and the board examined under magnification for residue and corrosion, salted liquid leaving a hygroscopic film that draws moisture from the air and drives corrosion continuously long after a board appears dry. The board was cleaned and dried under controlled conditions before any energisation, the drive assessed on a native connection, and imaged write-blocked on restored operation.
The outcome
No power applied before inspection, the board cleaned and dried under controlled conditions and the drive imaged on restored operation. 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: quantity is not the measure — composition is. Salt stays behind when the water goes, draws moisture from the air, and drives corrosion continuously. And liquid wicks along cable entries and under components, so what you could see on the outside tells you nothing.
Drive that got food or drink on it
Don't plug it in again — applying voltage across a conductive residue film is what turns a cleaning job into a component failure, and each attempt does it again. Salted liquid is materially worse than plain water: water evaporates and leaves comparatively little, while salt stays behind, draws moisture out of the air, and drives corrosion continuously, so a board that feels bone dry can carry a damp conductive film indefinitely. Fats and organic matter hold it against the board. And the visible quantity means nothing, because liquid wicks along cable entries and under components. Rice doesn't help and heat drives residue further in. Get it cleaned before it's energised.
Don't power it — call Oxford Data Recovery on 01865 593000; inspected under magnification before any energisation, board cleaned and dried under controlled conditions, imaged on restored operation.
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.