On a side issue, my problem with USB loading with certain external USB drives persists.
Back to the topic at hand. I’ve had problems with most other methods of unbricking when using an alternate hard drive from the one included with the original WD My Cloud device. Its apparent that what works for one person doesn’t always work for the next person. Could be the methods that push a single “.img” file to the hard drive may cause problems if the drive isn’t the standard size that comes with the WD My Cloud. Or possibly if the drive was formatted differently prior to being used in the WD My Cloud enclosure. Or its some other issue.
What is certain is that for some, when they either unbrick and upgrade, or just upgrade, the Dashboard doesn’t load properly or at all. This appears to indicate something isn’t loading properly post firmware upgrade. Quite possibly (or not) due to some sort of GPT issue on the hard drive. It would be nice if there was an easy fix that didn’t require one to go through various methods or steps to reload the firmware from these non sanctioned, non official WD supported methods.
Below are the general steps I used which I modified from this link (from the OP post). I make no guarantee it will work for others. It worked in my instance to setup a 1T Seagate drive for use in the My Cloud enclosure. I haven’t gone back and tested the initial 250GB drive I put in the WD My Cloud enclosure that had the problem of missing Dashboard post upgrade from 03.04.01-230 to 04.04.01-12. At some point I plan to test that drive to see if fixing the GPT entry fixes the failed Dashboard loading issue. Edit to add: Just tried the 250GB drive and it too was able to correctly update to the latest firmware and the Dashboard loads properly using the directions posted below (started at step 1 and did the GPT rewrite).
One can copy the following into another document (Word or notepad) for easy use and printing out.
How to unbrick, replace or restore original WD My Cloud single hard drive firmware:
These basic directions assume you have a 4GB or larger USB flash/pen drive, a computer with SATA connectors or some form of external SATA enclosure/docking station, basic knowledge of how to boot PC using a boot disc, basic knowledge of how to use Linux.
Note: Use and proceed at your own risk!!!
• Download original_v3.04.01-230.tar.gz to a flash drive: https://drive.google.com/file/d/0B_6OlQ_H0PxVQ2l5MTNvQk1xSUU
• Used Ubuntu Live/Boot CD: http://www.ubuntu.com/download/desktop
• To avoid damaging non WD My Cloud hard drives remove or disconnect them from the computer.
• Backup any data on your My Cloud as these directions may result in the erasure of all data on hard drive.
• Insert USB Flash/Pen drive containing the file original_v3.04.01-230.tar.gz (or it's extracted contents) into PC before booting with Linux Live/Boot CD
• All terminal commands run from Root user or Sudo. For purposes of this guide Sudo was used.
• After booting with Live/Boot CD open terminal window by typing:
[ctrl] + [alt] + [t]
Then type:
sudo apt-get update
sudo apt-get install mdadm parted
To install new/used hard drive start with step 1.
To repair existing bricked WD My Cloud hard drive start with step 13.
Note: Starting from step 1 will erase hard drive contents. If hard drive contains important data, backup hard drive before proceeding.
1. Find the My Cloud hard drive name (sda, sdb, sdd, sdc, sde, etc.) by typing:
sudo fdisk -l
or
sudo parted -l
Note: For these basic directions "sdb" is used.
2. If you get GTP errors running fdisk or parted then try the following command:
sudo gdisk /dev/sdb
Then type "o" then type "w" to fix GTP errors.
3. Run parted utility:
sudo parted /dev/sdb
4. Type "print" to see what partitions exist on hard drive.
5. If any partitions exist, remove each of them by typing "rm 1" (where 1 - number of partition)
6. Create new table:
mklabel gpt
mkpart primary 528M 2576M
mkpart primary 2576M 4624M
mkpart primary 16M 528M
mkpart primary 4828M -1M
mkpart primary 4624M 4724M
mkpart primary 4724M 4824M
mkpart primary 4824M 4826M
mkpart primary 4826M 4828M
set 1 raid on
set 2 raid on
Type "quit" to exit parted.
7. Format data partition:
sudo mkfs -t ext4 /dev/sdb4
8. Reboot computer, boot back to Linux Live CD. From command line run:
sudo apt-get update
sudo apt-get install mdadm parted.
9. Run sudo fdisk -l or sudo parted -l and note the drive names just incase the /dev/sd* location changed.
10. Create main RAID partition, type:
sudo mdadm --create /dev/md0 --level=1 --metadata=0.9 --raid-devices=2 /dev/sdb1 /dev/sdb2
11. Wait for RAID creation to complete, type:
sudo watch cat /proc/mdstat
Wait to 100%. Then type:
[ctrl] + [c] for close.
12. Stop auto-loaded raid, type:
sudo mdadm --stop /dev/md0
If /dev/md0 not found type the following to find RAID mount point:
sudo ls /dev
or
sudo grep md
13. Start normal raid (must be /dev/md0), type:
sudo mdadm -A /dev/md0 /dev/sdb1 /dev/sdb2
14. Using terminal window navigate to USB Flash/Pen drive location. Example: /media/ubuntu/<drive name> If the contents of file original_v3.04.01-230.tar.gz have not been previously extracted on the USB Flash/Pen drive, type:
sudo tar xvfz original_v3.04.01-230.tar.gz
15. Upload backup images to WD's hdd:
sudo dd if=kernel.img of=/dev/sdb5
sudo dd if=kernel.img of=/dev/sdb6
sudo dd if=config.img of=/dev/sdb7
sudo dd if=config.img of=/dev/sdb8
sudo dd if=rootfs.img of=/dev/md0
16. A Note: If for what ever reason the My Cloud fails to boot (white LED), or problems with upgrade to newer firmware failing/not working (ex. UI fails to load) try the following alternative step.
sudo mdadm --stop /dev/md0
sudo dd if=kernel.img of=/dev/sdb5
sudo dd if=kernel.img of=/dev/sdb6
sudo dd if=config.img of=/dev/sdb7
sudo dd if=config.img of=/dev/sdb8
sudo dd if=rootfs.img of=/dev/sdb1
sudo dd if=rootfs.img of=/dev/sdb2
17. Shutdown PC from terminal window by typing: shutdown -p -H 0 Or use "Logout" from menu.
18. Disconnect hard drive from computer/external connector and connect to WD My Cloud circuit board. Then connect power to the My Cloud circuit board to turn on WD My Cloud. Boot process may take 5-10 min or longer. LED light should change from White to Blue.
Note: If the WD My Cloud fails to boot with either a solid white or red LED, then reattach hard drive to PC/docking station, reinsert USB Flash/Pen drive, boot back into Linux, go back to step 13, then proceed to step 16 to push the three "img" files to their respective partitions, shut down PC and try booting the hard drive again with the WD My Cloud circuit board.
If the drive still fails to boot (white or red LED), the GTP entry probably needs to be repaired. If that is the case try step 2 above to rebuilt the GPT entry (will probably erase drive contents) and then perform the rest of the subsequent steps. If step 2 doesn't work then start from scratch at step 1. Backup any files if needed from sdb4 (the mountable ext4 partition containing the shares) prior to starting from step 1.
19. After WD My Cloud boots to Blue LED, access the Dashboard with web browser (http://wdmycloud/). Proceed through initial access screen then enable SSH on the Settings -> Network -> Network Services section. Often the capacity will be incorrectly listed, fix by selecting Quick Restore (or Quick Factory Restore) from the Settings -> Utilities section. The device will reboot and rebuild the system files.
20. After factory restore has been performed and WD My Cloud boots, restore any settings (like Static IP) as needed and update the firmware if needed. Be patient. If there was existing data on the hard drive it may take the WD My Cloud OS a long time to scan/catalog the files.
Notes:
How Linux sees drive contents of a 250GB drive:
Number Start End Size File system Name Flags
3 15.7MB 528MB 513MB linux-swap(v1) primary
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
5 4624MB 4724MB 99.6MB primary
6 4724MB 4824MB 101MB primary
7 4824MB 4826MB 1049kB primary
8 4826MB 4828MB 2097kB primary
4 4828MB 250GB 245GB ext4 primary
