Desktop externals · lab notes · PLY-2025-0935
It Mounts Straight Away, and the Window Is Empty.
This Elements sat in a cupboard in Mannamead and came out once a month to take a copy of whatever was on the family PC: the camcorder tapes once they were put onto the computer, the school photographs, and every bit of paper we own
. On the Sunday in question it spun up as it always did and mounted within a second, then produced no folders at all — twenty years of stuff, and a blank window
. Before anybody telephoned us, someone in the household had run chkdsk over it.
Sounds like yours? Talk it through.
0800 6890668
Why it happens.
NTFS holds its names in one structure, the master file table; the contents of the files sit elsewhere on the platters entirely. Ruin that table and every listing vanishes, though every byte in every file remains at the address it was originally written to. Any of several things will do it: a write that stopped part-way, a partition entry a few sectors out of place, an unlucky patch of weak sectors. Hence a drive that mounts in a second and then offers you an empty window is usually a failure of record-keeping rather than a broken mechanism. Two matters wanted settling before anything else: whether this drive could safely be read, and just how much chkdsk had managed.
The kit this job called for.
How the job runs →| The kit | What it did here | Why we keep it |
|---|---|---|
| ACE Lab PC-3000 Express | SMART and both defect tables read before anybody assumed anything | Drops the disk into its maker's service mode, out of reach over plain ATA |
| R-Studio Technician | Reconstructed the file table from surviving records and from the mirror | Reads nearly every file system, and rebuilds RAID sets from images |
| UFS Explorer Professional Recovery | Where names had gone, carved the files by their signatures | Mounts what other software will not: APFS, ReFS, XFS, ZFS and Btrfs volumes |
How it ran.
Establish the hardware is sound, then turn to NTFS
No serious reading happened until the drive had been put through a short interrogation at firmware level: its SMART history, how many sectors had been remapped, and both defect lists, primary and grown. Everything came back clean, which counts for a good deal here — a sound mechanism means imaging at full speed rather than picking through slowly on salvage settings.
Image first. Repair nothing but the image
Every repair tool alters whatever it is pointed at, and one such tool had already been over this drive once. The order of work followed from that: nothing else would go near the original. Seen through the image, the damage lay in one continuous band. NTFS keeps a backup of its earliest and most important records too, and that had survived very nearly intact.
Give the nameless files something to be sorted by
Where an entry had been deleted outright by chkdsk, the file itself had to say what it was. Signatures for JPEG, MP4, PDF and the Office formats were read straight from the clusters. Files were then grouped by format, and within each format by date, taken from timestamps carried inside the files. The result is a set somebody can genuinely sit down and go through, instead of thousands of numbered items.
How it ended up.
There was no loss at all. Paperwork, school photographs, transferred tapes: everything came back. Most arrived under its own names in its own folders, and the rest arrived grouped by format and date. A new drive carried it home, together with a word about where a sole copy ought not to live — beside the very computer it is copying.
Pages people open after this.
Also tagged: desk drives.
Seeing the same thing?
Leave it switched off and post it in. Nothing happens until the diagnosis, which lists what can still be read and what cannot.