How I unbricked my MBL after the November 2012 firmware update

WD Legacy Products My Book Live
21

here is the output from:

MyBookLive02:~# tail -n 50 /var/log/daemon.log
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:12:45 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket

and:

MyBookLive02:~# tail -n 50 /var/log/daemon.log.1
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket
Dec 30 16:05:07 MyBookLive02 cnid_metad[3040]: error in accept: Socket operation on non-socket

22

Best I can suggest is to manually keep an eye on those two log files. They are already flushed out with that error (issue known to W.D.) so I suggest you just erase them and reboot the MyBook Live.

Obviously this does not affect every MAC owner so is there any service on your MAC you can temporerally turn off to stop this problem from manifesting itself?

Once you free-up space you can correct those two configuration files and the Dashboard UI on your MBL should burst into life.

23

Not sure about what services on my Mac I can turn off but will take your advice and manually keep an eye on the log files and erase them when they get too big and wait on a proper fix from WD.

Thanks for all you help on this!  I am sure glad I saw that advice regarding enabling ssh otherwise I would be sending this unit back for a refund.

The bricked UI does seem to be linked to the size of these two files because once I disappeared them it came back even before a re-boot.

So thank-you thank-you thank-you and have a great and HAPPY NEW YEAR!!!

24

So, am new to this.I just bought a MBL, and i keep reading a lot about enabling the SSH before doing a firmware update…how would I do that? I want the new firmware to enable the WD 2Go (which is why I bought this drive).

Once I enable SSH, what is the best way to update the firmware?

25

see greatbrit’s first post in this subject and follow it exactly.

26

To enable SSH:

  1. Assuming Windows, go to ‘Network’.  You should see ‘MyBookLive’ and an all caps “MYBOOKLIVE”.  If you have the correct ‘view’ you’ll see the former as a black image that looks just like the MBL.  Double click that and it should bring up your browser to the correct IP address.  Or you can just type mybooklive/UI/login , or if you already know the IP: (in my case) 192.168.0.104/UI/login into your browser.

  2. You should now be in the User Interface (UI), also known as ‘dashboard’ of your MBL.  Or you may have to log in first.

  3. Now go to mybooklive/UI/ssh and set your SSH

  4. while you are at it, click on ‘settings’

  5. click on ‘Media’ and check the ITunes and Twonky check boxes, and click on ‘Network’ and check the box for FTP

27

Thanks guys, I got the firmware updated and enabled ssh while not bricking the dashboard. This is my second unit, I bought one yesterday and started the setup without reading the forum. The dashboard bricked on that one so I returned it to the store and got a new one.

I know nothing about sshs or any of this technical stuff so it is good to have you all here for support.

28 
DEVICEID="<censored>"
DEVICEAUTH="XXXXXXXXXX <censored> XXXXXXXXXX"

My desperation outlawed common sense ! Good Point.

-Eff

29

Should be simple. Disassociate your MyBook Live with WD2GO and re-register your MBL from scratch. I’m guessing that’ll generate a another unique DEVICEAUTH.  :smiley:

30

Myron,

    Iam on LEDS after seeing some link here(mostly for blue ring and white devices).

http://mybookworld.wikidot.com/leds

On my device under /sys/class/leds/

I have the following

Effbook:/sys/devices/virtual/leds/a3g_led# ls
blink color max_brightness power subsystem uevent

Is this same for those who has correct LED lightings on mybook NAS? just checking LED not lighting up properly issue again is not due to some config file screw up

-Eff

31

Another update

    When I updated file color file under /sys/devices/virtual/leds/a3g_led with Red/white/Yellow device shows steady RED color and blink file when changed to yes - LED Blinks too.

But for color green,voilet the LED stays off.

So I guess LED is working but only partially and if we could zero in what script or process which creates these files probably will get more on the LED puzzle.

-Eff

32

I now have another problem. When I attempt to mount the MBL I get the error message:

Message from server “MyBookLive02”

Something wrong with the volume’s CNID DB, using

temporary CNID DB instead. Check server messages

for details. Switching to read-only mode.

I guess this is realted to the netatalk issue.  I sure hope WD get this thing fixed soon as this issue is breaking my ability to use all their iOS apps and WD2go.com.

33

With the LED issue it seems there has been a manufacturing fault.

34

Having SSH enabled gives you a route in just in-case something malfunctions.

dani3l wrote:
Thanks guys, I got the firmware updated and enabled ssh while not bricking the dashboard. This is my second unit, I bought one yesterday and started the setup without reading the forum. The dashboard bricked on that one so I returned it to the store and got a new one.

I know nothing about sshs or any of this technical stuff so it is good to have you all here for support.

35

Hi,

Look like I’m in the same boat. What working fine before and stop working after the automatic upgrade Firmware.

Well I can access my Dashboard login page but the password doesn’t work anymore. I know it the good one because it doesn’t return “Incorrect password” just the login page.

So I try to

My LED is green and flashing…

I’m out of tough…

Any Help.

Thanks

StarWolf

36

Just a throught…  Clear any cookies associated to your MyBook Live from your browser and try again.  Also, try logging in without using a password.

37

Thanks,

I did a clear All of History, cookies and password on IE9.0. Try login without password and it keep saying “Password incorrect”. Try with good password and it just refresh the screen without error.

I try with all browsers I had, Firefox 8 & 9, Internet IE9.0, Google Chrome and Safari.

No Lucks.

Weird that even SSH for SFTP doesn’t work even after trying the special URL.

Regards,

38

Your out of luck. Same happened to me, I returned mine back to the store for a new one. On the new one I I enabled ssh and uploaded the firmware that way…it works. Point of the story is if you are locked out and did not enable ssh you are out of luck.

39

Well, I was looking for a secure solution and tough this device was cheap/simple/overall good enough… Since I got it, I had issue and this problem from the new firmware, ok bad luck can happen but not with all the people who complaint about it… sorry WD but you lost my my trust on your NAS to consider putting my data. I’ll go the manual way and build it my self. Now question is Windows or Linux?

Thanks everyone for you kind support.

Starwolf

40

Also I wasnt able to acces my dashboard anymore.

Tried the manually restore the firmware with putty. This didnt solve anything.

Then i looked at my dynamicconfig.ini file and it looked like this:

[config]
SUBDOMAIN=""
DEVICEID="99904"
DEVICEAUTH="b68dca233be914bcab8421f438bef60"
EXTERNAL_IP=""
EXTERNAL_PORT=""
EXTERNAL_SSL_PORT="443"
INTERNAL_IP="192.168.178.19"
INTERNAL_PORT="80"
DEVICE_SSL_PORT="443"
REMOTEACCESS="TRUE"
COMMUNICATION_STATUS="relayed"

 So also for me adding the extra lines solved the issue.

Thanks for this information!