New Release - Firmware Version 02.02.02-020 for My Book Live (8/31/11)

[ATY583]

Anyone know how to get the UI (dashboard) back after installing the new firmware?  MBL's SSH is not enabled so I can't use the SSH method.  The WDsmartware/quickview is not picking up the MBL either.  It kept ask me to connect MBL to the local network.  However, MBL is connected to the network and I can see its IP on my router.  Even typing the MBL's IP directly in the browser doesn't work as it displays a blank page.  Really regretting updating the firmware now.

[nogui]

Have exactly the same problem as ATY583 's. Any ideas ?

thanks

[jwcarwenk]

Judging from the posts here, the new firmware has some serious problems. I have also had serious problems.  

I have two 2TB MBL drives connected to the same router. One was working fine before firmware upgrade to 020202-020-20110825.deb and is about 4 months old. It has not seen muchuse and has spent the time in sleep mode. The other is brand new and was immediately upgraded to 020202-020. I am configuring these devices from Mac Leopard.  

After firmware upgrade, I can find both devices and their file systems using Mac's finder. The first issue I noticed is that both devices were in continuous disk operation mode even withno other computers or devices on the network. The older unit flashed yellow-red (or perhaps green-red); the new unit blinked green. The disk operations continued even with the MBLs disconnected from the network (ethernet unplugged). The other problem was communication errors on trying to run diagnostics, which I describe below. 

I turned the two drives off for 24 hours. I turned them on, unconnected to the router. Status lights are red, as they should be. However, both drives are doing incessant disk operations, noisy and quite warm. The operations began as soon as the disks were fully booted. I then plugged the two drives into the network. The new unit has a continuous blinking green light that seems to correctly reflect the fact that it continued its busy disk operations. The older unit resumed the red-green alternating blinking light (this is not a possibility given in the manual). Both units are accessible and I can open files on them. 

Both units are accessible from the dashboard. The dashboard says the status of both units is "good". On the new unit, I try to run a short diagnostic test but  the new unit logouts before it completes the request and is apparently suffering some sort of network disconnect. However, I do not appear to lose my mount point on the Mac. After several tries, it does not log out but I get the error message: "31319 Unknown error. Please ensure you are not facing network connectivity issues and try again." 

 On the older unit, I tried to run the short diagnostic test: it proceeds and then gives an error message: "31319 Unknown error. Please ensure you are not facing networkconnectivity issues and try again." I try to run it again and I get "30400 A bad request was made". This unit will also logout, but not as frequently. The older unit does not get the proper time from NPT server,so something is wrong with its internet access. 

I have downloaded the system status using the support page on the dashboard for both units, but I don't know what to look for in the logs. It would be helpful if someone could let me know how to enable ssh onthe MBL using my Mac. 

Any help would be appreciated, but I think I am dead in the water until a new release of firmware comes out. 
jwc

[Myron]

I wonder...  In the Samba documentation there is something about if the Samba server is configured as a workgroup master browser then there should not be a second Samba sever configured the same because if there is then the two Samba severs endlessly force elections on who is going to be tbe browse list master.

Could this be reason with both MyBook Lives on the local network?

I can't test this. I only have one MyBook Live.

I did read that your drives chatter away even with the network cable unplugged. Could that be Twonky goping through the collection of media on the disc and the `monitor.io` script doing it stuff?

[romanr]

Hi, I'm really tired of that NFS kernel bugs. Can you please switch to the unfs3 user space daemon (lenny) instead of the kernel implementation? That kernel crashes are really unsuitable, because its even impossible to reboot the device remotely when that "Oops" happened. I can see ppl post the same issues for another WD devices, like WDTV. Seems PPC NFS kernel implementation is really unstable.

[Myron]

Actually, the Lunix OS seems to do a good job of keeping an eye on some of the services. When I first encountered the problem I didn't realise where the problem was because as soon as the Samba service panicked and quit then some watchdog within the MyBook Live noticed and reloaded the Samba service which incidentally made me think the problem was with Microsoft's SyncToy. It's when I looked at the logs a week(ish) later I noticed that Samba was having virtual fits.

[romanr]

The system "keeps an eye" on services indeed, but the NFS daemon is running IN-THE-KERNEL, so when it crashes the kernel becomes really unstable. I propose to discard the in-kernel NFS implementation and switch to the unfs3 user-space NFS daemon, which is much more stable and no less in speed. The unfs3 daemon may be taken from lenny distro. Configuration changes are minimal (exports file fix).

[Myron]

I ain't a Linux Guru but the issue I'm describing is with the Samba service. Does that daemon within the kernel ring out just outside of the kernel ring?  I;m asking this because even though (ages ago) Samba was having a dickyfit the Linux OS remained stable at that moment in time.

[GrappaGourmet]

Allow me to shout:

THIS PRODUCT **bleep** !

Now, the facts. My LAN is built around an Airport Extreme router. Stations are iMac nd MacBookPro, both running updated Snow Leopard.

I've bought this unit because I wanted a NAS, not a simple external USB drive. It is 4 months old.

The unit has been working over the last 4 months, but always with bad performance - I mean veeeeery slow access to files (songs and photos, only 200 GB).

All previous firmware updates occurred flawlessly. This last one, however, besides having taken a lot of time to download, got stuck in the beginning of initialization, with a message like "connection error".

I'm sure no one touched the cables and there was not a power failure, so why "connection error" ?

Now, all I get is a black brick with a beautiful blue light that shines white, from time to time - over the last hours.

Resetting the unit was useless. Dashboard is gone. FINDER doesn't find the unit, neither IP SCANNER does.

I never liked this product, from installation day. I guess I was fooled by WD brand name. **bleep**.

Should I return it to WD? From Brazil? At whose expense? **bleep**, again.

[GrappaGourmet]

Sorry for all those "bleeps", but this unit really "bleeped" me off.