In the (unlikely?) event that WD decides to conduct a contest to determine which MBL is the sleepiest, I would like to nominate my MBL as a possible candidate for the doziest MBL out there. Below is an extract from its user.log.
MyBookLive:~# date
Mon Feb 10 12:12:32 EST 2014
MyBookLive:~# cat /var/log/version.log
02.03.01-024 Wed Oct 26 00:07:52 EDT 2011
02.10.09-124 Fri Nov 18 00:05:56 EST 2011
MyBookLive:~# tail -57 /var/log/user.log
Jan 22 06:25:12 localhost logger: exit standby after 85793
Jan 22 06:35:19 localhost logger: Enter standby
Jan 23 06:25:11 localhost logger: exit standby after 85792
Jan 23 06:35:19 localhost logger: Enter standby
Jan 24 06:25:12 localhost logger: exit standby after 85793
Jan 24 06:35:19 localhost logger: Enter standby
Jan 24 21:15:44 localhost logger: exit standby after 52825
Jan 24 21:25:51 localhost logger: Enter standby
Jan 25 06:25:12 localhost logger: exit standby after 32361
Jan 25 06:35:20 localhost logger: Enter standby
Jan 26 06:25:11 localhost logger: exit standby after 85791
Jan 26 06:35:19 localhost logger: Enter standby
Jan 27 06:25:11 localhost logger: exit standby after 85792
Jan 27 06:35:19 localhost logger: Enter standby
Jan 28 06:25:12 localhost logger: exit standby after 85793
Jan 28 06:35:16 localhost logger: Enter standby
Jan 28 14:12:13 localhost logger: exit standby after 27416
Jan 28 14:22:18 localhost logger: Enter standby
Jan 29 06:25:11 localhost logger: exit standby after 57773
Jan 29 06:35:16 localhost logger: Enter standby
Jan 30 06:25:11 localhost logger: exit standby after 85795
Jan 30 06:35:16 localhost logger: Enter standby
Jan 31 06:25:11 localhost logger: exit standby after 85795
Jan 31 06:35:16 localhost logger: Enter standby
Feb 1 06:25:11 localhost logger: exit standby after 85795
Feb 1 06:35:16 localhost logger: Enter standby
Feb 1 06:52:11 localhost logger: exit standby after 1015
Feb 1 07:02:16 localhost logger: Enter standby
Feb 1 12:42:06 localhost logger: exit standby after 20390
Feb 1 12:52:10 localhost logger: Enter standby
Feb 2 00:57:11 localhost logger: exit standby after 43501
Feb 2 01:07:16 localhost logger: Enter standby
Feb 2 06:25:11 localhost logger: exit standby after 19075
Feb 2 06:35:16 localhost logger: Enter standby
Feb 3 01:47:02 localhost logger: exit standby after 69106
Feb 3 01:57:06 localhost logger: Enter standby
Feb 3 06:25:12 localhost logger: exit standby after 16086
Feb 3 06:35:16 localhost logger: Enter standby
Feb 4 06:25:11 localhost logger: exit standby after 85795
Feb 4 06:35:16 localhost logger: Enter standby
Feb 5 06:25:12 localhost logger: exit standby after 85796
Feb 5 06:35:17 localhost logger: Enter standby
Feb 6 06:25:11 localhost logger: exit standby after 85794
Feb 6 06:35:16 localhost logger: Enter standby
Feb 7 06:25:12 localhost logger: exit standby after 85795
Feb 7 06:35:16 localhost logger: Enter standby
Feb 7 14:02:09 localhost logger: exit standby after 26812
Feb 7 14:12:13 localhost logger: Enter standby
Feb 8 06:25:11 localhost logger: exit standby after 58378
Feb 8 06:35:16 localhost logger: Enter standby
Feb 9 06:25:11 localhost logger: exit standby after 85795
Feb 9 06:35:16 localhost logger: Enter standby
Feb 10 06:25:11 localhost logger: exit standby after 85795
Feb 10 06:35:16 localhost logger: Enter standby
Feb 10 11:57:10 localhost logger: exit standby after 19314
Feb 10 12:08:14 localhost logger: Enter standby
Feb 10 12:10:45 localhost logger: exit standby after 151
MyBookLive:~#
I was away for a few weeks and no one was using the MBL. As you can see from the above log extract it often slept for 85,795 seconds per day during this period. That’s a whopping 23 hours 50 minutes of quality sleep time each day. Per /etc/crontab It typically only woke up at 06:25 each day for 10 minutes to run its daily cron jobs and once a month on the first Sunday at 06:52 to perform its monthly cron jobs (as seen on Sun 01 Feb 2014).
This is all the more remarkable when you consider that this same device originally wouldn’t sleep at all when I first powered it up in October 2011. This “never goes to sleep” saga was detailed in the post:
You might also notice that once the sleep problem was resolved in Dec 2011 while the device was still running the then current firmware, I never again updated the firmware and it is still running that same Ver 02.10.09-124 that was originally released on 17 Nov 2011 !
Back in 2011 would I have bought the device if I had known I was going to have problems? Probably not. However now in retrospect I’m somewhat happy that the problem occurred as I now know much more about networking and Linux than I would had the device worked to spec out of the box. So my advice to anyone currently experiencing problems of one sort or another (especially those on the WD My Cloud forum) - hang in there and you will likely be well rewarded in the end with a better product and some invaluable knowledge that you might not have otherwise obtained.
