New Release - My Book Live Firmware Version 02.32.05-046 (9/26/12)

This is a minor update to my previous post.

At about noon today, I left the house; I turned the drive off (with the dashboard) before I left. By the way, maybe I should mention here that I have neither SmartWare nor TimeMachine installed.

It’s now about 2:30. As soon as I came home I turned the drive back on. All “obvious” systems are “go”: I can access both my data and the dashboard.

I’m going to have to wait awhile to see whether the drive goes to sleep. I checked in the dashboard, and “sleep mode” (or whatever it’s called) is checked.

I’ll keep you posted.

Is there a direct download to the deb file so that we can upgrade locally?

After about an hour, the blue light is on, and my newly updated MBL is slumbering nicely.

Hmmm, just to test, I think I’ll wake it up.

It woke up as expected. :smiley:

For me, at least, this update has been OK.

JoeyG wrote:

After about an hour, the blue light is on, and my newly updated MBL is slumbering nicely.

 

Hmmm, just to test, I think I’ll wake it up.

 

 

It woke up as expected. :smiley:

 

For me, at least, this update has been OK.

If you check user.log, how long did it stay asleep? I mean, I see the blue light and I can wake it up. My problem is it wakes itself up :slight_smile:

HalexF wrote:


If you check user.log, how long did it stay asleep? I mean, I see the blue light and I can wake it up. My problem is it wakes itself up :slight_smile:

Hi HalexF,

I only let it sleep a couple of minutes before waking it up.

I’ll watch it over the next couple of hours and report again.

Either this is old news or mybooklive doesn’f want to find the update!!!

Current F/w is  02.32.05-144 which was released a while ago? is the 02.32.05-046 f/w an update to this or are WD still running split versioning of Firmwares?

was the update pulled againnn??? i cant seem to download it from the WD website

I’ve now been observing the drive for about four hours.

It goes to sleep as it should, but as soon any there’s any activity on my network, either locally or with the internet, the light goes from blue to solid green.

It only “flashes” green when I directly access it.

I can understand why local network activity would cause the drive to go “on alert” (solid green color), but I’m not sure why using the internet does.

In any case, as I’ve said, the update pretty much does what it should, at least in my context, i.e., no shares, no remote access.

Theagustin wrote:

was the update pulled againnn??? i cant seem to download it from the WD website

I think they’ve got the manual update turned off.

02.32.05-144 and 02.32.05-046 are equivalent. The 02.32.05-144 was the patch for those people that downloaded the firmware before we pulled it. You are up to date.

And yes - you can not manual update at this time. You will need to go into the dashboard and do a check for update if it hasn’t already detected the new firmware.

JoeyG wrote:

I’ve now been observing the drive for about four hours.

 

It goes to sleep as it should, but as soon any there’s any activity on my network, either locally or with the internet, the light goes from blue to solid green.

 

It only “flashes” green when I directly access it.

 

I can understand why local network activity would cause the drive to go “on alert” (solid green color), but I’m not sure why using the internet does.

  

Okay, thanks. The funny thing is, I see the exact same sleep pattern when I’m using my Apple TV, pulling content from the MBL constantly, having my computer turned on with hourly backups via Time Machine and so on. Five minutes here, a few seconds there…

Only once have I seen it asleep for hours, that was when my laptop was at a friends’ house over night. But I mean, I turn it off at night so there really shouldn’t be any different…

It’s very strange, in any case. And there still has been no answer from any WD staff… Not to say “oh, that’s odd” or “we know about the problem” or anything else. Equally strange behaviour from them as from the MBL in other words. Must be a WD thing :wink:

Hi

I have updated from 02.32.05-044 to 02.32.05-144 via Dashboard with success.

Since the version before addition of AirPlay funtionality to the MBL/WD2GO app,  I haven’t been able to use remote access via WD2GO, but with this patch all functionality is back to normal, except LED light. But it is a minor problem to me.

If no new “missing features” arrive in the near future, I will sit back relaxing and won’t upgrade more firmware :dizzy_face:

Regards

Brondt

@HalexF

I’m going to have to revise my analysis.

