Ericnepean wrote:OK, thanks schumaku, I'll try to edit update.sh . I'll have to read up on vi first.
No need - I've done the (not-so-hard) job for you
:
=====
Limitations: This is intended for users experiencing the Re-launch process [bcclient] error in the logs - which is typically caused by a binaries vs. libraries mismatch from previous failed updates to v.3.7.0 and/or v3.7.1.
A. Upload the attached ZIP to the NAS Public share, ie. \\[NAS]\Public
B. Upload the firmware image (.img - the content of the ZIP archive) to the NAS Public share, ie. \\[NAS]\Public
C. Ensure SSH access is enabled on the NAS, so you can login from your computer (NAS Web UI - function search: ssh)
D. Login ot the NAS Linux shell from your computer (Windows:
puTTY, OS X Terminal app: $ ssh admin@[NAS-IP-address]) using the admin credentials. There you can enter the commands (the [~] shows just the current directory, the # is the prompt.
E. Change the current directory to the NAS Public share:
[~] # cd /share/Public
F. Optional: Check the firmware image cksum, compare with the cksum in the Notes of the
http://www.qnap.com - Download section of your NAS model. The first number marked
bold is the checksum, the second is the file size – TS-419P firmware used as an example here
[/share/Public] # cksum TS-419P_3.7.1_20120615.img
54380152 148006491 TS-419P_3.7.1_20120615.img
F. Extract the attached
update-no_lock_system_update.zip
archive:
/share/Public] # unzip update-no_lock_system_update.zip
Archive: update-no_lock_system_update.zip
inflating: update-no_lock_system_update.sh
G. Backup and replace the update.sh in /etc.init.d :
[/share/Public] # cd /etc/init.d/
[/etc/init.d] # cp update.sh update-original.sh
[/etc/init.d] # cp /share/Public/update-no_lock_system_update.sh /etc/init.d/update.sh
H. Use the manual update as documented here:
http://wiki.qnap.com/wiki/Manually_Updating_Firmware - unless there is something wrong, only the steps 1-2-3 are required. Needless to say - at the end compare the checksum, and do _not_ reboot if the process does not succeed.
=====
Ericnepean wrote:If its not to much to ask, I have a few of questions.
You are welcome to ask. I appreciate people inquiring first!
Ericnepean wrote:If one executes the "advanced" reset that resets the NAS back to factory configuration, does this also set the firmware back to the original version?
thee is no "original" version stored on the NAS, no need to IMHO.
Ericnepean wrote:You mention that I could overwrite the partition area with dd : do you mean to overwrite the partition table, or to overwrite the partition of the drive being used by the OS? I did try dd /help, but its not clear to me what arguments I would use for this action. (I don't have the facility to overwrite externally)
Using the process above, this is really not required, ie. for the first drive /dev/sda (sdb sdc ....):
[~] # dd if=/dev/zero of=/dev/sda bs=512 count=1
Ericnepean wrote:Is it normal for the "man" and "info" commands to be not working i.e command not found?
Well, this is an embedded system, the compleete firmware is ~150 MB - while a "complete" Linux distribution does span multiple DVD.
Regards,
-Kurt.