Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Casebook

The lab · casebook

Recent recoveries, exhibit by exhibit.

This is an ongoing record of what has come across the bench (anonymised, validated and stored alongside the page detailing what went wrong). Click on any exhibit to view information on that specific type of recovery.

Talk it through with an engineer
01273 964902

Exhibits from the bench.

On the homepage →
EX · BDR-2026-0857CHECKED ✓

A four-bay DS with mixed drives, crashed by its own good intentions

The storage had two 4TB and two 8TB hard drives, one of which failed, and when DSM attempted a rebuild overnight it ended in Volume Crashed. What really happened behind the scenes: three different mdadm arrays, of which two were OK and one was "degraded" but could be recovered. Each array was assembled outside of the box in sequence. The btrfs tree rolled back to the previous generation, and every share was restored.

All shares restored5 days in lab
EX · BDR-2026-0851CHECKED ✓

A Sussex practice's SQL database, Suspect at 8:55am

Power outage overnight. Database marked as 'Suspect' when morning arrived. An emergency repair from an IT contractor was about to be done. Forensic copies of the system were made first, and after that things looked much better than they had at first. We were able to replay the log and recover the database on the forensic copy, attach it cleanly, and the appointments were only delayed twenty minutes instead of a week-long delay.

Attached clean24 hrs in lab
EX · BDR-2026-0846CHECKED ✓

Two production VMs, deleted on a Friday, provisioned-over by nothing

An administrator ran their clean-up script against the wrong directory. As no one worked off this datastore over the weekend, nothing was written over either VMDK file, and therefore they both survived, unlinked but intact. We pulled both out of the VMFS image on Monday, and by Tuesday evening (payroll included) we had managed to recreate their descriptors and have both systems running within a sandbox.

Both VMs booted3 days in lab
EX · BDR-2026-0841CHECKED ✓

A 4TB BarraCuda that woke up claiming to be nothing at all

Working at midnight, 0GB at breakfast — the classic translator failure, platters untouched. Two service-area modules repaired over the terminal, the translator regenerated, and the drive introduced itself correctly long enough for a complete, unhurried image.

100% imaged3 days in lab
EX · BDR-2026-0834CHECKED ✓

A shucked Passport, an initialised disk, and a very close call

The owner followed a video on YouTube and plugged the bare WD hard disk directly into a SATA dock. Before they realised this could have been an error in judgement, they had accepted Windows' prompt to initialise the hard disk. The original board had also arrived in the same envelope. We extracted the encryption keys off the bridge on the original board, fixed the minor damage done during initialisation on the image and decrypted, intact, the pictures that are part of fifteen years of family history.

98% recoveredThe board saved it
EX · BDR-2026-0827CHECKED ✓

Six hundred wedding RAWs, 'recovered' once already

Free software had returned 600 files — all previews, none printable. The original card, thankfully unused since, imaged cleanly; the CR3s reassembled from their fragments, and the couple's gallery delivered at full resolution — including the forty frames the free tool did not return at all.

640 full-res frames72 hrs in lab
EX · BDR-2026-0822CHECKED ✓

An accountancy firm's RAID 5, one week before year-end

In June, drive two failed. No one noticed until August, when drive four failed during a rebuild. In actuality, drive four's images showed it had nineteen bad sectors and did not actually fail. We were able to successfully complete a stripe rebuild using three active members and an almost fully operational fourth member, and the practice filed on time with everything.

19 bad sectors, not 2 dead drives6 days in lab
EX · BDR-2026-0816CHECKED ✓

A ProLiant that survived the power cut but not the restart

A power outage caused the UPS to exhaust itself. When the server was restarted, the Smart Array controller wanted decisions that nobody could safely make. Each of the four disks was imaged, the RIS metadata was read, and the delayed parity was honoured. The database for practice management was mounted from the rebuild, with all data included up to the last write the cache had flushed before the power went out.

Database mounted clean5 days in lab
EX · BDR-2026-0811CHECKED ✓

The 'repaired' laptop with none of the owner's files on it

After a Brighton student's computer came back from the repair shop, everything worked as expected, but there was an entirely new, empty hard drive installed in it. The old drive, pronounced dead, was stored in a drawer and clicking. Donor heads were fitted and used to create a two-day image of the old drive. Every essay, picture etc. was copied onto the new drive the repair shop had put into the computer.

100% recoveredAfter the 'repair'
EX · BDR-2026-0803CHECKED ✓

