Anonymised, technically honest write-ups of real recovery patterns from the bench — what arrived, what had actually failed, what the fix took and what went home. Read them as previews: if your situation is on this page, so is your likely outcome. A few of these arrived as emergency data recovery jobs — same method, compressed clock — and every one came through the same data recovery services: imaged first, worked in-house.
A months-old drive that beeps quietly, still offers to eject, and has lost its files. Why those two facts come from two different components.
// undetermined post-impact fault —…Knocked onto the floor and now dead, with no other symptom described. What not working can mean after a fall, and the one detail worth reporting.
// impact damage sustained with…Knocked off while plugged in and working, and now a short whirr and silence. Why being powered at the moment of impact is the fact that changes everything.
// post-impact damage with reads…A knocked drive that crashes the editing software, with thousands of images and the catalogue on it. Why the catalogue needs its folder paths intact.
// head-to-platter contact…A laptop knocked while restarting, a grinding drive, and a series of remedies that each made it worse. Why grinding ends all further attempts.
// device enumerating without…A portable drive listed in Device Manager, absent from the desktop, and showing the wrong colour. Why the indicator is worth reporting.
// head assembly failing to…A portable drive whose light behaves normally while the drive clicks. What separates a click from a beep, and why the light is not the reassurance it seems.
// drive repeatedly attempting…A drive that enumerates, flashes continuously and never presents its contents, with a possible drop behind it. What continuous activity actually indicates.
// head assembly failure —…Twenty years of documents on a drive that clicked once and was stopped immediately. An honest framework for the question everyone asks first.
// suspected connector or joint…A drive with what looks like a loose connection, and the instinct that makes it worse. What a faulty connection really means and how to test it safely.
// cracked connector or internal…A drive that worked only while held at an angle and now does not work at all. What position-dependent recognition means, and why the habit made it worse.
// readiness sequence attempted and…A drive whose light burns steadily for a couple of minutes and then gives up. Why a timed sequence is more informative than a dead one.
// combined impact and compression…A drive that took an impact and then a crushing force. Two different kinds of damage in one accident, and why the case must not be bent back.
// impact damage sustained with…A console drive that fell while in use, responded once on restart, and has done nothing since. Why the first attempt after a fall is the best one.
// mechanical start failure…A drive that beeped, vanished, appeared once more and then stopped. Why an intermittent early stage is a window rather than a reprieve.
// impact damage to the mechanism —…A drive dropped onto a soft surface that no longer works. Why what it landed on matters far less than people assume.
// impact damage sustained with…A student filmmaker's entire final-year footage on a drive that slipped off the desk while editing. The technical position, and the call to make today.
// connector or joint failure at…A loose connector, a well-researched plan to bypass it, and the reason that plan fails on many portable drives. Plus what a data check can tell you.
// post-impact damage producing…A dropped drive that demands formatting on one attempt and reports a parameter error on another. Why getting both is more informative than either.
// start resistance followed by…A drive making both sounds, visible as a device and absent from the file manager. What each noise means and why hearing both narrows it.
// mechanical failure with no…A second drive failed with noises, and the owner's next move was to protect the one that still worked. The right instinct at exactly the right moment.
// impact damage sustained with…A dropped drive with a terabyte on it and only a few recent files needed. Why naming that changes the work, the risk and the price.
// impact damage with a component…A school's external drive with a part loose inside the casing. Why the rattle is the most urgent symptom there is, and why not to shake it.
All the lights, the sound of spinning, and then silence where the drive should appear. What the quiet part of a start-up is, and where his stops.
// two independent faults requiring…Two failed externals, a customer-supplied drive to receive everything, and one assumption worth examining before any figure is agreed.
// failure to report geometry —…Unknown, uninitialised, and reporting no size whatsoever. Why a missing capacity is a different fault from unallocated space, and a better clue.
// drive stalling on reads long…A stop error and a restart every time the drive is accessed. Why the crash is the drive's symptom rather than the computer's fault.
// legacy media with dormancy…Two decades-old machines, photographs to rescue, and a Mac and phone to use them on. The question nobody asks: what will the data actually arrive on?
// motor or head start failure —…An old drive that beeps, already replaced, and an owner asking whether the data is worth pursuing. An honest framework for deciding, either way.
// progressive media degradation —…Days of slowdown, a window used to save the smaller files, and then nothing. Why the small ones copied and the large ones did not, and what wore it out.
// readable metadata over…The folder tree shows perfectly, nothing will copy, and the drive is making a sound. Why the noise turns a patient problem into an urgent one.
// excessive current draw during…A drive that starts, gathers speed, and shuts off after a few seconds with a faint binding sound. What that pattern says about current and bearings.
// progressive media degradation…An export that crashed the application, then the file manager, then the machine. Why a long export is the hardest thing you ever ask a drive to do.
// failure to reach readiness with…A drive that powers, attempts to start, fails, and tries again — seen on every machine and a television too. What the repeating cycle is costing.
// severe read degradation at media…Seven minutes to open a folder, 900GB still readable, and an owner who wants a copy made now. The right instinct, and why consumer cloning tools fail.
// undetermined at enquiry —…A laptop drive removed and unresponsive, with a request for photographs and video alone. Why naming your priority genuinely changes how the job is done.
// self-reported drive fault…A drive that failed with no notice, and an event log showing the machine had known for three hours. Where those warnings go, and why nobody sees them.
// read failures with escalating…A drive Windows recognises that takes forever to open and drags the entire machine down. Why one failing device degrades a whole system.
// readiness or interfacing failure…An engineer confirmed the drive spins normally and is not clicking, and still could not recover it. What spinning proves, and what it does not.
// spindle or motor obstruction…A very large drive dropped and now buzzing rather than clicking. What buzzing indicates, and why platter count changes the calculation.
// read failures with escalating…A repair tool stalled just short of finishing and a drive showing full activity with no throughput. Two symptoms that describe the same thing.
// progressive read degradation…A drive that stalled repeatedly during a copy, made one noise, and has not been recognised since. Reading a failure that announced itself in stages.
// head assembly failure on both…A pair of drives from different makers that failed the same way, and a request to repair them just long enough. Why that is not how it works.
// head unload or park mechanism…A six-year-old internal drive that produces one dull sound each time the machine starts and is no longer detected. What a single clunk describes.
// localised unreadable regions…A drive that reads normally for seconds and then locks up everything touching it. Why the window is real, and the worst way to spend it.
// to be distinguished between…A bare internal drive reported as not powering up. Why that is usually inferred rather than observed, and what the difference changes.
// enclosure-dependent presentation…A 3TB drive that worked in its case and became unreadable once removed. Two reasons that happens, and why putting it back is the answer.
// no fault attributable to the…An old iMac disposed of years ago with its hard drive deliberately saved. Why that was the right thing to keep, and how such a drive is read.
// host failures with storage…Two replaced laptops kept for their files, both dead when the time came. And why one machine's error message is not about its drive at all.
An ultra-compact stick that has failed with files still on it. Why the smallest sticks work hardest, and what an internal chip fault actually means.
// ssd self-reporting failure while…A backup image started the night it was already too late, a drive that fails its self-check, and an owner who has his recovery key. What each of those means.
// drive-side failure with…An external SSD invisible on a Mac, with the caddy, cable and power already ruled out by substitution. What that eliminates, and what remains.
// deliberate reimage on…A machine reimaged to its base build, taking the original partitions with it. Why solid-state storage makes this much harder than the same event on a disk.
// filesystem or partition damage…A stick demanding a format, software bought to fix it, and a confusing pile of files that will not open. What those strange files actually are.
// controller failure most likely,…A 1GB stick that worked until recently and now works nowhere. What age genuinely does to flash memory, and why old sticks are not archives.
// interrupted write leaving filing…A system crash during a large save, a stick that chimes but never appears, and no physical damage. Why the interrupted write is the whole story.
// mechanical stress to the…Course notes on a stick that was bent while plugged in. Why bending is worse than it looks, and why straightening it is the thing not to do.
// controller-level failure with no…An SSD that no computer will acknowledge, and a well-meant diagnosis based on how hard drives behave. Why solid-state failure looks completely different.
// identification succeeding while…A drive the firmware always sees and no operating system can address, across Windows, Linux and console tools. What that gap describes precisely.
// deletion on trim-enabled storage…A deleted work folder, recovery software run by an IT team, and results described as encrypted. Two very different explanations, and how to tell them apart.
// excessive current draw…A stick no computer will see that becomes hot whenever it is connected. Why heat is the one symptom that means unplug it immediately.
// encryption sealed to the…An encrypted drive that unlocks only in the machine it came from, and a machine whose screen has died. Why his research was right and what follows.
// interrupted flush and close —…A stick ejected properly and pulled a second too soon. Why the click starts a process rather than finishing one, and what the wait is for.
// device-bound encryption with key…Videos moved onto a card that the handset had encrypted, and which will not play after decryption. What that setting does and where the key lives.
// early-life controller failure…An NVMe drive that failed within two months, taking a child's saved games with it. Where the saves may also live, and the warranty trap.
// controller failure progressing…A portable SSD invisible to a Mac while identical drives work on the same cables and ports. The cleanest elimination an owner can perform.
// intermittent access with…A stick a shop declared corrupted, prompting to format, which opened once on a different computer. Why that single success settles the question.
One picture deleted in-camera by mistake. Why a single photograph follows exactly the same rules as a whole card, and why the clock matters more.
// directory metadata readable over…Six hundred files listed perfectly with correct dates, all opening blank. Why the listing and the content are two different reads, and what that means.
// filesystem or partition damage…The prompt appeared, they cancelled, and now the photographs are unreachable. Why cancelling was the single best decision available to them.
// physical damage to a monolithic…Holiday photographs on a card whose casing was damaged. Why the casing is the card, what decides the outcome, and what a successful recovery costs.
// folder structure or filesystem…A card the camera reports as empty while the pictures are still on it. Why a camera only looks in one place, and what to check before assuming loss.
// controller failure with total…A card that failed halfway through a download and is now refused by three devices. Why transfers find weaknesses that shooting never does.
// controller failure with no…A card no reader will see and the camera itself refuses to format. Why failing to format is informative, and why it is the reason the photographs survive.
// early-life failure with…A holiday's footage lost on equipment bought days earlier. Why new is not the same as reliable, and what placeholders on the camera actually mean.
// partial physical overwrite —…Navigation software downloaded onto a memory card instead of onto the device. A genuine overwrite, and the honest arithmetic of what survives.
// repeated deletion and reuse —…Four thousand photographs taken over a decade on one card, deleted repeatedly whenever it filled. The honest answer about what reuse leaves behind.
// partition or filesystem…A microSD that announced itself removed while the phone lay untouched on a desk after an update, and now shows as unallocated. What that sequence means.
// controller failure with total…A card no computer and no camera will acknowledge, across three operating systems. What a complete elimination buys you, and why stopping is the right call.
// in-camera quick format — index…A work card formatted in-camera by mistake, and an owner who found recovery software and chose not to risk it. Both instincts were right.
// partial physical overwrite of…Clips recovered from a formatted card that play muffled audio, white noise and no image. What that specific combination of symptoms describes.
// partial overwrite by loop…A camera connected to a computer that powered up and resumed recording. Why the file kept its old timestamp and showed the wrong footage.
// directory structures lost or…A card reporting thirty gigabytes used while every tool finds no files. Why that combination is good news, and the one check that could change it.
// controller responding partially…A card that freezes the tools meant to inspect it, across several readers and machines. Why hanging is a specific symptom rather than a general one.
// directory structures readable…Images missing from a camera and a card, with a single picture briefly reappearing. Why intermittent visibility says the photographs are still there.
// filesystem structures left…A card removed from a phone without unmounting, now unreadable. Why phones are riskier than computers for this, and what it did.
// filing structure altered or…A card that worked in a camera until it was put into something else. Why the devices you insert a card into are not passive readers.
// physical damage to a monolithic…A card with its shell broken open and the chip exposed. Why there is no temporary repair, and what the real route to the photographs is.
// directory metadata readable over…Files that copy across with correct names and display nothing, and a recovery app that did not help. Why an app was never going to.
// controller responding partially…A card that is ignored by laptops and locks up the camera it came from. Why crashing a device points somewhere better than damaged contacts.
// controller responding partially…A card stuck perpetually at initialising, with a repair tool already run against it. What that probably did, and why the answer is reassuring.
// quick format with content intact…A formatted camera card where the footage is visible to tools and will not rebuild into playable files. Why fragmentation is the whole problem.
// controller failure with no…A card that produces no response whatsoever when inserted. Why total silence points somewhere better than it feels, and why software could not help.
// failure surfacing under…A card that worked yesterday and threw an access error mid-copy this morning. Why failing during a transfer is a specific and hopeful finding.
// early-life failure with…A card bought new, formatted in the camera, and declared corrupt hours later with a wedding on it. Why new is not safe, and what the scans cost.
// filing structures unreadable to…A camera rediscovered with a son's birth photographs still on it, reporting corruption. Why the camera's verdict is not the last word.
// controller failure with no…A microSD from an old handset, unrecognised everywhere, a decade unpowered. What age does to flash, and why older cards hold up better.
// filesystem structures unreadable…A phone reporting a card as unsupported and offering to set it up. Why that wording misleads twice, and what it will actually do.
A replacement laptop approved, the old one kept, and only the drive coming back. What that drive can and cannot give you, and why software is not on it.
// boot failure of undetermined…A Mac that will not start, a request to grab the data and reset it, and a screen question. Why the order of those two jobs is the whole answer.
// machine-side failure with…A Mac written off and a straightforward question about price. Why the machine's year sets the figure far more than how broken it is.
// machine-side failure with…An owner offering to remove the blade module himself before bringing it in. Genuinely helpful, with two cautions and one thing not to buy.
// two independent faults —…An iMac that lost its own drive during an OS update, and a backup appliance flashing amber on the same day. Two devices, two jobs, one order to do them in.
// reported storage-memory fault…A Mac that shut down normally and never woke, and a repair centre's verdict on the memory chip. Two meanings of that phrase, and how to tell which.
// undetermined — enclosure…A Mac blade module removed and tried in a generic USB enclosure without success. Why that test cannot conclude what people think it concludes.
// display illumination failure…A laptop unused for a year because the screen went dark. Why a backlight failure leaves a working machine, and the torch test that proves it.
// logical volume spanning two…A healthy SSD, a failing hard disk, and one volume spread across both. Why neither half is usable alone and what that means for the recovery.
// board-side failure on a machine…A Mac that will not start and a verdict of impossible. What is true in that, what is overstated, and the repair that would make it true.
// host failure with storage…An all-in-one that will not power up, with the drive sealed behind a bonded display. Why removing it is a job rather than a step.
// filesystem damage over…A crashed Mac whose disk appears on another machine and refuses to open. Why that combination proves the hardware and locates the fault.
// to be established between…A drive that had always worked, plugged into a new machine and suddenly unrecognised. Why a newer operating system can stop reading an older drive.
// board-side failure following an…A Mac that died overnight after an update, and a recovery attempt that offers two options. One reinstalls the firmware; the other erases the drive.
// board-side failure on a machine…Critical files on a Bootcamp partition inside a Mac that will not power on. Why the Windows side is behind the same encryption as everything else.
// no bootable system located —…A Mac showing a flashing question mark folder. What that symbol actually reports, and why it is about booting rather than about your files.
// filesystem damage over…A Time Machine volume recognised by Disk Utility and refusing to open. The first question to ask, and why backup volumes are harder to rebuild.
A mirrored pair that fell together and both failed. Why redundancy does not survive a single event, and why two damaged copies still beat one.
// array degradation progressing…A network drive showing a warning light, an array error in the logs, and a replacement disk bought but never fitted. The window seen and not taken.
// quick format over an array…A dual-drive external set to RAID, formatted by mistake, holding artwork. Why one drive letter over two disks changes what a format actually did.
// pool coherence lost through…An enterprise pool that lost coherence after an office move, with drives possibly misconnected. Why ZFS refusing is honest, and what not to run.
// array or partition structures…A Mac-formatted array connected to a Windows machine by mistake, and then invisible to the Mac. What Windows does uninvited, and why one line matters.
// array metadata destroyed by…A RAID 5 that lost two disks, then had a fresh array created on top of it. Why imaging first saved this, and how original geometry is derived.
// correlated failure across…Two network storage units mirroring one another, and both failed. Why replication is not a backup, and why supplying both units helps.
// single-disk failure with no…A single-disk network drive that failed with years of photographs and music on it. Why owning a NAS is not the same as having redundancy.
Invisible on one Mac and greyed out on another, with the disk audibly spinning. Why greyed out is a specific state rather than a failure.
// quick format with partition…Making a Windows recovery drive wiped an entire portable disk, partitions and all. Why the warning is easy to miss, and what actually survives.
// partition loss with localised…Unreadable sectors, a lost partition, and a requirement that names and structure survive. Why that specification decides the method rather than the price.
// progressive filesystem or…Files disappeared first and the drive followed, yet it still shows up on another laptop. Why that order and that detail together are good news.
// read-integrity failure — data…A drive reporting that its own data failed a checksum. What that message means precisely, the one free check worth doing, and the tool to avoid.
// filesystem structure damage over…A manufacturer's support team explained filesystem corruption accurately. What their answer gets right, and the one thing it does not address.
// volume claimed by an operating…Not enough space internally, so the installer offered the external drive and she accepted. What that did to the data on it, and what to stop doing now.
// filesystem or partition damage…Two descriptions that cannot both be true at once. Which one is actually happening decides everything, and telling them apart takes one look.
// primary filesystem index damaged…A drive where recent files have vanished and the contents look years out of date. Why that specific symptom points somewhere precise and hopeful.
// historic file loss of…A wedding video missing from one of two drives, with no idea when it went. Why you should hope it was on the older, slower one.
// unfinalised media container —…A long voice memo the right size that will not play, lost to a power cut mid-recording. Why the index is written last, and how the file is repaired.
// no device fault — unsaved work…A hundred and twenty pages left open for a month with autosave off, gone after a restart. Where the traces live, and the honest limit if none were written.
// partition table entry damage —…A two-partition drive where one opens normally and the other has vanished. Why that localises the fault, and the repair that would lose both.
// multiple independent sources…Deleted from a computer, cleared from a drive that was then dismantled, and a card someone says they wiped. Which source to try first.
// device failing to complete…A drive throwing numbered Windows errors that the internet fixes with driver advice. What those codes actually describe, and why reinstalling won't help.
// volume-level failure over a…A drive Windows lists as a disk and refuses to open as a drive. Why that gap is narrower than it looks, and what the listing itself tells you.
// read failure at device level —…A drive reported as having lost everything alongside a hardware error. Why nothing has been removed, and why the distinction changes what to do.
// filesystem directory unreadable…A drive that lost its own name, shows as full in properties, and will not open. Why both of those observations are more encouraging than they sound.
// not a deletion — folder…Recovery scans that returned every other deleted item and not the missing folder. Why that absence is evidence, and what to do instead of recovering.
// localised read failure on a…A video job where some files will not open and recovery software cannot see them. Why his own diagnosis was exactly right, and what actually helps.
// read failure beneath an…A BitLocker volume with the key available and read errors underneath it. Why the image must come before the decryption, and what a bad sector costs.
// read failure surfacing under…A machine stuck at the login screen, forced off, and reporting a drive failure since. Why nothing has been wiped, and what the hang really meant.
// filesystem structures unreadable…A card described as converted to RAW, and an owner who refused to format it. Why nothing converted anything, and why his instinct was right.
A rugged drive that met water, a flickering light, and a career's work inside. What the resistance rating actually covers, and where water gets in.
// liquid damage with conductive…A substantial amount of tea and a machine that is now dead. Why what was dissolved in the liquid matters more than how much of it there was.
// electrical damage from supply…A drive killed by an ageing power supply rather than by anything of its own. Why storage is the usual casualty, and the machine not to test it in.
// over-voltage damage from…Two of three drives dead after a cable from a different modular power supply was used. Why those cables are not interchangeable, and what it does.
// input-device failure over a…A spill that destroyed a keyboard and trackpad while the Mac itself ran perfectly. The free thing to try first, and why a second spill mattered.
// fresh liquid ingress with…A spill that happened hours ago rather than weeks. The one situation where speed genuinely changes the outcome, and the four things not to do.
// liquid contamination with…A drink spilt over a drive, a night in rice, and a squeal on the first connection. Two mistakes in sequence, and which one did the damage.
An honest confession about taking a drive to a computer shop. How a bench establishes what a previous attempt did, and why disclosure helps you.
// output padded across unreadable…Files recovered by a high-street shop and handed back unopenable. Why they cannot be repaired, and why the only route runs back to the source.
// two independent faults — one…One drive opened by a colleague and never reassembled, another with its connector snapped off. What years of exposure does, and which to prioritise.
// media degradation with…Four tests passed, one failed, and a conclusion of media corruption. What each stage actually checks, and the question the report does not answer.
// incomplete copies produced from…Video files that copied but will not open, a failed conversion, and a verdict of no data. The question worth asking: which object was actually examined?
// reported memory-level…A second opinion on a verdict that may well be correct. What NAND degradation actually is, why it is a genuine wall, and what still deserves checking.
// controller-level failure with no…An IT provider relaying a client requirement no bench can promise. How to handle absolute expectations honestly, before the work rather than after.
A drive left at reception and a fair question about what happens next. The stages, the realistic timings, and where free diagnosis does not apply.
// undetermined between host…A broken machine, a friend who tried, and years of photographs of a child. Why the job she has been braced for is not the job she actually needs.
// no device fault — credentials…A former employer's laptop locked from a distance, and a long access code demanded. Who holds that key, and why the route runs through them.
// undetermined at enquiry —…A sensible question before dropping a drive off. What is supplied, what to bring, and why a memory stick is usually the wrong destination for a recovery.
// two independent faults requiring…Two failed devices, two honest guesses, and an owner who stopped before experimenting. Why that instinct is worth more than any technical knowledge.
// image file present but its…A disk image made as a safety copy, never opened since, now refusing to mount. What the message means, and why an untested backup is only a hypothesis.
// not applicable — custody and…A drive handed to a drop-off point, a promised call that did not come, and a holiday closure. What paperwork should travel with a device, and what to ask.
// undetermined pending…A recovery quoted at one figure and then at a much higher one, plus a friend's verdict on head damage. How to compare quotes and weigh an informal diagnosis.
// graphics or mainboard failure…A display that broke up with coloured artefacts and a burst of noise, then a black screen. Why that combination points away from the drive entirely.
// no device fault — file-level…Photographs encrypted by a Windows setting nobody remembers choosing, thumbnails still visible, and a password recalled a decade later. What is still needed.
// undetermined at enquiry —…A drive that failed days before a deadline, with a course at stake. The parallel track that matters more than the recovery, and what to do today.
// legacy media requiring…A twenty-year-old laptop drive and two pre-smartphone handsets. Why the old phones are often easier to recover from than a modern one would be.
// likely host or operating system…A PC that powers but will not boot, photographs that would be nice to have, and a drive that is probably fine. When specialist recovery is the wrong purchase.
// undetermined — connector fault…A customer saying plainly that nothing on the machine is critical and price will decide. Why that is a reasonable position and how to price it honestly.
// undetermined between…A company laptop returned with a new account and the original data gone. What likely happened, why the storage type decides the odds, and what to establish.
// liquid damage with corrosion…An insurer replacing a water-damaged laptop and holding the drive. Why the urgent step here is administrative rather than technical.
// undetermined — listing…A reasonable request for a file listing before committing to a recovery. When that can be provided, when it cannot, and why the answer differs.
// not a fault — forensic…A device disclosed in live legal proceedings and a request for full forensic examination. Why it should be instructed through a solicitor.
// undetermined — logical,…A student on a budget with documents on a failed stick. The three fault tiers that decide the figure, and why capacity is not one of them.
// not applicable — communication…A card delivered to a lab, a quoted turnaround passed, and no word. What a customer should expect, and why silence is a process failure.
// platter stack separated with…Platters removed from a drive and scratched, with a request to list what is on them. The hardest answer in this archive, given plainly.
// undetermined — spanning external…A fair question about pricing a dead drive from a description. Why the same three words span the cheapest and most expensive work in the trade.
// to be established by assessment…A sensible offer to provide the destination media for a recovery. The answer is yes, with three caveats that decide whether it helps.
// flash device failure —…Years of tapes and discs digitised by a company and delivered on a single memory stick that failed. Where the real answer probably lies.
// controller-level failure with no…A customer who named his fallback before the work began. Why that single sentence is the most useful thing in a recovery enquiry.
// system volume or boot failure —…A self-employed person whose only machine will not load its system. Why the data and the working-again problem are separate, and which comes first.
Case 1000: eleven months of being told his data could not be saved, on a machine whose drive simply lifts out. Why nobody told him.
// progressive media degradation…Case 850: a check disk crawling at a sector every five seconds, a snapped connector, and a backup covering everything except the thesis.
// post-dormancy mechanical failure…Case 900: a dormant laptop that booted, and died in the time it took to fetch a cable. The one boot you get, and why sequence decides everything.
// no device fault — an authority,…Case 950: an estate asked for imaging before access on an encrypted machine holding a scholar's unpublished work. The doctrine the archive had not stated.
Details are anonymised and identifying specifics changed; the technical patterns are exactly as the bench sees them, week in, week out. No case file is a guarantee — every drive earns its own diagnosis — but if you recognise your symptom above, you’re reading the most likely shape of your own job, including the part where it works out.
The free diagnostic writes the first page: what failed, what’s recoverable, the fixed figure. Glasgow recovery case files all end the same way — with the data going home.