Sadly, I have the same problem. I bought the device 5 days ago and immediately updated the firmware. So I do not know how it would be behaving before the upgrade.
In the first days, with 1500 files, I several times saw the blue light, which lasted long or maybe did not notice the green light coming back.
But after āpurchasingā the last version (blame my best selling Samsung led Tv which is not compatible with the old version of twonky comingĀ with my new brand device !!), I noticed that the drive failed to sleep or woke up to soon. and saw my drive with blinking green light for 24 hours. After that I tried several ways including rebuilding twonky db, disabling all media receivers, googling for disk activity etc.
Then, I removed all media feeds checkboxes in the config page and all of a sudden the disk activity stopped.
But again cannot sleep because of a byte of disk activity seen around every 5 minutes.
other than this I did not touch any of the original system file etc.
62 seconds that all he can sleep: and this loops again for other 62 secondsā
Sep 15 00:50:41 localhost logger: Enter standby
Sep 15 00:51:43 localhost logger: exit standby after 62
We have another release of the firmware coming out next month. We have some additional things we are looking at to resolve a number of issues that have been reported here on the forums.
I got some kind words. Some software on the MyBook Live W.D. may not have much control over. Iām assuming the Twonky Media server is one of them. Not sure about the Remote Control part (WD2GO). Iāve been critical a bit myself but always throught about things three times to make sure Iām critical for the right reason.
At the moment I donāt operatte Twonky iTunes or the remote control and the MBL does sleep. Mind youā¦Ā I do recall a thread on here about the drive idle time out being so short the the drive heads ramp and un-ramp themselves a thousands of times an hour(ish) and that this feature is is to save energy as the MBL is supposed to come with energy saving credentials.
Hmmmā¦Ā Ā If the drive spends more time awake than asleep then thatās the energy conservation down the pan?
Maybe, somehow make it easier to turn on and off the additional services?Ā Could there be a simplified version of the Web UI where is a mobile phone access it through itās own browser then options are presented to turn on and off the Twonky, iTunes, remote access and FTP services?Ā (Just an idle idea.)
Iām on 02.02.02-020ļ»æ also and the device doesnāt sleep; iāve turned off twonky, itunes and remote control aswell - no luck. After I turn off FTP, it goes to sleep and stays there. With FTP on it doesnāt or wakes up after 60 seconds.
Because of the chrooted vsftpd I was thinking because the process is touching /shares it would keep the WDLive from sleeping as this is the HDD and not the ramdisk. So I commented the #anon_root=/shares in /etc/vsftpd.conf, restarted the vsftpd service and now my unit sleep even when FTP is running. The only downside, every user that has FTP access can see the entire folder structure (/ instead of /shares) but in my network environment thatās no problem. If you expose your FTP server to the outside world that could be a problem!
Anyway, Tony, maybe something to check out! Iām a new WDLive user and Iām loving it so far.
Now this is strange because my /etc/vsftpd.conf has the line ā¦
anon_root=/shares
Ā ā¦ and my MBL sleeps.Ā So what is different between your VSFTPD configuration and mine?Ā Can you post the entire contents of your /etc/vsftpd.conf here?
Also, anonymous access should be disabled. Have you enabled the anonymous login? If youy have then these automatic bots trying to find vunlarable FTP services will be hitting your FTP service on your MBL like mad because they can login to anonymous.
This is the W.D. prefered factory VSFTPD configuration . . .
Updated to F/W 02.03.01-024 from 02.02.02-020 late last night (Tues 25 Oct 2011 shortly after the release was posted) and it didnāt resolve the inability of my MBL 3TB to go into standby. With āstandbyā enabled and set to 10 minutes and just about all kinds of access disabled (Media, ftp, Remote Access, etc) the drive briefly goes into standby and quickly starts up again. The Blue standby light stays on for about 61 seconds. However by listening to the drive inside the enclosure I hear the hard drive spin-down and almost immediately spin-up again - so its actually only in standby for 1 or 2 seconds. The log reflects that duration that the Blue led is on.Ā I have not transferred any files to the MBL - so its not transcoding files (whatever that is).
The following was extracted from /var/log/user.log:
Oct 26 00:18:14 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:29:00 localhost logger: Enter standby
Oct 26 00:30:01 localhost logger: exit standby after 61
Oct 26 00:38:28 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:38:28 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:38:40 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:40:40 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:40:40 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:41:35 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:41:35 localhost apache2: 192.168.0.11 WebUI::session_id=d93e21b83c94185858db5bc3641a913c
Oct 26 00:53:17 localhost logger: Enter standby
Oct 26 00:54:18 localhost logger: exit standby after 61
Oct 26 01:05:27 localhost logger: Enter standby
Oct 26 01:06:28 localhost logger: exit standby after 61
A possible clue as to the problem: Myself and a friend both bought 3TB MBLs on the same day. I got the last one from Future Shop (Kanata store in Ottawa, Ontario) and he got one from Best Buy (Kanata store). Mine came with F/W 02.01.06-26 and when I read that the F/W wouldnāt go into standby I immediately (within 45 minutes of first power-up) upgraded to F/W 02.02.02-020. After this F/W update the drive would not go into standby except as descibed above. My friends MBL was possibly an older model and contained F/W 01.xx.xx - somethingĀ prior to 01.05.07. So he had to update his F/W twiceĀ - once to get to 01.05.07 and again to get to 02.02.02-020. Unlike my MBL, his drive reliably goes into standby and stays there. So Iām thinking that possibly the problem may be due to me having a newer version of MBL that he does. Possibly I have a different hardware rev or possibly the F/W in my hard drive itself is different than his. If this theory is correct perhaps WD may be able to track down the problem by looking into what changes have gone into the newer versions of MBL.
I consider this problem so severe that I will not be using my MBL untilĀ a fix to the standby problem is available. For WD, email me if you want my S/N if you think it will assist in tracking down my H/W and F/W rev levels.
Regards to WD and Good Luck with your troubleshooting,Ā WilliamH
Mine was preinstalled with F/W 01.xx.xx, after upgrading to 02.02.02-020 I also have standby problems. Although not the entire time, sometimes it sleeps just fine. Other times (mostly during the night) it wakes up every 60 seconds after sleep. I have the feeling something is still running in the bg, when I ssh to the box I see the ālsā command active in top.
Also in /var/log the mediacrawler.log is updated frequently with error messages. Weird thing is that i disabled the mediacrawlerā¦:
MyBookLive:/var/log# tail mediacrawler.log
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
I purchased 3TB MBL yesterday, updated to the very latest firmware, disabled Twonky, iTunes, remote and FTP, backed 400GBs of audio and video data successfully overnight ā¦ but the drive never sleeps, just like many others have reported here. Iām considering taking this thing back because I need it to sleep, unless thereās something else that I missed that I should be doing.
Excerpt from `/var/log/user.log`
Nov 1 06:39:23 localhost logger: Enter standby
Nov 1 17:02:23 localhost logger: exit standby after 37380
Nov 1 17:23:10 localhost logger: Enter standby
Nov 1 17:24:11 localhost logger: exit standby after 61
Nov 1 17:35:21 localhost logger: Enter standby
Nov 1 17:44:49 localhost logger: exit standby after 568
Nov 1 17:55:53 localhost logger: Enter standby
Nov 1 18:25:43 localhost logger: exit standby after 1790
Nov 1 18:36:47 localhost logger: Enter standby
Nov 1 23:18:39 localhost logger: exit standby after 16912
Ā You sure you donāt have any other deviced on your network thatās interacting with your MyBook Live to cause it not to sleep?
A friend of mine had the same issue with a Verbatim Mediashare, which was fixed when he port forwarded his NAS in the router settings. I donāt know if it will help here though.
My MBL is sleeping now like a charm ā¦ must have been the pics like discussed earlier in the thread. But I still have iTunes, remote access and Twonky disabled. Iām going to try enabling them one at a time and see what happens.
from my experience if thereās Remote Access enabled, MBL doesnāt sleep. It could be caused by 300 GB of photos on it. Have no clue how long Ā it takes to process it. It would be worthy to give it a try to enable Remote Access if thereās no data/very few of data.
See my posting of 26 Oct 2011. My MBL 3 TB is running the latest F/W (02.03.01-024 of 25 Oct 2011) and it will not reliably go into sleep mode (standby).Ā I have never added ANY files to it. Media, ftp and remote access are all disabled and the browser is not accessing the DashBoard. With standby set for 10 minutes the drive will still not sleep for longer than 61 seconds at 10 minute intervals. The 61 seconds is the period that the Blue LED is on. The actual drive spindown periodĀ (as determined by listening to the drive) is much shorter - on the order of 1 or 2 seconds. The drive was received with F/W 02.01.06-026 installed and it did not sleep as received. It did not sleep after update to F/W 02.02.02-020 that supposedly fixed the standby problem. It still does not sleep with the latest F/W (02.03.01-024) but I was not expecting that this would fix the problem as that F/W release was advertised as a security fix. I have not had any reply from WD staff as to whether they are still actively looking into this problem. I hope that they are still working on this problem as I consider the drive unusable while this problem still exists.
There is no difference if I disconnect the MBL from the router (an SMCD3GN). The drive still refuses to go into sleep/standby mode except as previously reported (for 61 seconds (1-2 seconds actual) every 10 minutes). I assume that this implies that whatever is preventing it from sleep/standby is strictly an internal process.
Iām running WinXP SP3. However I donāt think that makes any difference as the MBL 3TB will not sleep/standbyĀ even if it is the only device connected to the router - all with no remote access, media or ftp enabled. In fact the MBL wonāt go to sleep/standby even if it is not connected to the router. i.e. when itās not connected to anything.
