Every case file here is a real job off the South Gyle 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.
Every reset combination from the help pages, a drained battery, even a spell in the cold — nothing woke it.
His account was compact and complete. A WD Passport 4TB with "a lot of important data on it"; on connection.
A lifetime's music archive in WAV and FLAC, on a drive that had always been slow to appear but always appeared.
The Passport made a scraping noise for less than a second; a dialog called it damaged; the files opened anyway — and then Windows offered to fix it.
His triage was sensible and cheap-things-first: a fresh USB cable, careful observation, an honest guess that the sound was the read head trying.
The backup drive on her 2009 MacBook Pro declined repair, granted a read-only afternoon, then vanished from the desktop for good.
The winking modesty undersold a decent diagnosis: power present, nothing in Explorer, and a mechanism that felt and sounded wrong to a careful hand.
His report was diagnostic gold: the Passport spins up, announces itself correctly as a device, and then tells DiskPart it holds zero bytes.
The 3TB portable's decline was gradual and well-witnessed: transfers that froze the whole machine, then total invisibility.
October's failure got shrugged at; the expendable disk takes the blame in every two-drive machine.
The Seagate Expansion was five months old, bought in the Boxing Day sales, and failed suddenly while filing converted documents onto it.
The drive fell mid-playback and never appeared again; the expert's verdict was a damaged motor and a disk that won't spin.
The Passport went from perfect to hollow in days: both PCs recognise a device, both assign a letter, and neither can see a volume name, a directory.
A 6TB archive drive that attempts spin-up and gives up; a Mac that sees the device and offers to initialise it.
Two very different machines refused the same drive, and one of them didn't just refuse — the file manager went down every time it tried.
The repair shop's verdict was honest and vague: the hard drive has failed or is broken.
He described the sequence exactly: power on, disk spins, a few clicks, spin-down, and the drive drops off the computer entirely.
He was refreshingly clear: the drive is clicking and unreadable, he has a replacement already, he wants the data back at the lowest sensible cost.
His enquiry paired a familiar fault with high stakes. A WD My Passport: "failed with around 1TB of critical data on it.
A short, hopeful enquiry with the question everyone really asks: the drive isn't recognised, and can everything still be there.
His enquiry was economical and his preference explicit. A 2TB external drive: "sounds like motor stuck in a loop." A request for the recovery cost.
A precise mechanical report: the internal USB connection point on a portable drive has snapped, so it can't be plugged into anything.
A vivid, plain-language report: the connector broke off a portable drive and is now loose inside the casing, rattling around.
A relaxed enquiry about a dead external: no power at all, three-quarters full, not vital data, just wants a cost.
A short enquiry with a clear cause: a WD Passport stopped working right after being dropped.
A nearly-new drive, barely used, mostly for charity work — froze while viewing files, and now the laptop pings on connection but the drive only beeps.
A brisk, practical enquiry: a failed 500GB portable that won't boot, and two straightforward asks — a price, and how to get it to the lab.
A Western Digital external: "it has just started making a funny noise and now not connecting to my MacBook… are you able to repair/recover it?" This page.
His measurement makes the case: an external drive knocked just fourteen inches onto a laminate floor, now beeping on power-up and invisible to his MacBook.
A college lecturer's report so precise it reads like the drive's own service manual: first the light and a beep every few seconds.
He reconstructed the accident himself: laptop on, hub unpowered, the Seagate sipping standby voltage — enough to start something, not enough to finish it.
Years of pet photos and videos, around 100GB of the irreplaceable kind, on a drive that suddenly clicked on connection.
His enquiry read like a well-kept logbook. A 27-inch iMac from 2010, its internal drive laid out in four named partitions.
The tone was cheerful; the physics was not. His 2TB Western Digital external — "actual capacity is 1.81TB," he noted.
Her elimination was textbook: four different computers, a healthy spin, no strange noises, and total unanimous silence at the interface.
His honesty did the diagnosis: months of connect-disconnect at every accidental touch, then a week of errors, then folders that failed the deeper he went.
A hopeful, low-key enquiry: two old external drives whose external DC power adaptors are long gone, wondering if any data survives.
Her report was admirably terse. A Seagate BarraCuda 4TB: "weird noise when plugged in, computer not reading.
A dead drive from her parents' PC, silent on power, that she's researched enough to clean the board but wisely won't solder.
A husband's careful report: his wife's Mac-formatted 3TB WD My Book fell from her desk onto hardwood.
A courteous enquiry with a big number in it: a 10TB Seagate external, holding around 4TB of disc backups.
Her WD My Book Studio fell, powered up, worked — and the next day began clicking and shutting down.
The drive: an external that "no longer appears in My PC when I plug it in, and used to make a quiet beeping sound.
His report was a methodical tour of every door, each found frozen shut. The Toshiba external "made the sound and lit up all normal".
A wonderful vintage enquiry, reported with an engineer's precision: a 1997 industrial machine PC, its original three-gigabyte Western Digital Caviar.
He was told, by a service counter that honestly admitted it lacked the expertise, that his SSD's mechanical parts had failed in the heat.
An IT team's honest incident report: a Windows upgrade reimage — quick format, not a secure wipe, as he precisely noted.
Plugged into the motherboard, it slowed and crashed the whole PC; through a USB dongle it lasted longer but kept dropping.
All her work lived on one memory pen; it was in the side of her tablet when it got bent.
Her enquiry laid out a problem this trade meets more often as the years pass. The machine: "an old ASUS Transformer Book, 10.1-inch, 2GB RAM on Windows 8.
He wrote on a colleague's behalf, had already run a three-system elimination, declined the format offer, and named his suspect: sustained overheating.
His enquiry arrived carrying a precise technical prescription he'd been given elsewhere, and asked only whether we could do it.
A model diagnostician: copying footage from cards to an SSD when the SSD failed; cards then emptied and bin cleared.
His report was precise, and the precision is diagnostic. A 64GB Verbatim USB stick, new, used for video editing.
His enquiry was all business: "I would like a quote to recover data on a USB stick that is not recognised, please." Six words of problem.
The tersest enquiry in this volume: "SSD not readable." Three words — and sufficient, because with solid-state drives there is often genuinely nothing more.
A Samsung T7 Shield holding a mixed .mov and .mp4 archive, where some files now open to nothing — reporting a size of zero KB.
A son enquiring for his father: a 2TB Crucial SSD from the old PC, not detected.
A courteous, detailed enquiry: his laptop's NVMe M.2 SSD randomly stopped working, the laptop maker's diagnostics (and a lot of rebooting) didn't revive it.
A father writing at speed for his daughter: her end-of-year coursework, two weeks of work on one file, saved to a Toshiba memory stick.
An evening's decline, precisely observed: her USB stick worked, then a folder full of documents suddenly read empty on every computer.
A meticulous international enquiry: his laptop's SK Hynix SSD is a System-on-Chip design — controller and NAND fused in one package.
A disorienting failure, well investigated: mid-use, his Windows 11 PC restarted itself and came back up in Windows 10 — an old install on another drive.
A Surface Pro 7 that sailed through a Windows update and refused to boot the next morning — no loading dots, no recovery-USB boot, nothing.
A polite enquiry with two practical questions: what would it cost, and does he need to supply a device for the recovered footage?
One five-day trip on a 128GB card, one in-camera format, and just a single photo written since — near-perfect discipline.
His competence ran right through the enquiry — which makes the one gap in it all the more human.
The card played perfectly on her laptop at breakfast; hours later, inserted to move the videos onto her storage system, it appeared nowhere.
An unbranded 64GB card, shipped in the box with his hardware sampler and serving ever since as its sole storage.
His PC's only drive quit in the middle of updating a game, leaving the boot-device error and one hopeful observation: the BIOS still sees it.
Safe mode offered him one road back: install the system update — and lose everything on the drive.
Most enquiries report feelings; his reported numbers. The 64GB microSD from his phone appears briefly, then drowns.
The front light blinked, First Aid found nothing wrong, a second power adapter changed nothing.
Her enquiry read like a bug report: top of each image visible, remainder gray; onset after transferring or viewing; recognised by camera and computer.
Her enquiry contained a diagnosis she'd assembled without quite naming. "I think my phone has corrupted my SD card.
The dual-card adapter, the messy backup folders, the mysterious json files she cleared as junk.
She'd run the perfect control experiment without meaning to: every other memory card works in both her devices; only this one fails in both.
He knows his editing software offers a repair path; he's wisely wary of trying it with limited IT skills and no second copy.
A precise report of chaos: a loose lock switch, a split casing, and a cascade of contradictory errors across camera, Explorer and the photo app.
Her timeline pointed straight at the cause: perfect the night before, corrupted right after a system update, nothing else changed.
A microSD card from a dash cam stopped working, with footage to recover.
Following a phone call, a customer posts a faulty CompactFlash card next-day and asks for two specific things: treat it as critical, and clone the card.
A corrupt 32GB SanDisk Extreme microSD, unreadable from any device, and recovery software already tried and failed.
Her microSD card won't read anymore — and worse, it crashes Explorer whenever she tries.
An enquiry from a distinct technological era: a JVC Everio hard-disk camcorder.
Her enquiry came with a theory, and the theory holds up. "I recently purchased an adapter for my SD card and I believe it has corrupted the SD card.
His phone announced a damaged SD card and offered to reformat it — warning that all data would be lost. He didn't press it.
His microSD card isn't detectable on the phone or a Windows PC — not erroring, not misbehaving, simply absent from every device.
Her report was a small museum of odd symptoms, precisely observed. A microSD card: "some of the files are now missing.
The enquiry came from a working shoot, with the calm of someone who needed an answer more than sympathy.
A precise, local enquiry: his 64GB SanDisk microSD corrupted after filming, and Disk Utility now sees it only as a 32MB drive demanding a format.
An exemplary symptom log: a 64GB Kingston microSD that began by freezing the phone it lived in, now unrecognised by that phone and three different readers.
Her enquiry told the truth in the first line and asked the hard question in the second. "I have mistakenly.
A father's methodical enquiry: the microSD from the kids' camera, two or three years of them aboard and never backed up, now invisible to a USB dock.
A precise little mystery from a camera card: 400-plus photos listed fine, half of them cut across to the laptop, and days later the card reads empty.
He was formatting the new drive to APFS Encrypted and gave it the old drive's name mid-job; the year-old twin promptly vanished from the desktop.
He ejected too soon, mounted the 4TB on another machine, ran Disk Utility's repair — and suspects the repair itself finished the job.
Transfers went slow, then erratic, then stopped — but the USB-C drive still powers, spins, mounts and shows its full catalogue.
The strangest symptom in the visibility genre: the virtualisation layer greeted the drive by name and asked which world it should join.
He knew the advice — turn it off straight away — and confessed plainly that he didn't.
Copying crashed after one or two files; the folders sat visibly intact; so she tried what the capable try — a whole-disk cloning utility.
The Apple-formatted Seagate quit mid-transfer and now performs mounting without completing it.
He did real investigative work: checked in the terminal, found the system had begun encrypting the partition and then stopped mid-process.
His 2014 MacBook Pro stopped recognising its 1TB SSD, and he's managed to remove the drive.
His older MacBook Pro boots to the classic sight: a flashing folder icon with a question mark.
An unusual hardware story told matter-of-factly: his MacBook won't switch on unless its faulty sound board is disconnected, and when it does boot.
His enquiry described a trap built into modern convenience, sprung exactly as designed. "My daughter has deleted her university notes from her iCloud account.
A careful, self-aware enquiry: his photos and videos going back more than fifteen years were backed up from his phone to the laptop.
His account carried its own diagnosis, hidden in plain sight. A late-2011 MacBook Pro that "started to run very slowly recently" — lightly used.
His enquiry opened with the honesty that makes a case easy to help. A 2017 MacBook: "I was getting recurrent messages that the disk was almost full.
A son's meticulously structured enquiry for his father's late-2015 iMac.
Her enquiry had already done the hard thinking, and stated it plainly. A late-2012 Retina MacBook Pro that "has completely stopped turning on and will no.
Hers was candid and braced for disappointment: about half a year of photos from an old iPhone, backed up in their day onto a MacBook and, she believed.
His enquiry described due diligence colliding with a wall of contradiction. A 2017 27-inch iMac with a Fusion Drive in trouble.
The controller refused to activate the spare and rebuild; a colleague diagnosed a bearing in the seventh drive — grinding under load, normal at idle.
He arrived with his homework already done — a four-bay Synology unit that "is not starting up," and the manufacturer's own support verdict pasted in full.
Formatted on his Linux desktop, filled with 800GB of photos, then re-housed in an external case.
An engineer's enquiry from a prototype industrial rig: the 2TB NVMe vanished from the BIOS of its own machine, a second identical unit, and a laptop.
A retired software developer, volunteering for a charity with years of data on one server drive and a sketchy attitude to backups.
A laptop malfunction; a self-administered restore — "I tried to restore it myself. I thought I had everything I needed backed up." And then the discovery.
The landing was as gentle as landings get; the drive beeps anyway and shows on neither of his Macs.
He got agonisingly close: an all-in-one USB adapter gripped the snapped connector well enough for a full deep scan — and the results had nowhere to land.
His report combined a heavyweight patient with an unusually thoughtful request. The drive: a Toshiba enterprise-class 18TB, 7,200RPM.
This enquiry came with an institution's measured care. Written on behalf of a staff member at a large organisation.
A failed WD MyCloud, and a sensible sequence: someone removed the drive from the casing to read it directly — and hit a wall, unable to access anything.
An eight-bay QNAP, RAID 5, reported with admirable precision: drive 3 failed a year ago and was never replaced, drive 6 failed a fortnight ago.
A chilling homecoming: all files gone from his WD My Book Live, and a manufacturer's advisory in his inbox.
An enquiry five years in the making, practical and quietly moving: her late husband's QNAP Thunderbolt NAS holds the family's photos and videos among.
Everything was on the Toshiba because she was between computers — wedding photographs, pictures of her late parents, a consultant's working files.
She blamed herself first — the drive hadn't been ejected properly before shutdown.
His enquiry read like a well-run project brief. The failed 1TB laptop drive: "it reads as a physical disk in file-recovery software.
He wrote as the helper — an IT hand whose "customer has been hit with a ransomware infection" — and did the most useful thing a helper can do.
His two-bay NAS held the family photo archive; the ransomware renamed everything and demanded a three-figure Bitcoin sum.
The recursion stings: the drive holding her only laptop backup was consumed creating the install media meant to restore that laptop.
e., percentage of data recovered — and how much this would cost?" The case around it: a Seagate 1TB external holding "essential personal files.
Power cuts happen in his area — he said so himself — and one of them landed in the worst possible minute: hours into an unattended overnight copy.
The installer asked for an external drive to write setup files to; he reasonably expected a new folder.
A careful enquirer following up a phone call: his drive went through a Windows reset, he has most files backed up, and he wants only specific folders.
Years of trust in a local shop, undone when a new engineer wiped his files trying to fix something — photos and letters lost.
Her enquiry described a sudden, specific failure. A Toshiba 1TB drive she'd used for a year.
A business's worst Thursday, reported in one devastating sentence: cryptolocker ransomware encrypted the server's files and database.
A Seagate Expansion 1TB external: "it is detected when I plug it in, the light comes on and I can hear the disk moving.
Her report read like a small mystery, precisely observed. Browsing her external drive on a Mac for training-course materials.
A four-year-old Seagate 2TB Expansion throwing "disk structure is corrupted and unreadable" out of the blue, no physical damage; then her own investigation.
An institutional enquiry with the artefacts precisely described: an archive drive lost an entire folder and its structure.
Her enquiry was the candid report of a capable attempt, taken exactly as far as home tools go.
An enquiry structured as a numbered self-triage — how it failed, whether it was dropped, whether it powers, what the error says.
A Windows update corrupted his laptop's system; he salvaged everything except one paradox.
Her report described the moment every mass file move threatens. "I created one big folder with small different folders inside, with 12,000 pics.
An unlucky sequence reported with complete clarity: Disk Management open to format a brand-new HDD.
A technically fluent confession from an OpenBSD user: a format aimed at an SD card landed on the laptop's SSD, was cancelled immediately.
A list-format confession that decodes into one of Windows's cruellest traps: after a failed driver install and a restart, his desktop came up empty.
He switched on the surge-protected extension, heard a pop, smelled burning — and the destination drive was dead.
He confessed before he was asked. A Seagate Barracuda 2TB desktop internal had "stopped working"; and, in his words.
It began with a reasonable annoyance — no on/off switch — and ended with a dead enclosure, a dead hub, and an apology for the long story.
A laptop dropped fully into bath water, dried for a week, now won't switch on and the screen is separating. Years of uni and work files aboard.
A power shortage killed his Hitachi 1TB; the original board later gave smoke and a smell on power-up, so he bought two donor drives and a brand-new PCB.
A holiday accident with a chemistry lesson inside: the phone went into the sea, turned itself back on, vibrated continuously for half an hour, and died.
An enquiry written with unusual gravity: three hard drives deliberately damaged, two holding irreplaceable professional and personal data.
Her Passport declined without drama — no drop, no water, no noise — and she'd already been through one firm's door and out again.
A tidy corporate handoff: the in-house IT team assessed a director's failing iMac, replaced the drive.
A clicking drive already through one recovery lab, which swapped in donor parts and still couldn't get it to initialise.
Her clicking, unrecognised external went to a high-street retailer's data-recovery service first, without success.
A candid, self-aware enquiry: he dropped a drive mid-boot, then — his word, mistake — powered it up ten more times while it beeped.
A rare pleasure: an enquiry built around a local computer shop's genuinely competent written diagnosis.
An unusually well-prepared handover: the Apple Store diagnosed his non-booting 2011 MacBook Pro, confirmed the drive wasn't corrupted.
An unusually transparent starting point: his 1.5TB Samsung had already been opened and diagnosed by another company.
He was the helper in this story — a web developer whose client's laptop was "dropped and damaged and stopped working.
He found the $sysreset folder and read it correctly — a Windows reset had swept the MD's data.
The folder was simply gone. His diagnostics were methodical: checkdisk reported a clean surface.
Four to five years of a producing and mixing career on one Seagate Expansion — sessions, stems, masters.
Working shooters live by card discipline, and one pouch let him down: the morning's full card mistaken for a fresh one, formatted.
The stick asks for a password neither of them ever set. The vault's label points to an enterprise encryption product.
He ran the elimination properly — borrowing the known-good cable from the drive's identical twin.
He needed the 8th; the box could only reach back to the 16th. He'd already disconnected it — the single best move available.
He changed companies; the work laptop stayed behind; the drive it had BitLocker-locked came with him.
His report needed no translation. A 2TB hard drive that "sometimes shows up as a mapped drive but cannot be accessed".
No warning, no noise — the desktop's 4TB Seagate hybrid simply wasn't there one morning.
The 5TB clicked without spinning; the identical donor drive was already bought; the board swap had already failed.
He arrived with a completed diagnosis in hand: heads replaced elsewhere, 94.74GB identified across 1,884 folders, a 95%-or-better confidence rating.
A dead Samsung SSD, four terabytes wanted onto the incoming replacement, and a refund due from the retailer for a drive that genuinely failed.
He returned the car for repairs; the dashcam had recorded footage he believed told a story.
A completely dead drive — not even a light — 700GB aboard, no urgency, and an enquirer who asked the policy questions most people only wonder about.
The Barracuda from his iMac clicks briefly on power, falls silent, and reads nowhere.
A 5TB he definitely needs recovered; two old 500GB laptop drives he'll decide about once he knows the numbers.
A drive that spins up, grants a few seconds of directory access, and shuts itself down.
This one isn't a broken drive — it's an active intrusion, and it needs different, urgent advice.
A blunt, honest question: a WD external drive, a forgotten password, can we crack it.
A single-line enquiry with no symptoms, no model, no detail — just a laptop that needs data recovery.
A painful, particular predicament: his cryptocurrency wallet opens, the balance is visible.
The drive arrived by post with a letter folded around it: what happened (the laptop shut down mid-work and never restarted).
Enquiries don't come more honest than this, and honesty this complete deserves the same back.
A Kingston 512GB stick corrupted while writing two files at once; a consumer recovery program found everything by name before the laptop cut its power.
A 2015 MacBook Pro SSD, already through two recovery firms — and the second one's closing email was a model of professional honesty.
Her enquiry covered two casualties: a MacBook whose liquid damage killed the power path.
A refreshingly different request: his 6TB G-Drive — a Time Machine backup of his whole iMac — died at two years old, still under warranty.
Case 550, closing the volume: a computer shop's technician met a dropped, beeping external drive carrying a working artist's collection.
The four-hundred-and-fiftieth case file arrives with its thesis pre-written by its own enquirer.
The five-hundredth case, the completion of two full sites, and the last word of a long argument this archive has been making all along.
The six hundredth case file closes Volume Twelve exactly where the archive began.
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.