This is my sleep log. It shows the date. The times it entered and woke up from sleep. The seconds sleeping and the amount of time in standby mode. This system is currently not being used very much.
May 14 19:41:55 00:05:11 15796 4:23:16
May 14 00:10:17 03:00:12 10195 2:49:55
May 14 03:06:05 03:29:38 1413 0:23:33
May 14 03:34:44 10:06:23 23499 6:31:39
May 14 10:11:28 10:15:58 270 0:04:30
May 14 10:21:04 11:22:24 3680 1:01:20
May 14 11:30:32 11:30:41 9 0:00:09
May 14 11:36:47 11:37:43 56 0:00:56
May 14 11:42:48 20:06:21 30213 8:23:33
May 14 20:12:28 20:54:06 2498 0:41:38
May 14 21:06:20 21:17:11 651 0:10:51
May 14 21:22:17 22:11:12 2935 0:48:55
May 14 22:16:17 22:18:14 117 0:01:57
May 15 22:23:19 00:00:48 5849 1:37:29
May 15 00:05:53 03:00:12 10459 2:54:19
May 15 03:06:05 03:45:24 2359 0:39:19
May 16 03:50:29 03:00:13 83384 23:09:44
May 16 03:06:20 08:16:00 18580 5:09:40
May 17 08:21:06 00:57:12 59766 16:36:06
May 17 01:02:17 01:17:12 895 0:14:55
May 17 01:22:17 03:00:14 5877 1:37:57
May 17 03:05:53 03:10:12 259 0:04:19
May 18 03:15:17 03:00:13 85496 23:44:56
May 19 03:06:19 03:00:14 86034 23:53:54
May 19 03:06:20 17:34:26 52086 14:28:06
May 19 17:55:51 17:55:59 8 0:00:08
May 19 18:01:05 18:01:11 6 0:00:06
May 19 18:06:16 18:17:12 656 0:10:56
May 20 18:22:17 03:00:12 31075 8:37:55
May 20 03:05:38 03:17:11 693 0:11:33
May 20 03:22:16 05:16:44 6868 1:54:28
May 21 05:21:49 03:00:12 77903 21:38:23
May 21 03:06:05 05:08:18 7333 2:02:13
May 22 05:13:23 03:00:12 78409 21:46:49
May 22 03:06:05 13:17:11 36666 10:11:06
May 23 13:22:17 03:00:13 49076 13:37:56
May 23 03:06:20 15:47:22 45662 12:41:02
Thanks, Ralphael. How would I make the mount command permanent?
Normally I would make that change in /etc/fstab but apparently WD is using a script to mount the drives so I wouldn’t recommend trying to remount the root in a startup script because the root may not have been mounted yet.
For everyone info, none of my changes are permanent even though some of my posts have shown the use of “update-rc.d wdphotodbmergerd disable”.
The reason that I stopped using the update-rc.d is twofolds, one is that users have been reporting that the update-rc package is no longer included with the firmware and the 2nd reason is I wanted my device to revert back to standard on bootup because of my problems that I had with the first firmware update that locked my drive for 3 hours in white light mode.
Thus I include all my stops in a script that I use when I SSH into a freshly booted Drive. I figure that I have 30 seconds before my device becomes non-responsive when it tries to index and thumbnail everything; although I think in version 3.04 WD has included a failsafe that stops the scans when you reboot a non-responsive WD.
In regards to the latest Firmware that Rac is suggesting that we should upgrade into because the fix seems to be implemented, I would wait for the reason that many users are still having other incidental problems. Rac has the best of all worlds as he has two WD Clouds (one with the latest firmware and the other not). I myself will wait until WD announces that Sleep has been fixed in the latest firmware and than wait for at least another month or two for everyone to have tested the reliability of that version.
I also have that problem of being on version 3.04 which may or may not update successfully with skipping several updates.
I may just buy another Cloud (6TB) and rather then upgrading the firmware on my old cloud, I’ll just sell it
Why don’t you use the S98user-start script? It is a symbolic link to /CacheVolume/user-start. This is the
next to last script run on reboot. I’ve put all of the commands to stop scripts in this file. It does not get
over written on a firmware upgrade.
RAC
Nice on the fact that it does not get over-written and I might one day if I reboot it enough. Right now I think I only rebooted the device twice last year.
For now I prefer to be in control killing those pesky process gives me the feeling of booting up my old IBM PC and issuing commands at the DOS prompt :-P
Could you please post your monitorio.sh? I’m about to give up and leave the device on forever I’ve heard that this HDDs are designed to work always on, and that spinning up/down frequently destroys them.
I’ve had bad experience with other HDDs before so unless I get this to work properly, I’ll have no other choice.
BTW, I need to leave twonky and samba on.
PS: Has anybody tested minidlna? Is it less hdd intensive (I.E. can it answer a client query without spinning up the disk?)
The file is to big to list here. But the changes I made are:
touch /tmp/standby
logger “Enter iow_root=$iow_root iow_datavol=$iow_datavol ior_datavol=$ior_datavol”
enterStandbyTime=date +%s
sync <======= new solution, this sync seems to work better
sync <======= new solution, this sync seems to work better
sleep 10 <======= sleep 10 seconds waiting for the access to settle
if [“$1” == “debug”]; then
The lines in red are my changes. With the remoount of the root disk samba should not be a problem. Twonky I’m not sure what effect it has on sleep. I have minidlna installed and it’s working. Not sure about the disk intensity. But minidlna can be setup to only scan when files are added.
RAC
PS. My system only woke up at 03:00AM for 13 days.
I’ve heard that this HDDs are designed to work always on, and that spinning up/down frequently destroys them.