Hi. Two days ago I bought WD My Cloud 4TB (WDBCTL0040HWT-EESN), and updated it to the newest version: “WDMyCloud v04.04.02-105 : Core F/W”.
Unfortunately, I’m experiencing problems with the Drive Sleep. It randomly wakes up, even when it’s not used, for example at night. I have disabled all features like: “DLNA”, “Mac Backups”, “iTunes”, and even “Cloud Access” for test. It didn’t help at all. I don’t use the WD My Cloud Desktop or Mobile App, only smb on Windows and Android to access the files. The drive is still waking up at night or in day, when it’s not used… I have got very sensitive ears. Even though the drive is not that loud - it woke me up around 3 times last night. I would really like to fix this problem, instead of refunding the NAS.
Here is the last night log (the cloud was not accessed during this time, and the Cloud Access was disabled):
2016-02-25T01:31:51.372614+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2016-02-25 01:31:43.738525000 +0100)
2016-02-25T02:17:09.659403+01:00 di=H10IhkTgem notice logger: exit standby after 2107 (since 2016-02-25 01:42:02.318525000 +0100)
2016-02-25T02:28:34.348600+01:00 di=H10IhkTgem notice logger: exit standby after 74 (since 2016-02-25 02:27:20.788525000 +0100)
2016-02-25T02:47:06.380364+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2016-02-25 02:46:58.698525000 +0100)
2016-02-25T02:59:51.255567+01:00 di=H10IhkTgem notice logger: exit standby after 154 (since 2016-02-25 02:57:17.408525000 +0100)
2016-02-25T03:16:14.009033+01:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2016-02-25 03:16:06.471949001 +0100)
2016-02-25T06:53:30.678214+01:00 di=H10IhkTgem notice logger: exit standby after 12425 (since 2016-02-25 03:26:25.071949001 +0100)
2016-02-25T07:17:09.898959+01:00 di=H10IhkTgem notice logger: exit standby after 197 (since 2016-02-25 07:13:52.881949001 +0100)
2016-02-25T08:01:09.511267+01:00 di=H10IhkTgem notice logger: exit standby after 2028 (since 2016-02-25 07:27:20.991949001 +0100)
2016-02-25T08:01:19.568527+01:00 di=H10IhkTgem notice logger: Rotated atop, atop_size=3198659 atop_upload_size=8290
2016-02-25T08:40:35.747237+01:00 di=H10IhkTgem notice logger: exit standby after 1755 (since 2016-02-25 08:11:20.721949001 +0100)
2016-02-25T08:58:23.366455+01:00 di=H10IhkTgem notice logger: exit standby after 396 (since 2016-02-25 08:51:47.881949001 +0100)
2016-02-25T09:34:09.196538+01:00 di=H10IhkTgem notice logger: exit standby after 741 (since 2016-02-25 09:21:48.741949001 +0100)
2016-02-25T10:05:24.688940+01:00 di=H10IhkTgem notice logger: exit standby after 1264 (since 2016-02-25 09:44:20.221949001 +0100)
2016-02-25T10:29:54.662875+01:00 di=H10IhkTgem notice logger: exit standby after 859 (since 2016-02-25 10:15:35.651949001 +0100)
And the day log:
2016-02-25T16:37:54.286606+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2016-02-25 16:37:41.602290001 +0100)
2016-02-25T16:59:18.859231+01:00 di=H10IhkTgem notice logger: exit standby after 57 (since 2016-02-25 16:58:16.282290001 +0100)
2016-02-25T17:17:09.620577+01:00 di=H10IhkTgem notice logger: exit standby after 455 (since 2016-02-25 17:09:29.912290001 +0100)
2016-02-25T17:40:13.971321+01:00 di=H10IhkTgem notice logger: exit standby after 768 (since 2016-02-25 17:27:20.892290001 +0100)
2016-02-25T18:00:33.325076+01:00 di=H10IhkTgem notice logger: exit standby after 603 (since 2016-02-25 17:50:25.382290001 +0100)
2016-02-25T18:16:03.575815+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2016-02-25 18:15:50.892290001 +0100)
2016-02-25T18:29:11.237483+01:00 di=H10IhkTgem notice logger: exit standby after 171 (since 2016-02-25 18:26:15.102290001 +0100)
2016-02-25T18:55:28.837338+01:00 di=H10IhkTgem notice logger: exit standby after 17 (since 2016-02-25 18:55:11.132290001 +0100)
2016-02-25T19:05:57.801571+01:00 di=H10IhkTgem notice logger: exit standby after 17 (since 2016-02-25 19:05:40.182290001 +0100)
2016-02-25T19:20:29.699286+01:00 di=H10IhkTgem notice logger: exit standby after 16 (since 2016-02-25 19:20:13.812290001 +0100)
2016-02-25T19:30:58.680971+01:00 di=H10IhkTgem notice logger: exit standby after 17 (since 2016-02-25 19:30:41.012290001 +0100)
2016-02-25T19:31:12.973476+01:00 di=H10IhkTgem notice logger: Tally daemon not installed, exiting tally function
2016-02-25T19:50:31.444185+01:00 di=H10IhkTgem notice logger: exit standby after 545 (since 2016-02-25 19:41:26.822290001 +0100)
2016-02-25T20:00:49.961751+01:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2016-02-25 20:00:42.732290001 +0100)
2016-02-25T20:14:35.832643+01:00 di=H10IhkTgem notice logger: exit standby after 214 (since 2016-02-25 20:11:01.082290001 +0100)
2016-02-25T20:41:10.608759+01:00 di=H10IhkTgem notice logger: exit standby after 983 (since 2016-02-25 20:24:47.032290001 +0100)
2016-02-25T20:42:22.783336+01:00 di=H10IhkTgem notice logger: Tally daemon not installed, exiting tally function
2016-02-25T21:01:43.358280+01:00 di=H10IhkTgem notice logger: exit standby after 548 (since 2016-02-25 20:52:35.902290001 +0100)
2016-02-25T21:35:09.626208+01:00 di=H10IhkTgem notice logger: exit standby after 1395 (since 2016-02-25 21:11:54.542290001 +0100)
2016-02-25T22:16:42.625212+01:00 di=H10IhkTgem notice logger: exit standby after 1882 (since 2016-02-25 21:45:20.732290001 +0100)
2016-02-25T23:15:50.569421+01:00 di=H10IhkTgem notice logger: exit standby after 2936 (since 2016-02-25 22:26:54.272290001 +0100)
Please note that sometimes it wakes up after 7 seconds or less than 5 minutes, while I’m not using it at all…
I read many topics about this problem, unfortunately I didn’t find the working solution. Someone recommended to modify monitorio.sh and add:
sync
sync
sleep 10
after “touch /tmp/standby”. Unfortunately it didn’t help too - I was just getting “exit standby after 17” instead of “exit standby after 7”…
If anybody knows a solution for this problem, I would very appreciate any help.