WD My Cloud Not Accessible? Don't Press That Reset Button.
UK WD My Cloud data recovery since 2002 — single-bay My Cloud, Mirror, EX2, EX4 and PR series. Units that vanish from the network, show a red or white light, or never finish booting. Free UK collection and free diagnosis.
What this means and what to do next
WD's My Cloud family spans everything from the single-drive units sold as ‘personal cloud’ backup to the multi-bay Mirror, EX2, EX4 and PR series used by small businesses. They share a common design: a small Linux system running WD's OS on flash-backed firmware partitions, with your data on an ext4 volume — plain on single-bay units, on top of mdadm RAID on the multi-bay models.
When a My Cloud stops being accessible on the network, the cause falls into one of three areas. The unit's own electronics or firmware have failed (constant white/blinking LED, boot loops, dead unit); the drive inside has failed (red LED, clicking, or the unit boots but the share is empty); or the data volume has been corrupted — often after a power cut, a failed firmware update, or an interrupted RAID rebuild on the Mirror/EX models.
All three are recoverable, but My Cloud units punish improvisation. The reset and restore functions are close together in both the physical button behaviour and the dashboard, and WD's own recovery guidance for bricked units involves writing to the drives — acceptable for rebuilding the unit, destructive if you still need the data. The lab route is simpler and safer: the drive comes out, gets imaged, and the ext4 volume (and mdadm layer on multi-bay units) is reconstructed from the image. More on our NAS recovery service →
Why a WD My Cloud disappears from the network
1. Failed firmware update or corrupted system partitions. Symptom: the LED never reaches steady blue, the dashboard is unreachable, and the unit may loop or sit blinking white indefinitely. The Linux system partitions are corrupt but the data volume is usually untouched. Recovery: image the drive and read the data volume directly — we don't attempt to revive the unit's firmware with the original drive inside, because WD's unbrick procedures overwrite parts of the disk.
2. The drive inside has failed. Symptom: red LED, clicking or beeping from the enclosure, or the unit boots to an empty share. Single-bay My Clouds live or die with their one drive, and the drives inside — WD Red or Green depending on age — fail like any mechanical drive: heads, motor or electronics. Recovery: standard hardware data recovery, with cleanroom head-stack work where needed, then reconstruction of the ext4 volume from the image.
3. Power cut or unclean shutdown corrupted the volume. Symptom: the unit appears on the network but shares won't open, or the dashboard shows the volume as unavailable. The ext4 journal or the mdadm metadata on multi-bay units was left inconsistent. Recovery: reconstruct from an image and repair the filesystem on the copy. Left alone, this is one of the most complete recoveries there is — unless a restore option has been used first.
4. Accidental System Restore or factory reset. Symptom: the unit works perfectly — but the shares are empty, because a long-press reset or a dashboard restore rebuilt the data volume. Recovery: stop using the unit immediately; every hour it runs writes further data over the old volume. A fresh mkfs typically overwrites only a small fraction of the disk, so prompt lab recovery of the previous filesystem's contents has a good outcome, falling to nothing as the unit keeps running.
How Data Clinic recovers a WD My Cloud
Start with the free diagnosis: tell us the model, what the LED is doing, whether the unit responds at all, and what has been tried — in particular whether any reset has been pressed. We'll tell you honestly whether it sounds like electronics, drive failure or volume corruption, and what the likely outcome is. Collection is free from any UK address.
In the lab the enclosure is opened and the drive removed — the My Cloud chassis is never trusted with the original drive again. Healthy drives are imaged immediately; failed ones go through electronic or cleanroom mechanical repair first. On Mirror, EX and PR units every bay is imaged and the mdadm layer reassembled from the images.
The ext4 data volume is then reconstructed and your folder structure extracted — including the Time Machine backups and camera uploads these units so often hold. Data is returned on new media. Standard turnaround is 5–20 working days, Priority 2–5 days, with a 24–48 hour emergency option for business-critical cases.
Get a free initial diagnosis in 60 seconds
In the tool below, choose RAID/NAS/Server and the symptom that matches your My Cloud — not visible on the network, red LED, or won't finish starting up. The tool routes NAS cases straight to our team.
What our customers say
"Three years of family photos on a drive that suddenly failed. Data Clinic collected next day, kept me updated through the cleanroom work, and got everything back. Worth every penny."
"Honest, fixed-price, no-fix-no-fee. Quoted by another lab at three times the price. Recovered 100% of my files."
"Reasonable cost, clear communication, and they were straight with me about what was recoverable and what wasn't. Recommended."
Frequently asked questions
My My Cloud has a solid red light. What does it mean?
On most My Cloud models a red system LED means the unit has detected a fault — commonly a failed or failing drive, sometimes an overheated unit or corrupted system state. If the data on it matters, treat a red light as a signal to power down and get it assessed, not to experiment with reboots and resets.
I pressed the reset button and now my files are gone. Can they come back?
Often, yes — if the unit is stopped quickly. A restore rebuilds the data volume with a fresh filesystem, but that process overwrites only a small part of the drive; your files' contents largely remain until new activity overwrites them. Unplug the unit now and don't let it run another backup. Recovery success falls the longer the unit keeps running.
Can I open the enclosure and connect the drive to my PC instead?
The drive won't be readable in Windows — the volume is ext4 on a Linux system, and on multi-bay units it's inside an mdadm RAID layer, so Windows will offer to initialise the disk (declining that offer is essential — initialising writes a new partition table). If the drive is healthy, a Linux machine can read it; if it's failing, every minute of DIY connection makes lab recovery harder. When in doubt, image first.
Do you recover the multi-bay models — Mirror, EX2, EX4, PR4100?
Yes, all of them. The multi-bay units use mdadm RAID under WD's OS — RAID 1 on the two-bay models by default, RAID 5 commonly on the four-bay ones. We image every drive and reassemble the RAID from the images. For 2-disk RAID 0/1 units, recovery is on a No Data – No Fee basis.
How long does a My Cloud recovery take?
Standard service is 5–20 working days and covers most cases; Priority is 2–5 working days; the emergency tier targets 24–48 hours where a business depends on the data. Diagnosis is free and comes with a fixed-price quote, so you'll know the cost before deciding.