In-depth write-ups of real recoveries and investigations — the diagnosis, the tools and exactly how each job was brought back. Most drives are imaged on our PC3000 and DeepSpar systems before any recovery begins. For shorter summaries, see our case studies.
A document library on a failing drive, and recovery software left running for two days. Why the scan rate is itself a diagnosis, and why to stop it.
A knocked drive that whirrs and beeps, and a diagnosis found online that is nearly right. What the beep actually is, and why the difference matters.
A bus-powered external drive that does nothing at all when connected. The free test worth running first, and why it fails more often than you would think.
A nearly new drive that beeps with no drop and nothing on it. Why new drives fail, and an honest answer to whether this is a simple fix.
A drive whose connector has failed while the disk still spins, and an owner asking whether to attempt it. An honest answer about doing it yourself.
A drive that failed partway through backing up, and now will not be recognised. The question worth asking before commissioning any recovery.
A drive that finally started clicking with no single incident behind it. Why cumulative handling is a real cause, and what it means for the odds.
An eleven-year-old drive with a failing connector that appears empty once removed from its case. Two reasons it looks blank, and neither is erasure.
A drive that worked in the morning, took a light knock at lunchtime and failed. Why gentle is enough when the drive is running.
A rugged portable drive that stopped while a film was streaming from it. Why sustained reading is when drives fail, and what the timing narrows.
A drive that developed a quiet beep while backing up photographs, with no drop anyone remembers. Why no incident is needed, and what the sound is.
A dropped drive that eventually mounts and then will not open its video files. Why ten minutes is a symptom rather than slowness.
A drive dropped from a desk that kept working for days and then began grinding. Why a delay does not mean the fall was harmless.
A drive that begins to spin up and never appears at all, not even as an unknown device. Why that particular absence points at power.
A backup drive that got audibly worse over twenty-four hours of retrieval attempts. What the change in sound means, and why use caused it.
A drive knocked off a chair that now rasps on power-up. What that sound is, why the height did not matter, and the one thing to stop.
A dropped portable drive where the port, not the mechanism, is damaged. Why it worked briefly afterwards, and what must not be discarded.
A work drive that buzzes and is not recognised by either machine it is tried on. Why testing twice already answered half the question.
A nearly empty drive that lists files and will not open them. Why how full a drive is changes the odds, and what to mention.
A drive that appears without a capacity while the file manager loads forever. Why those are one symptom, and why to unplug it now.
A dropped password-protected drive that authenticates and then stops responding. Why two layers are involved and only one has failed.
A drive absent from the computer that a recovery program can nonetheless scan. Why both things are true, and why stopping was right.
A drive pulled out mid-use that now spins without connecting. What ejecting actually protects, and what it does not explain.
Two separate external drives that stopped responding together. Why that is rarely coincidence, and what to identify before buying a replacement.
A drive demanding a format from an owner who read about it, worried, and stopped. Why restraint is a technique rather than an absence of one.
A drive from a decade ago that a new laptop cannot install the software to open. What that software actually did, and what it means now.
A drive listed in the system's device tree and absent from the desktop. Why those are different lists and what the gap identifies.
A drive holding music projects that spins without appearing. Why folder structure matters as much as the files for project-based work.
A drive that worked on one laptop, was plugged into a managed work machine, and then failed on both. What might have happened in between.
Client archives being moved to the cloud from a drive that keeps failing mid-transfer. Why bulk migration is the hardest load there is.
A drive listing everything and refusing to copy the files behind a deadline. Why the healthy majority should be copied first.
A drive left connected to a TV for months, power-cycled every time the set was switched off. Why that is hundreds of hard starts.
A drive spinning normally and ticking on a regular interval. Why the spacing of a sound tells you as much as the sound itself.
A drive that disconnected on its own a week before it failed. Why that was the warning and what it usually means.
A drive that looked present until it was asked to write. Why writing fails before reading, and what the discovery moment tells you.
An external drive whose light comes on while nothing turns. Why that light proves less than it seems, and what silence narrows it to.
Thirty-eight recordable discs being archived, and the ones from a single batch failing together. Why that pattern points at the dye rather than damage.
An owner offering to film the noise his drive makes. Why that is genuinely useful, and why repairing a drive and recovering data are different goals.
Old college drives that read perfectly on an older Windows PC and fail on newer machines. Why the machine that worked is the answer.
A large drive showing a tiny capacity and refusing to initialise. Why a wrong size is one of the most specific symptoms there is.
An owner who measured components and identified a suspect part. Why that instinct is right, and the one thing that must not be swapped.
A student machine from the nineties that still starts, holding a final-year project. Why this is a transfer problem rather than a recovery.
A drive listed in one Windows tool and absent from the other. Why those two lists mean different things, and what the gap identifies.
A mains-powered external drive that will not start, and an owner who has assumed the worst. Why the cheapest cause is the likeliest.
A data drive that vanished after a system update, and the one check that shows the update was not the cause.
A drive that mounts, shows its partitions, and fails about a minute later every time. Why that window is the whole recovery.
A drive no longer recognised, and an owner with a plausible theory that sits one layer too high. What being recognised actually requires.
An external drive whose activity light blinks continuously while no disk shows up. What that light is actually reporting.
A drive that stopped spinning after the wrong adapter was plugged into its enclosure. What that damages, and why the platters are usually fine.
A drive flagged by the manufacturer's own diagnostics that shows up only briefly in a dock. Why that verdict is worth trusting.
Several recovery packages that all find nothing except bad sectors. Why that is the software telling you it is the wrong tool.
A drive that announced its own imminent failure before stopping. What that warning is, and what to do the day you see it.
An owner who ran every published diagnostic and tested the drive in several machines. Why the eliminations are complete and testing now costs.
A drive opened and spun in ordinary room air, now showing a visible scratch. Why this must stop immediately and what the mark means.
A drive appearing as uninitialized and an owner who could not find a straight answer. The answer, and what 150,000 bad sectors mean.
Two drives removed from their cases and neither recognised through the same reader. Why the shared component is the suspect.
A drive that makes two clicks and powers itself down rather than clicking continuously. Why that difference is informative.
A powered desktop drive dropped from a shelf where the enclosure still runs but the drive shows nothing. Why that split is useful.
Two old laptop drives kept for family photographs, held back by a misunderstanding about compatibility. A free correction.
A drive board destroyed by a modular power supply mismatch, and an owner who bypassed the protection. Why that told him something useful.
An owner who compared his failing drive against a working one and found it sounded normal. Why that comparison is a real diagnostic.
An owner who shucked his drive and tested it natively before asking. Why that is the elimination most people skip, and its one risk.
An external solid-state drive that a Mac and a camera both stopped recognising. Why two unlike hosts agreeing is a stronger elimination than two computers.
A stick that produces the usual chime and never appears on screen. Why that sound proves more than most people realise, and where it stops.
A camera device with a broken port, and an owner who scoped the job precisely: extract the data, reassemble it, do not repair it. An honest answer.
A password-protected stick that stopped opening after an update, still reporting content inside. Where the data actually is, and what still works.
An SSD reporting almost no wear that will not boot, after three weeks of attempts. Why that number exonerates the memory and points elsewhere.
A customer who named his email and browser profiles as recovery priorities. Why that request is unusually well-informed and what most people forget.
A laptop being repaired this afternoon with the failed drive inside it. Why the urgent step is a sentence to the repairer, not a technical one.
A portable SSD formatted by accident where recovery tools returned nothing at all. Why not-overwritten is true and does not help.
A drive visible in Disk Utility where the repair tool fails partway. Why a repair that could not finish is better news than one that succeeded.
A flash drive written over by disk-imaging software aimed at the wrong device. What that actually overwrote, and why some of it usually survives.
An NVMe drive the system can see that will not return a single byte. Why identification and reading are separate, and where the fault sits.
A budget laptop whose 64GB storage is a chip on the mainboard. What that changes, and the one question that decides everything.
A card that fails partway through copying with a confusing error and then vanishes until reinserted. Why the message points the wrong way.
A solid-state drive demanding a format after working normally weeks earlier. Why refusing matters more on an SSD than anywhere else.
A dead ultrabook with storage soldered to the board, where repair is not worth it. Why the two costs are linked, and the lower bar that applies.
A dead computer with a system SSD and a separate data drive. Why treating it as one problem costs time, and which disk to read first.
A USB stick that cooked during a set and now heats up the moment it is connected. Why each attempt costs, and where the music is.
A physically damaged microSD that heats up on connection. Why there is no chip to lift off, and why the heat must stop first.
A work USB stick that enumerates and will not open after a host crash. Why that split is good news, and what not to let Windows do.
A solid-state drive that lost its directory, from an owner who stopped backing up because it had no moving parts. Why that reasoning fails.
A stick that disconnected in an expansion port and has not been seen since. Why hubs cause this, and the backup drive that arrived too late.
A laptop solid-state drive invisible to firmware, bootable media and reseating. Why those three eliminations point somewhere specific.
A failed boot drive left untouched because its owner fitted a new one. Why that single decision is the difference, and what was on it.
A card demanding a format that then refused to be formatted. Why the failure was lucky, and what it reveals about the fault.
A failed data drive that prevented the machine starting at all. Why a non-system drive can do that, and the free fix for the computer.
A dropped laptop that overheats and shuts down, briefly revived by chilling. Why cooling it is a mistake, and why it need not run at all.
A USB stick that powers up and is recognised by no computer, confirmed by an IT department. What the light proves and what it does not.
A drive that died suddenly and shows nothing through a USB caddy. Why the adapter is a variable worth eliminating before the drive.
A failed drive an owner is trying to initialise. Why that would have destroyed the data, and what the failure reveals about the fault.
A failed solid-state drive and a suggestion that the memory chips could simply be removed. Why that works on cards and rarely on an SSD.
A USB stick that crashes a computer, is invisible to another, and works perfectly in a printer. Why the printer succeeding is the key finding.
A solid-state drive removed mid-use that no longer appears anywhere, in either enclosure. What an unclean removal does and does not explain.
An encrypted drive whose password works and whose contents are unreachable. Why that means two separate layers, only one of them broken.
A high-capacity stick that overheats and drops out during large transfers. Why smaller batches did not help and what actually does.
A drive the computer switched off rather than failed to see. Why an active rejection is a different and more specific finding.
A stick the system sees intermittently, left powered in a port overnight. Why intermittency changes what you should do next.
A stick the system enumerates and then refuses to bring into service. What that specific message reports and where it places the fault.
An industrial logger flooded after vandalism, holding a few megabytes of readings that cannot be recorded again. Why small memory helps.
A camera card that came back unreadable after being used on someone else's computer. The free question to ask before anything technical.
A card that disconnected partway through an import and then imported nothing. Why the reader is the cheapest suspect and almost nobody checks it.
A camera that reformatted a card abroad, then a handful more frames taken before the loss was noticed. Why where they landed matters more than how many.
A memory card that failed in a phone, and a SIM that failed at the same time. Why two unrelated components failing together points at the handset.
A memory card that failed in normal use with nothing to explain it. What actually wears a card out, and why the phone is worth suspecting.
A formatted card shot over with new footage, and an owner asking about the remainder. Why this time the arithmetic genuinely works.
A Mac offering three buttons partway through a card transfer. What each one does, and why the owner picked the right one.
An SD card whose write-protect tab has broken away and which no longer reads. Why that tab is mechanical, and the free workaround.
A single action-camera file corrupted when recording stopped abruptly. Why the index is written last, and how the clip is rebuilt.
A card listing two hundred photographs that none of them will open. What a file that exists and fails actually means, and what survives.
A drone card erased in preparation for sale, with the footage still wanted. Why it comes back, and what that means for anything you sell.
A card that shows pictures in the camera and nothing on the phone. Why the card is fine, and four free things to try.
A transfer where the local copy was moved, the card was cleared, and the uploads turned out unreadable. Why the card is still the answer.
A card emptied by mistake and set aside untouched. Why this is the best position there is, and the one thing that keeps it that way.
A new card throwing an error in the camera and offering to format. Why refusing was right, and why new cards fail more than they should.
A card that stopped mid-recording and now makes the camera shut down when inserted. Why that risks the camera as well as the footage.
A card producing two different errors on different attempts. Why alternating messages mean intermittent detection, and what to stop.
A small, long-serving card that failed without warning in an old camera. Why flash ages even when it sits unused, and what to do about it.
A gallery that counted down while photographs disappeared. Why what she watched was the index being cleaned rather than files being deleted.
A card that failed in a handset which had been misbehaving for weeks. Why the phone is the suspect, and what not to put in it next.
A card where the oldest and newest photographs survive and a contiguous band in between has vanished. Why that pattern names its own cause.
A card that dropped out during an event, taking the day's photographs with it. Why the used space showing is the best sign there is.
A card that stopped working during a transfer through an inexpensive reader. Why the reader is a suspect and what the glitch was.
A memory card that lost almost all of its declared capacity after the phone was dropped. Why that number is a fallback rather than a measurement.
A shoot backup formatted for a borrowed Mac that now demands formatting at home. Why nothing is wrong and what accepting would cost.
A recovery that returned every filename and no working file. Why that combination has a specific cause, and the trade-off it forces.
A card that survived a smashed phone and was then bent in the reader meant to protect it. What physical deformation does to a card.
Primary research footage on a card that both the recorder and the computer refuse to read. Why doing nothing was the right instinct.
A professional video card dented by a dog and now unreadable everywhere. Why this class of card has a route a microSD does not.
A sealed camera that flooded on the last day of a holiday. Why the card must come out now and what not to do with it.
A decade-old card whose videos start, stop and pixelate. Why flash memory fades with time and what that means for anything archived on it.
A water-damaged Mac from a year when the range was split. Why the exact model decides whether the drive lifts out or the board is the only route.
A desktop Mac written off for a failed graphics card, with wedding photographs on it. Why that diagnosis says nothing at all about the data.
A Mac that froze and now shows no internal drive in Disk Utility. Why recovery mode makes that absence far more significant than it looks.
A liquid-damaged laptop quoted at more than it is worth. Why that figure says nothing about the data, and why time matters here.
A laptop that died suddenly, from an owner unsure it is worth recovering. An honest answer about cost for that generation.
A desktop hybrid volume that will not mount and cannot be repaired by the disk utility. Why it needs both halves, and what not to allow.
A laptop that loads to the end of its start-up bar and goes no further, while the disk utility still sees the drive. What that combination means.
An old desktop knocked while being moved, showing a question mark and failing repair attempts. Why the failed repair was the lucky part.
Three people checked a Mac drive and gave three answers. Why healthy hardware and an unreadable volume are entirely compatible.
A liquid-damaged laptop a repairer could not revive. Why the year it was made decides whether the storage can leave the board.
Two retired laptops, one with a trackpad pushed up from beneath. Why that is a safety matter before it is a recovery one.
A year of university work gone from a desktop after three months away. Why files that never existed have usually just moved.
A Mac that lists a drive in grey and refuses to mount it. Why that appearance is a precise finding rather than a vague one.
A dissertation writer who needs a handful of files from a laptop that died months ago. Why a small scope makes a small job.
A forgotten password on a machine too old to reach the reset servers. Why the account lock may not stand between you and the files.
A desktop showing a prohibitory symbol and an owner unsure what their backup actually holds. Why that is two questions, one answerable today.
An older laptop that stopped starting after a major system upgrade, with target disk mode also failing. What each failure narrows down.
A desktop that will not start, holding a photo library and editing catalogue. Why those must be recovered whole rather than as pictures.
A damaged volume that crashes the computer partway through every transfer. Why copying is the wrong tool and what to use instead.
A disk utility reporting a drive as non-bootable, and what that word actually measures. Two different questions about the same drive.
A production office finding two dead drives at once — one silent, one that runs for five seconds. Why those are unrelated and which is cheaper.
A network drive that is healthy and unreachable because there is no wired connection. Why this may not be a recovery job at all.
A drive taken out of a failed network appliance and shelved. Why it is still readable, and the prompt that would destroy it.
A network storage unit switched off deliberately for a router change that then refused to start. Why the power cycle is the event.
A four-disk array that lost two members, one of which returned after a cold restart. Why that returning disk is the whole case.
A machine doubling as a company server where the second drive failed. Why the working drive proves a lot, and what the mail files change.
Former array members repartitioned for reuse, taking the set down. Why a partition table is small, and what that means for the data.
A large array that lost two members and went offline. Why more disks never meant more tolerance, and what a rebuild really costs.
A network unit with two failed disks in a spanned rather than striped configuration. Why that is much better news than it sounds.
Array members kept after the computer that hosted them was scrapped. Why the disks still describe the set, and what must not be done.
A ten-year-old network array across two chassis that would not restart after routine cleaning. Why the shutdown is the event, and disk order.
A network array down after a power cut, and an owner told the disks cannot go in another machine. What that advice gets right and wrong.
A network drive with a broken casing and an owner asking for a replacement shell. Why the box is the least important part.
A network array run for months with a failed member removed. Why a degraded array is a silenced warning, and what to do now.
A two-bay mirrored unit inaccessible after one disk failed. Why each disk holds a complete copy, and where the fault probably is.
A network unit whose files were encrypted by an attack, with only the largest files untouched. Why a mirror did not help and where to look.
An array that took over a week to reconstruct and has cycled ever since. Why the rebuild duration was itself the warning.
A new disk that reported failed as soon as it was fitted, taking a second member with it. Why a brand-new drive failing rarely means a bad drive.
A network drive wiped by a remote command in a mass incident. Why a factory reset is not an erase, and the lesson underneath it.
An array in an error state that refuses to reconstruct automatically. Why that refusal is protective rather than a fault.
A laptop stuck for hours on a repair screen. Why that process is not passive, what it can do to a failing drive, and when to switch it off.
Photographs that copied across with the right size and will not open, after a transfer was interrupted. The question to ask before any recovery.
A business PC that has stopped working and keeps blue screening. Which causes involve the disk, and what to stop doing before anything else.
A pen drive returning one very specific Windows message. What that wording narrows it to, and the repair command that would make it worse.
A drive appearing as unknown and not initialised, with an owner afraid to press the button. Why that fear is exactly right.
An encryption setup interrupted partway, leaving a drive that unlocks with a password but has no working recovery key. What to do today.
A film dissertation on an exFAT drive that will no longer mount. Why that format fails this way, and what camera footage allows.
A deleted coursework file still appearing in the application. Why that listing proves nothing, and the free places to look first.
A drive erased to make it work with a new machine. Why the data is probably still there, and why the format was avoidable.
A laptop drive holding a phone backup, wanted for the pictures in it. Why a backup is a database and what to ask for instead.
A work card left partway through encryption and no longer showing its footage. Why the key belongs to your employer, not to you.
A conflict prompt answered wrongly, replacing a finished document with an old draft. Where versions survive, and why to hurry.
An old Mac drive that appears in Disk Management with no drive letter. Why nothing is wrong with it, and the prompt to refuse.
Production footage damaged while being offloaded from a recorder. Why the first question is where the original media is now.
An encrypted stick left half-converted when the process failed partway. Why both halves survive, and the host that should not have run it.
A user who saved to a network home drive for months while it silently stopped syncing. The one instruction for IT, before anything else.
Coursework lost to a single corrupted file, on a machine that has since been reset. What that pattern suggests and where to look now.
A data drive that started demanding a format after an operating system was reinstalled on a separate disk. What setup may have written where.
A boot repair that formatted the data drive and was followed by a full reinstallation. What survives two destructive steps in sequence.
A student who accepted a prompt to repair her USB stick and now cannot open anything. What the fix did and what to check first.
A laptop whose own diagnostic passed the hard disk and failed a memory module. Why that changes everything, including how to copy the data.
A deletion that recovery software could not find, on a drive nobody could finish scanning. Why the second fact explains the first.
A liquid spill followed by a machine reporting no boot device and scans that find no drive at all. Why the scanning advice could not work.
An encrypted work laptop drive where the recovery key was retrievable from the organisation's directory. What escrow looks like when it works.
A laptop reset in an attempt to fix it, on a drive that was physically failing. Why that was the worst available response, and what survives.
A disk whose partitions disappeared after a forced reboot. Why there is usually a second copy of the table, and what not to let anything write.
A manufacturer referral, a price beyond reach, and a claim that the drive needs opening. Two things worth checking before accepting either.
A drive assessed as functional with corrupted files and a recommendation to reformat. Why those statements pull against each other, and which to act on.
A formal evaluation report clearing the electronics and failing the surface scan. How to read it, and whether a second opinion is worth the delay.
A drive in poor condition that an unskilled attempt has made worse, handed on by someone who recognised their limit. What to preserve and report.
An IT department recommending a format on a drive that clicks and never mounts. Why those two things cannot both be addressed by the same remedy.
An owner who lifted the lid to check the heads, said so plainly, and had the contamination cleaned. Why the honesty was the useful part.
An owner who recovered most of a failing drive himself and wants the rest. Why the part he has is now the asset, and what the remainder costs.
An authorised service company that declined an old laptop. Why unfixable and unreadable are different findings from different trades.
Files retrieved by a consumer tool that will not open. Why that usually means the recovery was wrong rather than the files damaged.
A repair shop copied a failing PC to an external drive and the copy will not open either. Why a transfer is not done until files open.
A beeping drive a shop declined to fix. Why they were technically correct, and why it still does not answer the question asked.
An owner who imaged his own failing drive before asking for help. Why that changes everything, and the one thing to check about the image.
A liquid-damaged laptop a repair shop could not fix, holding doctoral work. What a failed repair changes, and why time matters here.
A drive assessed by another lab in 2009, quoted, declined and kept. What that old report still tells us, and what has changed since.
A laptop taken in for slowness that came back empty. What to establish before anything else, and why the original drive matters.
A repair shop that formatted a customer's memory card as a diagnostic step without asking. Why the data is probably still there.
A solid-state drive recovered once and returned to service, now failed a second time. Why a recovered drive is not a repaired one.
A machine held onto for years after a failed recovery, and an owner who admits trying something she was told not to. What to establish now.
A customer planning ahead while their drive is on the bench, asking how much space a backup will need on a new machine. A practical answer.
A drive already assessed elsewhere, and a fair question about paying for the same thing twice. What a second assessment adds, and what it doesn't.
A university laboratory that could not proceed for months because of internal processes. What that delay costs technically, and how to shorten it.
A charity's drive opened by a well-meaning engineer, holding music that could simply be converted again. The honest sum, done out loud.
A customer posting a card in after a phone quote. The six things worth putting in the box, and the two things worth leaving out.
A visiting student with a clicking drive and a fixed departure date. Why saying the date changes the work, and how delivery is arranged.
A request for express handling on a failed drive. What speed can genuinely buy, what it cannot, and the one stage that must not be rushed.
A school asking whether a relaxed deadline reduces the cost of a recovery. An honest answer, and what genuinely does.
An update that triggered an encryption prompt on a second-hand laptop, with no key anywhere. An honest answer, and the one place left to look.
Recordings erased from a games console handed on to siblings, and used since. An honest answer, and the places they may still exist.
A drive holding a year of travel photographs that took twelve years, three households and a failed attempt to reach its owner. Case 1100.
A drive that will not spin, holding photographs the owner would like but does not need. An honest answer about what no-spin costs.
A failed drive whose owner kept copies elsewhere. Why the right first step is an audit, and how that shrinks the job.
A cloud account that wiped a decade of photographs, and a broken laptop in a spare room that turned out to hold the last copy. Case 1150.
A practical question about what a customer supplies for a recovery, and the more urgent problem behind it.
A drive left unrecovered for months because of cost, holding personal material. What waiting costs, and who sees your data on a bench.
An encrypted stick holding ten years of family photographs, with no password. The one place the recovery key was almost certainly saved.
A card full of images that photography shops declined to duplicate. Why their caution was reasonable, and how to do it properly yourself.
A thousand deleted photographs, three different answers from three people, and one word that reveals what actually happened. Case 1200.
A collection of failed drives from several machines, and how to triage them before spending anything.
Two years of teaching materials lost across one evening, in three steps that each looked like ordinary computer trouble. Case 1250.
Start with an instant online quote, or call and talk it through with us first. You'll have a clear, fixed price before any work begins.