WD My Cloud randomly wakes up the drive when Drive Sleep is enabled

I’ve been looking into the possibility of using a USB to avoid the cache problem. Just not sure
of the best way to go about fixing the problem.

RAC

Dear all,

I tried all steps however my sleep time is very low.
I was looking for dhcp requests in daemon.log and realized that a process is printing below logs very often. I thing when system prints logs, it will wake up the system. Can you please help me to stop the below logs?

May 5 10:14:10 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:12 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:13 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:13 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:14 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:14 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:14 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:14 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:14 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:15 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:15 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:15 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:15 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:16 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:16 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:16 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:19 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:19 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong
May 5 10:14:19 WDMyCloud Airplay-Plugin: GetLargeResourceRecord: opt 65002 optlen 8 wrong

I’ve figured out how to suspend above logs.

/CacheVolume/twonkymedia/twonkyserver.ini

change vlevel to 5 to suspend the logs.

Log level (0:debug, 1:trace, 2:info, 3:warning, 4:error, 5:critical)

vlevel=5

after this modification I will monitor the hdd if it will sleep more.

Hello guys. After update to firmware version: v04.05.00-315
My drive again wakes up every ~10 minutes:

2017-05-03T12:05:46.615449+02:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2017-05-03 12:05:39.026754001 +0200)
2017-05-03T12:29:23.477375+02:00 di=H10IhkTgem notice logger: exit standby after 196 (since 2017-05-03 12:26:07.766754001 +0200)
2017-05-03T12:59:33.250960+02:00 di=H10IhkTgem notice logger: exit standby after 589 (since 2017-05-03 12:49:44.666754001 +0200)
2017-05-03T13:29:33.396500+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 13:19:54.506754001 +0200)
2017-05-03T13:59:33.310211+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 13:49:54.676754001 +0200)
2017-05-03T14:29:33.403603+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 14:19:54.436754001 +0200)
2017-05-03T14:59:33.268551+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 14:49:54.656754001 +0200)
2017-05-03T15:29:33.299851+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 15:19:54.506754001 +0200)
2017-05-03T15:59:33.290764+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 15:49:54.456754001 +0200)
2017-05-03T16:29:33.256608+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 16:19:54.516754001 +0200)
2017-05-03T16:59:33.272441+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 16:49:54.596754001 +0200)
2017-05-03T17:29:33.300484+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 17:19:54.546754001 +0200)
2017-05-03T17:59:33.298605+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 17:49:54.496754001 +0200)
2017-05-03T18:02:36.753787+02:00 di=H10IhkTgem notice logger: calculate_share_size after 3
2017-05-03T18:51:51.205357+02:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2017-05-03 18:51:43.596754001 +0200)
2017-05-03T19:14:33.291975+02:00 di=H10IhkTgem notice logger: exit standby after 141 (since 2017-05-03 19:12:12.476754001 +0200)
2017-05-03T19:44:32.834899+02:00 di=H10IhkTgem notice logger: exit standby after 578 (since 2017-05-03 19:34:54.666754001 +0200)
2017-05-03T20:14:33.020676+02:00 di=H10IhkTgem notice logger: exit standby after 578 (since 2017-05-03 20:04:54.186754001 +0200)
2017-05-03T20:44:33.215255+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 20:34:54.326754001 +0200)
2017-05-03T21:14:33.275292+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 21:04:54.496754001 +0200)
2017-05-03T21:44:33.275628+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 21:34:54.566754001 +0200)
2017-05-03T22:14:33.287351+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 22:04:54.506754001 +0200)
2017-05-03T22:44:33.300822+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 22:34:54.566754001 +0200)
2017-05-03T23:14:33.282779+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 23:04:54.566754001 +0200)
2017-05-03T23:44:33.254354+02:00 di=H10IhkTgem notice logger: exit standby after 579 (since 2017-05-03 23:34:54.536754001 +0200)

I am using file: /CacheVolume/user-start with:

mount -o remount,noatime,nodiratime /dev/root /
/etc/init.d/nfs-kernel-server stop
/etc/init.d/nfs-common stop
/etc/init.d/upnp_nas stop
/etc/init.d/mDNSResponder stop
/etc/init.d/wdphotodbmergerd stop
/etc/init.d/wdnotifierd stop
/etc/init.d/wdmcserverd stop
/etc/init.d/restsdk-serverd stop
/etc/rc2.d/S20restsdk-serverd stop
/etc/init.d/cron stop

