As I have seen many questions about debricking (recovering) the MyCloud, I figured I would write up a guide for the tech savvy users that get stuck. This is a last hope recovery procedure and will erase all data. Please download your appropriate image below and follow the steps.
DISCLAIMER: This assumes your warranty is already void. DO NOT open your MyCloud if you intend to keep your warranty. I am personally writing this procedure and I have zero ties to Western Digital. They would probably not encourage this.
Second USB drive of 8GB size or higher for the extracted MyCloud image from above (NTFS or exFAT required for 4GB+ file sizes)
Extract the appropriate MyCloud .7z file to a USB drive and rename the extracted file to “mycloud.img”.
Open your MyCloud’s case being very careful not to break the tabs. You can still close it if you do break the tabs but it won’t be as secure of a fit. I followed this video.
Carefully remove the hard drive from the enclosure and then remove the screws that hold the board to the hard drive.
Power off your computer and then connect your computer’s SATA cord to the MyCloud hard drive.
Boot the GParted Live disk, choosing low end graphics mode if you get a black screen when you first let it fully boot.
When the GParted graphical application comes up, ignore any errors if prompted and do not edit any partitions. In the drop down list in the top right corner, figure out the device paths of your WD MyCloud and USB stick and make note of those. Example: /dev/sda for WD MyCloud, /dev/sdb for USB stick that has recovery image
Close the GParted graphical application and open a terminal session. Mount your usb drive if necessary and change into the directory of the extracted image. Follow the example below, replacing /dev/sdb with the device path of the USB stick that contains the recovery image.
mkdir /mnt/usb; mount /dev/sdb /mnt/usb; cd /mnt/usb
In terminal type the following, replacing /dev/sda with the device path of your WD MyCloud. Don’t worry if it errors, this just ensures the drive is unmounted.
umount /dev/sda
In terminal type the following, replacing /dev/sda with the device path of your WD MyCloud. Make sure the input file is .img extension and is NOT the .7z archive file! This command will write the recovery image back to the MyCloud giving you a fresh drive. You will see very little feedback while this occurs.
dd if=mycloud.img of=/dev/sda
Hopefully dd will take some time and then report success. If so, run “shutdown -h now” to shutdown the GParted Live disk. You are done!
Hook the MyCloud hard drive back to the MyCloud board and attempt to power on the drive. Hopefully you will get the blue light after a bit.
Could anybody confirm that it is possible to open the case without breaking the tabs? Imho they are constructed in such a way that this is not possible.
Point 11)
If you are lucky MyCloud will boot to blue light, but most probably you have a faulty situation because these images are not ok.
I wonder why WD does not make available correct images.
You can see in the angle of the video when he opens it, no broken tabs.
I don’t know why you say the images are bad… I PERSONALLY restored using the 2tb one with zero issue. I understand you may have issues with certain bugs but calling it unstable or faulty is just not true.
For anyone curious, the 3tb file I link to in first post is same md5 as the 3tb image mentioned in the other thread. Thomas, sorry I can’t help further. Good luck!
This was the only solution that worked for me. Â I have the 4TB model and flashed it with the 2TB image. Â I was able to resize it with my Linux computer using fdisk, deleting the ext4 partition and creating that same partition number again using all the space available. Â The WD software automatically formatted the blank partition. Â So this was a quick fix that works well.
Glad to hear! Thanks for the resize tip for 4TB. If anyone would be so kind as to point me at a full virgin image for the 4TB, I’ll gladly update the original post.
I have restored my 3TB with a 2 tb img. It works fine, but only with 2 tb free space
I try to resize by following the guide, but when i do this, i Can acces the drive? My cloud, is just blinking blue, but i can acces either the Dashbord or any mountet drives
I have restored my 3TB with a 2 tb img. It works fine, but only with 2 tb free space
I try to resize by following the guide, but when i do this, i Can acces the drive? My cloud, is just blinking blue, but i can acces either the Dashbord or any mountet drives
Does anyone know where to get a 3tb img?
It is not really necessary to have a 3TB image.
Describe how you tried to resize it, most probably you did not exactly what is required.
Hm difficult answer… If the drive can’t be recognized currently, you may be out of luck. That being said, I would expect dd could still at least try to read the raw drive and save it to an image. from that maybe you could find some tools online to recovery your files from the corrupt disk. if even dd is unable to save the drive though (through something like dd if=/dev/yourdrive of=/output/of/drive.img) then I would expect it’s a physical issue with the disk and the only way to get it would be through professional disk recovery services ($$).
I’ll just describe my solution (just in case it will be useful to anyone).
Firstly, I’ve used SATA - USB convertor, so this way I’ve connected disk to my notebook.
dd command failed to me: it hanged for 6 hours without completion. while dd for 3Tb image worked flawlessly in minutes, but the firmware there was broken or not compatible to my disk.
So’ ive uploaded the firmware via Ubuntu disk utility as backup update and assembled drive back. It ran correctly w/o errors.
Secondary, I’ve made factory restore, so I was able to register users again and use SSH. Still there was a problem with diskspace of 2Tb instead of 3 physical terabytes.
Then I’v tried old-school unix fdsik utility to alter /dev/sda disk and resize or delete/create sda4 partition. Fdisk showed that it is not the best utility as GPT partition been used and recommended to use parted utility. Parted utility could be a solution here, but it showed that it cannot make changes to partition unless partiton is used by drive. Umount comand did not helped. Looks like there have been some autoreconnect scripts. So I’ve googled till gdisk utility, which actually equal to parted, but can work without dependency to used by OS partitions. So, it showed broken GPT partition table and I fixed it by using options ( r    recovery and transformation options (experts only), d use main GPT header (rebuilding backup)), then I’ve ran w and made a reboot. GPT fixes were needed due to the fact, that utility wasn’t able to use unalocated space before them, maximum amount was the same as for previous partition. Then I’ve deleted 4th partition and created a new one with extended diskspace. Then again w and reboot.
After reboot it was still shown 2Tb in dashboard, so I’ve made yet another factory restore and ran first configuration utility. Next setp - I’ve loaded firmware update from 14.06.2014 and still using it flawlessly.
I just get bluelight but cant acces it 
