Sorry fellows - Sleep/StandBy is still not working. Same problem as when the MBL 3TB was received in September 2011 with F/W 02.01.06-26. Sleep/StandBy didn’t work as received or with updates to F/W 02.02.02.020 or 02.03.01-024. And now it’s still not working with F/W 02.10.09-124 released Thur 17 Nov 2011. I have installed no software from CD, have transferred no files to the MBL, and have not enabled Media, FTP or Remote Access. The drive spins down every 10 minutes for about 1 second (as determined by listening to the drive) and the Status LED changes from Green to Blue for a period of 60 or 61 seconds and then goes back to Green. The var/log/user.log file reports reliably the transition of the Status LED with the entries “Enter standby” (LED goes from Green to Blue) and then 60/61 seconds later reports “exit standby after 6x” (LED goes from Blue to Green).
Extract from user.log taken after the F/W update follows:
Nov 18 00:08:45 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:08:55 localhost logger: Wait for system ready - skipping start of orion services…
Nov 18 00:08:56 localhost rc.local: begin script:
Nov 18 00:08:56 localhost logger: /etc/rc.local: currentRootDevice = /dev/md1
Nov 18 00:08:58 localhost 0_wd-nas_upgrade: begin script: /etc/rc.local
Nov 18 00:08:59 localhost NSPT_upgrade: begin script: /etc/rc.local
Nov 18 00:08:59 localhost admin_upgrade: begin script: /etc/rc.local
Nov 18 00:08:59 localhost logger: PATH=//sbin://bin://usr/bin://usr/sbin://usr/local/bin://usr/local/sbin
Nov 18 00:08:59 localhost logger: PKG=Admin
Nov 18 00:08:59 localhost logger: CALLER=rc.local
Nov 18 00:08:59 localhost logger: PKG_DIR=/etc/wdcomp.d/Admin
Nov 18 00:08:59 localhost logger: mountBasePath=/
Nov 18 00:08:59 localhost logger: restorePath=/
Nov 18 00:08:59 localhost logger: SETTINGS_DIR=/etc/wdcomp.d/Admin/saved_settings
Nov 18 00:08:59 localhost logger: OLD_SETTINGS_DIR=etc/wdcomp.d/Admin/saved_settings
Nov 18 00:08:59 localhost logger: ~ admin_upgrade, trigger = rc.local, condition = /etc/.updateInProgress
Nov 18 00:08:59 localhost logger: refreshing paths and permissions…
Nov 18 00:08:59 localhost pkg_postinst: begin script:
Nov 18 00:08:59 localhost networking-general_upgrade: begin script: /etc/rc.local
Nov 18 00:08:59 localhost 0_wd-nas_default: begin script: /etc/rc.local
Nov 18 00:08:59 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:09:00 localhost NSPT_default: begin script: /etc/rc.local
Nov 18 00:09:00 localhost WebUI_default: begin script: /etc/rc.local
Nov 18 00:09:00 localhost apache2: 192.168.0.13 WebUI::session_start()
Nov 18 00:09:04 localhost apache2: 192.168.0.13 WebUI::session_start()
Nov 18 00:09:04 localhost apache2: 192.168.0.13 WebUI::session_start()
Nov 18 00:09:05 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:09:05 localhost apache2: 192.168.0.13 WebUI::session_start()
Nov 18 00:09:10 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:09:21 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:09:23 localhost admin_default: begin script: /etc/rc.local
Nov 18 00:09:23 localhost apache-php-webdav_default: begin script: /etc/rc.local
Nov 18 00:09:23 localhost date-time_default: begin script: /etc/rc.local
Nov 18 00:09:23 localhost networking-general_default: begin script: /etc/rc.local
Nov 18 00:09:26 localhost logger: /usr/local/sbin/monitorio.sh: waiting for system to become ready…
Nov 18 00:09:29 localhost logger: Starting orion services: miocrawlerd, mediacrawlerd, communicationmanagerd
Nov 18 00:09:30 localhost logger: WD NAS: Email alerts REST API failed to return Success
Nov 18 00:21:40 localhost logger: Enter standby
Nov 18 00:22:41 localhost logger: exit standby after 61
Nov 18 00:32:48 localhost logger: Enter standby
Nov 18 00:33:48 localhost logger: exit standby after 60
Nov 18 00:43:55 localhost logger: Enter standby
Nov 18 00:44:56 localhost logger: exit standby after 61
Nov 18 00:55:03 localhost logger: Enter standby
Nov 18 00:56:03 localhost logger: exit standby after 60
Can we please go back to the drawing board on this one as I expect that I will not be the only one with the same problem. Thanking you in advance (for the next FW release and hopefully a final fix to this problem) As I did moments after my last F/W update, I will now be powering down the MBL and will not use it again until this problem is resolved.
Nov 18 02:51:04 localhost logger: Enter standby
Nov 18 02:52:06 localhost logger: exit standby after 62
Nov 18 03:36:37 localhost logger: Enter standby
Nov 18 03:37:38 localhost logger: exit standby after 61
Nov 18 03:47:42 localhost logger: Enter standby
Nov 18 06:25:07 localhost logger: exit standby after 9445
Nov 18 06:35:11 localhost logger: Enter standby
Nov 18 12:45:33 localhost logger: exit standby after 22222
Nov 18 12:55:36 localhost logger: Enter standby
Nov 18 12:56:38 localhost logger: exit standby after 62
Nov 18 13:06:42 localhost logger: Enter standby
Wonder for the reasons for coming out os standby one minute after it’s gone into standby. I’m guessing this is to do with the way /usr/local/sbin/monitorio.sh works.
We tested sleep pretty extensively this time. It may be something else on your network. Do you have a browser window open to the My Book Live Dashboard? We do make calls to the drive from the Dashboard, so that will keep it from sleeping. Also, if you use the Quickview application, that also makes calls from time to time. Disable that app to see if it sleeps. I have been running this several months here at WD and at home and see it sleeping most of the time.
Thanks for getting back to me on my continuing MBL 3TB Sleep problem. I should have mentioned it in my earlier post in this thread but I took care to move the browser away from the Dashboard while I was looking for the MBL to Sleep. I was however accessing the drive via SSH (via PuTTY) to capture the user.log. From previous trials I realize that if a browser is pointed to the MBL you get entries like:
and that this keeps the MBL awake. I think you may have mentioned this in a previous thread. (I don’t think accessing the MBL via SSH keeps it awake). Also this continuous drive running (except for a one (1) second spindown every 10 minutes) occurs even if the router is disconnected from the MBL.
There are a couple of apps called Quickview (I have the real old one for viewing files). I presume you were talking about the newer Quickview app associated with iTunes. I don’t have that app nor do I have iTunes loaded on my WinXP SP3 computer. At any rate, no Quickview app was running when the log file was made (and the browser (FireFox 8.0) was not accessing (or even pointed to) the Dashboard).
Since you don’t seem to have many (any?) drives in-house that exhibit this problem, I would be willing to try “anything” to resove this problem So feel free to ask me to try any sort of test or trial that you can think of to try and capture data that would help your gurus nail down this problem. I think that the MBL is a great concept and congratulations to WD for coming up with it. I would really like to get going with all the things that the MBL was designed for but am reluctant to start until “we” resolve the Sleep issue.
quickview is the little blue and white icon in your notification area that, when you hover over it, will show capacity, temperature status, and if you right click, lets you shut down or launch the dashboard
What do you mean by that? We allways have support direct connections between your My Book Live and your remote device. The issue is that not all routers are the same, and not all networks are the same. We have included a new option in the UI to allow you to specifically set the ports that WD 2go will use. You will then need to go into your router and configure port forwarding to the My Book Live IP to use those ports.
Just updated to the latest firmware that was released on 17th using automatic update via Chrome, just like what I did a couple weeks back. A little bit of a bumpy ride this time. I applied the update and then suddenly My Book Live got disconnected and even device manager fail to locate it properly (triangle exclamation mark). Tried updating the drivers as well but to no avail. This left me no choice but to reinstall WD SmartWare including the device drivers, in short, everything, before I could get it back online again - WHEW!!
Now the updated version seems to solve nearly everything I’ve encountered so far- thumbnail image preview is now fully functioning, the My Book Live drive icon under My Computer now being corrected (no more 2 identical and confusing icons showing wrong capacity info), lightning fast loading speed, and so much more.
Thank you, WD, for your excellent job and not forgetting us end users, unlike other companies do. You guys are truly one of a kind and please keep up the good work!!
Ah. Good point. The QuickView application. Yes, I do have that active. SmartWare is not installed. For me it’s not a big issue. I guess when all the computers are off then it makes sense for the MBL’s drive to spin-down and remain spun down until needed. Exactly what it’s doing. Thanks.
WDTony wrote:
We tested sleep pretty extensively this time. It may be something else on your network. Do you have a browser window open to the My Book Live Dashboard? We do make calls to the drive from the Dashboard, so that will keep it from sleeping. Also, if you use the Quickview application, that also makes calls from time to time. Disable that app to see if it sleeps. I have been running this several months here at WD and at home and see it sleeping most of the time.
Upgrade via the WebUI went trhough fine. 2 issues so far
it removed my crontab which I had to recreate from memory
oddly my XP PC’s could no longer access their mapped drives using the mybooklive hostname (mybooklive). I kept getting the wonderfull network connection failed windows message. I could ping the MBL by hostname and IP address
in the end I had to disconnect the mapped drives and recreate them using the IP address rather than the hostname. even a local hosts file in windows made no difference ?