Case file · NAS & RAID · BDR-2025-0914
I Took the Cloud Disk Out and Still Can't Read It.
The My Cloud went unresponsive, and the owner did the intelligent things in order: pulled the disk, connected it directly, and armed Windows with a utility that allows access to linux drives via windows
. Still nothing — also can't access the files
. Most of the data existed elsewhere; the part that didn't was the point.
Same symptoms on your desk?
01273 964902
The decode.
The Linux-format barrier was the obvious suspect, and the utility ruled it out — genuinely good detective work. What that leaves is a fault below the filesystem: either the drive is failing to deliver reads reliably, or the volume structures themselves are damaged. A My Cloud complicates matters slightly by layering its own arrangement over standard Linux storage, so a tool that reads a plain ext4 partition may still find nothing recognisable to open.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Imaged the drive with timeout control the desktop utility could never apply | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| UFS Explorer RAID Recovery | Parsed the NAS volume layout — the layer beneath the filesystem | Reads NAS volume managers as they actually are, not as a flat array |
| R-Studio Technician | Cross-checked the recovered tree against what the owner expected to find | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Confirm what the owner's testing had already narrowed
The drive read erratically under bench conditions — completing some reads, stalling on others, with no clear pattern to the desktop tools that had been trying. That erratic behaviour alone was enough to defeat any utility running on a normal operating system, which retries and then gives up.
Image at the hardware level, patiently
With timeouts controlled and stalls handled by reset rather than abandonment, the drive imaged substantially complete. The weak regions were logged rather than fought, and revisited at the end when the rest was already safe.
Unwind the NAS layers, not just the filesystem
From the image, the volume layout was parsed properly rather than treated as a plain partition — the arrangement WD's firmware writes over standard Linux storage, then the filesystem within it. The shares opened in their proper structure and the files the owner hadn't backed up were located.
The outcome.
The uncopied remainder recovered and reunited with its backed-up siblings. The owner's methodical elimination had saved real diagnostic time; the imaging and the layer-by-layer parsing did the rest.
Related on the index.
More from NAS & RAID.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.