But after the last update it simply wakes up all the time, even when all those services are disabled. Is there any workaround for it? Also, is it safe to flash an older firmware version, without losing any files?

EDIT:
After downgrade to an older version following: WD My Cloud v3.x, v4.x and v2.x Firmware Versions Download Links the problem is gone! However, I’m still disappointed that I can’t use the newest version :frowning:

Hi Mona,

Did you check the /var/log folder with ls -lrt?
Is there any repeating logs written to the hdd?
I found some logs disabled them.

Thanks for your answer. Only user.log was updated, and only with “sleep”, “wake up” information. However, restoring previous firmware version fixed this problem. This problem is also discussed here: Firmware 4.05.00-315 Discussion and it seems like the new version of Samba is causing it. Hopefully the community will find a stable solution for this issue.

Dear Mona,
How did you restore the previous version?
Is there any quick way?
Thanks

See the link posted earlier in the discussion…

http://community.wd.com/t/wd-my-cloud-v3-x-v4-x-and-v2-x-firmware-versions-download-links/

Thanks Bennor, I will give it a try.

Hi guys.
For the last 3 years I’ve been using the user-start script which worked perfectly fine. Unfortunately, since exactly “2019-04-01T07:07:28 CET” I noticed that MyCloud wakes up every 20 mins ( 20 Minutes and 49 Seconds).
For example:

2019-04-01T07:38:29.521235+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 07:17:39.422988000 +0200)
2019-04-01T08:09:30.494961+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 07:48:40.492988000 +0200)
2019-04-01T08:40:31.487488+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 08:19:41.502988000 +0200)
2019-04-01T09:11:32.516295+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 08:50:42.432988000 +0200)
2019-04-01T09:42:33.526295+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 09:21:43.462988000 +0200)
2019-04-01T10:13:34.602128+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 09:52:44.412988000 +0200)
2019-04-01T10:44:35.516244+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 10:23:45.642988000 +0200)
2019-04-01T11:15:36.530733+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 10:54:46.442988000 +0200)
2019-04-01T11:46:37.536666+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 11:25:47.582988000 +0200)
2019-04-01T12:17:38.617825+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 11:56:48.452988000 +0200)
2019-04-01T12:48:39.625466+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 12:27:49.562988000 +0200)
2019-04-01T13:19:40.649837+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 12:58:50.592988000 +0200)
2019-04-01T13:50:41.521124+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 13:29:51.542988000 +0200)
2019-04-01T14:21:43.534357+02:00 di=H10IhkTgem notice logger: exit standby after 1251 (since 2019-04-01 14:00:52.402988000 +0200)
2019-04-01T14:52:44.512641+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 14:31:54.472988000 +0200)
2019-04-01T15:23:45.513782+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 15:02:55.442988000 +0200)
2019-04-01T15:54:46.523758+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 15:33:56.442988000 +0200)
2019-04-01T16:25:47.531998+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 16:04:57.452988000 +0200)
2019-04-01T16:56:48.626499+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 16:35:58.412988000 +0200)
2019-04-01T17:27:49.527811+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 17:06:59.602988000 +0200)
2019-04-01T17:58:50.640638+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 17:38:00.392988000 +0200)
2019-04-01T18:13:04.787786+02:00 di=H10IhkTgem notice logger: exit standby after 59 (since 2019-04-01 18:12:05.332988000 +0200)
2019-04-01T18:29:51.523742+02:00 di=H10IhkTgem notice logger: exit standby after 334 (since 2019-04-01 18:24:17.102988000 +0200)
2019-04-01T19:00:52.539826+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 18:40:02.462988000 +0200)
2019-04-01T19:31:53.665201+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 19:11:03.472988000 +0200)
2019-04-01T20:02:54.530674+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 19:42:04.602988000 +0200)
2019-04-01T20:33:55.516753+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 20:13:05.432988000 +0200)
2019-04-01T21:04:56.500462+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 20:44:06.452988000 +0200)
2019-04-01T21:35:57.515697+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 21:15:07.432988000 +0200)
2019-04-01T22:06:58.510246+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 21:46:08.402988000 +0200)
2019-04-01T22:37:59.518604+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 22:17:09.432988000 +0200)
2019-04-01T23:09:00.514556+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 22:48:10.462988000 +0200)

