New 419PII with Firmware issues

[schumaku]

Paul, In case the verbose update from the shell as per http://wiki.qnap.com/wiki/Manually_Updating_Firmware shows the "lock_system_update" issue - there is no other way to handle it than use my update.sh workaround.

[paulwit]

Hi All,

Thanks for the very complete description!

I have exactly the same problem on my TS412 when updating to 3.7.1. With the updated update.sh and the echo command it seems to work now

But, this is the end of the output of the update:

Code: Select all

Check uImage size ... Pass
Check initrd.boot size ... Pass
Check rootfs2.img size ... Pass
Check Flash ROM
Update Kernel ...
Update Basic RootFS ...
Update Basic RootFS2 ...
1+0 records in
1+0 records out
Update Finished.
/sbin/lock_system_update: symbol lookup error: /sbin/lock_system_update: undefined symbol: unlock_system_update
set cksum [2210110139]


So still a lock error. Can I ignore this (as the update has finished) and go ahead with rebooting? Or should I try something else first?

Thanks,
Paul

[schumaku]

It's ok - missed the "unlock" part - does not matter. Time ot reboot, and enjoy your NAS again!

[Yochh]

Just a question : after apply the procedure, should we replace the "update-original.sh" ?
Thanks in advance for the time you all spent ;o)

[schumaku]

Just a question : after apply the procedure, should we replace the "update-original.sh" ?

No, it will be gone again anyway following the reboot. The only reason I had choosen a different name was to have an opiton to check for the differences.

[rtomchak]

Thanks to schumaku today I successfully upgraded to 3.8.0. Right from the start had issues with graphic firmware update errors "failed to update". Finally went to the the schumaku information with my manual update error and bam it worked.

Thank you. Thank you. Thank you!

[frame_michael]

Hi All,

maybe you can help me - I am experiencing the same problems with my 419P and the latest 3.8.0 firmware
( localhost Re-launch process [lcdmond].
localhost Re-launch process [bcclient].)

So I decided to try and install the 3.7.3 firmware which was working fine - again.
First through the webinterface - failed.

Next I saw this thread and did as schumaku said. I unpacked the "update-no_lock_system_update.zip" and placed it
in /Public. Placed the firmware image for 3.7.3 there also.
Did everything as stated - and then the manual firmware install.
But I do get these error messages...

Sorry I am no Unix/Linux guy.


