Desktop externals · case file · MHD-2025-6935
The Drive Mounts, and the Window Is Empty.
A Cookham couple kept the Elements as their monthly second copy: the camcorder tapes we had transferred to the computer, the children’s school photographs and all of the paperwork
. Connected one Sunday for the usual update, it mounted immediately and opened on an empty window — two decades of folders and not one of them showing
. A chkdsk had been run over it before anyone thought to ask.
Much the same fault? Call us.
0800 6890668
In everyday terms.
NTFS keeps every filename in a single register, the master file table, and the files themselves elsewhere on the platters. Damage confined to that register — an update interrupted, a partition entry written incorrectly, a few weak sectors in an unlucky place — removes every folder from view at once while leaving the contents exactly where they were. So a drive that mounts willingly and offers an empty window is nearly always a bookkeeping failure. Before any of that, though, two things need settling: whether the mechanism itself is failing, and what the chkdsk pass wrote as it ran.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| ACE Lab PC-3000 Express | Interrogated SMART and both defect lists to clear the mechanism first | Reaches the vendor-specific commands that ordinary ATA has no way of issuing |
| R-Studio Technician | Rebuilt the master file table from the surviving records and the mirror | Its file-system coverage is wide and its array rebuilds hold up |
| UFS Explorer Professional Recovery | Signature carving for the files whose names could not be recovered | Reads the awkward filesystems others stumble over: APFS, ReFS, XFS, ZFS, Btrfs |
The lab work.
Rule out the hardware before accepting a software explanation
Before any serious reading began, the drive was questioned at firmware level: SMART history, reallocated sector counts, the condition of both defect lists. Everything returned sound. That finding carries more weight than it appears to, because a mechanism in good order lets the image run at full speed instead of at salvage pace.
Image it anyway; the repairs happen on the copy
Repair utilities write to the disk, and one had already been let loose on this one. That settled the method: nothing else would be allowed near the original. On the image, the register proved damaged along a single continuous stretch. The reserve copy that NTFS maintains of its most important entries had come through largely intact.
Put the nameless files into a usable order
Where the chkdsk pass had finished off an entry, the file was identified from its own contents: JPEG, MP4, PDF and Office signatures read directly from the clusters. Each was then sorted by type, and within type by the dates recorded inside each file, so that what came back had an order rather than being a pile of numbered strangers.
How the job closed.
Everything came home: the transferred camcorder footage, the school photographs and the paperwork. Most of it arrived under its original name in its original folder, and the balance was grouped by type and by date. It left on a new drive, and the household undertook to stop storing the spare copy in the same cupboard.
More of the jobs we've closed.
Filed beside Desktop externals.
Does any of that match your case?
Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.