2019-04-09T20:03:00.482196+02:00 di=H10IhkTgem notice logger: exit standby after 1255 (since 2019-04-09 19:42:05.398048002 +0200)
2019-04-09T20:31:12.914785+02:00 di=H10IhkTgem notice logger: exit standby after 1081 (since 2019-04-09 20:13:11.498048002 +0200)
2019-04-09T21:05:02.597908+02:00 di=H10IhkTgem notice logger: exit standby after 1296 (since 2019-04-09 20:43:26.818048002 +0200)
2019-04-09T21:36:03.475498+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-09 21:15:13.568048002 +0200)
2019-04-09T22:07:04.485731+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-09 21:46:14.448048002 +0200)
2019-04-09T22:38:06.496533+02:00 di=H10IhkTgem notice logger: exit standby after 1251 (since 2019-04-09 22:17:15.518048002 +0200)
2019-04-09T23:09:07.491082+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-09 22:48:17.528048002 +0200)
2019-04-09T23:40:08.487463+02:00 di=H10IhkTgem notice logger: exit standby after 1189 (since 2019-04-09 23:20:19.718048002 +0200)
2019-04-10T00:11:09.572521+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-09 23:50:19.478048002 +0200)
2019-04-10T00:42:10.504005+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 00:21:20.538048002 +0200)
2019-04-10T01:13:11.464381+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 00:52:21.478048002 +0200)
2019-04-10T01:44:12.492568+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 01:23:22.398048002 +0200)
2019-04-10T02:15:13.468856+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 01:54:23.438048002 +0200)
2019-04-10T02:46:14.609252+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 02:25:24.408048002 +0200)
2019-04-10T03:17:15.468587+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 02:56:25.568048002 +0200)
2019-04-10T03:48:16.594429+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 03:27:26.448048002 +0200)
2019-04-10T04:19:17.469790+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 03:58:27.618048002 +0200)
2019-04-10T04:50:18.477295+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 04:29:28.518048002 +0200)
2019-04-10T05:21:19.478604+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 05:00:29.408048002 +0200)
2019-04-10T05:52:20.483333+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 05:31:30.478048002 +0200)
2019-04-10T06:23:21.505487+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 06:02:31.378048002 +0200)
2019-04-10T06:51:56.610122+02:00 di=H10IhkTgem notice logger: exit standby after 1104 (since 2019-04-10 06:33:32.508048002 +0200)
2019-04-10T07:25:23.490594+02:00 di=H10IhkTgem notice logger: exit standby after 1396 (since 2019-04-10 07:02:07.708048002 +0200)
2019-04-10T07:56:24.505347+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 07:35:34.448048002 +0200)
2019-04-10T08:27:25.479155+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 08:06:35.508048002 +0200)
2019-04-10T08:58:26.495671+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 08:37:36.428048002 +0200)
2019-04-10T09:29:27.589769+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 09:08:37.458048002 +0200)
2019-04-10T10:00:28.483782+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 09:39:38.588048002 +0200)
2019-04-10T10:31:29.497608+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 10:10:39.498048002 +0200)
2019-04-10T11:02:30.501562+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 10:41:40.448048002 +0200)
2019-04-10T11:33:31.491959+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 11:12:41.468048002 +0200)
2019-04-10T12:04:32.496174+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 11:43:42.468048002 +0200)
2019-04-10T12:35:33.493604+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 12:14:43.478048002 +0200)
2019-04-10T13:06:34.489440+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 12:45:44.518048002 +0200)
2019-04-10T13:37:35.495921+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 13:16:45.468048002 +0200)
2019-04-10T14:08:36.485835+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 13:47:46.528048002 +0200)
2019-04-10T14:39:37.495205+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 14:18:47.558048002 +0200)
2019-04-10T15:10:38.472325+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 14:49:48.438048002 +0200)
2019-04-10T15:41:39.508482+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 15:20:49.408048002 +0200)
2019-04-10T16:12:40.500972+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 15:51:50.458048002 +0200)
2019-04-10T16:43:41.532083+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 16:22:51.468048002 +0200)
2019-04-10T17:14:42.500032+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 16:53:52.558048002 +0200)
2019-04-10T17:45:43.506474+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 17:24:53.418048002 +0200)
2019-04-10T18:16:45.471957+02:00 di=H10IhkTgem notice logger: exit standby after 1251 (since 2019-04-10 17:55:54.508048002 +0200)
2019-04-10T18:47:46.490527+02:00 di=H10IhkTgem notice logger: exit standby after 883 (since 2019-04-10 18:33:03.458048002 +0200)
2019-04-10T19:18:47.498449+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 18:57:57.468048002 +0200)
2019-04-10T19:49:48.495066+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 19:28:58.518048002 +0200)
2019-04-10T20:20:49.492849+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 19:59:59.588048002 +0200)
2019-04-10T20:51:50.489421+02:00 di=H10IhkTgem notice logger: exit standby after 761 (since 2019-04-10 20:39:09.298048002 +0200)
2019-04-10T21:22:51.475156+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 21:02:01.518048002 +0200)
2019-04-10T21:53:52.487151+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 21:33:02.598048002 +0200)
2019-04-10T22:24:53.485235+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 22:04:03.468048002 +0200)
2019-04-10T22:55:54.566740+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 22:35:04.548048002 +0200)
2019-04-10T23:26:55.501771+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 23:06:05.638048002 +0200)
2019-04-10T23:57:56.482788+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-10 23:37:06.548048002 +0200)
2019-04-11T00:28:57.491573+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 00:08:07.548048002 +0200)
2019-04-11T00:59:58.489135+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 00:39:08.558048002 +0200)
2019-04-11T01:30:59.488917+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 01:10:09.428048002 +0200)
2019-04-11T02:02:01.492466+02:00 di=H10IhkTgem notice logger: exit standby after 1251 (since 2019-04-11 01:41:10.418048002 +0200)
2019-04-11T02:33:02.481849+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 02:12:12.638048002 +0200)
2019-04-11T02:47:28.522313+02:00 di=H10IhkTgem notice logger: exit standby after 255 (since 2019-04-11 02:43:13.438048002 +0200)
2019-04-11T03:04:03.480171+02:00 di=H10IhkTgem notice logger: exit standby after 384 (since 2019-04-11 02:57:39.498048002 +0200)
2019-04-11T03:35:04.590128+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 03:14:14.448048002 +0200)
2019-04-11T04:06:05.469874+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 03:45:15.498048002 +0200)
2019-04-11T04:37:06.504204+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 04:16:16.418048002 +0200)
2019-04-11T05:08:07.504391+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 04:47:17.428048002 +0200)
2019-04-11T05:39:08.487591+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 05:18:18.498048002 +0200)
2019-04-11T06:10:09.487609+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 05:49:19.418048002 +0200)
2019-04-11T06:41:10.476531+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 06:20:20.498048002 +0200)
2019-04-11T07:12:11.481132+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 06:51:21.468048002 +0200)
2019-04-11T07:43:12.484380+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 07:22:22.458048002 +0200)
2019-04-11T08:14:13.578460+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 07:53:23.518048002 +0200)
2019-04-11T08:45:14.481454+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 08:24:24.548048002 +0200)
2019-04-11T09:16:15.485839+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 08:55:25.408048002 +0200)
2019-04-11T09:47:16.488255+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 09:26:26.458048002 +0200)
2019-04-11T10:18:17.487094+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 09:57:27.408048002 +0200)
2019-04-11T10:49:18.502084+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 10:28:28.448048002 +0200)
2019-04-11T11:20:19.490164+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 10:59:29.548048002 +0200)
2019-04-11T11:51:20.501459+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 11:30:30.468048002 +0200)
2019-04-11T12:22:21.490321+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 12:01:31.528048002 +0200)
2019-04-11T12:53:22.486508+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-11 12:32:32.548048002 +0200)

