3.7.1 Upgrade Issues

[kourosh]

I have a TS 410 which has fallen to pieces after the latest upgrade. Since the upgrade it has set the network settings to DHCP and every time I try to go to network settings in the WEB GUI it brings me to the login screen. I have tried to change the settings from Qfinder but it keeps staying on DHCP. I even loaded the backup.ini but the problem stays on. Is there a corrupt file somewhere or is there a bigger problem.

[shenga]

There was a problem that many of us experienced with 3.7 back in June and ended up many of us having to revert back to 3.6.1. Qnap then pulled the firmware a few days later acknowledging there was a problem. i know this isn't an answer to your problem but perhaps try and go back to the previous firmware build.

I for one will never ever install the update again as soon as it comes out. Lost ALL my data first time around (noobie) and lost a whole weekend 2nd time around (last month). I always find myself taking a deep breath before attempting a qnap firware upgrade. Shouldn't be so but it is what it is..............

[kourosh]

Thanks. Same here. I have no idea why this is such a flaky device when it comes to firmware upgrades.

[valmorph]

Up until the previous firmware (3.6.0) I never had any problems updating my TS-410. Just clicked on the update button and a few minutes later could play with the new features.

That update (3.6.0) however reuired all the fiddling around with manual install. I'll probably skip 3.7.1 unless it magically decides to update itself virtually automatically.

[corrco]

Does seem to be a bit of a bomb,doesn't it? I have the TS-410, which updated without incident. My TS-559 Pro II has had all kinds of issues, most noticeably vanishing from the network. I downgraded to 3.6.1 and applied the samba patch, and it was restored. Tried the upgrade to 3.7.1 again and it now sort of works - if I ping it and connect via Qfinder enough times it will eventually show up as its IP address. Argumentative QNAP support person insisted this was a windows problem - funny how it's only a windows problem in 3.7x. This thread might point to the root of the problem, and possible solution. I am not sure how they are getting the upgrade log info, so must do more research:

viewtopic.php?f=11&t=60750

[pwilson]

Does seem to be a bit of a bomb,doesn't it? I have the TS-410, which updated without incident. My TS-559 Pro II has had all kinds of issues, most noticeably vanishing from the network. I downgraded to 3.6.1 and applied the samba patch, and it was restored. Tried the upgrade to 3.7.1 again and it now sort of works - if I ping it and connect via Qfinder enough times it will eventually show up as its IP address. Argumentative QNAP support person insisted this was a windows problem - funny how it's only a windows problem in 3.7x. This thread might point to the root of the problem, and possible solution. I am not sure how they are getting the upgrade log info, so must do more research:

viewtopic.php?f=11&t=60750

I had no challenges with either v3.7.0 or v3.7.1 on my TS-419P+, but my PC runs under Linux, and my QNAP is always on DHCP anyway. (I use DHCP-Reservation in my router to ensure that my QNAP is always issued the same IP address via DHCP when it starts up). Every single device (of the 39 devices present) in my network uses DHCP & DHCP-Reservation, especially my Servers, Printers, NAS units and Smartphones. DHCP reservation puts the "brains" of my network in the "router" rather than in the individual devices I attach to it, this made it a little tricky to setup the router, but very easy to manage thereafter.

In fact even my Virtual machines within my "real" machines, connect to my network by DHCP, and they get "real" IP addresses within my normal networks IP Pool, complete with DHCP-Reservation. Tricky or not, it was definitely worth the effort to set up my router this way. All my network configuration is inside my router where it should be!

I not sure whether this proves QNAP Support's assertion or not, but it might add fuel to your conversation.

Patrick.

[ascii]

i have also upgraded by TS-410 today.
i went from 3.5.0 Build 0816T to 3.7.1

i preformed the upgrade via webGUI.
everything went fine.
[/] # /sbin/getcfg System Version
3.7.1
i can connect via ssh. ftp is also running.

but the WebGUI is not working.

but the webserver seems to be running
[/] # ps ax | grep http
3154 admin 2812 S /usr/local/sbin/_thttpd_ -p 8080 -nor -nos -u admin -d /home/httpd -c **.* -i /var/lock/._thttpd_.pid
5703 httpdusr 5196 S < /usr/local/apache/bin/apache -k start
5704 httpdusr 5252 S < /usr/local/apache/bin/apache -k start
8403 httpdusr 5512 S < /usr/local/apache/bin/apache -k start
9439 admin 568 R grep http

not on port 80 and also not on 443 as it used to be.
[/] # grep Listen /etc/config/apache/apache.conf
Listen 80

i rebooted the NAS already

had anyone the same problem and fixed it?

[schumaku]

I would not trust in the version number shown - supect a partial update, well, one more.

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. From there, run the 1-2-3 steps from the guide here http://wiki.qnap.com/wiki/Manually_Updating_Firmware

[ascii]

thanks for the hint.
i trying it right now.
that would ** if it tells you update complete but only does a partial upgrade

UPDATE:
wel that did not fix it.
still the webGUI does not work.

Code: Select all

login as: admin
admin@192.168.2.5's password:
[~] # mkdir /mnt/HDA_ROOT/update
[~] # cd /mnt/HDA_ROOT/update
[/mnt/HDA_ROOT/update] # rm -rf /mnt/update
[/mnt/HDA_ROOT/update] # mv /share/download/TS-410_3.7.1_20120615.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-410_3.7.1_20120615.img
cksum=2607828074
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-410
version = 3.7.1
16+0 records in
16+0 records out
3.7.1
OLD MODEL NAME = TS-410
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
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.
set cksum [2607828074]
[/mnt/HDA_ROOT/update] # reboot
[/mnt/HDA_ROOT/update] #


[schumaku]

Some good news at least

Any insight on restarting it? Spotted the thttpd was operational before of course.

[~] # /etc/init.d/thttpd.sh restart
Shutting down thttpd services: thttpd.
Starting thttpd services: thttpd.
[~] # ps -ef | grep thttpd
19006 admin 3004 S /usr/local/sbin/_thttpd_ -p 8080 -nor -nos -u admin -
19038 admin 568 S grep thttpd
[~] # ps -ef | grep stunnel
3644 admin 332 S /usr/sbin/stunnel /etc/stunnel/stunnel.conf
19041 admin 580 S grep stunnel

[ascii]

both are running
[~] # /etc/init.d/thttpd.sh restart
Shutting down thttpd services: thttpd.
Starting thttpd services: thttpd.
[~] # ps -ef | grep thttp
10349 admin 3008 S /usr/local/sbin/_thttpd_ -p 8080 -nor -nos -u admin -
10381 admin 568 S grep thttp
[~] # ps -ef | grep stunnel
4254 admin 2300 S /usr/sbin/stunnel /etc/stunnel/stunnel.conf
10384 admin 568 R grep stunnel

do you know where the logilfes from the thttp is.
maybe its a rediect problem or so. as far as i remember the webgui is a cgi script but the browser normaly starts looking for html oor php side.

[schumaku]

Of course, you have cleared the browser's cache, do you?

It's a different Web server, not Apache there. Seen a bunch of similar reports over time in the forum, but don't remember having seen or spotted a real way to analyze it.

Consider to contact QNAP support please.

[ascii]

yes i used firefox and internetexplorer. with and without clearing cache

[schumaku]

Is the session established when ie. telnet to the NAS on port 8080, and type-in (invisible) a GET / :

C:\>telnet ts-459proii 8080
(connection established, screen black)
GET /

[ascii]

the port seems to be open.
i think it might me a redicet problem.
i raised a call at qnap