I had the problem. I did the system restore. And at least the full factors restart (what is maybe a good thing to do right away)
After that my Cloud was going to sleep mode, but after the first upload not more. Than i went to the dashboard, to try to turn off any “constant connections” that may hold my cloud turned on.
I went to Settings > General and there is under Language and clock the option “NTP Service” (i´ve turned it off) and under Cloud Access the option “Cloud Service”
After i turned off these two thing my cloud was going to stand by mode. But i wanted to know what of these two is the problem. I turned on the NTP Service (because i think that a Clock Service would not make such a big issue, and i saw much people talking about this for years and WD dos not give an answer)
After that my cloud was still going to sleep, i turned the Cloud Service on and it was not going to sleep. Now it´s turned off.
I don´t know if this is a problem that this option is turned off, but the cloud is now making his job.
How are you determining your My Cloud is actually going to sleep?
This sleep problem is a vexing one for many of us. There are quite a few threads that cover various ways and methods people are trying to get their My Cloud to sleep for longer than 10 minutes at a time. There are several background services within the My Cloud that cause it to wake up at random times breaking the sleep cycle. Those services cannot be shut down through the Dashboard, instead one has to use SSH to connect into the My Cloud and disable or shut them down. There is also the issue of the My Cloud waking at 2am or 3am to check for firmware even though a user may have disabled the check for updates option.
Another user created a script one can run to see how often their My Cloud actually sleeps and for how long, it may surprise many to see how little their My Cloud sleeps in default configuration.
While the blue LED may be pulsing on and off indicating the drive is supposedly sleeping, that doesn’t mean the drive is actually sleeping and for how long the drive is sleeping. If one watches that front LED for a long length of time, they’ll see their My Cloud come on all by itself without any user intervention, stay on for a period of time then go back to what appears to be sleep mode.
Unfortunately WD typically doesn’t comment on these kinds of bugs/issues. Which leaves it to we users to try and fix the sleep problem(s) ourselves. Like my prior post indicates and the links discuss, one can find out exactly how often their My Cloud is actually going to sleep using the sleep.awk and sleeptime.sh scripts mentioned in those links. Chances are most will be surprised at how infrequent their My Cloud is actually sleeping.
Typically the My Cloud I use, and which doesn’t have any services disabled via SSH, sleeps for only about 15% to 20% of the time during good days during long unused periods. Often I can hear the drive spin up without any user intervention which is frustrating. Supposedly the sleep period time out is set for 10 minutes within the firmware which means each time the firmware kicks the drive on, it will take 10 minutes of inactivity before the drive will try to go back to sleep.
Have you issued the following command:
“mount -o remount,noatime,nodiratime /dev/root /”
Without the root partition set to these options. Every time a file is accessed on the root partition a kjournal entry is written to the disk. This could cause the disk to never sleep. I don’t use my My Cloud that much. It sleeps over 70% of the time. I do have some processes stopped. Before firmware version 303 my MY Cloud would sleep up to 23 hours. Only waking up at 03:00 in the morning. WD added the atop program with firmware version 303. This program causes the device to wake up every 8 hours. If you stop the process. It gets restarted again later. The 8 second sleeps seems to be caused by the fact that the programs that the monitorio.sh script use get flushed during heavy processing like what is done at 03:00 AM. So monitorio.sh puts the disk in standby mode. Then monitorio.sh checks to see if it needs to do anything. In the process of checking it need a program that has been flushed. Now the disk is woke up to bring the program back into memory.
Yeah I’ve issued that command in the past and while it made some difference the My Cloud still had trouble staying asleep for long periods of time. I’ve experimented with many of the SSH issued commands mostly to mixed success. Currently I have the firmware at default though and will at some point go back and meddle with the sleep issue. Just stupid that we users are forced to do this in the first place.
If you have it set to default. I’m surprised it sleeps at all. I’ve seen two different cases where samba would access a file about once a minute. I’ve seen a problem where the S20restsdk-serverd would generate error messages every few minutes.
Remote access is disabled. Lots of restsdk errors in the log(s):
2016-04-04T15:02:10.156234-04:00 di=NqJQ6FTJD8 notice restsdk[7159]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
At the point now where if it sleeps more than 15% to 30% either stock or with the various SSH end task commands its been good.
Yes, know that I have to stop the restsdk entery to stop the log errors. Just haven’t bothered to really dig in to do it at startup other than previously to do so for testing purposes. Currently I’m leaving the My Cloud in stock mode for the time being.
Again, know that. Just haven’t done it other than for testing purposes a month or two ago when trying to get the sleep issue resolved. Reverted back to default and haven’t taken more time to review thie sleep issue. Like mentioned above it was a mixed deal, while turning off the restsdk at startup and one or two other commands worked others did not. Sleep is still hit or miss on my My Cloud.
Just haven’t done it other than for testing purposes a month or two ago when trying to get the sleep issue resolved. Reverted back to default and haven’t taken more time to review thie sleep issue. Like mentioned above it was a mixed deal, while turning off the restsdk at startup and one or two other commands worked others did not. Sleep is still hit or miss on my My Cloud.