It looks very strange to me. I restarted MyCloud several times, but it’s always 1250 seconds. This “fixed” time makes me think it’s something running on MyCloud causing the wake-up. If it was a call from the external device this time would change after MyCloud restart.
Is there any command/script that would help me to detect which proces causes it, or what file is being read?

I would appreciate any help.

What version of firmware are you using. I’m on 04.04.02-105and it is not waking up every 20 minutes.

Thanks for the reply:
Current Version WDMyCloud v04.05.00-327 : Core F/W

Before 1st of April it was all fine:

2019-03-29T08:32:45.091979+01:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2019-03-29 08:32:37.402988000 +0100)
2019-03-29T16:02:28.065643+01:00 di=H10IhkTgem notice logger: exit standby after 26373 (since 2019-03-29 08:42:55.962988000 +0100)
2019-03-29T18:27:11.668355+01:00 di=H10IhkTgem notice logger: exit standby after 8072 (since 2019-03-29 16:12:39.382988000 +0100)
2019-03-30T01:30:04.021576+01:00 di=H10IhkTgem notice logger: exit standby after 24577 (since 2019-03-29 18:40:26.672988000 +0100)
2019-03-30T02:36:51.598282+01:00 di=H10IhkTgem notice logger: exit standby after 3396 (since 2019-03-30 01:40:15.292988000 +0100)
2019-03-30T02:49:14.087227+01:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2019-03-30 02:49:06.382988000 +0100)
2019-03-30T06:52:07.397983+01:00 di=H10IhkTgem notice logger: exit standby after 13962 (since 2019-03-30 02:59:25.042988000 +0100)
2019-03-30T07:21:56.616991+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2019-03-30 07:21:48.902988002 +0100)
2019-03-30T11:11:13.975203+01:00 di=H10IhkTgem notice logger: exit standby after 13146 (since 2019-03-30 07:32:07.552988002 +0100)
2019-03-30T17:33:33.497806+01:00 di=H10IhkTgem notice logger: exit standby after 22328 (since 2019-03-30 11:21:25.332988002 +0100)
2019-03-30T17:49:01.527403+01:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2019-03-30 17:48:53.842988001 +0100)
2019-03-30T19:38:10.070370+01:00 di=H10IhkTgem notice logger: exit standby after 5938 (since 2019-03-30 17:59:12.492988001 +0100)
2019-03-31T03:15:10.859086+02:00 di=H10IhkTgem notice logger: exit standby after 23209 (since 2019-03-30 19:48:21.342988001 +0100)
2019-03-31T03:17:13.906666+02:00 di=H10IhkTgem notice logger: calculate_share_size after 2
2019-03-31T03:28:53.018872+02:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2019-03-31 03:28:45.322988001 +0200)
2019-03-31T05:44:15.344549+02:00 di=H10IhkTgem notice logger: exit standby after 5673 (since 2019-03-31 04:09:41.982988001 +0200)
2019-03-31T06:25:09.334909+02:00 di=H10IhkTgem notice logger: exit standby after 1843 (since 2019-03-31 05:54:26.302988001 +0200)
2019-03-31T08:08:26.714603+02:00 di=H10IhkTgem notice logger: exit standby after 5586 (since 2019-03-31 06:35:20.602988001 +0200)
2019-03-31T08:12:35.212820+02:00 di=H10IhkTgem notice logger: calculate_share_size after 4
2019-03-31T08:40:39.767448+02:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2019-03-31 08:40:32.082988000 +0200)
2019-03-31T14:50:17.567787+02:00 di=H10IhkTgem notice logger: exit standby after 21567 (since 2019-03-31 08:50:50.692988000 +0200)
2019-03-31T18:07:44.776176+02:00 di=H10IhkTgem notice logger: exit standby after 11236 (since 2019-03-31 15:00:28.912988000 +0200)
2019-03-31T18:25:13.696231+02:00 di=H10IhkTgem notice logger: exit standby after 7 (since 2019-03-31 18:25:05.952988000 +0200)
2019-04-01T01:06:47.843639+02:00 di=H10IhkTgem notice logger: exit standby after 23483 (since 2019-03-31 18:35:24.662988000 +0200)
2019-04-01T04:34:35.260311+02:00 di=H10IhkTgem notice logger: exit standby after 11856 (since 2019-04-01 01:16:59.082988000 +0200)
2019-04-01T04:57:33.943493+02:00 di=H10IhkTgem notice logger: exit standby after 644 (since 2019-04-01 04:46:49.222988000 +0200)
2019-04-01T05:15:03.056601+02:00 di=H10IhkTgem notice logger: exit standby after 377 (since 2019-04-01 05:08:46.282988000 +0200)
2019-04-01T05:44:00.685416+02:00 di=H10IhkTgem notice logger: exit standby after 1065 (since 2019-04-01 05:26:15.322988000 +0200)
2019-04-01T06:16:14.223825+02:00 di=H10IhkTgem notice logger: exit standby after 8 (since 2019-04-01 06:16:06.592988000 +0200)
2019-04-01T06:36:13.810073+02:00 di=H10IhkTgem notice logger: exit standby after 588 (since 2019-04-01 06:26:25.192988000 +0200)
2019-04-01T07:07:28.500133+02:00 di=H10IhkTgem notice logger: exit standby after 1264 (since 2019-04-01 06:46:24.822988000 +0200)
2019-04-01T07:38:29.521235+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 07:17:39.422988000 +0200)
2019-04-01T08:09:30.494961+02:00 di=H10IhkTgem notice logger: exit standby after 1250 (since 2019-04-01 07:48:40.492988000 +0200)

