Data Recovery Case File · Portable Drives · The Catalogue Without the Library
Listed, sized, and unreachable: a Passport serving its index while its contents fail — and the files brought out from behind the listing
The cruellest symptom pattern in portable-drive failure is the one that looks almost fine. His 1TB My Passport Ultra "stopped working" in the most deceptive way possible: plug it in and Windows recognises it, the file directory loads, every file appears with its name and size — and then the wall. Videos "can't be played"; other files won't open; and copying anything off fails with "can't read from the source file or disk," the copied file landing at zero bytes despite its listed size. His question was the practical one — what would full recovery cost? — and the answer starts with why a drive can be a perfect librarian and a failed library at the same time.
| Device | WD My Passport Ultra 1TB — full directory tree visible with names and sizes; all content access failing |
| Reported symptoms | Drive recognised; listing loads completely; opens fail across file types; copies abort with source-read errors, producing 0-byte output files |
| Fault class | Media/firmware degradation across the data regions — the compact catalogue territory still serving, the contents behind it failing |
| Equipment used | DeepSpar USB Stabilizer 10Gb · ACE Lab PC-3000 Express + Data Extractor |
The decode: catalogue and contents live in different places
A volume's listing — every name, every size, the whole browsable tree — lives in the filesystem's compact paperwork: small, dense, endlessly re-read structures occupying a sliver of the drive, often the healthiest-served territory it has. The contents are everything else: a terabyte of scattered data across the wide surface. His drive had split exactly along that line — paperwork territory still answering, data territory failing its reads — and every symptom follows. Explorer shows the complete catalogue because the catalogue genuinely reads. Videos won't play because playback requests the actual content and the requests die. And the zero-byte copies are the split made visible in one artefact: the copy engine creates the destination file, asks the source for its contents, receives errors instead — "can't read from the source file or disk," Windows' honest wording — and abandons a container it never got to fill. The listed size was the catalogue's claim; the empty copy was the surface's answer. Read correctly, the pattern is quietly good news wrapped in a scare: the paperwork's survival means the map of his terabyte is intact, and the data behind it is failing to serve, not proven to be gone — the distinction on which this entire fault class turns. His restraint completed the setup: no repair tools, no repeated mass-copy attempts marching failing territory, just the symptoms noted and the enquiry sent.
The recovery
On the PC-3000 through the USB Stabilizer, the drive's retry behaviour was retired and its degraded condition addressed at the level desktop copying can't reach — then the surviving catalogue earned its keep as the plan: the filesystem map banked first and used to sequence the imaging, cooperative regions at pace, the failing data territory negotiated last in bounded, error-managed passes that recover rather than abandon. Coverage closed in the high ninety-nines. From the image, the listing he'd been staring at finally connected to its library: files opening, videos playing, copies completing at their true sizes — verified across the set — and delivered on new media, with the small residue of genuinely unrecoverable territory itemised by name instead of discovered one failed double-click at a time.
Outcome
Full practical recovery — and the pattern filed for every future owner staring at a perfect listing over an empty well: names-and-sizes-but-nothing-opens means the index outlived the surface, and the contents usually still exist behind it. The correct response is the counterintuitive one — stop browsing, stop retrying copies, stop letting anything walk that failing territory — because the catalogue will keep loading right up until it doesn't, and every content request in between spends reads the recovery needs. One session of noting symptoms, as his was, costs almost nothing. The listing was never lying to him. It just needed a reader that could reach the shelves.
Everything listed, nothing opening
Stop after the pattern confirms itself on two or three files — repeated opens and copy attempts all march the same failing regions. Don't run CHKDSK or repair utilities against source-read errors; the paperwork isn't the patient. Note a few filenames that matter most (the intact catalogue makes priority imaging genuinely effective), power the drive down, and have the contents read at hardware level. Zero-byte copies mean the containers were made and never filled — the originals are usually still waiting to fill them.
The shelves are still stocked — call Belfast Data Recovery on 028 9002 0144 before another copy attempt runs.
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.