Call us — 0141 404 0294
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Formatted & Logical Faults · The Label Is the First Casualty

When the Drive Loses Its Own Name

Her enquiry described three years of work and a sequence of small signs that together say something quite specific. A WD My Passport holding photographs from "converting colour slides to digital over 3 years. There was still space on it when an automatic update started on Windows, so I packed in for the day. Next day I restarted, but the PC wouldn't recognise it and a new name for it went on called Local Disk (E:). A pop-up appeared telling me it was old and obsolete and to download the new version. I didn't, and switched off. Later I reconnected to find via properties that it was full, and I am still unable to" — open it. Three years of scanning is an enormous amount of irreplaceable effort. And two of her observations are considerably more encouraging than they appear.

MediaWD My Passport portable external hard drive holding three years of digitised photographic slides — volume label no longer displayed; capacity reported as full; contents inaccessible
Reported situationFailure coinciding with an automatic system update · drive subsequently presenting under a generic name rather than its own label · manufacturer software prompt declined · properties reporting the volume as full · contents not accessible
Fault classFilesystem directory unreadable with allocation data intact — volume label and file listing absent while capacity accounting remains readable
Equipment usedWrite-blocked imaging before any repair · directory structures reconstructed on the image from surviving allocation and backup records · signature carving alongside · images validated by rendering

The decode: what losing the name means, and why "full" is good news

Why it now says Local Disk: a drive displays its volume label — the name given to it when it was formatted or renamed — and that label lives inside the filesystem's own structures. When Windows can read those structures it shows the name; when it cannot, it falls back on a generic description. So a drive that has always shown its own name and now says Local Disk is telling her that the filesystem is no longer being read properly. That is an early and specific sign rather than a cosmetic quirk, and it is the first thing to go.

Why "full" is the encouraging part: the observation that changes the picture. The used-space and free-space figures shown in properties do not come from listing files — they come from the filesystem's allocation data, the records tracking which parts of the disk are in use. For Windows to report the drive as full, it must be reading that allocation information successfully. So the drive is working, the volume is being read at some level, and the accounting survives. What is missing is the directory — the records naming the files and describing where each one sits. Her photographs are physically present, the disk knows the space they occupy, and nothing currently lists them.

Why that is a good position: because allocation data and directory records are stored separately, and filesystems keep backup copies of their key structures at known locations. A directory that cannot be read can frequently be reconstructed from those copies and from the allocation records that survive — which returns the folder tree and filenames rather than an unnamed carve. That distinction matters enormously on three years of scanning, where the organisation is part of the work.

The pop-up she was right to decline: the message about the device being obsolete and needing a new version is manufacturer utility software, not a system requirement. It has no bearing on whether the drive works, and installing software in the middle of a fault is exactly the wrong moment — anything that writes to the drive works against the structures a reconstruction needs. Ignoring it was correct.

The update timing: a system update writing extensively while a drive is connected, followed by a shutdown, is a very ordinary way for filing structures to be left mid-write. That is consistent with everything she describes and points away from drive failure.

What to avoid now: every offer to scan, repair or format, and any attempt to add files to the free space Windows believes exists.

On the bench

The drive was imaged write-blocked before any repair, so that everything happened against a copy. On the image the allocation records — the ones her properties dialogue had already proved were readable — were used as the starting point, and the directory structures reconstructed from the filesystem's backup copies and from what the allocation data described. That route returns the folder tree and filenames rather than a flat carve, which on three years of organised scanning is most of the value. Signature carving swept alongside for anything beyond structural repair, and every image was validated by rendering at full resolution.

The outcome

The directory reconstructed from surviving allocation and backup records, with the folder structure and filenames returned intact. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose drive has lost its own name: the volume label lives inside the filesystem, so a drive that now shows a generic name is telling you those structures are not being read — an early and specific sign; but properties reporting the drive as full is genuinely good news, because used-space figures come from the allocation records rather than from listing files, so the disk is being read and the accounting survives while only the directory is missing; those are stored separately and filesystems keep backup copies, so the tree and filenames can usually be rebuilt rather than carved. Ignore manufacturer software prompts during a fault.

Drive showing a generic name instead of its own

Take both of your observations seriously, because together they're encouraging. A drive displays the name it was given, and that label lives inside the filesystem — so showing "Local Disk" instead means those structures aren't being read, which is the first and most specific sign of a directory problem. But if properties still reports the drive as full, or shows a sensible used-space figure, that's genuinely good news: those numbers come from the filesystem's allocation records rather than from listing files, so the disk is being read successfully and only the directory naming your files is missing. Your photographs are physically there and the disk knows the space they occupy. Don't install any manufacturer utility that pops up telling you the device is obsolete — that's not a system requirement and writing to the drive now works against you. Refuse every scan, repair and format.

Drive that lost its name and shows as full?
Those two facts are hopeful — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, directory rebuilt from surviving allocation and backup records, folders and filenames returned.
Request a quote online →

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.

0141 404 0294