So I really don’t know what’s wrong. I don’t think I modified anything on 1st of April.

checkgen1.txt (940 Bytes)
change this file to checkgen1.sh
Then run
sh checkgen1.sh 10

This will display files that have been accessed in the last minute. Since the test is every 10 seconds the files will appear multiple times .

Thank you. I started the script, but it doesn’t list files which I just accessed by SMB. Is this expected behavior, or something is wrong?

Here’s the output of command “tail /proc/mounts”:

WDMyCloud:/nfs/Public# tail /proc/mounts
/dev/sda4 /DataVolume ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback 0 0
/dev/sda4 /CacheVolume ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback 0 0
/dev/sda4 /nfs/Mona ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback 0 0
/dev/sda4 /nfs/Public ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback 0 0
/dev/sda4 /nfs/Cala_zawartosc ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=writeback 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
tmpfs /etc/samba/msg.sock tmpfs rw,relatime,size=1024k,mode=700 0 0
tmpfs /etc/samba/msg.sock tmpfs rw,noatime,size=2048k,mode=700 0 0
tmpfs /etc/samba/msg.sock tmpfs rw,relatime,size=1024k,mode=700 0 0

And that’s what checkgen1 shows:

WDMyCloud:/nfs/Public# ./checkgen1.sh
21-13-07 sda1 607258 34952 sda2 690722 34952 sda3 487296 577792 sda4 6789402 3318376 sda5 1408 0 sda6 1408 0 sda7 384 0 sda8 768 0
/sys
/dev/xconsole
/dev/ptmx
/dev/pts/0
/tmp/sess_sdi5r2jpbtnajt2huh72hi73v6
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source

