Data Recovery Case File · Home NAS · The Appliance That Won't Hand It Over

Structurally fine and totally inaccessible: a My Cloud Home's private data layer, translated at last

The self-diagnosis in this enquiry was the most technically accurate this archive has received for its product class — and the product class is exactly why it still needed us. He'd removed the drive from a WD My Cloud Home; it spun up and enumerated over USB perfectly; he could see its multiple Linux-based partitions, including the 1.85TB data partition; he correctly suspected LVM or XFS; and he'd tested it against both Windows and his Synology NAS — a genuinely well-equipped attempt — with no mount from either. His conclusion, verbatim and vindicated: "the drive is structurally fine — just inaccessible due to the file system or enclosure software dependencies." Precisely so. And the dependency in question is deeper than most owners ever discover before this exact moment.

Why even his Synology couldn't read it — the Home difference

Here's the decode his excellent triage deserved. The My Cloud Home is not, despite the family name, a conventional NAS storing files on a mountable volume: it's a cloud-first appliance whose firmware manages the user's data through its own application-level storage layer — content indexed and organised by the device's software and tied to its account system, sitting inside those Linux partitions in a structure that belongs to the product, not to any public filesystem standard. That's why the failure pattern was so absolute and so clean: Windows saw foreign partitions; his Synology — fluent in every mainstream Linux filesystem — saw structures that parse but contents that don't resolve into browsable files, because the resolving was always the appliance's private job. Nothing was corrupt; nothing was encrypted against him in the ransom sense; the drive was simply speaking a dialect only its own dead-or-discarded enclosure ever spoke. His "enclosure software dependencies" phrase was the whole diagnosis. The recovery, correspondingly, is an act of translation rather than repair.

The extraction — the dialect, translated

The drive was imaged once, write-blocked — healthy hardware or not, originals stay untouched — and the translation ran on the copy: the appliance's storage layer parsed as the structure it is, the application-managed content walked at the level where his photos and videos actually live, and the collection reassembled into ordinary files — names recovered where the layer preserved them, the remainder organised by the images' and videos' own internal dates, which for a photo archive is the organisation that matters. Verification meant opening pictures and playing footage across the span; delivery meant a plain external drive in plain folders, readable by Windows, his Synology, and everything else he owns — the data's first day outside the dialect since the appliance first ingested it. His delivery note carried the one recommendation his setup had already half-implemented: the recovered archive went onto the Synology as standard files, where the next dead enclosure can't hold them hostage.

Outcome

Full recovery of a drive that was never broken — and the product-class warning this page exists to publish. Before trusting any storage appliance with your archive, ask the question almost nobody asks in the shop: if this box dies, can the bare drive be read by anything else? Conventional NAS units mostly answer yes-with-effort (their layers are standard, as other cases in this archive show); cloud-first appliances of this design answer no — the data's shape depends on the product's own software, and a dead enclosure means translation, not just extraction. That's not a reason to avoid them; it's a reason to run a real backup beside them, and to know — as this owner now does, the vindicated way — that "structurally fine" and "accessible to me" are separate properties, purchasable separately.

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.