I have the 4TB version. Initially I was having issue that I can’t access the webUI with error access denied. I have no other choice but to do the 4secs reset. After this the issue is still there and then I tried the 40secs reset. This made me lose the SSH access and I still got the error access denied from the webUI.
The question is how long does it takes for the device to initialize at first boot after overwriting both raid mount with the rootfs.img?
I got it fixed, the extracted rootfs image was corrupted somehow when transferred to a VM as I can’t loop mount the image. Thanks to this useful thread… Did a few tweaks, 50-70Mb/s up and 60-80Mb/s down.
Just to share how I restored the rootfs.img below. If you do this, be prepared to void the warranty. For my case it was already voided on day one due to root
Details with resized photos :
1) Remove the harddisk:
Place up right on a flat surface with the device rear facing you, slide in two 15cm rulers into both rear openings (starting from the top curves all the way till the bottom end). Alternatively you can use two credit cards but you need to align them near the inner/outter catch clips. Apply light pressure at the top of the device towards the flat surface while you gently tap on the two rulers inwards. The plastic catch clips should easily pop off after a few taps. To remove the cover, slide it out towards the front of the device along the slide guide. After sliding the harddisk out, remove the three obvious securing screws from the PCB then separate the PCB from the harddisk via its sata connector. Be extra careful not to damage the “protruding” LED light.
2) Three options to mount the harddisk:
a) Mount the WD Red harddisk to any PC extra sata port and plug in the sata power cable. Hotplug would be great.
b) Get a SATA-to-USB cable/adapter. Never tried this but I think you will need a way to power up the WD Red harddisk.
- c) Get an External Harddisk enclosure. Doesn't matter USB2/3/eSata as long as it supports Sata harddisks.
3) Restore the two 2GB Raid partitions with rootfs.img extracted from the official firmware:
If you're using Linux Distro, I'll assume you'll know the rest of the recovery steps. But for Windows, best is to download any LiveCD/gparted ISO or Linux Distro ISO and run them via VM for Windows. This can be easily achieved even without installing the distro, use the "Try" method. I shall not elaborate on how to run/use a VM, you can find these online especially on how to load the USB filters. For my case Lubuntu via Virtualbox's USB filter to load my External Harddisk enclosure USB interface. For LiveCD use gparted app, for any other distro I would recommend DISKS app. Advanced users may use "dd" dump. Transfer the rootfs.img to your distro working area such as ~/Desktop via SMB or SFTP. Select your harddisk and locate the two 2GB Raid partitions and choose the rootfs.img to dump into these two partitions. With DISKS app or forked "dd", you can dump the two partitions at once. You can choose to backup these two partitions prior overwriting but I think it's unnecessary due to it's already corrupted but unless you need to retrieve back any custom modifications to the rootfs.
Once you have restored the two 2GB Raid partitions, assemble back the device and power up. The public shares should appear within 2-3mins and you can proceed with the My Cloud's Quick Restore if necessary. If you still can't still the shares, check if the original rootfs.img is not corrupted. You should be able to loop mount this rootfs.img on the Linux distro and browse its contents. Else your partition table is really corrupted. Read up more on this thread for the solution provided.