We're taking on new cases now · Weekdays, 9am–5:30pm Need it back quickly? Call 0800 6890668
MKDR Milton Keynes Data Recovery 0800 6890668 Get it diagnosed
MKDR / Casebook / It Mounted on a Sunday and Showed Nothing

Case notes · Desktop externals · MKD-2025-4935

It Mounted on a Sunday and Showed Nothing.

The Elements was the sensible precaution — a Stony Stratford couple’s monthly copy of the camcorder tapes we had put onto the computer, the children’s school photos and every bit of paperwork. Plugged in one Sunday to bring it up to date, it mounted straight away and showed an empty window. Twenty years of folders, and not one of them there — and a chkdsk had already been run on it before anyone thought to ask.

Confirmed by the customer All cases anonymised

Same fault? Start here.
0800 6890668

Without the jargon.

A drive that mounts cheerfully and shows you an empty window has a records problem, almost always, rather than a contents problem. Every name on an NTFS volume is held in one master register, and a single injury there — a write cut off mid-update, a partition entry written wrong, a few weak sectors in the wrong place — takes every folder out of view at once without shifting a byte of what they contain. Two things have to be settled first: whether the mechanism is failing, and what that chkdsk pass wrote while it ran.

The kit this job needed.

See how a job runs here →
KitWhy it was usedWhat it gives us
ACE Lab PC-3000 ExpressQuestioned SMART and the defect tables to clear the mechanism firstTalks to drives in each maker's own command set, beyond what standard ATA covers
R-Studio TechnicianPut the master file table back from what survived and from its mirrorCopes with almost any file system; dependable array rebuilds
UFS Explorer Professional RecoveryContent carving for files whose names could not be brought backAhead of the pack on difficult filesystems: APFS, ReFS, XFS, ZFS, Btrfs

What happened on the bench.

01

Clear the mechanism before believing a software answer

The drive was put through firmware-level questioning before anything read it properly: SMART history, reallocated counts, the state of both defect lists. Every answer came back sound. That mattered more than it sounds — a healthy mechanism means the image runs at full speed rather than at salvage pace.

02

Image it regardless; mend the copy, not the drive

Repair tools write, and one of them had already had a go at the original. That decided the method: nothing further would touch the drive itself. Working on the image, the register turned out to be damaged across one continuous stretch, while the reserve copy NTFS keeps of its most important entries had largely come through.

03

Put the nameless ones into an order that helps

Files whose entries the chkdsk pass had finished off were identified by what is inside them instead — JPEG, MP4, PDF and Office signatures, read straight out of the clusters — then filed by type and by the dates recorded within each file, so that nothing came back as a heap of numbered strangers.

The outcome.

The tapes, the school photographs and the paperwork all came back — most of it under its own name in its own folder, the remainder sorted by type and date. It went home on a new drive, along with a stated intention to keep the second copy somewhere other than the same cupboard.

The lesson: A backup nobody ever checks is a wish rather than a plan. An empty window on top of a full disk fools nobody who copies it first.

Does that sound like your device?

One lesson runs through the lot: cut the power, let us look for free, then decide with the facts in hand.

0800 6890668