Data Recovery Case File · Formatted & Logical Faults · Nothing to Scan
The Help Sites Told Her to Scan Something That Is Not There
Her enquiry describes a spill and then a search for advice that led nowhere it could have led. "I spilt tea on my laptop. Then when I tried to turn it on again it displayed a message saying no boot device found and something to do with installing a hard drive. When I tried to scan the hard drive as lots of help sites said to do, it said that there was no hard drive fo"und. Everything she was told to do was reasonable and none of it could have worked. You cannot scan a drive the machine cannot see — and after a liquid spill, there is one thing that matters far more than any of it.
| Media | Laptop internal drive following liquid ingress — machine reporting no boot device found; drive not detected by any scanning attempt |
| Reported situation | Liquid spilled onto the machine · machine reporting no boot device found on power-up · guidance followed to scan the drive · scanning tools reporting no drive present · contents required |
| Fault class | Drive not detected following liquid ingress — connection, board or drive; corrosion progressive while power is applied |
| Equipment used | Machine kept unpowered and uncharged after assessment began · drive removed and assessed separately from the machine on a native connection · board and connector inspected for corrosion under magnification · imaged write-blocked on restored detection |
The decode: why the advice failed, and the thing to do instead
Why no scanning tool could help: recovery and scanning software asks the operating system for a device and reads it. Where the machine reports that no drive is present, there is nothing to hand over — so every tool returns the same answer, and each one she tries will return it again. The failure of those tools says nothing about her data; it says the drive is not being detected, which she already knew from the boot message.
Why the advice was offered anyway: "no boot device found" has many causes, and on a machine that has not been near liquid the commonest are a boot configuration problem or a drive that is present but unreadable — for which scanning is sensible. The guidance is written for the general case. It does not fit hers, because the cause is known and it is the spill.
What the spill has most likely done: three candidates, in order. Liquid reaching the connector between the drive and the board, leaving corrosion on contacts that must be clean to carry a signal. Damage to the board's storage circuitry, so the machine cannot address the drive at all. Or liquid reaching the drive itself, which on a sealed mechanical drive means its exposed board rather than the platters.
Why the distinction is good news in two of the three: a corroded connector and a damaged mainboard both leave the drive untouched. Removing it and reading it on other equipment resolves the case entirely, and neither is a recovery in the difficult sense.
The instruction that matters more than everything above: stop powering the machine. Liquid damage is driven by voltage. A wet or contaminated board with power across it corrodes actively, eating through traces and component legs, and every power-up during troubleshooting advances that. She has been switching it on to try things — which is exactly what the advice invites — and the tea is doing more damage each time than any of the attempts could have undone.
Why time matters too: corrosion continues slowly even unpowered. This is the one fault class where deliberating has a real cost, and it argues for acting rather than researching further.
What not to do: not power it, not charge it, not attempt to dry it with heat, and not put it in rice — which does nothing useful and introduces dust and starch.
On the bench
The machine was kept unpowered and uncharged from the point of assessment, since voltage across a contaminated board drives corrosion continuously and each troubleshooting power-up advances it. The drive was removed and assessed separately from the machine on a native connection, which resolves the case entirely where the fault lies in the connector or the mainboard rather than the drive. The board and connector were inspected for corrosion under magnification, and imaging followed write-blocked on restored detection.
The outcome
The machine taken out of use, the drive assessed separately and imaged on restored detection. 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, for anyone told to scan a drive after a spill: no scanning tool can help, because they ask the system for a device and your machine reports none — so every tool gives the same answer and it says nothing about your data. Stop powering it, which matters far more. Liquid damage is driven by voltage, and each attempt advances the corrosion.
Liquid spill followed by no boot device found
Stop switching it on — that matters far more than anything else, and it's the opposite of what troubleshooting guides have you doing. Liquid damage is driven by voltage: a contaminated board with power across it corrodes actively, eating through traces and component legs, so every power-up during testing advances the damage. And no scanning tool could have helped anyway, because they ask the operating system for a device and your machine is reporting that none is present. There's nothing to hand over, so every tool returns the same answer. Two of the three likely causes are good news, though — a corroded connector or damaged mainboard circuitry both leave the drive itself untouched, and it reads fine on other equipment. Don't use heat, and don't use rice.
Stop powering it — call Newcastle Data Recovery on 0191 406 1051; kept unpowered, drive assessed separately from the machine, connector and board inspected for corrosion under magnification.
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.