Help unbricking WD MyCloud (messed up Debian system, solid white light)

I made the mistake of ssh’ing into the device and running apt-get update / apt-get upgrade. While I was ssh’d in, I noticed many binaries could not run due to the following error:

libstdc++ "ELF load command alignment not page-aligned"

I realzed too late that I couldn’t SSH in after that, and upon rebooting, got the white light of doom. The funny thing is, SMB was still running, but a port scan revealed that no other services were available. No SSH, no HTTP (hence, no dashboard).

I was able to remove the drive and plug it into my laptop via USB. I’m running archlinux on my laptop. When I plugged in the drive, here’s what the partition scheme looked like:

GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7C725966-C430-432A-B9AE-A0DA9A753C91
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 31597 sectors (15.4 MiB)

Number Start (sector) End (sector) Size Code Name
   1 1032192 5031935 1.9 GiB FD00 primary
   2 5031936 9031679 1.9 GiB FD00 primary
   3 30720 1032191 489.0 MiB 0700 primary
   4 9428992 5860532223 2.7 TiB 0700 primary
   5 9031680 9226239 95.0 MiB 0700 primary
   6 9226240 9422847 96.0 MiB 0700 primary
   7 9422848 9424895 1024.0 KiB 0700 primary
   8 9424896 9428991 2.0 MiB 0700 primary

My system also automatically provisioned the RAID1:

$ dmesg | grep raid1
[275859.614738] md: raid1 personality registered for level 1
[275859.614963] md/raid1:md127: active with 2 out of 2 mirrors

$ ls -l /dev/md
total 0
lrwxrwxrwx 1 root root 8 Aug 2 01:40 1_0 -> ../md127

 I mounted /dev/md127, and confirmed that this was the root filesystem. So, I downloaded the latest firmware from  here, and extracted the rootfs.img. I then used dd to write the image to /dev/md127:

$ sudo dd bs=32M if=rootfs.img of=/dev/md127

I double checked that /dev/md127 could mount successfully and was able to verify that the new filesystem was there and in-tact.

Unfortunately when I rebooted the MyCloud device it still had the white light, and this time I couldn’t ping it at all. I let it run overnight (in case it was doing a disk check or something) with no luck. Any ideas on what I need to do to get the rootfs installed/bootstrapped correctly?

See if the following link helps.

Thanks, I’ve read through that thread as well as every other one I could find on unbricking. There does not seem to be a solution in the particular thread you linked to.


I was finally able to restore my device by restoring from an entire disk image (not just the rootfs raid1 partitions). Not sure why restoring the rootfs by itself never worked, I’m guessing I must have messed something else up.  The image I ended up choosing was the one provided by Yo_Bubba in this thread (mycloud2tb_transmission_v03.04.01-230.7z). I was wanting to install transmission anyway, so that made it easier.

I ended up just using dd to restore the image onto /dev/sdb (after backing up my files):

dd if=mycloud2tb.img of=/dev/sdb

Then I just used gparted to resize the 2TB partition to 3TB (filling the rest of my disk space).