A Sussex logistics firm, offline at 9am, trading by Thursday

The RAID setup on their booking system crashed when they started their week, on Monday morning, with a rebuild already failed. All members were imaged back to back through Tuesday. On Wednesday the RAID was rebuilt virtually and by Thursday at lunch time the verified database was handed over to the customer. The work was completed with priority and without any dramatics.

Trading in 4 daysPriority case
EX · BDR-2026-0788CHECKED ✓

A WD My Passport, dropped at the top of the stairs

Clicking on power-up and a dissertation due in nine days. Donor heads, a careful image, and the bridge's encryption keys carried across — every chapter and reference file came home with time to spare.

100% of the thesis72 hrs in lab
EX · BDR-2026-0785CHECKED ✓

A Hove agency's mirror, undone by its own rebuild

Their two-bay RAID system had two red lights showing a failure. Then a DIY rebuild took place, in the process overwriting the unit's own metadata. Images of both drives were created, reading past the areas of damage. The mirror was restored using either image, depending upon which had the healthiest copy of each area. Their shared drive was whole and operational again.

100% recovered5 days in lab
EX · BDR-2026-0779CHECKED ✓

A wedding on a card that woke up blank

Their 512GB SanDisk card was functioning properly at midnight, however by morning it was completely blank. A forensic duplicate of the card was created first. The file system was rebuilt on top of the duplicate. A deep carve was then performed behind it for anything orphaned. Ultimately the couple got every frame and the photographer retained the client.

Every image back48 hrs in lab
EX · BDR-2026-0770CHECKED ✓

An iMac Fusion Drive that faded out over a fortnight

The mechanical portion of their Fusion Drive was failing, causing the volume associated with it to fail. Images of each of the two drives were made. The Fusion logic was rebuilt across both of these images. As a result of this recovery process, a design studio was able to recover a decade of client work in full, after the Apple Store had said the machine was beyond help.

98% recovered5 days in lab
EX · BDR-2026-0766CHECKED ✓

A teacher's laptop, dropped the week before results

The unit was beyond cost-effective repair, and the internal drive was clicking. With donor heads and a careful image, in three days she had in hand the five-year cache of lesson plans, coursework grades and student reports.

100% of user files3 days in lab
EX · BDR-2026-0761CHECKED ✓

A silent Seagate with fifteen years of a family business on it

There were two failed heads and a drive which hadn't spun for weeks. With the new donor heads installed, the drive's image was 96% complete after the initial pass. And the accounts, invoices, and photographs all left the lab verified.

96% recovered4 days in lab
EX · BDR-2026-0754CHECKED ✓

An NVMe that stopped being seen mid-update

Ten years of a photographer's edited catalogues were successfully recovered after the laptop's firmware was updated improperly and the system drive did not come back. It was possible to access the drive through technical mode, rebuild its translation tables, and recover the catalogues intact.

99% recovered5 days in lab
EX · BDR-2026-0748CHECKED ✓

A factory's RAID 5 with two dead members, recovered over a weekend

After production data got hung up on a server that had eaten its second drive while being rebuilt on a Friday, all four disks were imaged. A stripe was re-created using three-and-a-bit good images and the factory was operational on Monday morning.

100% critical data1 weekend
EX · BDR-2026-0743CHECKED ✓

A snapped stick holding a sole trader's entire accounts

Stepped on in a site office, connector torn clean off. The monolith was read through its test pads, the controller's layout reversed, and seven years of invoices and CIS records handed back before the tax deadline.

100% recovered3 days in lab
EX · BDR-2026-0652CHECKED ✓

A burst pipe, a home office, and a drive in a sandwich bag

The owner's instincts regarding the unit were spot on; they never powered it up, sealed it wet and posted it to us the very next morning, and we took care of treating the contacts so that we could replace the shorted board with another one carrying over its ROM. We also created a full image of the entire contents within that week, saving twenty years' worth of family photographs, dry side up.

100% recovered4 days in lab
EX · BDR-2026-0647CHECKED ✓

A photographer's archive drive, off the back of a van

When a portable external drive containing three years of client shoot photos was dropped during the load-out from a wedding, it was clicking by the time it was plugged in to check. We installed one donor head assembly and completed imaging it in two days. Each gallery was restored, including the one from that morning.

99% recovered4 days in lab
EX · BDR-2026-0642CHECKED ✓

A Hove architect's workstation, locked by its own BIOS update

