Data Recovery Case File · Power Users, Developers & Linux · The Different Geometry
Healthy drive, wrong translator: how an external case can make a full disk look blank — and how a Linux filesystem's redundant records brought every photograph home with its name
The timeline mattered, so he gave it properly. A 3TB hard drive, only a couple of years old and about 130 hours of use, formatted at installation in his Linux desktop and dedicated to one job: "storing my photos — about 800GB of images." Then the move that started everything: the desktop retiring from daily duty, the drive re-housed in an external case. On his Windows laptop: wouldn't mount. Back in the desktop: "it wouldn't recognise it and mount there either." Then the spiral, reported without varnish: "I reinstalled the OS on my desktop several times, trying various different Linux versions, but none was able to find and mount the drive"; back in the case, a partition-finding tool, "without success"; then a free recovery application, which "found about 30,000 files" — anonymous, structureless, the carver's usual heap. Three decodes below: the two innocent non-faults that launched the spiral, the one place it likely drew real blood, and the property of his chosen filesystem that made the ending kind.
| Media | 3TB hard drive, ~130 hours total use — 800GB of photographs, Linux-native filesystem, recently moved from internal desktop service into a USB external case |
| Reported attempts | No mount on Windows via the case · no recognition back in the original desktop · several Linux reinstalls across distributions · a partition-finding tool: nothing · a free recovery application: ~30,000 anonymous files carved |
| Fault class | Enclosure sector-geometry mistranslation compounded by damaged partition structures — the drive mechanically healthy and barely worn throughout |
| Equipment used | Native-interface imaging, bypassing the case entirely · geometry normalisation on the image · Linux-filesystem reconstruction from redundant superblock records · full structure-preserving extraction with names, dates and folders |
The decode: two non-faults, one wound, and the filesystem that keeps spares
Non-fault one — Windows was never going to see it: the drive wore a Linux-native filesystem, which Windows does not read unaided. Its silence on the laptop was compatibility, not damage — the least alarming symptom in the whole story, arriving first and setting the tone anyway.
Non-fault two — the case that spoke a different geometry: the genuinely disorienting moment — the builder desktop no longer recognising its own drive — has a known villain. USB external cases contain a translator chip, and on large drives of this class, many translators re-describe the drive's sector geometry to the computer: same territory, different grid references. Partition tables written under one description look misaligned or absent under the other. Present the drive through the case, and even its home system can be handed a map that no longer matches the terrain — a full, healthy disk made to look blank by translation alone. Nothing on the platters had changed. The description of them had.
Where the spiral drew blood: the repeated OS reinstalls and tool passes were solving that phantom — and somewhere in the sequence, the drive's real partition structures took a wound; the honest candidates are the translator writing its assumptions or an installer's hand passing too near the patient. Which is why the recovery application then "worked" in the saddest way available: thirty thousand carved fragments, stripped of the names and folders that make 800GB of photographs an archive rather than a haystack. One mercy ran under everything: 130 hours of use meant a barely-churned surface — the photographs themselves lying in long, undisturbed runs.
The filesystem's own insurance: his Linux format keeps redundant copies of its defining records distributed across the volume precisely against days like this. Damage the primary, and the spares remain — findable, consistent, and sufficient to rebuild the whole structure. His choice of filesystem, made casually at installation years ago, turned out to be the best decision in the case.
The recovery: past the translator, rebuilt from the spares
The drive was imaged on native connections — no case, no translator, the geometry read as the platters actually hold it — and everything ran on the copy. The surviving redundant records were located and cross-checked, the filesystem's structures rebuilt from them, and the volume stood up whole: directory tree, filenames, dates. The 800GB came across as an archive again — folders of shoots and years, verified by opening images across the span — with the carver's thirty thousand anonymous orphans rendered happily irrelevant.
The outcome
The photograph collection delivered structure-intact on new media, and a short technical note for the power user he is: what the case's translation did, why the desktop was deceived, and how the redundant records paid out. Free assessment, one fixed written figure including VAT, no recovery, no fee — and the external case retired from service with a caution against re-employment on any drive that matters.
Drive moved into an external case — now no system sees it properly
Stop before the spiral: a large drive that goes "blank" the moment it enters a case has usually met a translation problem, not a failure — and the drive's home system can be deceived through the same case, so test it back on a direct internal connection before believing anything. Keep OS installers well away from a patient drive. Read a carver's anonymous thousands as a method's confession, not a result. And if you run Linux-native formats: the redundant records are your parachute — provided nothing keeps writing while you fall.
It's usually translation, and the structures usually survive — call Edinburgh Data Recovery on 0131 202 0491; read natively, rebuilt properly, one written figure, no recovery, no fee.
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.