Case file · NAS & RAID · BDR-2025-0928
My Cloud Drive Went Quiet, Then Strange.
The My Cloud had lived quietly on the router — hooked up to my router and I haven't touched it
— until it started making a strange sound
and vanished from everywhere at once: no USB, no network. The warranty's fine print delivered the modern predicament perfectly: hardware covered, data not.
Same symptoms on your desk?
01273 964902
The decode.
A network drive is an ordinary drive in a clever box, and clever boxes fail loudly in one specific way: when the drive inside stops responding, every access route disappears simultaneously. That simultaneity is the diagnosis — a network fault would leave USB working, a bridge fault would leave the network working. Losing both at once, accompanied by a new noise, points squarely at the mechanism inside.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Head-mapped imaging once the mechanism was made stable | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| PC-3000 Data Extractor | Managed read passes with reset control on a drive that had been struggling | The imaging half of the PC-3000 platform, driven by the firmware half |
| UFS Explorer RAID Recovery | Parsed the My Cloud's Linux volume layout from the image | Reads NAS volume managers as they actually are, not as a flat array |
On the bench.
Get the drive out of the box and diagnose it as a drive
The enclosure was opened and the drive assessed on its own terms. The strange sound resolved to a mechanical fault in the head assembly — which the NAS firmware had been experiencing as a drive that stopped answering, hence the total disappearance from both access routes.
Repair enough to read, then map the surfaces
The mechanical fault was addressed with matched parts and a head map built before bulk reading. The surfaces had taken some damage from the period during which the NAS kept trying to access a failing drive — unattended network storage tends to keep retrying long after a human would have stopped.
Read the Linux layout, not a Windows one
The image was then parsed as what it is: a Linux volume arrangement written by WD's firmware, not an NTFS disk. Shares came back in their proper structure, which is what makes recovered NAS data usable rather than merely present.
The outcome.
The data recovered in full and returned on new media; the empty enclosure went off to claim its warranty. Both halves of the predicament resolved, in the only order that works.
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.