Now then… I’ve had a similar problem but I rebooted my MBL before trying to do an update. Luckily I had SSH enabled so managed to download the Debian upgrade archive from WD’s product support site and directly invoke the script that initiates an update from file. I’ve recently documented what I did in the official “latest firmware” thread/discussion on this here community forum. Hopefully you have SSH access enabled. If not… Pass. Dunno then. Maybe it needs to go back to Western Digital if the reset button does not work.
When the update completed the Dashboard became alive.
My post copied from the other thread…
Thought I would turn off all the services and then reboot my MBL. On reboot the Dashboard UI is not accessible. The IP is allocated dynamically but the IP is reserved on the router so the IP stays the same.
Luckily I have kept SSH enabled so had to download te update file to the
Public share and initiate the update by executing the firmware update by file script.
NAS:/DataVolume/cache# . /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/apnc-020202-020-20110825.deb
basename: invalid option -- 'b'
Try `basename --help' for more information.
Now… What is
basename. Why did it fail to execute? From the colour of the LED and the hard drive sounding busy I am assuming at the time I post this that the updatre is in progress. I’m keeping the SSH session open during the update in-case closing the interactive sessions also terminates the update.
Why would a simple reboot kill the Dashboard UI?
EDIT: Luckily the update using
updateFirmwareFromFile.sh worked and the Dashboard UI began working again under the current firmware. Still, after a reboot why did the Dashboard UI die after a reboot?