The light has now been solid blue for a couple of hours. What changed in the constellation is that I turned off my Lenovo S20, which might have “wake-on-lan” still activated in the BIOS, though I’m not sure if this has anything to do with it.

Perhaps even more important is the fact that the S20 is the only one of the nine computers we have that runs Win7 (pro x64). All the others have 32-bit XP SP3.

Currently there are two cable-connected computers and one on wi-fi running on our little network. As I’ve said, the light has been blue since I turned off the S20 a couple of hours ago.

Which OS are you using?

I haven’t changed firmware since last spring, and my MBL has always gone from green to blue and back seemingly at random. Considering that I have a desktop, two laptops, two printers, a Roku, a web-enabled blu-ray player, a Kindle and a smartphone on the local network, I’m pretty sure I’ll never figure out what’s causing it to wake. Not a big deal to me though.

Having a problem updating IP address of both my WD Live, 1 TB and 2 TB, drives not updating their DHCP information.  If I have to boot the router for any reason I have to unplug the drives and restart them to obtain new IP address.

I did not have to do this with previous firmwares.

Haven’t started updating yet, but the update notification is point to the wrong release notes.

It’s pointing to http://support.wdc.com/nas/rel.asp?f=http://www.wdc.com/wdproducts/updates/?family=wdfmb_live23205#38;lang=eng which is the 2.32.05 - 144 release notes.

Really!  Really? 

After 6 months of waiting for the WD2Go relay connection problem to be fixed, I upgraded to 2.35.05-046 and the problem I documented in this thread and which is specifically listed as being fixed in the release notes, still occurs.  

The drive still does not send my external ip address to the www.wd2go.com server when issuing the command to do the port forwarding check so the server returns an error.  The drive interprets this as if the port forwarding has failed and the drive always switches to “relay mode”.  This despite the fact the ports are open.

This is likely because the following error is generated when communicationmanager is run:

“getaddrinfo() error : Name or service not known”

I reported the problem back  in June and I was told it was going to be fixed in the next firmware, which was pulled.  Finally this one comes out which specically lists this problem as being fixed in the release notes, but it’s not fixed. 

Now I’m forced to go back to my work around of using my router (which isn’t currently working since “curl” no longer runs on the latest version TomatoUSB for whatever reason).   I shouldn’t have to work around this bug.

:angry: :angry: :angry: :angry: :angry:

JoeyG wrote:

@HalexF

 

I’m going to have to revise my analysis.

 

The light has now been solid blue for a couple of hours. What changed in the constellation is that I turned off my Lenovo S20, which might have “wake-on-lan” still activated in the BIOS, though I’m not sure if this has anything to do with it.

 

Perhaps even more important is the fact that the S20 is the only one of the nine computers we have that runs Win7 (pro x64). All the others have 32-bit XP SP3.

 

Currently there are two cable-connected computers and one on wi-fi running on our little network. As I’ve said, the light has been blue since I turned off the S20 a couple of hours ago.

 

Which OS are you using?

I use OS X. But I mean, since I see the exact same sleep patterns both with all phones, pads, computers and other devices connecting to the router turned off as with them all turned on and connected - I doubt the problem lies somewhere else than either with the MBL or with the Airport Extreme Base Station, or their incompatibility.

I guess I’m mainly afraid that it will shorten the life span of the drive, constantly spinning up and down.

mbrondt wrote:

Hi

 

I have updated from 02.32.05-044 to 02.32.05-144 via Dashboard with success.

 

Since the version before addition of AirPlay functionality to the MBL/WD2GO app,  I haven’t been able to use remote access via WD2GO, but with this patch all functionality is back to normal, except LED light. But it is a minor problem to me.

 

If no new “missing features” arrive in the near future, I will sit back relaxing and won’t upgrade more firmware :dizzy_face:

 

Regards

Brondt

As of this morning I noticed that it actually still loses connection via WD2GO after a couple of  minutes, then I can go back to “root”  of the device, then re-connect and it will work again. It seems to be a problem only on 3G, when on a WI-FI connection, it works flawlessly??

Regards

Brondt

Craaaap - still can’t access my drive through WD2GO :frowning:

Should I rebuild the DB would that possibly help?