03-16-2012 11:17 AM - edited 03-16-2012 12:02 PM
"If you have issues with the Dashboard being inaccessible, please contact our customer support team to help you out. You can still access your data through normal means (Samba, AFP)."
Although I never lost access to my data, I still can't manage or configure the drive, or take advantage of its features, like WD2Go or WD Photo.
How would you react if your car dealer said dismissively, "No, the heater, air conditioning, and windows don't work, but you can still drive it"?
I have spoken with customer support, and they suggested an RMA, but with the amount of data I have on this drive, I'll have to go out and buy another drive of the same size to back this up before sending it in. Would they agree to sending me the replacement first?
Update: Sorry, I completely messed up that car dealer analogy. It's as if your car dealer had said "We took out your dashboard, so you won't have a speedometer, gas gauge, light switches, radio, or AC controls, but hey, you can still drive it." -That's what I meant.
03-16-2012 12:02 PM
Well, here's an update for my situation.
As I said earlier, the update seemed to go OK, and I got the e-mail about it completing successfully. But I never got the restart e-mail, which I expected.
File access is normal, but I could not get the Dashboard (aka the UI) to load.
I used the Quick View to shut it down and then powered it up again to restart it. It started correctly, with the LED going through the correct color sequence.
I tried loading Dashboard from one machine (Windows XP) and the initial background screen did appear. I picked the "Settings" option and I got this white box with a "Waiting" message and a spinning thing. After some minutes, probably 10 or so, the Settings menu DID appear. I clicked on Updates to see the version, and after 10 minutes or so, it did appear and did seem updated. Just for testing, I clicked on "Shares" and after a while, I got a timeout message. I went back and forth between the main Settings menu and the Shares menu and it worked once, but each screen taking about 10 minutes to show.
I then shut down my browser and tried to bring up Dashboard again using the Quick View. So far, it hasn't shown up and it's been probably 20 minutes or so.
So I did get it to sort of work once, but it's certainly not reliable. Something is still not right.
03-16-2012 12:06 PM - edited 03-16-2012 01:30 PM
They certainly will agree to sending a replacement first and let you return yours upon receipt of the replacement but, only after you give them your credit card information and let them place a hold in the amount of MSRP plus tax for an identical drive. At least that is what happened in my case and I must note that per WD customer care, the replacement currently on its way to me by UPS 2nd day air is not a new replacement but a recertified one. In most cases, you are required to pay the shipping charges to ship the faulty drive back as well.
Edit: I should have mentioned earlier that upon receipt of your faulty drive, the hold on your credit card will be released and the remaining warranty on your original drive will be transfered to the replacement within 60 days.
03-16-2012 12:27 PM - edited 03-16-2012 12:29 PM
The Dashboard did eventually come up, and I picked the Settings option. It took 3 minutes and 15 seconds for it to load. I was able to pick from the options on that menu, like "Updates," etc, pretty normally. It actually seemed pretty normal for a while. I even ran the short diagnostic and it took the 2 minutes it said it would, and gave a passing grade.
I got bumped out, somehow back to the main screen and taking the "Shares" menu again, it took a bit over 4 minutes to load, but it did load.
So it is behaving better, but still slow. Could there be some sort of background processs, like re-indexing, or something of the sort that is preventing the UI from behaving normally? And if so, will things get better as that process approaches completion?
The fact that the UI system still works, albeit slowly, indicates that there are no missing files.
I'm going to let it run for a day or so and see if things approach "more normal." I still want to confirm that it's sleeping like it's supposed to.
03-16-2012 12:29 PM - edited 03-16-2012 12:36 PM
Those having issues of the download being stuck at 10% can reboot the My Book Live, then download the update manually, and apply the upgrade manually. We are investigating why the firmware update gets stuck at 10% for some people.
If you have issues with the Dashboard being inaccessible, please contact our customer support team to help you out. You can still access your data through normal means (Samba, AFP).
We are looking at a more substantial update in April to address some of the issues that have cropped up over the last few months. As a note, this does not include a new Twonky version.
WDTony, I'm still on 1.03.03 with no problems but have been wanting to upgrade for awhile to get some of the new functionality. Would it be safe to say I should wait till the next update in April? Seems to be many issues with this release and maybe it should be pulled till you guys figure out what's wrong.
03-16-2012 12:39 PM
That's... discouraging, to say the least.
They want me to pay full retail first, then end up with the refurbished unit from the last guy who had the same problem?
And I pay for shipping? For THEIR problem?
03-16-2012 01:55 PM - edited 03-16-2012 02:08 PM
Don't want to be a pest, but I did want to give another update.
Right now, it takes about 7-8 minutes for the initial Dashboard screen to come up. I'm using Firefox as my default browser.
Within a screen, the sub screens seem to be pretty normal. Moving between main screens seems to take 3-4 minutes.
I was able to get to the SSH configuration screen and enabled it, just in case.
03-16-2012 04:44 PM
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
03-16-2012 06:52 PM
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