I’ve just bought My book live 2T and I’m unnable to get in web settings. After about 5 minutes its entered main page. After another 15 minutes, it gets to Settings. But it was empty.
Very very bad firmware. I will give it 13 days. Then I will return it.
edit: I can’t even see firmware type, update etc…
Thing is, previous firmwares modified /etc/hosts appropriately and this one does not. 
I’ve identified the bug where the /etc/hosts file is not correctly updated. Actually, it’s not updated at all.
The script with the MyBook Live exists. It’s named /usr/local/sbin/genHostsConfig.sh and it movifies the DHCP client configuration and /etc/hosts.
When the name of the NAS and/or description of the MyBook Live is changes the script /usr/local/sbin/modDeviceName.sh is used which changes several configuration files, which included the DHCP configuration but DOES NOT alter /etc/hosts.
Looks like when the firmware upgrade is performed then /usr/local/sbin/genHostsConfig.sh is not called so /etc/hosts remains incorrectly configured.
Now, how did W.D’s firmware team manage to miss that one? 
If /usr/local/sbin/genHostsConfig.sh is called then someone forgot to use the –force or -f options!
Just wondering, am I the only one getting the ramlog dump a third down their UI as shown in my post on page 7?
PS I turned it back on today and it goes White then blinking Green which has something to do with a log constantly writing. My UI seems to be fixed though and is slower than before but not by much.
This update was to specifically fix the issue where you could lose communication with your UI permanently. As I said earlier in the thread, we will be releasing a more comprehensive update to fix many more issues. These include several that are being reported (hosts file issues, UI displaying garbage - as an FYI this issue will go away on it’s own after 24 hours).
I know you all don’t have a lot of confidence in us, but hang in there - we will get this corrected. This issue with the UI disappearing was very difficult to track down, but once we were able to get it replicated and fixed, we wanted to get it deployed to the field as fast as possible.
Tony
WDTony, it’s not that we don’t have trust in you, that is obviously not the case, since most of us are “loyal” customers and true fans of WD products. This is about shock and surprise, especially since you said you guys knew about the problem.
If there were known issues with the release then in my humble opinion this should have been released as a beta for testing and not released for public. I do understand that it is not easy to maintain a perfect record, but it is still a shock.
The only help we received, technically, was from other community members. If WD just announced that an update will be rolled out soon it would have been sufficient. We were basically freaking out because we feared that we will lose all our data.
Not all of us are tech savvy, and glitches like that will make people panic, so to speak.
Nonetheless, WD provides great products, that’s why we have great expectations from it, to sound like a movie buff “With great power, comes great responsibility”.
Keep up the good work, I sincerely mean that.
Received my warranty replacement 3TB today. Came with 02.02.02-020 FW, which of course worse than 02.10.09–124 but it works. I did get the update notification, but I have decided to wait it out for a bit.
SenateX,
Like I said, getting this code release out that solved the issue I talked about was priority one. Other issues, though maybe still high, are not on the order of this one. You have to look at the severity of the issue and make a call. For example, the issue where the UI is slow or corruption occurs is related to a caching issue. After 24 hours it will clear as we rotate out the cache. Though that might be seen by you as a big bug, to us it is a lower severity and should not hold up getting out a fix that has much higher priority.
Tony
if you need v124, here is the link (perform a manual update)
martiansoldier wrote:
Received my warranty replacement 3TB today. Came with 02.02.02-020 FW, which of course worse than 02.10.09–124 but it works. I did get the update notification, but I have decided to wait it out for a bit.
it might not seem to be a big bug for WD, but I assure you that almost 100% of the users were highly concerned that the NAS was no longer working properly after that flash (I couldn’t even stream properly - the lag was excessive)
how many of these users are going to navigate to this page to find out that “just hold tight - we’re on it” and that some users have found fixes for the problem?
I contacted WD support and received a very nice form letter that was of no use (even when I posted this forum link)
If I didn’t know about what I learned here on the forums, I would of taken my drive back to the store from which I purchased it
How many people are 1)upset 2)tempted to take back their units cause they think it is wrecked?
I hope this provides a bit more insight into the customer’s perspective - imo you need to rollout a temp fix fast
Call them and return your units. Even if it’s caching for 24 hours, return it. It’s a mistake on their behalf by one or more of their programmers and left us in paniced states as many of us have no backup (kinda hard to backup 1.8TB on DVD’s now adays, I personally have maybe 150GB of it backed up on discs) and it reported as 0GB/2.8TB and blinks green and flashed red and showed the dump in the interface. Even if it fixes itself after the 24 hours, why risk the constant disc access/corruption for that long?
Just wanted to confirm my understanding:
If I am still stuck on firmware 124, unable to access the UI
and without SSH enabled,
Then this new firmware 129 doesn’t help me at all, right?
And there’s nothing I can do other than RMA?
Thanks guys
Fair play WDTony. I ain’t shooting over the bow. On a customer service and human phychology viewpoint, there is a mobile phone network I’m on called Giffgaff. What’s good with that company is that they’ve gone one step further then Western Digital when it comes to customer support.
They are very transparent when it comes to faults and service issues. All that’s needed for me is to go to the blog on the web and the staff at this phone company actually explain the reasons for failures and what’s being gone to rectify the problems.
In all fairness on here there is not a lot of feedback coming out of WD’s stable and it’s left to the users of this W.D. community to try identify the problems of which it’s good that some of the discussions make it to the W.D. firmware development team, but the feedback is missing! Like if there is some issue that’s been found, why does someone responsible for firmware builds NOT get directly in contact with the discoverer of the fault to find out exactly what they know.
For example, the issue of /etc/hosts getting corrupted. W.D. might now know why this is happening, I don’t know why it’s happening but someone on here may have an educated or idle idea that might just explain the reason.
For example, and Idle idea from me now. Maybe there is some service operating on the MyBook Live that is leaking memory or maybe there is some sort of stack overflow happening, or a buffer overflow condition that’s interfering with some part of the operating system that’s causing the wrong data being written to the file or even worse the wrong data being to the file system resulting in cross-linked files! In that case correcting one file of the cross-linked file instantly corrupts a file that was not corrupted.
It would also be good that IF there is a reason for missing out the NAS’s device name out of /etc/hosts then somewhere there is an explanation what the reason for this is.
People who are a lot more informed about why things are as they are will panic a lot less more. There are people putting their treasured memories on the MyBook Live and as good as SafePoint is, there will be people who have minimal knowledge.
W.D. also needs to listen to it’s customers a lot more.
For example, implement a selective backup! Allow shares, folders and sub-folders to be excluded from a SafePoint back-up. I know this can be done because I’ve done it so I have one 500Gb NAS that I can use to back-up a 1Tb NAS (the MyBook Live) which has more than 500Gb of data stored on it.
Get the thing to co-operate with on-line storage services like DropBox so user-selected shares and/or folders can synchronise with a DropBox storage area. I know it was mentioned. What would solve someone’s concerns of losing a small sub-set of files and folders if the drive suddenly fails due to old age,
The reason I wrote my comment about why /etc/hosts is not being updated and trying to find why is because no-one at W.D. is coming forward with an reason so it’s inevitable that people will begin to try find out why.
Maybe the reason someone decided not to update this file during the upgrade process is an attempt to prevent the hosts file getting corrupted and losing access to the WebUI?
I’ll give one suggestion right now that needs to be implemented into the MyBook Live.
Suggestion** :** When the MyBook Live starts up SSH access is enabled for 10 minutes as early on in the boot process as possible. If it is not accessed within 10 minutes it auto-disabled. If it is accessed within 10 minutes then it is set to remain enabled. It will be the owner’s choice to disable SSH from the Dashboard UI.
Why do this? In case the Dashboard UI fails and SSH had not been enabled. There will be a route to the back-end to that can be used to try fix the problems.
I’ve already once encountered the dead Dashboard UI after reboot. if SSH had been disabled then I would have been forced to RMA the NAS but I had remembered to enable SSH so recovery of my NAS ended up being a very sweet and simple procedure.
Yet another example, you’ll remember this, when Twonky kept failing all W.D. tech support could suggest was to do a full factory restore. I looked at it and the solution was to stop the Twonky service, erase two files and re-start Twonky. A solution that just took less than 5 minutes to implement and no need to wipe anything.
Seriously, the community here needs transparency, active feedback and reassurance.
I have seen that people have noted that there are updated versions of certain services that are stated to fix problems. Like the Samba service has been updated several times and maybe even VSFTPD. (I’m not including Twonky! Twonky is Wonky!)
Updates of these free-to-distribute services need to be reviewed and if they are not suitable for the MyBook Live, what are the reasons?
I guess that’s what people are asking for on this here forum. 
Just an additional point of note… On my NAS, even with the name of the device not in the hosts file and the Apache web server stating it can’t resolve the NAS’s name to the IP, how come the Dashboard UI on my NAS works quickly regardless of the state of the /etc/hosts file?
i agree with the sentiment here, you can’t roll out a firmware update that makes your system unusable, really, for the first 24 hours and expect people not to freak out, or call support, or come here asking questions.
it would have been easy to put one line of text in the release notes that says “may experience slow Dashboard response for the first 24 hours”. There. Done!
As it is, I think I will skip this update because my UI, my whole MBl, is acting totally fine (except for dead LED).
A suggestion to the users that posted on the first page of this thread, please edit your post and link to all the replies that included solutions for the problems. That way, if someone Googles it and found their way here, they’d have no problem fixing it.
try clearing IE cache…I had same issue, however after clearing IE cache, it worked.
@WDTony :
As many people here, when I had a lot of issues witth a brand new MBL, the only usefull help I received was from Myron and other contributors of this forum.
Even after opening an incident ticket and waiting for 10 long days, the only answer from WD was just unusefull and completely out of my problem.
So, instead of shooting on people who really help other people here and who are not paid for this, you should better listen to them, go back to work and improve your customer service level.
With all the troubles we have on each new firmare, how is it possible to be confident in WD team ?
Don’t forget, we are all customers.
Oh - I am not shooting Myron… Myron has been very instrumental to other users and to me in spotting potential issues. These have been communicated directly to the development teams. However; many of the times issues thought to be problems are not.
ThierryB wrote:
@WDTony :
So, instead of shooting on people who really help other people here and who are not paid for this, you should better listen to them, go back to work and improve your customer service level.
With all the troubles we have on each new firmare, how is it possible to be confident in WD team ?
Don’t forget, we are all customers.
You guys want transparency, and you want us to respond, but I can see why it’s difficult for anyone to want to respond with posts like this. Thierry, you’re not helping Myron’s point here.
| Forums | News and Announcements | Register | Help | Forum Guidelines |
Copyright © 2021 Western Digital Technologies, Inc. All rights
reserved.
|
Trademarks
|
Privacy
|
Community Terms of Service
|
Site Terms of Use
|
Copyright
|
Contact WD
|