There was some test MP4 file accessed during the check period (called 21.mp4).

How long did you run the checkgen1.sh script? It should run for at least an hour to get three samples.

It was running for around 5 minutes. I wanted to first test if the script detects files accessed from SMB shares.

I’ve good news: I think I detected what caused this problem.
It was either:

  • Stopped cron (I resumed yesterday to let it run for a full day)
  • External NAS device with OpenMediaVault. I restarted it before night. Not sure if it was the issue, but I’ll be observing it more.

Seems like it helped:

2019-04-12T07:09:15.645208+02:00 di=H10IhkTgem notice logger: exit standby after 13416 (since 2019-04-12 03:25:39.760101001 +0200)
2019-04-12T08:01:09.496722+02:00 di=H10IhkTgem notice logger: exit standby after 2503 (since 2019-04-12 07:19:26.880101001 +0200)
2019-04-12T08:01:19.212473+02:00 di=H10IhkTgem notice logger: Rotated atop, atop_size=3055062 atop_upload_size=1065
2019-04-12T08:12:11.661327+02:00 di=H10IhkTgem notice logger: exit standby after 51 (since 2019-04-12 08:11:20.670101001 +0200)
2019-04-12T08:26:19.178958+02:00 di=H10IhkTgem notice logger: exit standby after 237 (since 2019-04-12 08:22:22.710101001 +0200)
2019-04-12T11:48:48.555133+02:00 di=H10IhkTgem notice logger: exit standby after 11538 (since 2019-04-12 08:36:30.300101001 +0200)

Thanks for help.

One more question, I know that “chroot” exists, which would prevent those random wake-ups. Does anyone know if it has the “full” WD firmware running on it? Would it lose files/shares after installing? (I have full backups, but still restoring takes a very long time).

chroot is a program. It does not contain any firmware. Using chroot you could mount a USB device with different firmware. Then you chroot to the USB. Now anything you run will use the USB code to run. IF you want to play with chroot google chroot. There are several things you need to setup to be able to have access to your data files from the chroot environment.

Back in the days I suspected OpenVPN which I believe is the link between your cloud and WD Servers, on trying to connect.

After killing that service, by issuing
killall openvpn
(I believe as it has been a year since I last looked at this)

My Cloud seems to settle down.

Alternatively, rebooting the my cloud from time to time seems to settle it down also.

This is all I have from my memories…

Good luck

@rac8006 you should check if whether DHCP renew wakes up the cloud. This is something that is always in the back of my mind but I keep forgetting to mention it as one of the wake up factors.

I have not done much wok on the My Clouds lately. I’m in the process of making an older PC that I have been using to rebuild My Cloud software into a nas. It currently has a 4TB system disk and a 8TB mirror for my data. I.m about ready to take the two 6TB disk from my two clouds and put them in as a 6TB mirror. It has more cpus and memory than the clouds.

Interesting, run that command on my first gen and it indicates “openvpn: no process found”. I have remote access turned off in the Dashboard.