Energy saving not working well anymore after upgrading to latest firmware version 02.43.10 - 048

Hello,

energy saving is not working well anymore after upgrading to latest firmware version 02.43.10 - 048 (06/22/2015).

Before the upgrade, I could see the NAS switching correctly to stand-by (blue LED) and sitting in that state most of the time when not in use.

After the upgrade, the NAS stays always on (green LED). Sometime it recovers after rebooting the box, but then it stays green forever after using it once and disconnecting.

Can you please issue a new firmware update to address this ASAP? Being always on could damage the device.

Thanks,

Leo

Hi there and welcome to the WD community.

Perhaps there could be a device that is trying to access the drive remotely, try to reset the device by pressing the reset button on the back of the unit on top of the Ethernet port for 3 to 6 seconds see if this helps. if this does not work i would suggest contacting support for further assistance:

http://support.wdc.com/country/index.asp?lang=en%22

I am having the same issue after updating the firmware.

I found an old thread about the same problem:

http://community.wd.com/t5/My-Book-Live/My-book-live-never-sleeps/td-p/199912

I read through all 18 pages and tried everything that was suggested by different members but nothing helped so I looked into activity logs to try and find what was causing it to never sleep.

I noticed my recent log looked something like this:

Aug 25 03:20:31 MyBookLive logger: exit standby after 6
Aug 25 03:32:44 MyBookLive logger: exit standby after 128
Aug 25 04:13:15 MyBookLive logger: exit standby after 12
Aug 25 04:25:25 MyBookLive logger: exit standby after 126
Aug 25 04:45:40 MyBookLive logger: exit standby after 6

So even whilst I am asleep, with no devices on, it would not go into standby for more than a few minutes without automatically waking up again. Prior to updating firmware my device would sleep most of the day without waking up and my log looked like this:

Aug 10 09:45:56 MyBookLive logger: exit standby after 23738
Aug 11 03:00:14 MyBookLive logger: exit standby after 61453
Aug 11 18:25:55 MyBookLive logger: exit standby after 54936
Aug 12 03:00:14 MyBookLive logger: exit standby after 30254

I noticed that after every time it exited standby, there would be lots of entries mentioning “OrionClient” in one of the log files so I figured that was the culprit. I found this thread when looking into Orion:

http://community.wd.com/t5/My-Book-Live/Runaway-mediacrawler-The-Ultimate-Solution/td-p/578720

I followed the instructions to disable Mediacrawler, but it still didn’t help. However in one of the comments underneath, someone mentioned a command to stop Orion. They said that Mediacrawler is part of the Orion service, together with Miocrawler and Communicationmanager. However disabling Mediacrawler itself never worked but disabling Orion did enable the My Book Live to enter sleep mode and remain there without instantly waking back up.

After rebooting my device, Orion is re-enabled and again the My Book Live will wake up almost instantly upon entering sleep mode so it is definitely Orion causing it (in my case).

You can check your logs if you go into your My Book Live UI then go to “Support” at the side. Click “Create & Save”, under “Create and Save System report”. It will download a zip folder for you. Inside will be a “log” folder and inside that will be a “user.log” file. If you open that you should see how often it goes into standby and for how long. There should also be a “messages” and “messages.1” file inside the “log” folder. Open with a text editor and search for the world “standby” to see if you can figure out what is happening after it exits standby. For me there were lots of “OrionClient” entries. If yours is the same, try follow the disabling Mediacrawler instructions link above but use the stop Orion command in the bottom of comment 9 of that thread.

I hope WD release a fix soon since it doesn’t appear to be an isolated case and for me, it’s only temporarily fixed and was not something that could be achieved with a simple minor setting change. But hopefully that gives you a general direction to solving the issue. Although having read through the 18 pages of the first link, it appears different people have had different solutions despite the problem being the same. If only there was a way to rollback the firmware to an older version.

Thanks guys for taking the time and looking into this.

I’ve double-checked again today, since I didn’t have much time during the week, and I can see situation slightly improved after leaving the device powered off for one day:

Aug 26 00:17:07 NAS logger: exit standby after 1300 (since 2015-08-25 23:55:27.464486773 +0200)
Aug 26 03:00:07 NAS logger: exit standby after 9176 (since 2015-08-26 00:27:11.440486532 +0200)
Aug 26 05:04:31 NAS logger: exit standby after 6256 (since 2015-08-26 03:20:15.876487281 +0200)
Aug 26 09:16:27 NAS logger: exit standby after 14512 (since 2015-08-26 05:14:35.956486873 +0200)
Aug 26 10:06:34 NAS logger: exit standby after 2403 (since 2015-08-26 09:26:31.732488199 +0200)
Aug 26 12:15:29 NAS logger: exit standby after 6742 (since 2015-08-26 10:23:07.776487780 +0200)
Aug 26 13:42:22 NAS logger: exit standby after 4609 (since 2015-08-26 12:25:33.904485891 +0200)
Aug 26 22:00:11 NAS logger: exit standby after 29265 (since 2015-08-26 13:52:26.276486838 +0200)
Aug 27 03:00:14 NAS logger: exit standby after 16795 (since 2015-08-26 22:20:19.764487250 +0200)
Aug 27 12:30:46 NAS logger: exit standby after 33024 (since 2015-08-27 03:20:22.528486618 +0200)
Aug 27 20:45:17 NAS logger: exit standby after 29067 (since 2015-08-27 12:40:50.540486872 +0200)
Aug 27 21:05:38 NAS logger: exit standby after 7 (since 2015-08-27 21:05:31.444484988 +0200)
Aug 27 21:17:07 NAS logger: exit standby after 85 (since 2015-08-27 21:15:42.688486901 +0200)
Aug 27 23:40:47 NAS logger: exit standby after 8016 (since 2015-08-27 21:27:11.752487192 +0200)

Now, that said, I still agree with Onelement there must be some firmare problems there that needs to be fixed. Maybe it would be a good idea creating a support case and submitting the logs of the findings you collected. That would definitely give the WD team a clue about what’s going on and how to fix the issue.

Thanks,

Leo

After the last firmware update

 version 02.43.10 - 048

My Book Live 3 To, never go in sleep mode…with the blue led. Always stay flashing green…even with no network cable connected.

Before the update…absolutely no prob at all.

Now…

  • Problem with the sleep mode

  • After sometime no access to the device setting (have to power off/on)

  • After sometime no access to all my file.(have to power off/on or if i am lucky reboot in the setting)

So it’s not a rock solid Firmware…never have a problem with the previous firmware.

Now…its just a PITA…

I read alot to found a solution, and nothing in this forum (permanent solution)

Thanx for your help!