A firmware update changed the TPM's measurements overnight and the machine demanded a key nobody had written down. The Recovery Key ID led to the practice's Entra ID escrow; damaged BitLocker metadata was rebuilt with repair-bde onto a new drive, and every project file survived.

100% recovered3 days in lab
EX · BDR-2026-0638CHECKED ✓

A Sussex builders' merchant, encrypted overnight

The strain copied files, encrypted the copies and deleted the originals — so the originals were still carvable from free space, alongside a NAS snapshot the attacker missed. Trading resumed inside a week. Nothing was paid, and nothing was said to the attackers.

Back in a weekNothing paid
EX · BDR-2026-0633CHECKED ✓

A 4TB archive drive that went RAW after an unsafe removal

Pulled mid-write one evening; by morning it wanted formatting. Imaged in full, the boot sector and a damaged MFT mirror rebuilt on the copy, and fifteen years of a translator's client work returned with its folder tree intact.

100% recovered3 days in lab
EX · BDR-2026-0629CHECKED ✓

The wrong drive, quick-formatted during a Windows reinstall

Two identical 2TB drives in one tower; the one holding the family archive got the fresh install's format. Nothing else was written — so the old file table was recovered whole, and every folder came back under its own name.

Full tree back3 days in lab
EX · BDR-2026-0624CHECKED ✓

A Shift+Deleted accounts folder, two days before payroll

An entire year's bookkeeping removed with one confident keystroke on an office desktop. The drive was imaged that afternoon, the file table rebuilt, and the folder came back with every filename and date intact.

Full tree back24 hrs in lab
EX · BDR-2026-0618CHECKED ✓

A silent WD desktop drive after a summer power cut

Dead by the next morning after a power cut — no spin, no BIOS entry. A blown TVS diode and a scorched board; the ROM moved to a donor PCB and the drive imaged completely the same day it was opened.

100% imaged2 days in lab
EX · BDR-2026-0611CHECKED ✓

A three-click Seagate carrying a shop's entire till history

Clicking once a second by the time it arrived, with five years of EPOS records aboard. Two donor head assemblies and a patient image later, the accountant had a complete ledger and the shop made its VAT deadline.

97% recovered4 days in lab
EX · BDR-2026-0563CHECKED ✓

A Shoreham haulier's dashcam, deleted by the driver involved

The clip of a depot incident was gone from the cab camera overnight — deleted, not overwritten, as the card's image showed. Recovered, repaired and packaged with hashes the same week, it settled both the insurance question and the HR one.

Clip recovered intactSame-week bundle
EX · BDR-2026-0558CHECKED ✓

The forklift claim that footage settled in a week

A disputed warehouse incident, an insurer asking questions, and a recorder that had already looped past the incident — except for the deleted export a manager had made and binned. Recovered from the drive, hashed, documented, and the claim closed without a hearing.

Claim settledExhibit-grade bundle
EX · BDR-2026-0552CHECKED ✓

A Lewes farm shop's deleted week, mostly retrieved

A staff member cleared 'old clips' that included a theft. The recorder was stopped the same afternoon — the decision that saved the case. Index remnants restored four of the five deleted days with timestamps; the fifth came back by carving, playable but unlabelled.

4 of 5 days timestamped72 hrs in lab
EX · BDR-2026-0546CHECKED ✓

A Brighton shop break-in, and a DVR that kept on taping

By the time the insurer asked for footage, the recorder had been looping for nine days. The drive was imaged, the index parsed, and the incident window recovered from sectors the loop hadn't yet reached — exported twice, once for people and once for the claim.

Incident window recovered3 days in lab
EX · BDR-2026-0539CHECKED ✓

The client list that left three weeks early

A Worthing employer's suspicion started at a rival's pitch deck. The timeline said the rest: files staged into one folder, a personal cloud account signed in, uploads completed — twenty days before the resignation letter. The matter resolved on undertakings, quickly.

Resolved on undertakingsWhat happened when in 7 days
EX · BDR-2026-0534CHECKED ✓

A Part 35 report that shortened a Sussex dispute

Two businesses, one deleted folder, two theories. The imaged drive supported neither side's favourite story — and said so, with the timeline to prove it. The matter settled within a month of the report being exchanged.

Settled post-exchangeCPR 35 compliant
EX · BDR-2026-0527CHECKED ✓

A wiped laptop, and the fifteen minutes that mattered

