We are booking in new cases · Weekdays, 9am–5:30pm Urgent case? Call 0800 6890668
MHDR Maidenhead Data Recovery 0800 6890668 Send it in
MHDR / Casebook / The Cloud Drive Went Quiet, Then Strange

NAS & RAID · job file · MHD-2025-6928

The My Cloud Ground Away, Then Turned Red.

Since 2018 the box had lived in the back room of a Windsor framing shop, up on the guillotine cupboard where nobody looks at it, and nobody had. Then the counter staff began remarking on a grinding sort of hum, which we all put down to the compressor. Ten days later nobody could open the shared folder, and the light on the front had settled to solid red. WD would replace the unit under warranty; its contents remained, as they always do, the owner’s problem.

Outcome confirmed by the customer No names anywhere

Much the same fault? Call us.
0800 6890668

In everyday terms.

A single-bay My Cloud holds one copy of everything and no more. Set aside the app and the badge and you are left with one hard disk, plus a small computer whose whole purpose is to publish it — and every layer that computer offers, the shares, the web page, the status light, stands on that disk alone. When it stops answering, they all go dark in the same instant and for the same reason. One door, and behind it nothing but the disk. The half-noticed noise the shop had put up with for two weeks was that disk giving notice.

What the bench used here.

How a job is handled →
ToolWhy we used itWhat it brings
DeepSpar Disk Imager 4Worked head by head from a new map once the stack had been changedHead map first, then head-by-head reads, holding resets, timeouts and the power line steady
PC-3000 Data ExtractorKept resets and timeouts tight while a worn mechanism did the workThe PC-3000's imaging module, working under firmware-level control
UFS Explorer RAID RecoveryUnpicked the appliance’s stacked Linux volumes so the shares came back as sharesUnderstands the layers a NAS stacks on top of its disks, not just the array

The lab work.

01

Out of the enclosure, and assessed as a disk

On the bench and free of its case, the 8TB disk answered quickly: its heads had worn past dependable reading, and the grinding note was the sound of them failing at it. All the appliance’s software can see is storage that has stopped replying, which is why the shares, the dashboard and the light went out at once.

02

Replace the heads, then measure what the wear had taken

A donor stack from a matching drive restored the mechanism, and a map was drawn before any serious reading began. One region had paid for the shop’s patience: the till PC had spent hour after hour writing its order folder across to an appliance whose heads were already failing, and that stretch of surface showed what it had endured. Left to itself, no appliance has any notion of when to stop trying.

03

Treat the image as what it is: a Linux machine

WD layers its storage as stacked Linux volumes, and a tool that expects to find NTFS will make nothing of them. Taken on the terms the box itself uses, the image unfolded into the shares the counter had always known: the order book, customer artwork, job folders, rather than ten thousand files named with numbers.

How the job closed.

Everything the shop had asked for returned on new media, with a single exception stated plainly. A run of older customer artwork scans fell inside the worn band; those could not be read, and the report names them. The unit went back for its warranty replacement carrying nothing.

The point: Nothing tells an appliance to stop, so it will grind a failing disk for weeks. Chase a new noise; a one-disk box is storage, not a backup.

Does any of that match your case?

Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.

0800 6890668