Yep. Send him a private message via this forum (spot the envelope on the forum’s web page) to WDTony but I think he’ll tell you the same. Quite possibly he might be intereste dto get his hands on your MyBook Live to get their development tream to do some forensics to find out why your MBL’s got bricked by the firmware update?
Also… Which get be to frown… If the Daahboard UI screws up so you can’t access it anymore then you can not access the factory restore options which could possibly get the Dashboard UI back-up-and-working.
Whoever designed the way the Dashboard UI works and how the reset button works needs to be sacked. Especially removing any form of secondary access to the MBL. Like a 9-pin serial port to be able to connect a computer to a serial terminal to access the NAS’s Linux operating system should the networking component breaks down and also with SSH access is disabled by default. That is just stupid.
I have SSH enabled and this means if the Dashboard UI dies on my MyBook Live I can at least execute programs and stuff to try fix the problem and can use SFTP to put back files that may have got screwed up.
Thatt reminds me. I need to back-up everything under
/var/www and also back-up key configuration files under
/etc and whever else. Just in case I find myself with a bricked Web Dashboard UI or worse still a bricked drive.
For updates I don’t use the Dashboard UI now. I manually copy the firmware file onto the MyBook Live and invoke the script that starts the update manually. I have a feeling there is something within the Dashboard UI that screws up the update.
Why? Something unrelated I noticed. Was changing permissions on shares. Dashboard UI crapped out with a time out error but the scripts that were doing all the changes were still working.
That’s my tuppence worth.