New Release - Firmware Version 2.10.12-129 for My Book Live (3/14/12)

Have a 2Tb MBL, got email that firmware was available, got home, installed firmware ( took approx 10-15mins )

Everything up and running - clean as a whistle.

No new features, just fixes … however Menu UI does seem to be a bit more responsive  :)

Right everyone. When you perform the upgrade, be aware that there is some script performed during the upgrade to 2.10.12-129 which is not working correctly, but so far things things are working properly.

r--r-- 1 root root 63 Mar 8 19:41 2
-rw-r--r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r--r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r--r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r--r-- 1 root root 0 Mar 8 19:41 require.inc
drwxr-xr-x 5 root root 4096 Mar 16 02:20 root
drwxr-xr-x 2 root root 4096 Mar 8 19:41 sbin
drwxr-xr-x 2 root root 4096 Mar 8 19:37 selinux
drwxr-xr-x 21 root share 65536 Feb 21 22:16 shares
drwxr-xr-x 2 root root 4096 Mar 8 19:37 srv
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 10 root root 1100 Mar 17 01:32 tmp
drwxr-xr-x 14 root root 4096 Mar 8 19:42 usr
drwxr-xr-x 12 root root 4096 Mar 8 19:42 var

Contents of the file 2 =

//etc/nasglobalconfig.ini: line 1: [global]: command not found

This may explain why some MyBook Lives are getting bricked or the update throught he Web II is not working, getting stuck at 10%. I have made Western Digital aware about this issue weeks ago but it’s either been overlooked or ignored.

For my MBL the upgrade was performed by invoking the script to upgrade from file from the Linux command line.

The files that should not be in the root directory are . . .

-rw-r--r-- 1 root root 63 Mar 8 19:41 2
-rw-r--r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r--r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r--r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r--r-- 1 root root 0 Mar 8 19:41 require.inc

I’m scared. Mine is also stuck at  Upgrading 10% 

I never had issues in the past… I’m going to follow steps in this thread, hopefully it fixes it. If I loose ANY data I will stop using WD products. You’d think they test these things before a mass roll-out.

Update: My God Jesus…

I almost had a heart attack. Did the method recommended by one of the users (re-update from the red exclimation point) then a reboot, red light. Unplugged for 5 secs then plugged back in. Attempted to ssh after a bit then it reponded but didnt let me in with the pass. So I went to the UI and saw this:

Now it still shows this garbage but I can now access my files and junk…

After a reboot, it shows a blue light for about 15 seconds, then a red light for a good 45 seconds, then no light. At this point I can access my UI and I get this garbage from the pic:  http://pastebin.com/nQjQrXND 

Clicking the red exclimation does nothing because the text is in the way. I’m going to call them tomorrow ( http://support.wdc.com/contact/index.asp?lang=en) and see if they can send a new one so I can backup to it then send the corrupt-firmware one back. Should still be under warranty from NewEgg Canada. Meanwhile I’ll just leave it on like I have been using it for the past  9 months.

The same exact thing happened to me as well. After the upgrade, the web interface seemed to not work, but then I realized it just takes a long, time to load.

I am currently trying to load the /UI/ssh page to enable SSH just in case.

I have too much data on the drive, plus I can’t RMA, or to be exact it wouldn’t be easy at all since I’ll have to ship it to US then wait for the new one, also I’ll basically lose all my data.

There has to be a fix for this, isn’t there a way to “rollback” to the previous firmware?

I can’t believe WD would release such a glitchy firmware to the public.

We need a solution, fast.

IMHO they should pull the firmware before more people partially or fully brick their NAS devices. Just doesn’t make any sense to keep it up with all these reported issues.

I also had problems updating. It stopped at 1%. I waited for 15 minutes but nothing. I rebooted the NAS and manually updated the firmware which worked fine for me. Now the web interface is much slower but it’s working. I’m working with a iMac 27"  from 2010 with Lion 10.7.3 and Safari 5.2 (beta).

So I booted it up this morning and the red light was gone, but still had the issue. Called them up this morning, was on hold for a good 15 minutes before I got to someone. I gave my SN to the guy and told him the issue. He said the only way it could happen if you have a poor internet connection during the upgrade which is total BS because I never had this problem in the past, and my network is rock solid, but he insisted it was not a common issue. I told him about all the posts on this thread and he ignored me. I told him my address for the RMA and he said it was from the US and I’m in Canada (got the drive through newegg). He said that just means instead of 3-5 business days it will be 5-7. Initially he said I should backup the drive but I said I had 1.8TB used and didnt have enough space to back it up so hes sending me the same model and a free shipping label so I can copy to the new one and return the old one. Its going to charge my credit card but when they recieve the corrupted one, I will be refunded my charge. I asked if it was safe toupdate the new one, he said as long as my internet doesnt cut out (which it doesnt) it should be fine… but I don’t know if I should update the new one when it arrives before copying my files to it. Good thing my warranty is until April 2013. I am fairly disappointed and hopefully my new one doesnt have the same issue. Total call was 38 minutes.

i really wished i found this thread before i attemtped the flash to the latest firmware (129)

web flash - stuck at 10% - waited and waited and figured it failed

restarted the device and eventually gained access and flashed through the GUI with a local file

it worked … but the UI is so unresponsive now - takes so long to navigate

and initial network access (by a new device) seems to take a very long time as well

reverted the drive (lost my data, but it is all backed up) … and still the device is slow

tried to revert to v124 with no success (manually)

WD - FIX THE FIRMWARE

this firmware has some significant problems associated with it

Can anyone please post a tutorial on how to replace the latest firmware to the one before it? With SSH, without losing all the data on the device.

i have my data backed up so even a turtorial how to downgrade to 124 via SSH (data integrity not a concern) would be beneficial

The guy on the phone told me they are made so you cannot downflash. If he was telling the truth, then guess we’re out of luck.

I received a PM from WD support yesterday requesting my contact and SN of the drive and soon after, received a call from a support specialist. He requested that I return my drive to a different address rather than the usual RMA address, so that can test it and they also sent me a shipping label. I should receive my recertified replacement on Monday and will be shipping out my faulty drive soon after. I hope my replacement will have 124 on it and not the dreaded 129.

I’ve had the drive for about 4 months now and was extremely satisfied with it until the 129 firmware totally crapped on it!

Myron wrote:

Right everyone. When you perform the upgrade, be aware that there is some script performed during the upgrade to 2.10.12-129 which is not working correctly, but so far things things are working properly.

 

r–r-- 1 root root 63 Mar 8 19:41 2
-rw-r–r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r–r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r–r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r–r-- 1 root root 0 Mar 8 19:41 require.inc
drwxr-xr-x 5 root root 4096 Mar 16 02:20 root
drwxr-xr-x 2 root root 4096 Mar 8 19:41 sbin
drwxr-xr-x 2 root root 4096 Mar 8 19:37 selinux
drwxr-xr-x 21 root share 65536 Feb 21 22:16 shares
drwxr-xr-x 2 root root 4096 Mar 8 19:37 srv
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 10 root root 1100 Mar 17 01:32 tmp
drwxr-xr-x 14 root root 4096 Mar 8 19:42 usr
drwxr-xr-x 12 root root 4096 Mar 8 19:42 var

Contents of the file 2 =

//etc/nasglobalconfig.ini: line 1: [global]: command not found

This may explain why some MyBook Lives are getting bricked or the update throught he Web II is not working, getting stuck at 10%. I have made Western Digital aware about this issue weeks ago but it’s either been overlooked or ignored.

 

For my MBL the upgrade was performed by invoking the script to upgrade from file from the Linux command line.

 

The files that should not be in the root directory are . . .

-rw-r–r-- 1 root root 63 Mar 8 19:41 2
-rw-r–r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r–r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r–r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r–r-- 1 root root 0 Mar 8 19:41 require.inc

Can you please (or someone) else post a step-by-step guide for

a)upgrading through ssh

