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.
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.
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.
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.
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.
It slow down my acces to mybooklive dashboard. i downloaded my both MBL 2T and the other is 3T. Both having the same problems.
I even reboot, reset to factory setting by erasing my files first, but to no avail.
It took very long time to access my dashboard, luckily still can acces my folders but very slow. I have raise the RMA to return both my MBL one by one in order for me to transfer all my files when a new MBL arrives.
I tried to upgrade today, not having read the forums first. I too was stuck at the 10% mark on a hard wired desktop connection. I ended up following the suggestion of closing the browser and reopening it, without power cycling the drive itself. It went from installing to downloading, then back to installing. I had to jump in the shower, but in that time it seemed to work OK, as the first thing I saw was a happy flashing green light again, and then a message that it had updated successfully.
It looks like since I got back tonight and tried it out I haven’t noticed any slower access speeds through the web interface or otherwise yet. Lesson learned, even when the little dashboard says it has an upgrade available don’t do it until looking here first to see just how bad it **bleep** first!
What the WebUI is supposed to do is copy the upgrade file to a specific directory on the MyBook Live and invoke the script that upgrades from file. Seems there is an issue with the WebUI receiving the file from some computers. I dare not try and use the WebUI to send the file over and invoke the update so not I copy the upgrade file to the Public folder and invoke the script directly to cut out the WebUI from the process and this seems to work fine.
When the WebUI gets stuck at 10%, it does not even begin creating a copy of the upgrade file on it’s disc.
SenateX wrote:
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.
I highly recommend anyone with a dead UI or if you have had ANY problems with this drive, if you are still covered by your warranty, call them up ASAP. Tell them you can’t back up your data so they send you a new drive first. Do NOT update the new drive, just copy whatever files you can to it, then send the old drive back. They should send you a pre-paid shipping label.
Got stuck at 10% firmware install. After an hour, I backed up my drive (still angry about having to backup my backup), and then simply reloaded the browser screen. This brought me back to a 10% installing again. Reloaded again, and it didn’t pop up, so I clicked ‘Update’ in the UI, and it downloaded again, and installed properly. Back to working normally.
Me thinks W.D. needs to look at how the WebUI received and processes the update file before invoking the update.
I’m making guesstimates here, but I have witnesed the WebUI process finish and return to the menu BEFORE scripts have completed. I spotted this whenb I was changing access to several shares. The WebUI showed that it has completed but the scripts kept running for about another minute or two.
Following my observations I will no-longer due the WebUI to perform any firmware upgrades.
It would help that W.D. actualy check their scripts as a few posts earlier to this one I’ve highlighted files relating to the web server that drives the WebUI being dumped in the rot directory of the operating system’s partition.
I think that the people at W.D. are aware of some of these bugs but because “it works” thry choose to be lazy and not fix these upgrade script problems. The evidence is quite clear and concrete.
To people experiencing slow Web UI after the recent update: I looked into the error-log of the Apache-server and noticed several “sudo: unable to resolve host MyBookLive” log-entries. I modified the first line: “127.0.0.1 localhost.localdomain localhost” to include MyBookLive like this: “127.0.0.1 localhost.localdomain localhost MyBookLive”, which made the web interface much faster.
I highly recommend anyone with a dead UI or if you have had ANY problems with this drive, if you are still covered by your warranty, call them up ASAP. Tell them you can’t back up your data so they send you a new drive first. Do NOT update the new drive, just copy whatever files you can to it, then send the old drive back. They should send you a pre-paid shipping label.
I’m not sure if anyone has received a replacement drive yet to confirm if replacements will come with the older firmware. Per UPS tracking, I should receive mine tomorrow and I sure hope it will come with the older fw.
I did not get a shipping label with my RMA e-mail and when I asked customer care, I was informed that my RMA e-mail gave me an option to purchase a UPS shipping label at a discounted rate. However, a few hours later, a WD specialist contacted me and requested that I ship the drive to a different address where they can examine it and that is when I was offered a sihpping label. So return shipping is on your dime unless you can get WD’s customer care to send you a shipping label.
oh - and streaming 1080p videos lag significantly whereas before v129 of the firware (v124) there was no problems
edit: thanks for the file location - will try
edit2: yes after updating the file the WEBUI is fast again; thanks!!!
edit3: yes, I can stream to my iphone again - looks like this was the problem with the GUI/streaming lag problem.
I still wouldn’t recommend the update using the webGUI, if you really want to update then download the update file and update manually
for those needing help with editing the file, I used a portable version of winscp; logging into the device via the IP address with usename: root password:welc0me
the navigate to the file location and copy it to your desktop, use notepad to edit it, then copy it back (overwriting it)
