Data Recovery Case File · Liquid Damage · The Tea and the Broken Net

When the accident and the backup fail together: a tea-spilled MacBook's symbols decoded, a corrupted Time Machine explained — and the files brought home anyway

Her enquiry opened with the best-humoured confession in this archive's liquid genre: "A cup of tea — freshly made, milk no sugar — and a MacBook laptop: not the best combination, I will admit." The aftermath, reported precisely: the laptop "flashing two pictures in turn," one resembling a small device, the other the side of a laptop; unable to switch off properly — only a drained battery powers it down; and sometimes an Apple logo with a white progress bar appears, "but it then reverts" to the flashing pair. And then the twist that earns this page its title: "I have Time Machine enabled — however it appears that (and you couldn't make this up) it is corrupted." Last successful backup: Christmas Day. The accident took the laptop; the safety net turned out to have a hole in it. Both get decoded below, both were worked — and the recovery came from the patient most people would have written off first.

The decode: what the flashing symbols mean, why it won't switch off — and how a backup corrupts while you're not looking

The symbols, translated: a Mac cycling between firmware screens is a machine whose start-up keeps failing at a level below the operating system — the liquid's board casualties leaving it able to begin booting (hence the occasional logo and progress bar) but never to finish, relapsing each time into its low-level distress display. The refusal to power off cleanly belongs to the same layer: the power-management circuitry, an early casualty in most spills, no longer honouring the button — which is why only an empty battery ends a session. All of it is board news, and the liquid genre's central mercy applies in full: tea attacks electronics — traces, controllers, power management — while the storage itself, whether a drive or flash, typically rides out the flood intact behind them. Her machine was drowning at the doorway with the vault dry. The backup's betrayal, decoded without the disbelief: you could make it up, because it's common — Time Machine's network and disk backup sets are intricate layered structures, and they corrupt quietly over months of interrupted runs, sleeping mid-backup, and unclean disconnects; nobody notices, because nobody reads a backup until the day it's needed, which is precisely the day corruption gets discovered. The Christmas-Day date marks when the rot likely began: the last run that completed. The doctrine her double failure writes: a backup that's never been test-restored is a hope, not a copy — verified restores, twice a year, are the whole difference.

The recovery — two patients, and the accident's victim won

Both fronts were worked. The MacBook's storage was extracted from behind its drowned board and imaged write-blocked — and rose whole: the operating system's world intact to the moment of the spill, her documents and files current to that morning, the liquid's entire bill confined to the electronics around it. The Time Machine set was opened for structural repair in parallel and yielded its history in substantial part — useful corroboration, and a recovered archive of versions back through December — but the headline inverted the expected story: the spilled laptop was the better source, more current and more complete than the corrupted net beneath it. Delivery went out on new media in duplicate: the current estate from the machine, the version history from the repaired backup, organised and verified file by file — with the report's closing pair of instructions earned twice over: the laptop's board to a repair shop (the machine trade's job, per this archive's standing doctrine), and the new backup regime to a verified schedule, restored-from and proven, so that the next accident meets a net that's actually been load-tested.

Outcome

The documents home from the tea's victim, the backup's history salvaged alongside — and the double lesson filed with her good humour intact. After a spill: power down and leave it down (her battery-drain limbo was the machine doing this badly on her behalf) — no rice, no hair dryers, no repeated boot attempts through the flashing screens; the storage behind the drowned board is usually fine, and every powered minute risks the electronics corroding further under current. About backups: enabled is not working — test-restore twice a year, and treat a backup that's never been read as what it statistically is: a coin toss wearing a green tick. The tea took the doorway. The corruption took the net. The files, sitting quietly behind both failures, never actually went anywhere — which is the liquid genre's oldest promise, kept here in duplicate, milk no sugar.

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.