New 419PII with Firmware issues

Discussion on setting up QNAP NAS products.
frame_michael
New here
Posts: 8
Joined: Thu Nov 04, 2010 3:56 am

Re: New 419PII with Firmware issues

Post by frame_michael »

Hello schumaku,

if you have time, can you tell me what to do?
Is ist an error in the script or something serious?

many thanks for your time and patience
Michael
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: New 419PII with Firmware issues

Post by schumaku »

Not enough free space on /mnt/HDA_ROOT most likely.
frame_michael
New here
Posts: 8
Joined: Thu Nov 04, 2010 3:56 am

Re: New 419PII with Firmware issues

Post by frame_michael »

I managed somehow to apply the old firmware with your second to last script.
Is it safe to reboot - as I do not know what files in /mnt/HDA_ROOT to delete - in order to run your last script?
this is what df said.

Filesystem Size Used Available Use% Mounted on

/dev/sda4 356.5M 253.4M 103.0M 71% /mnt/ext
/dev/md9 509.5M 236.0M 273.5M 46% /mnt/HDA_ROOT

Since the latest manual firmware up/downgrade I have the following files in /mnt/HDA_ROOT/update:

[/mnt/HDA_ROOT/update] # ls -l
drwxr-xr-x 2 admin administ 4096 Jul 31 19:30 boot/
drwxr-xr-x 2 admin administ 4096 Jul 31 19:30 config/
-rw-r--r-- 1 admin administ 33 Jul 31 19:31 fw_info
-rw-r--r-- 1 admin administ 16 Dec 12 20:33 newver
-rw-r--r-- 1 admin administ 97689600 Jul 31 19:31 qpkg.tar
-rw-r--r-- 1 admin administ 72 Jul 31 19:31 qpkg.tar.cksum
-rw-r--r-- 1 admin administ 37369402 Jul 31 19:30 rootfs_ext.tgz
-rw-r--r-- 1 admin administ 78 Jul 31 19:30 rootfs_ext.tgz.cksum
lrwxrwxrwx 1 admin administ 20 Dec 12 20:32 update -> /mnt/HDA_ROOT/update/
-rwxr-xr-x 1 admin administ 5936 Jul 31 19:31 update_check*

This is what the lates firmware update spit out...

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
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: New 419PII with Firmware issues

Post by schumaku »

/sbin/write_log: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory

Not problem - the log entry was not written...

/sbin/lock_system_update: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory

...there is a "lock" ensuring only one process can update at the time. The initial loch enable is commented, so the failure here does not hurt...

/sbin/setsum: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory

...so here the checksum is not written to the configuration - I never figured out the sense of first not comparing the checksum, and then write the checksum (cksum) of the (now no longer existing) firmware image into the configuration file. Complete mis-design.

Yes, therefore you should be able tot reboot safely now.
frame_michael
New here
Posts: 8
Joined: Thu Nov 04, 2010 3:56 am

Re: New 419PII with Firmware issues

Post by frame_michael »

great - thank you very much for your help!
Jedi69
First post
Posts: 1
Joined: Fri Dec 14, 2012 7:49 pm
Location: Padova - Italy

Re: New 419PII with Firmware issues

Post by Jedi69 »

Great Schumaku!

Tried with your fixed file and boom: from 3.6.1 to 3.7.1 with no issues (save that stupid symbol lookup error as I was using the first release of the file)!!! Now I can hopefully start upgrading again...

Thanks again,

Jacopo
ecorini
First post
Posts: 1
Joined: Wed Jan 16, 2013 5:42 am

Re: New 419PII with Firmware issues

Post by ecorini »

Thanks for your help, i downgrade from 3.8.1( <- ** ) to 3.7.1!
tehcannon
First post
Posts: 1
Joined: Fri Feb 15, 2013 7:50 pm

Re: New 419PII with Firmware issues

Post by tehcannon »

Uh-oh. I followed all of the previous instructions because I kept getting

Code: Select all

/etc/init.d/update.sh /mnt/HDT_ROOT/update/TS-412_3.7.1_20120615.img
/sbin/lock_system_update: error while loading shared libraries: libuLinux_naspriv.so.2: cannot open shared object file: No such file or directory
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
[~] # 
When I used the second-to-last update patch, it looked like all was going well (it actually started patching, which was a first) but then I got

Code: Select all

< /share/Public/TS-412_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-412_20120801-3.7.3.img
cksum=4020334733
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-412
version = 3.7.3
dd: /mnt/update/newver: No space left on device


