There was another thread about this here with now solutions: http://community.wd.com/t5/WD-My-Cloud/My-Cloud-keeps-waking-up-after-a-short-while-7-seconds/td-p/803759 . Since that thread is closed, has anyone been able to resolve this issue where the drive only sleeps for a few minutes and then wakes up again? I’m on the old 3.0 firmware, but it’s my understanding that the 4.0 firmware doesn’t solve this issue. Anyone know how I can download my log to see why the drive keeps waking up all the time?
Hi there,
On the dashboard, you will be able to see the support section on which you can get the system logs of your unit there is a section to create and save a system report.
I would also recommend contacting support for further assistance on this matter:
Too bad your problem will NOT be solved by tech team.
No matter what you write them.
They have not solved it for several years now (it dates back to MyCloud’s predecessor!).
I was offered a replacement drive that now has same problem. I tend to run it 24/7 as hiss and hum is better than the constant wake-ups. Seems like WD does it on purpose to break down the HD inside prematurely to make an easy buck on new items.
1 Like
confirm. look at this madness:
Feb 4 00:47:48 WDMyCloud logger: exit standby after 8 (since 2015-02-04 00:47:40.783599001 +0300)
Feb 4 01:02:46 WDMyCloud logger: exit standby after 286 (since 2015-02-04 00:58:00.003599001 +0300)
Feb 4 01:17:08 WDMyCloud logger: exit standby after 250 (since 2015-02-04 01:12:58.003599001 +0300)
Feb 4 01:33:03 WDMyCloud logger: exit standby after 344 (since 2015-02-04 01:27:19.903599001 +0300)
Feb 4 01:52:46 WDMyCloud logger: exit standby after 571 (since 2015-02-04 01:43:15.213599001 +0300)
Feb 4 02:12:16 WDMyCloud logger: exit standby after 8 (since 2015-02-04 02:12:08.943599001 +0300)
Feb 4 02:40:25 WDMyCloud logger: exit standby after 1078 (since 2015-02-04 02:22:27.873599001 +0300)
Feb 4 02:59:27 WDMyCloud logger: exit standby after 530 (since 2015-02-04 02:50:37.123599001 +0300)
Feb 4 03:00:02 WDMyCloud getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
Feb 4 03:00:05 WDMyCloud getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.01.02-417&devlang=eng&devsn=WMC00000000&auto=0
Feb 4 03:05:02 WDMyCloud logger: disable lazy init
Feb 4 03:15:42 WDMyCloud logger: exit standby after 8 (since 2015-02-04 03:15:34.484458002 +0300)
Feb 4 03:38:59 WDMyCloud logger: exit standby after 786 (since 2015-02-04 03:25:53.604458002 +0300)
Feb 4 04:13:30 WDMyCloud logger: exit standby after 1459 (since 2015-02-04 03:49:11.694458002 +0300)
Feb 4 04:36:06 WDMyCloud logger: exit standby after 744 (since 2015-02-04 04:23:42.194458002 +0300)
Feb 4 05:00:08 WDMyCloud logger: exit standby after 830 (since 2015-02-04 04:46:18.174458002 +0300)
Feb 4 05:16:42 WDMyCloud logger: exit standby after 8 (since 2015-02-04 05:16:34.894458002 +0300)
Feb 4 05:27:23 WDMyCloud logger: exit standby after 29 (since 2015-02-04 05:26:54.164458002 +0300)
Feb 4 05:37:42 WDMyCloud logger: exit standby after 8 (since 2015-02-04 05:37:34.814458002 +0300)
Feb 4 05:51:12 WDMyCloud logger: exit standby after 198 (since 2015-02-04 05:47:54.214458002 +0300)
Feb 4 06:01:31 WDMyCloud logger: exit standby after 7 (since 2015-02-04 06:01:24.414458002 +0300)
Feb 4 06:13:48 WDMyCloud logger: exit standby after 125 (since 2015-02-04 06:11:43.854458002 +0300)
Feb 4 06:26:24 WDMyCloud logger: exit standby after 144 (since 2015-02-04 06:24:00.264458002 +0300)
Feb 4 06:39:17 WDMyCloud logger: exit standby after 161 (since 2015-02-04 06:36:36.244458002 +0300)
Feb 4 06:51:30 WDMyCloud logger: exit standby after 122 (since 2015-02-04 06:49:28.764458002 +0300)
Feb 4 07:01:49 WDMyCloud logger: exit standby after 7 (since 2015-02-04 07:01:42.264458002 +0300)
Feb 4 07:14:06 WDMyCloud logger: exit standby after 125 (since 2015-02-04 07:12:01.514458002 +0300)
Feb 4 07:34:12 WDMyCloud logger: exit standby after 594 (since 2015-02-04 07:24:18.274458002 +0300)
Feb 4 07:46:48 WDMyCloud logger: exit standby after 144 (since 2015-02-04 07:44:24.344458002 +0300)
Feb 4 07:59:24 WDMyCloud logger: exit standby after 144 (since 2015-02-04 07:57:00.174458002 +0300)
Feb 4 08:09:43 WDMyCloud logger: exit standby after 7 (since 2015-02-04 08:09:36.364458002 +0300)
Feb 4 08:24:30 WDMyCloud logger: exit standby after 275 (since 2015-02-04 08:19:55.734458002 +0300)
Feb 4 08:39:30 WDMyCloud logger: exit standby after 288 (since 2015-02-04 08:34:42.224458002 +0300)
Feb 4 08:54:36 WDMyCloud logger: exit standby after 294 (since 2015-02-04 08:49:42.384458002 +0300)
Feb 4 09:04:55 WDMyCloud logger: exit standby after 7 (since 2015-02-04 09:04:48.254458002 +0300)
Feb 4 09:15:36 WDMyCloud logger: exit standby after 29 (since 2015-02-04 09:15:07.664458002 +0300)
Feb 4 09:27:12 WDMyCloud logger: exit standby after 84 (since 2015-02-04 09:25:48.414458002 +0300)
Feb 4 09:39:40 WDMyCloud logger: exit standby after 136 (since 2015-02-04 09:37:24.354458002 +0300)
Feb 4 09:52:24 WDMyCloud logger: exit standby after 152 (since 2015-02-04 09:49:52.494458002 +0300)
Feb 4 10:11:54 WDMyCloud logger: exit standby after 8 (since 2015-02-04 10:11:46.784458002 +0300)
Feb 4 10:22:42 WDMyCloud logger: exit standby after 37 (since 2015-02-04 10:22:05.924458002 +0300)
my logfile looks like yours, I even contacted the manufacturer of my router, and sent them a logfile, too - just to be sure.
also there is a check for new firmware every night at 03:00, no matter what you selected 
d-fens wrote:
my logfile looks like yours, I even contacted the manufacturer of my router, and sent them a logfile, too - just to be sure.
also there is a check for new firmware every night at 03:00, no matter what you selected
Also have the 3AM wake up BS. Drive does sleep most of the time but seems to go nuts in the early morning hours. Even with zero usage it seems to be waking up once for that 3AM then 2-3 more times right after that. No clue what the drive is doing.
I have zero faith in this drive making it much past the 2 year warranty. I guess by then SSD will be cheap enough to ditch spinning discs.
Decided to run it 24/7 because the lame approach of the WD service and tech support regarding a pretty serious issue of th disc spinning up several times / hr. I think they do it on purpose to satisfy their planned obsolescence scheme for My Cloud. 
You should be ashamed of yourselves, WD.
I’ve done some research and found that the monitorio.sh file is checking the diskstats file to see if any writes
have occurred. It checks the md0 disk writes. This number seems to increase about 128 characters every minute.
This causes the sleepcount to be reset.
My question is what is the md0 partition? What is writing to the md0 partition.
RAC
The MD0 partitiion is part of a raid1 setup. /dev/sda1 and /dev/sda2 are part of the raid1 setup. I don’t know why
they would put a raid1 partition on the same drive. After some testing I have found that some process is writting/reading
the root partition. Every time monitorio.sh checks sthe /proc/diskstats file it finds that the 6th and 10th column for
the md0 entry have changed. Until these numbers remain the same for sleep standby time it will not put the disk in sleep mode.
Are you sure you have the plain vanilla MyCloud? Because that doesn’t have any RAID capability that I’m aware of.
Or do you have a MyCloud Mirror or EX, which have RAID. If you have either of those, you’re in the wrong forum…
http://community.wd.com/t5/WD-My-Cloud-Mirror/bd-p/mycloud_mirror
http://community.wd.com/t5/My-Cloud-EX2-EX4-WD-Sentinel-X-S/ct-p/network
yes. It is a 6TB model WDBCTL0060HWT-NESN. I didn’t think it had raid either. But if you do the following command.
mdadm --display /dev/sda. It shows that there is a raid setup. You can also do a ps -eaf|grep raid. I found that a process
[md0-1 raid1] was running. I’ve run across this while trying to find out why my device does not enter standby. I have two
of these devices and neither will enter standby.
RAC
hey, My 3TB Mycloud also sleep and awake constantly. To address the issue, I use tcpdump to monitor network access on my router, seem Mycloud will wake up even no network access. Then I tried to install inotify-tools to use inotifywait -rm \ to monitor disk IO. many WD process keep read and write disk, like smartstatustools. I just want a pure NAS, how could I disable redundant functions, I only need nfs, smb, afp and transmission.
What I’ve done so far is create a shell script to stop those processes that I don’t want running. Use of the sjhell script
alows me to make changes that are easily undone.
S99WDStop.sh
/etc/rc2.d/S50netatalk stop
/etc/rc2.d/S85wdmcserverd stop
/etc/rc2.d/S60mDNSResponder stop
I put this script in /etc/rc2.d. The last thing done on boot up is run this script which will stop those processes. If you don’t want to do that any more just remove the script or change the name from SWDStop.sh to sWDStop.sh. This will cause the sript not to run the next time you reboot.
Right now I’m trying to see what process is doing the I/O every few minutes.
I have a DNS-323 NAS and it sleeps most of the time. Not sure why these units don’t sleep most of the time.
RAC
To resolve the 3:00am Firmware update wake-up and 3:05am Raid check, here is what I found stops them. Hope this helps out a few folks :
cd /etc/cron.d
ls -altrp
Note the auto_update file below
/etc/cron.d# ls -altrp
total 52
-rwxr-xr-x 1 root root 242 Oct 25 2011 data-volume-config_cron
-rwxr-xr-x 1 root root 524 Apr 10 2012 php5
-rwxr-xr-x 1 root root 408 May 9 2012 system_monitor
-rwxr-xr-x 1 root root 130 May 20 2012 20-checkRAID
-rw-r–r-- 1 root root 72 Jan 3 2013 clean_alerts
-rw-r–r-- 1 root root 102 Sep 9 2013 .placeholder
-rw-r–r-- 1 root root 396 Oct 19 2013 sysstat
-rw-r–r-- 1 root root 589 Oct 19 2013 mdadm
-rwxr-xr-x 1 root root 121 Apr 15 2014 auto_update
-rwxr-xr-x 1 root root 510 May 2 2014 php5.dpkg-dist
-rwxr-xr-x 1 root root 82 Oct 1 19:57 rescan_internal_volumes
drwxr-xr-x 2 root root 4096 Feb 17 19:54 ./
-rwxr-xr-x 1 root root 0 Feb 23 16:07 WDSAFE
drwxr-xr-x 76 root root 4096 Feb 25 19:00 …/
/etc/cron.d# cat auto_update
00 3 * * * root /usr/local/sbin/getNewFirmwareUpgrade.sh immediate send_alert auto; /usr/local/sbin/checkAutoUpdate.sh
editing auto_update and commenting the above line in bold will stop the update from running but may not stop the drive from waking up?
So to take it a step further:
/etc/cron.d# cat /etc/crontab
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don’t have to run the `crontab’
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
0 3 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
10 3 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
20 3 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#
Commenting out the line above in bold stops the 3am wakeup. [ie: 0 3 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ]
regarding: 10 3 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
I may leave that active as it runs a job in /etc/cron.weekly that does a DB health check. Not sure if I need it, have to find out more
Now for the 3:05am RAID check. Since I’ve dispatched the 3:00am auto-update, no reason for the 3:05am pseudo raid array syncing which is used after an update has occurred,
So back to the /etc/cron.d/ listing
/etc/cron.d# ls -altrp
total 52
-rwxr-xr-x 1 root root 242 Oct 25 2011 data-volume-config_cron
-rwxr-xr-x 1 root root 524 Apr 10 2012 php5
-rwxr-xr-x 1 root root 408 May 9 2012 system_monitor
-rwxr-xr-x 1 root root 130 May 20 2012 20-checkRAID
-rw-r–r-- 1 root root 72 Jan 3 2013 clean_alerts
-rw-r–r-- 1 root root 102 Sep 9 2013 .placeholder
-rw-r–r-- 1 root root 396 Oct 19 2013 sysstat
-rw-r–r-- 1 root root 589 Oct 19 2013 mdadm
-rwxr-xr-x 1 root root 510 May 2 2014 php5.dpkg-dist
-rwxr-xr-x 1 root root 82 Oct 1 19:57 rescan_internal_volumes
-rwxr-xr-x 1 root root 0 Feb 23 16:07 WDSAFE
drwxr-xr-x 2 root root 4096 Feb 26 10:25 ./
-rwxr-xr-x 1 root root 122 Feb 27 16:31 auto_update
Note the 20-checkRAID file:
/etc/cron.d# cat 20-checkRAID
#
# check/repair RAID array
#
@reboot root /usr/local/sbin/20-checkRAID.sh reboot
05 3 * * * root /usr/local/sbin/20-checkRAID.sh
Simply comment out “05 3 * * * root /usr/local/sbin/20-checkRAID.sh” [ie # 05 3 * * * root /usr/local/sbin/20-checkRAID.sh]
Now the 3:05 am checkraid is disabled :) Or you can set it for a more convenient time as it’s standard cron entry format.
Pretty much my drive now remains in standby unless I call upon it to serve content.
I’ve accomplished that with what I’ve read here and found on my own [the 3am and 3:05 wakeups]. Here is a list of what I did to get to that point:
disabling the 3:00 and 3:05 items as detailed above
/etc/init.d/netatalk stop
/etc/init.d/wdmcserverd stop
/etc/init.d/mDNSResponder stop
I turned NTP off via the UI and have a cronjob run “/usr/sbin/ntpdate -s -u pool.ntp.org” at 20:00 when the drive would not normally be in standby due to pulling content from my TV.
My uses are simple; video + book +magazines on demand from my TV and Tablet [Android] - so what is good for me may not be optimal for everyone.
In effect I’m auditioning this WD MyCloud NAS. I may very well order another to replace a NAS by another manufacture that annoys me as even I can not keep that one “sleepy” for too long.
1 Like
Getting nice standby lengths when I’m at work
Mar 3 13:09:03 WD-NAS logger: exit standby after 48134 (since 2015-03-02 23:46:49.091435000 -0500)
Mar 3 18:07:36 WD-NAS logger: exit standby after 17175 (since 2015-03-03 13:21:21.101435000 -0500)
Closed the WD console at 23:46 on Mar 2. The 13:09 on Mar 3 could have been something network-wise that woke it?..The 18:07 is total mystery at a moment as it’s occurred the last 3 days:
user.log:Mar 1 18:07:28 WD-NAS logger:
user.log:Mar 2 18:07:32 WD-NAS logger:
user.log:Mar 3 18:07:36 WD-NAS logger:
Each of the above is each 24 hours and 4 seconds apart. Nothing logged anywhere else, I got home at 6:29 tonight so nothing “I” did…weird. Still twice in 18.5 hours is a great improvement from out of the box. Hopefully I can figure out the new 18:07 wrinkle.
Good news for those who stopped hoping and stopped plugging in their WD My Cloud in their socket. There has been an update ! My prayers from the 17th of Nov 2017 have been answered! Hallelujah!!!
Firmware Release 04.05.00-320 (11/28/2017)
Release Notes
What’s new!
Resolved SMB server (samba) security vulnerability (CVE-2017-7494) - Malicious clients can upload and cause the SMB server to execute a shared library from a writable share.
Improved Cloud Access connectivity from the device.
Resolved issue of MyCloud device waking up from standby despite no activity.
I hope that’s sarcasm. 
We have another thread discussing the sleep issues even with the very latest firmware for the first gen v4.x My Cloud’s. No real solid solution. Some report success with certain services disbled. Others like myself still have a My Cloud that wakes up constantly.
