From what I can tell, my unit never enters sleep mode.
Hello,
Make sure the option is on. Check page #78 of the user’s manual for more information.
http://www.wdc.com/wdproducts/library/UM/ENG/4779-705103.pdf
It is set to ON. I read an old post here that stated to turn OFF the time/date Network sync but that didn’t help.
I do not believe mine ever does either and it is running bare bones…no TIme Machine, Safepoint, media server, itunes…
tim
I’ve been trying to see why the disk never goes to sleep. The process monitorio.sh is the process that puts the drive in standby. It sleeps for 60 seconds and then reads a file called /proc/diskstats. It checks the md line and the sda4 lines.
The script below looks at the same values that monitorio.sh looks at. The last number displayed needs to be zero for 10 iterations. After 10 iterations of zero the disk is put into standby mode. create a file I called mine check.sh and put the lines isted below. You can create the file on windows using notepad or some other method. Then copy the file to the my cloud. If you run this script using ssh. CD to the directory that has the file. I out the file in /var/checkit.sh. So I cd to /var and do a ssh check.sh. On my system the last number is never 0. To get zero I have to stop several processes including monitorio.sh.
I hope the info helps.
while :; do
iow_root=awk -v disk="md1" '{if ($3==disk) print $10}' /proc/diskstats
ior_datavol=awk -v disk="sda4" '{if ($3==disk) print $6}' /proc/diskstats
iow_datavol=awk -v disk="sda4" '{if ($3==disk) print $10}' /proc/diskstats
d=date +%k-%M-%S
let c=iow_root-iow_rootold
echo $d “root” $iow_root “datavol” $ior_datavol “datavol” $iow_datavol $c
iow_rootold=$iow_root
sleep 60
done
I tried turning OFF the Cloud Service but that didn’t help. I then tried to power OFF my gigabit switch which appeared to reboot the device or at least the blue LED started to blink light in color. I was in W10TP which has speed issues(mentioned in another thread) so I rebooted in W7 and into sleep mode. It went into sleep mode so I went back into W10TP, sleep mode and it went to sleep again so I guess that turning OFF the Cloud Service plus a power cycle will get it to sleep.
If one want Cloud Service ON this isn’t much help!
EDIT:
I notice now that when the PC’s screen turns off because the timer setpoint has been reached the drive wakes up. I assume if left in that mode for another 10-15 minutes, it would go to sleep again.
I have implemented the check.sh script as suggested by RAC8006. In my system (which does not seem to sleep - at least I never see a flashing blue LED) the response to CHECK.SH does show the expected result of response of 0 as the last element of the response to the query.
CelticMyCloud:/var# sh check.sh
11-05-22 root 22608 datavol 4101650 datavol 4051048 22608
11-06-22 root 22608 datavol 4135578 datavol 4887112 0
11-07-22 root 22608 datavol 4249338 datavol 5583696 0
11-08-23 root 22608 datavol 4340474 datavol 6267488 0
11-09-23 root 22608 datavol 4361146 datavol 6267488 0
11-10-24 root 22608 datavol 4361162 datavol 6267488 0
11-11-24 root 22608 datavol 4361298 datavol 6267488 0
11-12-24 root 22608 datavol 4361442 datavol 6267488 0
11-13-24 root 22608 datavol 4361458 datavol 6267488 0
11-14-25 root 22608 datavol 4361466 datavol 6267488 0
11-15-26 root 22608 datavol 4361466 datavol 6267488 0
11-16-26 root 22608 datavol 4361466 datavol 6267488 0
11-17-26 root 22608 datavol 4361482 datavol 6267488 0
11-18-26 root 22608 datavol 4364330 datavol 6267488 0
11-19-26 root 22608 datavol 4364346 datavol 6267488 0
11-20-27 root 22608 datavol 4364362 datavol 6267488 0
11-21-27 root 22608 datavol 4371690 datavol 6267488 0
11-22-27 root 22608 datavol 4371842 datavol 6267488 0
11-23-28 root 22608 datavol 4392082 datavol 6267488 0
11-24-28 root 22608 datavol 4435778 datavol 6267488 0
11-25-28 root 22608 datavol 4471810 datavol 6666032 0
11-26-28 root 22608 datavol 4471826 datavol 6666088 0
11-27-28 root 22608 datavol 4471826 datavol 6666088 0
11-28-28 root 22608 datavol 4471826 datavol 6666088 0
11-29-28 root 22608 datavol 4471826 datavol 6666088 0
11-30-29 root 22712 datavol 4512418 datavol 6666456 104
11-31-29 root 22712 datavol 4512418 datavol 6666456 0
11-32-29 root 22712 datavol 4512682 datavol 6666456 0
11-33-30 root 22712 datavol 4512682 datavol 6666456 0
11-34-30 root 22712 datavol 4512682 datavol 6666456 0
11-35-30 root 22712 datavol 4513522 datavol 6666728 0
11-36-30 root 22712 datavol 4513522 datavol 6666728 0
11-37-30 root 22712 datavol 4513522 datavol 6666728 0
11-38-30 root 22712 datavol 4513522 datavol 6666728 0
11-39-30 root 22712 datavol 4513538 datavol 6666728 0
11-40-30 root 22712 datavol 4513538 datavol 6666728 0
11-41-30 root 22712 datavol 4513538 datavol 6666728 0
11-42-30 root 22712 datavol 4513538 datavol 6666728 0
11-43-30 root 22712 datavol 4513538 datavol 6666728 0
11-44-30 root 22712 datavol 4513538 datavol 6666728 0
11-45-30 root 22712 datavol 4513538 datavol 6666728 0
11-46-31 root 22712 datavol 4513538 datavol 6666728 0
11-47-31 root 22712 datavol 4513538 datavol 6666728 0
11-48-31 root 22712 datavol 4513538 datavol 6666728 0
11-49-31 root 22712 datavol 4513538 datavol 6666728 0
11-50-31 root 22712 datavol 4513538 datavol 6666728 0
11-51-31 root 22712 datavol 4513538 datavol 6666728 0
11-52-31 root 22712 datavol 4513538 datavol 6666728 0
11-53-31 root 22712 datavol 4513538 datavol 6666728 0
11-54-31 root 22712 datavol 4513538 datavol 6666728 0
That being the case, and having ensured the sleep option is turned on… noit sure what the problem might be.
tim
Your output is missing the last two numbers. There should be a $b $c after the $a as follows
echo $d “root” $iow_root “datavol” $ior_datavol “datavol” $iow_datavol $a $b $c
All three numbers should be 0 for 10 minutes. The first datavol is data read of the sda4 partition. The next datavol is data writes to sda4.
It looks like you did have a a ten minute time frame from 11-39-30 thru 11-49-31 with no activity on the disks.
To see if you disk is ever in standby look at the /var/log/user.log. You should see an entry as follows:
Mar 3 15:30:44 LauralandHardy logger: exit standby after 627 (since 2015-03-03 15:20:17.329490001 -0500)
this entry says that we exited standby as 15:30:44 after 627 seconds. That we entered standby at 15:20:17.
This shows that it was in standby for 10 minutes and 27 seconds. Below is the current check.sh script. Just run it
with a number of seconds you want it to sleep.
while :; do
iow_root=awk -v disk="md1" '{if ($3==disk) print $10}' /proc/diskstats
ior_datavol=awk -v disk="sda4" '{if ($3==disk) print $6}' /proc/diskstats
iow_datavol=awk -v disk="sda4" '{if ($3==disk) print $10}' /proc/diskstats
d=date +%k-%M-%S
let a=iow_root-iow_rootold
let b=ior_datavol-ior_datavolold
let c=iow_datavol-iow_datavolold
echo $d “root” $iow_root “datavol” $ior_datavol “datavol” $iow_datavol $a $b $c
iow_rootold=$iow_root
iow_datavolold=$iow_datavol
ior_datavolold=$ior_datavol
sleep $1
done
RAC
I have implemeneted the modified script and reviewed the userlog… seems the drive is going into standby for very short periods (I believe there are other threads on this issues) though there is never an indication given with the blue LED… I have turned of most all the “additional” functions (time machine, twonky etc) as they are not needed and teh MyCLoud works very well with my Plex server, WDTV live boxes etc with basic SMB file sharing.
CelticMyCloud:/var# sh check2.sh
16-07-06 root 24528 datavol 7417362 datavol 6669168 24528 7417362 6669168
16-08-06 root 24560 datavol 7417378 datavol 6669168 32 16 0
16-09-06 root 24560 datavol 7417394 datavol 6669168 0 16 0
16-10-06 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-11-06 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-12-06 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-13-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-14-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-15-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-16-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-17-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-18-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-19-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-20-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-21-07 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-22-08 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-23-09 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-24-09 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-25-09 root 24560 datavol 7417394 datavol 6669168 0 0 0
16-26-09 root 24592 datavol 7417394 datavol 6669168 32 0 0
16-27-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-28-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-29-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-30-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-31-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-32-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-33-10 root 24592 datavol 7417394 datavol 6669168 0 0 0
16-34-10 root 24624 datavol 7417394 datavol 6669168 32 0 0
16-35-10 root 24624 datavol 7417394 datavol 6669168 0 0 0
16-36-10 root 24624 datavol 7417394 datavol 6669168 0 0 0
16-37-11 root 24624 datavol 7417394 datavol 6669168 0 0 0
16-38-11 root 24624 datavol 7417394 datavol 6669168 0 0 0
userlog…
Mar 3 13:24:51 CelticMyCloud REST_API[23483]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 13:30:24 CelticMyCloud logger: exit standby after 218 (since 2015-03-03 13:26:46.109390001 -0500)
Mar 3 13:46:58 CelticMyCloud logger: exit standby after 7 (since 2015-03-03 13:46:51.249390001 -0500)
Mar 3 15:50:39 CelticMyCloud logger: exit standby after 8 (since 2015-03-03 15:50:31.659390001 -0500)
Mar 3 15:56:41 CelticMyCloud REST_API[1192]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 15:57:42 CelticMyCloud REST_API[1192]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 15:58:42 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 15:59:43 CelticMyCloud REST_API[24737]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:00:43 CelticMyCloud REST_API[2885]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:01:44 CelticMyCloud REST_API[1192]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:02:44 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:03:45 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:04:45 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:05:46 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:06:46 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:07:47 CelticMyCloud REST_API[2925]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:08:48 CelticMyCloud REST_API[4688]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:09:48 CelticMyCloud REST_API[4700]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:10:49 CelticMyCloud REST_API[4585]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:11:49 CelticMyCloud REST_API[4700]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:12:50 CelticMyCloud REST_API[4688]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:13:50 CelticMyCloud REST_API[4585]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:14:51 CelticMyCloud REST_API[4422]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:15:51 CelticMyCloud REST_API[4688]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:16:52 CelticMyCloud REST_API[4422]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:17:52 CelticMyCloud REST_API[4688]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:18:52 CelticMyCloud REST_API[4585]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:19:53 CelticMyCloud REST_API[4422]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:20:31 CelticMyCloud logger: exit standby after 8 (since 2015-03-03 16:20:23.529390001 -0500)
Mar 3 16:20:53 CelticMyCloud REST_API[4700]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:21:54 CelticMyCloud REST_API[4700]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:22:54 CelticMyCloud REST_API[6569]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:23:54 CelticMyCloud REST_API[4700]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:24:55 CelticMyCloud REST_API[6569]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:25:55 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:26:56 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:27:56 CelticMyCloud REST_API[7248]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:28:57 CelticMyCloud REST_API[6569]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:29:57 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:30:54 CelticMyCloud logger: exit standby after 8 (since 2015-03-03 16:30:46.689390001 -0500)
Mar 3 16:30:58 CelticMyCloud REST_API[6840]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:31:58 CelticMyCloud REST_API[7248]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:32:58 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:33:59 CelticMyCloud REST_API[7248]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:34:59 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:36:00 CelticMyCloud REST_API[7248]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Mar 3 16:37:00 CelticMyCloud REST_API[6897]: 192.168.0.110 OUTPUT DlnaServer\Controller\Database GET SUCCESS
the mystery continues. Thanks for assistance to date.
OK Here is what I did to get the drive to go into stand by. /etc/rc2.d/S20samba stop. After I did this the drive goes into standby most of the time. Today I noticed that it entered standby at 3 in the morning and exited standby at 2 in the afternoon.
So try stopping samba. This is not a fix. It just shows what is stopping the drive from going into standby.
RAC
Wow. If this is really true, then something went totally wrong during the last firmware upgrade. I will disable samba and see whether this truly stops the drive from going to sleep. I myself have now also the problem of a sleepless drive, which was not the case with the previous iteration of the firmware. Previously, the drive would go to sleep if not accessed, but now - with all computers on the network turned off - the drive never goes to sleep (I checked the log).
Let us hope there is an easy fix for that since I do need samba shares.
fk
I’ve also found that if you disconnect the MY Cloud device from the windows PC in my case. The writes to the root disk stop and the drive will sleep even with samba running. But as soon as I connect the drive to the windows PC. The writes start up again.
RAC
rac8006 wrote:
I’ve also found that if you disconnect the MY Cloud device from the windows PC in my case. The writes to the root disk stop and the drive will sleep even with samba running. But as soon as I connect the drive to the windows PC. The writes start up again.
RAC
Were you watching the drive at that time? I ask because when I shut off my gigabite switch, it appears to reboot or at least the blue LED turned white but I didn’t wait to see what it was going to do.
You must mean disconnecting your PC from the network, correct? The MC needs a network connection to even boot up.
I had my MC booted up but my PC OFF and setup a small video camera to monitor its sleep time. Used a video editing app to note the times.
S=sleep O=on
S-00:00:00
O=00:01:44
S=00:11:53
O=01:19:30
S=01:23:19
O=01:26:00
S=01:36:14
None of this makes any sense!
I did a lottle testing and found that if I unplug the network cable the drive does not wake up. But when I plugged it back in the drive woke up. Most likely to handle the cable being plugged in. But not sure if it was the unpluging or pluging in. That caused the drive to wake up. no need to watch the drive. Just look at the led. If the drive is sleeping the blue led will fade in and out. Or you could look at the /var/log/user.log to see when the drive is going to sleep.
The MY Cloud does not need the network to boot. I shutdown the device and disconnected the network cable. I then powered up the device. It booted up with a white light. After a while the white light started to blink. I then plugged in the network cable and the light turned blue. The light looked white when it was blinking but it could have been yellow which is what it is supposed to be when the cable is disconnected.
When I say disconnected on windows. I mean in windows explorer you right click on the drive letter and then click disconnect the drive.
On your system when the drive wakes up if will wait 10 mubites before it can go back to sleep.
rac8006 wrote:
I did a lottle testing and found that if I unplug the network cable the drive does not wake up. But when I plugged it back in the drive woke up. Most likely to handle the cable being plugged in. But not sure if it was the unpluging or pluging in. That caused the drive to wake up. no need to watch the drive. Just look at the led. If the drive is sleeping the blue led will fade in and out. Or you could look at the /var/log/user.log to see when the drive is going to sleep.
The MY Cloud does not need the network to boot. I shutdown the device and disconnected the network cable. I then powered up the device. It booted up with a white light. After a while the white light started to blink. I then plugged in the network cable and the light turned blue. The light looked white when it was blinking but it could have been yellow which is what it is supposed to be when the cable is disconnected.
When I say disconnected on windows. I mean in windows explorer you right click on the drive letter and then click disconnect the drive.
On your system when the drive wakes up if will wait 10 mubites before it can go back to sleep.
It’s not ready to use unless the LED is blue(OS loaded) or so says the instructions(LEDs on page 10 of the manual). To me that means booted up that’s why I used that term.
Under certain conditions it’s a ten minute interval but seems to vary a bit at times.
Yes the blue light means that it is booted up. But after it is booted up and the led is blue. If you pull the network cable
the led will start blinking. The book says yellow blinking. But it looked like it was white blinking when I pulled the network cable.
While the device is booting the light is solid white.
RAC
rac8006 wrote:
Yes the blue light means that it is booted up. But after it is booted up and the led is blue. If you pull the network cable
the led will start blinking. The book says yellow blinking. But it looked like it was white blinking when I pulled the network cable.
While the device is booting the light is solid white.
RAC
Yeah, I just tried that and it is a blinking yellow LED. I had cataract surgery in 2008 and before that lettering on my laptop keys at that time looked to be a pale white but clearly yellow after the surgery.
