After booting up with Ubuntu Desktop and copy and paste the commands, My cloud is back up but with the original issue.
I am not able to see any shares on the network, I can see the shares from the dashboard.
I have added a new share and cannot see this as well. I have set Public share in the on and off position and have the same results.
Added a new user and password no change.
This unit is for backup for my existing my cloud and will only be used internally.
If I turn on the DLNA media server, this will show on the network. I have updated the firmware to the latest.
If you haven’t already, double check the My Cloud network settings to ensure the My Cloud is using the same workgroup name as the rest of the devices on the local network. Also ensure the IP address the My Cloud has assigned is in the same IP address pool range (example: 192.168.1.x / 255.255.255.0).
Also, if you haven’t already done so, perform a 40 second reset. It is generally or typically recommended one do a 40 second reset after unbricking their drive.
On the Windows PC’s ensure the firewall isn’t blocking access to the My Cloud or local network. Also while the following is for Windows 10 some will apply to Windows 7; see, if you haven’t already, the following post and pay attention in particular to steps Windows 10 Specific Method 1 through Windows 10 Specific Method 5.
I have just installed a replacement 3tb drive in a v2 MyCloud, using the “alternative” method of this guide. If anyone else has a gen 2 MyBook, this may come in handy
Format a usb stick as fat32. Not NTFS or exFat. Fat32.
Copy the 2 files to the fat32 formatted usb stick
Insert the usb stick in your pc
Do what it says here:
Use Debian/ubuntu or any other linux distro (USB/CD Live image)
All “/dev/sda” change to your disk! (List disks in system: “parted -l”)
If this is new disk or damaged (formatted) old, recreate partitions first:
parted /dev/sda
mklabel gpt
mkpart primary 1049kB 2149MB
mkpart primary 8591MB -1MB
mkpart primary 7517MB 8591MB
mkpart primary 2149MB 3222MB
mkpart primary 3222MB 4296MB
mkpart primary 4296MB 6443MB
mkpart primary 6443MB 7517MB
q
mkswap /dev/sda1
mkfs.ext4 /dev/sda3
mkdir /mnt/boot
mount /dev/sda3 /mnt/boot
mkdir /mnt/boot/boot
cd /mnt/usb
cp uImage-wdrecovery /mnt/boot/boot/uImage
cp uRamdisk-wdrecovery /mnt/boot/boot/uRamdisk
Done. Connect disk back to WDMC and turn on.
After few minutes WDMC boots to “WD Recovery”. Go to webgui and upload official firmware.
Done!
Thanks to whoever wrote the guide. It just needed updated a little bit. I hope this helps some of you have a successful outcome.
Ok, for some reason my cloud stopped mounting my 3tb partition. So I wiped the drive to start again, but this time when I got to creating the swap file once the partitions had been created (mkswap /dev/sda1) I got an error message: cannot open /dev/sda1: Device or resource busy.
Gparted shows /dev/sda1 as a linux-raid file system, with a key beside it, and a mount point of /dev/md127. I cant unmount the partition or the mount point.
Hi. Sorry, I don’t speak Italian but hopefully you can read this with Google translate.
Have you used the same make and model of drive as the original? I think this is important. I had to build mine from new as I just bought the enclosure from eBay. But my v1 has a WD red so I bought one of those for the v2, and it worked. I followed the guide exactly and it worked first time.
No i try with Seagate hard disk 4Tb. But i don’t know if the problem is the model. I build all partitions same in the online guide for gen2 (i find only guide of Russia). I copy I want know if WD Company had A guide for replace the mycloud when the hd is broken. If you can a link for .img mycloud 4Tb (single hd). Or if there is another system (by back usb) for replace my cloud.
I tried the following step. It work for my cloud (Gen2) 3TB. I am not sure why I need to do twice on partition with different kernel uImage and uRamdisk. However, it works in my device.
I think if you go back and look at the instructions. It shows two ways to unbrick
the My Cloud. One way you take the disk out of the case. The other you use
a bootable USB with the recovery files without taking the disk out of the case.