As your NAS is new I will assume for the purpose of these instructions what your MyBook Live is named: mybooklive
Download the firmware file and copy it to the Public share from:
Log onto the MBL’s (My Book Live’s) dashboard. Once you have done chat change the web address to:
I would advise that you leave SSH enabled and change the password from the default of welc0me to something that’s a lot more secure, difficult to guess and easy to remember. Once you have gained access to the Linux command line you can change the password using the passwd command.
Tutotial on how to download and install PuTTY
(Within the tutorial above substitute the Hste Name for the name of your MyBook Live, which is: mybooklive )
Assuming the name of the firmware file you have downloaded is apnc-021009-124-20111113.deb then issue the command . . .
Two lines should appear showing the current firmware vission and what the new firmware visrsion will be.
Now… This is quite important. There will be no other feedback. It’ll look like it’s hung but it has not. Do not terminate the PuTTY session to the MyBook Live as this may kill the console process and prematurly terminate the update process. When the firmware update process completes your MyBook Live will reboot. A message should show on the console statiing that the MyBook Live is going to reboot.
I has a similar problem. Tries to upload the firmware file using the Dashboard UI and it got stuck. When I had a look at the back end the firmware file was not being written to the disc, so I bypassed the Dashboard UI and copied the firmware file to the MBL manualy and invoked he upgeade script manually. It did not take too long to upgrade.
Before you do upgrade there is chatter that you need to first upgrade to the last version of the v1 firmware and then upgrade to the latest v2 firmware but then there is also chatter that does not need to be done and to just update it to the v2 firrmware.
As your MBL is new and you’ ve not put any data there is no risk of losing data.
I’ve updated my firmware this way a few times without a hitch. What is be advisable is once SSH is enabled and the firmware file copied to the Public share, to shutdown the MBL correct way (don’t just pull the plug!) , power it up, login to the Linux operating system on the MBL usign the PuTTY program and the command given, initiate the firmware upgrade.
Proof that the method works is that my MBL is still fully functional. Enable SSH first because my experience of the previous firmware is after a reboot the Dashboard UI vanished so the only access I has is via PuTTY. Once the current firmware was applied the Dashboard UI came back. I don’t know why the Dashboard UI on my MBL vanished after a simple reboot but then I also remembered that a full shutdown and power-down/power-up once brought the Dashboard back.