Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Casebook / My Cloud Drive Went Quiet, Then Strange

Case file · NAS & RAID · BDR-2025-0928

My Cloud Drive Went Quiet, Then Strange.

The My Cloud has sat quietly on the router, hooked up to my router and I haven't touched it, but recently it started making a strange sound and disappeared from both the network and USB. The warranty is fine about covering the hardware, but says the data is not included.

Outcome verified with the client Details anonymised

Same symptoms on your desk?
01273 964902

The decode.

A network drive is simply an ordinary hard drive placed into a special box (the "clever" part) and those special boxes can fail in one very distinct way: if the actual hard drive in them ceases functioning, all access paths will vanish instantly. This simultaneous disappearance is how you know it isn't a network problem, because if there was a network problem your USB connection should still work. If there was a bridge failure, your network connection should still function. But losing both access routes simultaneously (and with a new noise) tells you exactly where the problem lies: with the mechanism inside the box.

Equipment on this case.

How a job runs here →
The systemWhat it did on the dayWhy this tool
DeepSpar Disk Imager 4Head-mapped imaging once the mechanism was made stableHead-map-aware imaging with per-head timeout, reset and power-cycle control
PC-3000 Data ExtractorManaged read passes with reset control on a drive that had been strugglingThe imaging half of the PC-3000 platform, driven by the firmware half
UFS Explorer RAID RecoveryParsed the My Cloud's Linux volume layout from the imageReads NAS volume managers as they actually are, not as a flat array

At the bench.

01

Get the drive out of the box and diagnose it as a drive

We opened the enclosure and examined the drive individually. It turns out that the strange sound was due to a mechanical failure of the head assembly (which the NAS firmware interpreted as a non-responding drive, resulting in the loss of visibility via both access routes).

02

Repair enough to read, then map the surfaces

We replaced the faulty components with matched parts and created a head map before doing a large read of all of the surfaces. Unfortunately, the surfaces suffered some degree of physical damage during the time the NAS continued attempting to access it while it was malfunctioning. Unattended network storage tends to continue retrying for longer periods of time than humans would continue attempting to access a drive that is known to be damaged.

03

Read the Linux layout, not a Windows one

After we completed the imaging, we then decoded the recovered image as it was originally constructed: as a Linux file system structure written by WD's firmware (not as a Windows NTFS disk). Once we did so, shares reappeared in their normal configuration. It is this structure that allows recovered data from a NAS device to be used instead of being merely available.

Where it ended up.

All of the data was recovered in full and copied onto new media, and then the empty enclosure was returned under warranty. The two sides of the dilemma have both been completely resolved, in the order they have to be.

What this case teaches: The manufacturer will repair/replace the hardware; however, nothing will restore lost data. Make sure to claim your hardware warranty after you've recovered your data from your failed device.

Recognise your own drive in this story?

The same rule applies for all cases previously shown: turn off the power first. Then allow your free diagnosis to complete prior to making a decision.

01273 964902