[/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
[/etc/init.d] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # ls
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
[/mnt/HDA_ROOT/update] # mv /share/Public/TS-419P_20120801-3.7.3.img /mnt/HDA_ROOT/update/
[/mnt/HDA_ROOT/update] # ln -sf /mnt/HDA_ROOT/update /mnt/update
[/mnt/HDA_ROOT/update] # /etc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.7.3.img
cksum=1541930685
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-419P
version = 3.7.3
16+0 records in
16+0 records out
3.7.3
OLD MODEL NAME = TS-419P
Allow upgrade
boot/
config/
fw_info
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.img
rootfs2.img.cksum
rootfs_ext.tgz
rootfs_ext.tgz.cksum
uImage
uImage.cksum
update/
update_check
update_img.sh
tune2fs 1.41.4 (27-Jan-2009)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
Update image using HDD ...
Check uImage size ... Pass
Check initrd.boot size ... Pass
Check rootfs2.img size ... Pass
Check Flash ROM
Update Kernel ...
^C/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory


Since then I did nothing - no reboot. In case the system doesn't come up again.

What can I do?

many thanks
Michael

[schumaku]

You are on the right path - now edit the (copied) update.sh file and comment all write_log entries, too. If you are not fluent in editing scripts, please contact QNAP support.

I'll try to find some time to provide an updated one within the next 24 hours.

Afraid - from this status, thee is no way forward nor backward. Also QNAP Finder will fail (due to the bcclient process crashes).

[frame_michael]

Hi schumaku,

thanks for your quick reply. I know this is a dumb question but what is the correct way to comment the lines out?
Sorry I am definitely a beginner here.

The best way for me though would be to wait for your updated script.

thanks
Michael

[schumaku]

Michael,

Can't find the time to test and write the doc today I'm afraid. Attached the zip file containing update-no_write_log-no_lock_system.sh - handling is very similar in he original thread you spotted.

If the script does throw errors - please do not change anything - just post the transcript in case. Do not reboot at that stage please!

If you don't want to go for the experiment - please contact QNAP Customer Service - referencing this thread. Mention supressing calls to write_log should lead to a correct update They should be able to fix this fix it for you. Just in case: There is no need to whatever bottom-up re-installation in case this idea is suggested

Sorry again - regards,
-Kurt.

[frame_michael]

Hi Kurt,

thanks for the script - was it updated?

Anyhow - here are the error messages (first time i misstyped...)


[~] # cd /share/Public
[/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
[/etc/init.d] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # ls
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
[/mnt/HDA_ROOT/update] # mv /share/Public/TS-419P_20120801-3.7.3.img /mnt/HDA_ROOT/update/
[/mnt/HDA_ROOT/update] # ln -sf /mnt/HDA_ROOT/update /mnt/update
[/mnt/HDA_ROOT/update] # /etc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.3.3.img
cat: /mnt/update/newver: No such file or directory
/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
[/mnt/HDA_ROOT/update] # /etc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.7.3.img
cat: /mnt/update/newver: No such file or directory
/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
[/mnt/HDA_ROOT/update] #

[schumaku]

Sorry - that was the old modded script - I'll remove it from the other post.

update-no_write_log-no_lock_system.zip

[frame_michael]

Hi,
tried it - first I thought it worked - but then I saw the error messages again...
But it seem's to be getting further


[~] # cd /etc/init.d
[/etc/init.d] # cp update.sh update-original.sh
<ublic/update-no_write_log-no_lock_system.sh /etc/init.d/update.sh
[/etc/init.d] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
< /share/Public/TS-419P_20120801-3.7.3.img /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # ln -sf /mnt/HDA_ROOT/update /mnt/update
<tc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.7.3.img
cksum=1541930685
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-419P
version = 3.7.3
16+0 records in
16+0 records out
3.7.3
OLD MODEL NAME = TS-419P
Allow upgrade
boot/
config/
fw_info
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.img
rootfs2.img.cksum
rootfs_ext.tgz
rootfs_ext.tgz.cksum
uImage
uImage.cksum
update/
update_check
update_img.sh
tune2fs 1.41.4 (27-Jan-2009)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
Update image using HDD ...
Check uImage size ... Pass
Check initrd.boot size ... Pass
Check rootfs2.img size ... Pass
Check Flash ROM
Update Kernel ...
Update Basic RootFS ...
Update Basic RootFS2 ...
1+0 records in
1+0 records out
Update Finished.
/sbin/lock_system_update: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
/sbin/setsum: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
[/mnt/HDA_ROOT/update] #


thanks for your help
Michael

[schumaku]

I'd say nothing to worry anymore. If you are keen to have the correct firmware checksum in the configuration, re-apply the firmware using the standard update.sh process following the reboot again - don' worry: Seriously, this has _no_ use at all. Instead of running the cksum (resp. md5sum for the Cisco OEM NAS) and ask the user to compare it to the data supplied with the firmware release notes - it's just written to the configuration file. As many details with the QNAP firmware - good idea, not very smart implementation.

I've updaed the script again so the cksum part is commented. Don't worry about the lock_system_update (unlock in fact) - just ensure there is just one concurrent update on-going please.


EDIT: Sorry - probably broken. Use the no_write_log-no_loc_system onde from here instead: viewtopic.php?f=11&t=61185#p304879

[frame_michael]

Hi Kurt,
I am so sorry - but it didn't work -
First I got the following end of archive error


[~] # cd /etc/init.d/
[/etc/init.d] # cp update.sh update-original.sh
<ublic/update-no_write_log_no_lock_system.sh /etc/init.d/update.sh
cp: cannot stat `/share/Public/update-no_write_log_no_lock_system.sh': No such f ile or directory
[/etc/init.d] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
< /share/Public/TS-419P_20120801-3.7.3.img /mnt/HDA_ROOT/update/
[/mnt/HDA_ROOT/update] # ln -sf /mnt/HDA_ROOT/update /mnt/update
<tc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.7.3.img
cksum=1541930685
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-419P
version = 3.7.3
16+0 records in
16+0 records out
3.7.3
OLD MODEL NAME = TS-419P
Allow upgrade
boot/
config/
fw_info
initrd.boot
initrd.boot.cksum
qpkg.tar
qpkg.tar.cksum
rootfs2.img
rootfs2.img.cksum
rootfs_ext.tgz
gzip: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
[/mnt/HDA_ROOT/update] #

Then I copied everything again - checked the cksum and downloaded your script again, unzipped it etc.
Now I get the following error - seems a } is not right?


[~] # cd /share/Public
[/share/Public] # cksum TS-419P_20120801-3.7.3.img
1541930685 148376094 TS-419P_20120801-3.7.3.img
[/share/Public] # cd /etc/init.d/
[/etc/init.d] # cp update.sh update-orginal.sh
<date-no_write_log-no_lock_system_no_cksum.sh /etc/init.d/update.sh
[/etc/init.d] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
[/mnt/HDA_ROOT/update] # mv /share/Public/TS-419P_20120801-3.7.3.img /mnt/HDA_ROOT/update/
[/mnt/HDA_ROOT/update] # ln -sf /mnt/HDA_ROOT/update /mnt/update
[/mnt/HDA_ROOT/update] # /etc/init.d/update.sh /mnt/HDA_ROOT/update/TS-419P_20120801-3.7.3.img
/etc/init.d/update.sh: line 91: syntax error near unexpected token `}'
/etc/init.d/update.sh: line 91: `}'
[/mnt/HDA_ROOT/update] #

I am very sorry...
Michael