b)How to access and delete the above files

I have seen a lot of people saying ‘I did that with ssh’ etc but bear in mind that not all people are linux experts and your help is appreciated. I made a question in previous page but never got an answer.

Thanks

I had that problem allong with error 31118 ? and several of those small boxs saying update failed but eventually it updated very strange…

yes, I can confirm these files exist

is there any way to modify the updateFirmwareFromFile.sh to force a flash downgrade?

-rw-r--r-- 1 root root 63 Mar 8 19:41 2
-rw-r--r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r--r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r--r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r--r-- 1 root root 0 Mar 8 19:41 require.inc

The garbage you are seeing it the contents of the file /var/log/ramlog.

It CERTAINLY should have NOT done that!

vahnx2 wrote:

I’m scared. Mine is also stuck at  Upgrading 10% 

I never had issues in the past… I’m going to follow steps in this thread, hopefully it fixes it. If I loose ANY data I will stop using WD products. You’d think they test these things before a mass roll-out.

 

Update: My God Jesus…

I almost had a heart attack. Did the method recommended by one of the users (re-update from the red exclimation point) then a reboot, red light. Unplugged for 5 secs then plugged back in. Attempted to ssh after a bit then it reponded but didnt let me in with the pass. So I went to the UI and saw this:

 

 

Now it still shows this garbage but I can now access my files and junk…

After a reboot, it shows a blue light for about 15 seconds, then a red light for a good 45 seconds, then no light. At this point I can access my UI and I get this garbage from the pic:  http://pastebin.com/nQjQrXND 

Clicking the red exclimation does nothing because the text is in the way. I’m going to call them tomorrow ( http://support.wdc.com/contact/index.asp?lang=en) and see if they can send a new one so I can backup to it then send the corrupt-firmware one back. Should still be under warranty from NewEgg Canada. Meanwhile I’ll just leave it on like I have been using it for the past  9 months.

My experience:

  1. Tried updating from the update reminder, using my wirelessly connected laptop.  Stuck at 10% for about 30 min.  I closed the dashboard but did not reboot the MBL.  Seems to work well.

  2. Opened dashboard on my wired desktop PC.  Disabled Norton SmartFirewall (I doubt that played a role but you never know).  Then ran the update from the update reminder on the wired desktop PC.  Update went without a hitch and took about 8 minutes.

Takeaways:  Be safe- Connect to your router with an ethernet cable, temporarily shut down your software firewall (not sure the firewall has to be disabled, but way find out the hard way).  If you get stuck for a while at 10%, close the dashboard, open the  dashboard and try again.  DO NOT REBOOT YOUR MBL UNTIL THE UPDATE COMPLETES SUCCESSFULLY!

Or, be safer and skip the update until the process if fixed.

The very least they can do is release a new firmware with all these issues fixed, then all of us that had issues with the web UI and the device acting up to update via SSH.

Anyone willing to post a detailed tutorial on how to update with SSH? Just in case they actually do release a fix for this faulty firmware.

terrible update - last night i was able to stream via samba to my iphone

no longer (it does work but significantly slower and video playback is often stopped - wasn’t like this before the firmware update)

terrible firmware WD - how could something like this been released?

with no option to downgrade - downgrade NEEDS to be made available just in case problems like this surface

I so wanna watch videos from my NAS right now before bed… but too scared to loose all 1.8TB of data. Guess I’ll just wait out a week until my RMA one arrives.