New Release - My Book Live Firmware Version 02.11.09-053 (4/23/12)

[Myron]

Gather the log files and tell what the last few lines of user.log are.

---

whsbuss wrote:
Still will not sleep. Any suggestions?

---

[whsbuss]

How do I get to the logs?

[Technaz]

Uodated firmware.. No hassles as before.. Well done WD. But please improve Customer Care in Singapore...Instead of helping for a workaround the last time they asked me to escalate to US team....

[TonyPh12345]

---

whsbuss wrote:
How do I get to the logs?

---

Via the Web UI... 

SUPPORT --> Create & Save (report)

[JoeyG]

I had exactly the same thing happen, and - like you - was lucky and got it to work using the manual update. It's a bit crazy that this version specifically says it fixes the "stuck at 10%" issue. I never ever had this problem before this version, so somebody's done something wrong. With all due respect to Tony, and recognizing how difficult it must be to program an update that's supposed to work on every computer no matter what the configuration is, I think his claim that this version is "rock solid" needs to be mitigated.

[Myron]

But here is the thing JoeyG.  It's a Network drive.  Essentially a seriously cut-down computer.  All the WebUI does is upload the update file into the MyBook Live and the entire update process happens inside the MBL. The process meter just seems to be there to reassure the user that the update is happening.

Point of proof if I update my MBL differently.  I manually copy the upgrade file to the MBL and then on the MBL's Linux command prompt invoke the script to start the update.  My computer's only then acting as a dumb Telnet terminal.

I would also be mightily puzzled why out of so many units with identical hardware, why so many would fail to update.

Only thing I can think of is that the firmware that is being replaced put the MBL's operating in such a state to interfere and break the update process.

[jr1221]

When I first tried to update my firmware it got stuck at 10% a time or two then I connected a ethernet cable directly from my router to my computer and it worked fine.  Although my wireless card shows 130 Mbps it still must not be as stable as my wired connection.  It worked first try after running a cable directly from the router to the pc.

[rocketscientist]

I'm wondering if maybe some of the "stuck at 10%" problems on this update are just not giving it enough time. I know that on the previous firmware update it was reported to be stuck for more than an hour, and that's obviously a problem. My observation on this update is that the progress meter is not at all linear with time. I didn't have my stopwatch out, but mine stayed at 10% for five minutes or so. I was starting to get a little nervous, but then it immediately jumped straight to 50%. The last 90% barely took any longer than the first 10%.

[barrygreybeard]

"When I first tried to update my firmware it got stuck at 10% a time or two then I connected a ethernet cable directly from my router to my computer and it worked fine."

I thought that when instigating an update from the UI the MBL would then take over and download the update direct to the MBL itself, but if it downloads it to the PC that started the update and then transfers it to the MBL, that could explain some of the long installation times if using a PC on an unstable wireless connection? Just a thought.

[Julian]

I initially received four error messages in a row that the update had failed. However, the device now reports it has the current firmware. I suspect the install package may not be checking carefully enough to determine what has already been installed. I have advised WD via trouble report reference is 120425-004734.