OLD MODEL NAME = TS-412
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] #
[/mnt/HDA_ROOT/update] #
This sounds like a bad thing. :(
Anyone got any tips?
Btw, I'm on a QNAP TS-412, upgrading from Version 3.5.2 Build 1126T if that's any help.
I'll try not to reboot, but I'm totally unsure how to proceed from here!
Sorry to ask for advice immediately on joining the forum btw, but I'm totally lost. :)
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: New 419PII with Firmware issues

Post by schumaku »

dd: /mnt/update/newver: No space left on device

...this is on HDA_ROOT. You might find some remaining stuff from whatever (older Twonky data/logs, system logs, ....) on HDA_ROOT ... but it might be not easy to identify what is taking up space there.

Consider to contact QNAP Customer Service.
modiglian
First post
Posts: 1
Joined: Thu Nov 25, 2010 5:59 am

Re: New 419PII with Firmware issues

Post by modiglian »

I followed the procedure and updated from 3.7.1 to 3.8.0 just fine.

Then I did it again to go from 3.8.0 to 3.8.2 and the update process was taking an abnormal long time until it crashed and returned to the prompt.

checked the free space and /mnt/HDA_ROOT was full, oh woe me!

I looked inside /mnt/HDA_ROOT/update_pkg (with that name, it seemed the first suspect) and BINGO! a lot of .tgz and .tar.gz packed files (and two directories) dated Nov-2012... the date of the last firmware applied.

Since the system isn't going to unpack those every time it needs to run an app, I copied those to a directory at /share/Public (just in case) did:

[/mnt/HDA_ROOT/update_pkg] # rm -rf *

And... there you go, a bunch of mb free on HDA_ROOT!

Kids: rm -rf * it's a veeeeery dangerous command, wipes everything in the current directory and anything else under it, so MAKE SURE you are in the correct directory /mnt/HDA_ROOT/update_pkg before using it (or use another procedure to clean the old files)

Started the update procedure again (copy the .img, etc...) and run the modified update.sh

Worked like a blessing

Reading the update.sh script the 5th line declares "UPDATEPKG_DIR="/mnt/HDA_ROOT/update_pkg" that's where the new firmware will be unpacked by the update script, if there are old packets in /mnt/HDA_ROOT/update_pkg taking a lot of space, just wipe them, the update script will unpack there the new ones.


If it fails and you get a brick, I'm just a diseased dog without a penny, send the lawyers somewhere else. :mrgreen:
kobed
First post
Posts: 1
Joined: Sat Apr 06, 2013 4:18 pm

Re: New 419PII with Firmware issues

Post by kobed »

Worked for me on my TS - 219P+
Thanks!!
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: New 419PII with Firmware issues

Post by schumaku »

modiglian wrote:checked the free space and /mnt/HDA_ROOT was full, oh woe me!
...
I looked inside /mnt/HDA_ROOT/update_pkg (with that name, it seemed the first suspect) and BINGO! a lot of .tgz and .tar.gz packed files (and two directories) dated Nov-2012... the date of the last firmware applied.
...
Since the system isn't going to unpack those every time it needs to run an app, ...
"Just" every time the NAS is booting, or when new services are enabled...
modiglian wrote:[/mnt/HDA_ROOT/update_pkg] # rm -rf *

And... there you go, a bunch of mb free on HDA_ROOT!


While it's a valid work-around - on a healthy, and properly operating NAS (I don't say the QNAP do so by default...) it is _not_ required to remove these files. The effective issue will more likely persist and just moved to the next firmware update.
lambdaman78
First post
Posts: 1
Joined: Sat Jan 14, 2012 8:33 am

Re: New 419PII with Firmware issues

Post by lambdaman78 »

schumaku wrote:No need - I've done the (not-so-hard) job for you 8):
>>>>>>>>>>>>>>>>
Thank you Kurt,
your Script did the trick on my TS-119 as the same error occure by updating from 3.8.1 to 3.8.2 ....

Regards,
Tobias
andrewhorton
Starting out
Posts: 14
Joined: Tue Oct 04, 2011 5:17 pm

Re: New 419PII with Firmware issues

Post by andrewhorton »

schumaku wrote:No need - I've done the (not-so-hard) job for you 8):
@schumaku - thanks for your help. I ran this last night, no problem whatsoever. There were some not important looking error messages after the "update finished" message. I ignored them and rebooted. All good. I really like this new interface, and the Photo and Music station apps look pretty good. Thanks again.
Post Reply

Return to “Turbo Station Installation & Setup”