Took forever like 30 minutes before the white light changed over to the blue light. Then the device was unresponsive. At first I can SSH into the device, but then after a few minutes, all connections dropped including my SSH. When I tried to Web connect/UI to the device, very slow and eventually unresponsive.
Connecting an external HDD to the Cloud device immediately causes a lot of thrasing on the new drive causing both the cloud device to disconnect.
SSH to the device just after it boots up and by using
The device works normally after these two commands.
If I simply shutdown the device and plug it in again, the device becomes unresponsive. I do not want to restore it back to OEM as 3.5TB of data takes a long time to copy.
This definitely needs a fix, especially with your next update.
I’ve been a long time user of the WD Live 2TB product and recently and finally got the device to sleep by following some of the instructions from the forums. This was the turning point for me as I discovered this tiny world of linux running on a $150 NAS.
Loving the concept of the tiny linux running in the WD Live, I decided to stay with the Western Digital Products and bougt the 4TB WD Cloud as well as a WD 4TB My Book so the two can interconnect via the USB 3.0 port.
It took a couple of days to upload 3.5TB of photos (I’m a photographer) which works out to something like a few million photos (I kid you not). Although I use the cloud sharing app, I have no need of seeing tiny sizes of my photos and this was the problem with my WD Live trying to index them all. So I have created a couple of scripts that turns off some of the services and this seems to be working unless you can indicate that it would be a problem.
You really need an option on the UI menu to turn off wdmcserverd and wdphotodbmergerd as I do not need indexing. Without these services, I still am able to use the WDCloud app without a tiny photo showing up, but that is fine.