Every case file here is a real job off our own bench: what arrived, what had failed, how the recovery ran, and what went home. Eleven files are live below, rewritten properly from the bench archive — and more join them as the archive gives them up.
A three-platform elimination with the evidence attached: his 2TB portable drive enumerates everywhere.
His enquiry read the situation almost perfectly before it arrived. The 2TB LaCie Rugged Mini.
A charming, precise enquiry: an old iPod that still lights up when connected to mains power — but its buttons no longer work and no MacBook will recognise it.
An enquiry written between flights: a sports-media professional working overseas, home for a short window, one external drive beeping instead of mounting.
A dropped portable drive that still browses but stalls on every copy: why partial function is a clock, and how 500GB of photos were imaged out.
An owner who correctly diagnosed stuck heads and asked to drop the drive in. Why it must not be powered again, how to transport it, and the terms.
A dead 2TB drive holding essential coursework, and an owner who cannot spend much. How to find out what it needs without risking anything.
A quiet constant scratching, then a sharp loud one. Of all the sounds a drive makes, this is the one that means unplug it immediately.
An impact-damaged portable drive and a well-specified enquiry. What expedited service actually buys, what flat-file delivery means, and how the terms work.
A weird noise, then the drive vanished. Why that order of events matters, what she had already ruled out, and why it must stay unplugged.
A drive only months old that started beeping and will not open. Why new drives fail too, and why claiming the warranty first would cost the data permanently.
Dropped, then plugged in to check, and it clicked. What the first ten minutes after a drop decide, and why the checking is the expensive part.
A drive that had started to beep and no longer appears. Why the word started matters, what the tone is, and why each connection makes it worse.
Pushed off a desk, and now it spins up before it starts clicking. Why that order localises the damage, and what showing in devices means.
A clicking drive, a complete set of tests already done, and a question containing one wrong assumption. Broken and lost are not the same thing.
Her enquiry captured, in one frustrated paragraph, a contradiction that stalls thousands of owners: the machine's verdicts didn't agree with each other.
The patient: an aging Hitachi USB external drive, no longer recognised anywhere. His elimination: different USB cables tried.
His report described, with unusual clarity, a drive negotiating its own decline. The 750GB external "will not mount on my MacBook.
A short enquiry with a distinctive symptom: her Toshiba external drive mounts wherever it's plugged in.
A tentative, self-aware enquiry about a very old wound: a drive dropped in 2010 that never spun properly again.
A media hoarder's confession in three acts: the 14TB external dropped; the endless scan-for-errors that never finished; and the shucking attempt.
His enquiry was one urgent line with a diagnosis already aboard: "Seagate 1TB external HDD corrupted.
A methodical report of a dignified disappearance: his 9-year-old WD Black 2TB desktop drive vanished from the BIOS of every computer he tried.
Some enquiries are three lines because three lines is honestly all an owner can say: "HDD won't be recognised anymore. Also tried in a dock with no luck.
Two sentences, and the whole shape of a working photographer's nightmare: "I have a Toshiba hard drive, and suddenly a few weeks ago.
A terse, complete brief: a Seagate 2TB, physically damaged, unable to connect, photographs wanted.
His enquiry read like tidy bench notes, and it earns the comparative decode it accidentally set up.
A conscientious report of the full liturgy: the 5TB WD external stopped reading on macOS, and he tried resetting, dismounting and remounting.
A practical, modest ask: the old hard drive keeps disconnecting, a new SSD is already installed, and all he needs are some video files off the old disk.
An unusually well-handled enquiry: his 2TB G-Technology drive stopped being recognised by his Mac, and rather than guessing, he asked the manufacturer.
A 6TB G-Drive that wouldn't start, revived by a substituted power adapter — and everything since has been the drive telling him to stop.
An industrial case with a wince in the middle: a 40GB drive from a CNC machine's control PC died — spinning, but with heads that never move.
A drive whose light comes on but shows no folders: the visibility ladder decoded, what it means, and how the data came back. Free assessment, fixed quote.
A 4TB external drive with spinning platters that no computer or dock will recognise: why spinning is not readiness, and how the data came back.
A drive that vanished from the desktop and stayed invisible across leads and computers: the elimination decoded, and why repair and recovery differ.
I would like to know what is on it. How a dormant drive is inventoried before any commitment, what years in a drawer change, and the answer he got.
A donor board fitted to a matching drive and still nothing. Why the board alone is never enough, what the chip holds, and how the 2TB was recovered.
A 2014 drive and a 2002 one, recovered together. What two decades change about interfaces, donors and handling, and which was easier.
A boot drive that vanished from the BIOS on two machines while still spinning. Why BIOS invisibility is the most definitive symptom there is.
Slow to appear, then vanishing, then a light and nothing else. Seven years of family photographs behind a three-stage decline, and what each stage meant.
A 4TB desktop drive pulled to the floor, now unseen and making an unhealthy noise. Why desktop drives fare worse in a fall, and what the noise decides.
The connector broke clean off the drive. Why a snapped port is not always a simple repair, and why removing the disk can make things worse rather than better.
Family videos behind a broken connector, and a fair question about what recovery delivers. What you get back, on what media, and why sizes differ.
A drive listed among devices, absent as a disk, sounding normal. What that split means, and a straight answer on charging if nothing comes back.
No noise, no connection, no recognition at all. Why total silence is a different fault from a noisy drive, and in one important respect a more hopeful one.
A salvaged internal drive and a plan to plug it into a working PC. Why that is the riskiest way to read it, and what to do instead.
A 2TB drive that started clicking and became inaccessible, with one directory that matters most. Whether priorities can be honoured, and when they cannot.
The computer died, the drive came out, and the photographs were never backed up. Why a failed PC often means a perfectly healthy disk.
She was told her drive had suffered stiction and wanted a price. What the word actually describes, why powering it up is the danger, and how it is priced.
His own diagnosis offered two possibilities, and they sit at opposite ends of the price range. How the two are told apart before anything is opened.
It used to light up when connected and now it does not, and no laptop will read it. Why a light that goes out points somewhere specific.
No drive icon on the desktop and no way in. Why the desktop is a display setting rather than a diagnosis, and the two places to look instead.
Spinning normally in a caddy and still invisible, with the owner's own diagnosis pointing at the controller. He was right, and here is what it means.
A 4TB drive with family photographs that will not start, and an owner asking where to send it. How to pack a failed drive so the journey costs nothing.
A parent's worst-case reading of a household accident: the laptop dropped with the USB stick in its port, the stick bashed, and.
A technically thoughtful enquiry that nearly diagnosed itself: a flash drive used read-only through an unpowered four-port hub suddenly showed empty mid-idle.
The enquiry was four lines of understated student anxiety: "My USB stick is slightly damaged so will no longer work in my PC.
A work USB stick, knocked while seated in the laptop's port and snapped across the top — not cleanly through, but enough that no computer recognises it.
A PC builder's tight corner, stated in two lines: the M.2 SSD no longer shows in BIOS or boots Windows, a warranty replacement is on its way.
A methodical elimination, properly reported: the laptop's 256GB M.2 NVMe SSD failed, was moved to a USB caddy.
His report was the restrained, careful kind, and its most important word was hiding mid-sentence. The drive: a 240GB SSD, used for data storage only.
The question arrives four years late and fully self-aware: a 250GB SSD that failed young — eleven months old, inside a warranty never claimed.
Her account is a two-day decline recorded with a teacher's precision. "Over the weekend I tried plugging my memory pen into my laptop.
Someone called his USB stick a hardware issue. In a device with no moving parts that covers three faults with three very different outcomes.
A phone flash drive that stopped opening in its app. Why the app is not the storage, and the free test worth running before anything else.
A non-responsive Surface, a repair declared impossible, and a numbered list of what mattered. Why that list changes the job.
An SSD that stopped dead with no warning and vanished from the BIOS on every port. Why health tools miss this, and what recovery involves.
A laptop whose storage was two small SSDs striped together. Why one module alone yields nothing usable, and how the photos were carved.
A memory stick whose light comes on while no computer will see it. Why the LED is wired to the power and not to the data, and how the files came back.
A one-line enquiry about a stick that will not appear. The five questions that turn it into a diagnosis, and the three levels of visibility on a Mac.
A stick that misbehaved for months before it failed, taking a timelapse with it. What flash warnings mean, and an honest answer on recovering all of it.
A stick that worked last month and now will not appear on a MacBook. Why Finder is a curated view rather than the truth, and the free checks that come first.
He looked into the connector, saw a contact folded over on itself, and proposed two solutions. Both were sensible, and one was nearly exactly right.
Nothing in Device Manager, nothing in Disk Management. Her elimination is complete, so here is exactly what chip-level recovery involves from there.
The connection chime plays and no drive appears. What the sound actually confirms, what it does not, and where the fault sits between the two.
A drive full of pictures connected to a new computer and declared corrupted. Why unreadable and corrupted are not the same, and the question to settle first.
Three tools defeated by one drive: it will not mount, First Aid fails and scanners cannot read it. Why that is a single finding rather than three faults.
A crash, a brief return to the password screen, then a drive the BIOS could no longer see. A failure caught in the act, and what that timeline reveals.
The Mac message with three buttons, one of which erases everything. What it actually means, which button to press, and why the stick is probably fine.
Two identical sticks bought together: one now demands formatting, the other holds her coursework. Why the healthy twin is both useful and a warning.
A photo import crashed partway, and the stick has been unreadable ever since. Where the imported files went, and why a move is riskier than a copy.
Coursework on a corrupted stick with deadlines through the month. The recovery matters, and so does the conversation to have with your university today.
A stick that is plugged in and asks for a disk, with childhood photographs on it. What that contradictory message actually reports, and where it leaves you.
An 8GB stick that does not respond, and a fair question about cost. Why capacity is almost irrelevant and what actually determines the figure.
A physically broken memory stick and a fair question about odds. Five ways they break, and why where the fracture runs decides everything.
A stick full of work resources that stopped without warning. Why suddenness points at one component, and why that is the more hopeful answer.
A stick constantly plugged in and out of a television now registers but refuses to open. Why a TV is not a neutral host, and what it has been writing.
A business laptop that will not start and a folder on the system drive that is needed. Why the machine and the drive are two separate questions.
Pulled from a laptop without ejecting and now unreadable. What eject actually does, and the extra thing an SSD is doing that a card is not.
A failed drive holding over a terabyte of photographs and video, and a replacement waiting to be claimed. Why the order of those two decides everything.
Invisible on one computer and visible but unopenable on another. Why two platforms disagreeing is a diagnosis rather than a puzzle.
A gentle question carrying years of resignation: a Kodak camera's memory card threw an error near the end of a holiday, demanded reformatting.
A precise commercial enquiry: three dashcam SD cards, all with corrupted files denying access.
A doubly sharp enquiry: two SD cards corrupting images in parallel — one living in a camera, one in a laptop.
A stick of photos from two cameras, corrupted after a failed eject — and a consumer recovery tool's strange half-result: every phone photo back.
A step-by-step escalation told with complete honesty: videos wouldn't finish downloading from the SD card, retries failed, rescue software ran.
A working photographer's worst small accident: the Lexar 64GB professional UHS-II card carrying video from a Sony mirrorless shoot, dropped on removal.
A card that carried a honeymoon for two days and then refused to give the photographs back.
The engine cut, the dashcam died mid-recording, and one clip will not open while every other file is fine. Why the file simply has no index.
A phone card that stopped reading overnight, with the laptop insisting no card is present. Why that means the controller has stopped.
A hairline crack across a camera card, spotted long after the trouble began. Why a partial crack still severs the card, and how the photos came back.
Around a hundred RAW files deleted from a camera card. What actually decides the odds, and an honest answer on software versus a service.
Photos opening as grey rectangles or with half the picture blank. What that pattern says about the damage, and how the originals came back.
A card that failed in a phone reader, then told the camera it could not be read. Why the camera is now the danger to the photographs.
The camera can just about show the pictures, but no computer will take them. Why a camera is more forgiving, and how the originals came back.
Delete all pressed by mistake, and the card taken out straight after. Why that instinct saved the photographs, and what a camera delete does.
A young family member erased the videos, and nobody is quite sure how. Why the answer to that question changes the odds, and how to ask it.
A long interview clip cut short by a low battery, a camera restore accepted, and the card showing empty. What the restore did, and what shooting on cost.
A phone card that failed, with photos and documents wanted back. The question worth answering first: how much of it was ever on the card at all.
A card the phone stopped reading and the computer calls faulty, with no visible damage. Why half-answering is its own fault, and the free test to run first.
A camera card retrieved from a dog and no longer readable. What chewing actually damages, the one question that decides the outcome, and what to bring.
A card that stopped mid-usage and is now refused by four devices. What suddenness indicates, and what getting old really means for flash.
A card formatted in the camera and then used again. Why the second recording decides everything, and what survives outside its footprint. upfront.
Footage needed for an insurance claim, lost by pulling the card from a laptop mid-write. What that does, and why the card must not go back in the camera.
A card that died mid-edit and is now refused by both the Mac and the camera. Why editing directly from a card is the underlying risk.
A capable owner who got 90% of the way there: the PCIe SSD extracted from a mid-2014 15-inch MacBook Pro Retina, a third-party blade enclosure purchased.
A 2018 MacBook Air that simply stopped, a suspected hardware fault, and a lot of important university notes inside.
Her enquiry was matter-of-fact and, read closely, more hopeful than she knew. "I'm a uni student and my laptop is preventing me from typing in my password.
A 2020 16-inch MacBook Pro with liquid damage and, per Apple, damage to the main board — and an owner hoping for both his data and his machine back.
He replaced his MacBook drive and lost his Office apps. Why installed programs cannot be transferred, and what should be moved across instead.
A forced shutdown, a flashing question mark, and a blade SSD silent in an adapter. Why fitting is not the same as speaking.
A document trashed by mistake and the trash emptied. Four places it may still exist on a Mac, and the honest difference an SSD makes to the odds.
A repairer diagnosed an electrical fault in the SSD and referred her on. Why the blade should be tested away from the machine before it is condemned.
Three beeps, repeating, and a Mac that will not start. That pattern is a diagnostic code, and it points somewhere other than your files.
A very old Mac that will not start in safe or recovery mode, with nothing backed up. Why its age is the best thing about the situation.
A modern Mac reaching recovery mode and no further, with water damage found. Why recovery mode working is meaningful, and the offer there to refuse.
A Mac working yesterday and showing a flashing folder today. What the symbol means, then the process step by step and what each stage costs.
The password is correct and the Mac refuses it. Why a damaged lock is a different problem from a lost key, and why that difference is hopeful.
A partial recovery that returned the files and left the pictures behind. Why photo libraries fail a migration when ordinary documents survive it.
A dead logic board on a machine whose storage is soldered to it. Why the board and the data are the same problem, and what that means for the price.
An IT team's honest account of a routine change with an unwanted consequence.
Five 3TB drives in RAID 5, a five-bay NAS whose main board no longer powers on.
One disk failed, the second is warning, and the array has no redundancy. Why the power cycle revealed rather than caused it, and why both must be imaged.
A server disk flagged as predicted to fail, not reading properly, and running hot when pulled. What that warning means and what must not happen next.
Six or seven disks from a server of twenty-five years ago, holding the family photographs. Why the missing controller does not matter, and what does.
The appliance will not power up and the manufacturer no longer supplies spares. Why a mirrored pair is the best possible news, and the filesystem catch.
A twin-drive desktop enclosure that has stopped powering up. Why the configuration question matters more than the fault, and the cheapest test first.
A two-bay NAS knocked over, one disk now clicking, and no redundancy in the configuration. An honest answer on what full recovery depends on.
A mirrored NAS rested for a fortnight and now invisible on the network. Why the appliance's own system lives on the disks, and what that implies.
Eight disks, an OS that will not start, and work files inside. Why a failed operating system says almost nothing about the array beneath it.
Eight disks reinitialised in error with eighteen terabytes inside. Why the unit must be powered down this minute, and what a resync would destroy.
A short, weighty enquiry from an employer: a member of staff has suddenly left, wiping his company laptop on the way out.
A practical enquiry in two halves: the technical (a laptop knocked hard near the drive, the drive moved to a caddy.
Windows reinstalled onto a failed drive brought the PC back and took the old files with it. What survives, what overwrites it, and how they came back.
A 2TB drive demanding a format, and a consumer scan that reached 1% in hours. Why the prompt must be refused, and how the data came back.
A specific Windows error, precisely read: why swapping the enclosure can make a healthy drive unreadable, and how a 500GB archive was recovered intact.
One tool reports the drive as normal, another calls it RAW, and reads keep failing. Why contradictory tools mean the answer is physical.
A fatal hardware error, then a repair scan that reached a third of the way in twenty hours. Why the slowness was the diagnosis, and why cancelling was right.
A 4TB portable that stopped reading after a routine copy. Why writing is when faults surface, and why the copy revealed rather than caused it.
The machine powered down during a Windows update and a data drive came back with a letter but no access. What that split means, and why not to run a repair.
He was patiently copying files off a failing drive to prevent further damage. The instinct was right and the method was making things worse.
Forty design files permanently deleted, then recovery software installed on the same machine. How much that costs you, and why stopping early mattered.
A company drive reset by a departing member of staff. Which reset option was chosen changes the odds completely, and here is how each one behaves.
Listed by name, powered, and refusing to open. Why being seen and named is genuinely good news, and the repair button to leave alone.
A decade of photographs behind a corrupted filesystem. What a recovery of that size actually returns, how it is checked, and what to ask for.
She cancelled a copy, the drive crashed, and it has not appeared since. What cancelling actually does, and why the eject failure is the real clue.
A scan that listed every file and could not open one of them. Why that is not a software failure but a map of exactly where the damage is.
A drive that will not initialise and shows no partitions at all. Why the map has been lost rather than the territory, and the offer that destroys it.
Visible in firmware and Device Manager, absent from Explorer, and reported unknown in Disk Management. What four levels of visibility tell you.
A client shoot gone from a session folder that is still there and empty. Why a surviving folder points somewhere specific, and where to look first.
Software that found everything, saved it, and produced files that will not open. Why they are the right size and unreadable, and what recovers the rest.
A short, sharp enquiry after a water spill: the MacBook Air won't turn on, the data is wanted, and the question is priced on a condition.
A desktop drive that will not take power at all: the three places the supply stops, why substituting an adapter is a hazard, and how the data came back.
A PC hard-reset mid-work and the drive stopped registering, taking a year of footage with it. What a reset does to a drive mid-write.
Liquid damage, a logic board written off, and a migration that crashed halfway. Why the storage cannot be removed, and how the exam material came back.
A spill, a dead MacBook, and weeks of failed attempts. Why every guide she found assumed a drive that this machine does not have, and what the real route is.
Water reached the board and corroded it, and the laptop is finished. Why corrosion is a board disease rather than a storage one, and what decides the route.
A portable drive plugged into the wrong socket on a television. What overvoltage actually destroys, why the light still works, and why the platters are fine.
A spill, a careful drying-out, and a machine that boots without seeing its drive. Why drying addresses one problem and leaves the worse one running.
A spill, a machine that will not start, and a manuscript with no copy. The honest position on Apple silicon, and the free places to look first.
A bruised arrival: his clicking drive, showing as unallocated space, went to a recovery firm who fitted four donor heads — destroyed, they said, in seconds.
A repair shop proved the drive was the fault and referred him on. What opening a drive actually means, and why most recoveries never need it.
A repairer replaced the storage chip and the laptop works again, but the data was on the chip he took out. The one question that now decides everything.
A backup drive that stopped registering, and the question nobody asks first. Where the original data went, and why a backup is so often the only copy.
Three consumer tools run on one card, and five corrupt files between them. Why the tools were not the problem, and what the corrupt output actually proved.
A dropped drive that a relative in the trade had already opened under filtered air. Whether a previous intervention counts against you, answered straight.
Donor heads fitted elsewhere, the service area still unreadable, and minimal platter damage. Why matched heads sometimes are not, and what that leaves.
A repair got the PC booting again, and days later the drive stopped being recognised. Why the fix bought time rather than solving anything.
Her message wasn't a fault report — it was the other kind of enquiry this archive takes seriously.
A dropped laptop, a 104GB SSD invisible in a caddy on a new machine, Windows 11, and the detail that outranks all the others.
Does a previous recovery attempt push the price up? An honest answer on what changes a quote, what does not, and why the figure is fixed before any work.
A non-booting drive, and an owner who wants it repaired if physical and recovered if not. How the two are told apart, and why the order is the same.
What sets the price of a head recovery, why no honest figure comes from a sentence, and why head damage is sometimes not the diagnosis.
A wallet file deleted years ago, missing from backups and from software scans. The honest odds, the places still worth searching, and one safety rule.
A drive used weekly for years that suddenly demands a password its owner never created. What that usually means, and the reset that would destroy everything.
She needed the projects and photographs but not the films. An honest answer about what selective recovery does and does not save you.
Two questions in one enquiry: a ten-year-old laptop drive that crashed after making noise, and whether locked phones can be recovered. Both answered straight.
Locked out of a Mac with disk encryption switched on and no original recovery key. Why generating a new key does not help, and what to do first.
She found her backup and no longer needed the recovery. What a laboratory does with drives left behind, how long they are kept, and how they are destroyed.
Two paragraphs of diagnostic language and a request for a quote. What those phrases actually mean, and what a report should tell you instead.
Footage from four months ago on a recorder that holds one month. Why overwritten is a different word from deleted, and why the answer is almost certainly no.
A straight question deserving a straight answer. The two fee structures, which one applies to your card, and what actually moves the price.
A dead machine holding other people's information. What a business should ask a recovery firm about confidentiality, handling and secure disposal.
The six hundred and fiftieth case file closes Volume Thirteen with a chain of institutions each doing its job properly.
An executor winding up her father's business, locked out of his Mac and three drives. Who is entitled to the data, and what authority cannot do.
Case 750: a wedding photographer whose drive has already had heads and platters replaced without success. Whether a third look holds any potential.
Case 800: thirteen years of design work behind a connector that tore away with pins attached. The four questions answered, and why he did everything right.
No client is ever identifiable — devices, faults and outcomes are real; names and details that could point at a person are not published. Each file covers the same ground: the arrival story, the diagnosis in plain language, the bench work that followed, and the honest result including anything that couldn’t be saved. Between them they answer the question every visitor is really asking — ‘has this lab seen a failure like mine?’ — and for a bench with two decades behind it, the answer is very nearly always yes. Beyond the files above, the process page shows how every one of them ran, and the reviews show how they ended.