A leaver ran a wiping tool the night before returning their machine. The tool's own logs, the run window, and the files it missed were all recovered from the image — and the timeline of what happened first told the rest of the story.

What happened when establishedReport in 8 days
EX · BDR-2026-0521CHECKED ✓

A Sussex firm's project files, gone from the index

Files a client insisted had been stolen turned out, on the timeline, to have been deleted from a shared drive by a sync misconfiguration — and most were recoverable. The honest answer ended the dispute faster than the suspected one would have.

Dispute resolvedReport in 6 days

The archive — every case, written up.

BDR-2025-0308A Dropped Drive Full of RAW FilesPortable drives BDR-2025-0903A Fatal Hardware Error, Then Two ClicksDesktop externals BDR-2025-1103A RAID Five Against the ClockNAS and arrays BDR-2025-1106A Teacher's Resources on a Silent DrivePortable drives BDR-2025-0603After the Power Cut, No Drive DetectedElectrical damage BDR-2025-1110Apple Couldn't Fix It, Ten Years of FilesThe Apple side BDR-2025-0907Corrupted Footage From the ShootMemory cards BDR-2025-0311Cyclic Redundancy Check on My Life's WorkLogical & corruption BDR-2025-0607Dropped, and Now Only a Slight ClickThe Apple side BDR-2025-1113Dropped, but Everything Appears OKLogical & corruption BDR-2025-0611Found It, Looked at It, and It DiedDesktop externals BDR-2025-0911I Chipped the Corner Off the SD CardMemory cards BDR-2025-1117I Deleted the Files and StoppedLogical & corruption BDR-2025-1120I Think the Disc Inside Has BrokenDesktop externals BDR-2025-0914I Took the Cloud Disk Out and Still Can't Read ItNAS and arrays BDR-2025-0614I Took the Lid Off to Check the HeadsElectrical damage BDR-2025-1124I Tried DMDE, Then the Grinding StartedDesktop externals BDR-2025-1127It Beeped Halfway Through the TransferHonest limits BDR-2025-0315It Beeps and Shows the Wrong SizeDesktop externals BDR-2025-0918It Couldn't Save, Then It Couldn't ReadFlash and solid-state BDR-2025-0618It Dropped Mid-Transfer and Pulled the USB OutElectrical damage BDR-2025-0319It Got Slower Until It Wouldn't OpenPortable drives BDR-2025-0322It Lights Up but Doesn't WhirrPortable drives BDR-2025-0621It Mounted Slowly, Then I Ejected It EarlyThe Apple side BDR-2025-0326It Passed SMART but Failed the Drive TestLaptops & desktops BDR-2025-0921It Slows the Whole Computer to a CrawlDesktop externals BDR-2025-1131It Spins and Lights, but Won't MountPortable drives BDR-2025-1134It Whirs Five Times, Then StopsPortable drives BDR-2025-1138It Worked Yesterday and Holds My Clients' JobsPortable drives BDR-2025-0330Locked Out by My Own FingerprintHonest limits BDR-2025-0925More Rattle Than Normal, and No Longer SeenPortable drives BDR-2025-0928My Cloud Drive Went Quiet, Then StrangeNAS and arrays BDR-2025-0932My Folder Became Zero-Byte FilesLogical & corruption BDR-2025-0334One Drive Clicks, the Other FadesDesktop externals BDR-2025-0625The BIOS Detects It, but Windows Doesn'tPortable drives BDR-2025-0935The Folders That Were There Are GoneDesktop externals BDR-2025-1141The Laptop Died, but the Drive May Be FineThe Apple side BDR-2025-0628The New PSU Blew the BoardElectrical damage BDR-2025-0632The Old Adapter May Have Shorted the BoardElectrical damage BDR-2025-0337The Port Was Always Flaky, Now It BeepsPortable drives BDR-2025-0635The Read/Write Head Is BentPortable drives BDR-2025-0639The SSD That Works in No LaptopFlash and solid-state BDR-2025-0939The USB Stick No Computer Will ReadFlash and solid-state BDR-2025-0341Two Drives Down in a Four-Drive ArrayNAS and arrays BDR-2025-0642Two Failed Drives in a RAID 5 ArrayNAS and arrays

45 case files, anonymised and verified — each one the full story: what arrived, what it meant, what the bench did, and what came back.

The next exhibit could be yours.

Every case above started with the same free diagnosis yours would.

01273 964902