General NAS-Central Forums

Welcome to the NAS community
It is currently Mon May 01, 2017 12:37 am

All times are UTC




Post new topic Reply to topic  [ 22 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: Wed Oct 24, 2012 8:53 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
Changing the firmware from 4.4 to 3.2 resulted in lack of opportunities to enter the server page. I suppose the solution will change the firmware. But how to do it if i don't have access to the page. I managed to connect to the server via telnet but here my knowledge ends. Please help


Top
 Profile  
 
PostPosted: Thu Oct 25, 2012 11:16 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
Try to clear your browser cache. If that doesn't help, try a factory reset.


Top
 Profile  
 
PostPosted: Thu Oct 25, 2012 2:05 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
I tried on another computer and nothing.
Resets (button for 16 sec) with hard drive and without.
Still can't enter the web site. NSA starter utility detects all correctly and I can browse the files but nothing else.


Top
 Profile  
 
PostPosted: Thu Oct 25, 2012 4:55 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
Explain how the problems started. I tried downgrade firmware from 4.4 to 3.2. NSA reported that the file is invalid. Then I tried to load the newer firmware release 4.4. Then the page is suspended and after a reboot NSA210 can not access the Web GUI and the NSA UTILITY shows firmware 3.20 and online status. Any suggestions on how to get out of this situation? I was able to run telent.


Top
 Profile  
 
PostPosted: Thu Oct 25, 2012 6:12 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
Hm, it is possible to flash over telnet, but that is a risky action. I'd rather find out the actual problem and fix that.
Can you post the outputs of
Code:
ps

netstat -lpt


BTW, why did you downgrade?


Top
 Profile  
 
PostPosted: Sun Oct 28, 2012 6:25 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
sh-4.1# ps
PID TTY TIME CMD
11251 pts/0 00:00:00 sh
11302 pts/0 00:00:00 ps
sh-4.1# netstat -lpt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:netbios-ssn 0.0.0.0:* LISTEN 2039/smbd
tcp 0 0 0.0.0.0:ftp 0.0.0.0:* LISTEN 2001/pure-ftpd (SER
tcp 0 0 0.0.0.0:telnet 0.0.0.0:* LISTEN 3248/telnetd
tcp 0 0 0.0.0.0:ipp 0.0.0.0:* LISTEN 1816/cupsd
tcp 0 0 0.0.0.0:microsoft-ds 0.0.0.0:* LISTEN 2039/smbd
netstat: /proc/net/tcp6: No such file or directory
sh-4.1#


Top
 Profile  
 
PostPosted: Sun Oct 28, 2012 6:27 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
DLNA server in version 3.2 work beter


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 6:42 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
Obviously no webserver is running.

I've done some research, but I can't think of what could have happened. When your system told the 3.20 firmware was invalid, it should have been rejected. But your NSU reports 3.20.

The problem is, the firmware consists of a kernel, an initramfs, and a rootfs, in two mtd (flash) partitions, and a disk partition. These three parts can be written separately, but should be from the same firmware version.

I *think* somehow one of the parts is of a different firmware versions than the others. So this one should be replaced by the right one. The point is, which part is different, and which firmware version are the other parts. As far as I understand you, there are two version of 4.40 and one version of 3.20 possible.

So I need some dates. Can you give the outputs of
Code:
uname -a
ls -la /
That should tell something about the age of the kernel and the initramfs.

The rootfs is harder, as I suppose it's not even mounted. But maybe it is. Can you give
Code:
cat /proc/mounts
ls -la /ram_bin/


Quote:
sh-4.1#
I suppose you are using an FFP stick, right?


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 6:50 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
yes i use FFP stick:

sh-4.1# uname -a
Linux nsa210 2.6.24.4 #1 Sat Jul 4 00:54:26 CST 2009 armv5tejl GNU/Linux
sh-4.1# ls -la /
total 78
drwxr-xr-x 16 root root 4096 Oct 26 03:36 .
drwxr-xr-x 16 root root 4096 Oct 26 03:36 ..
-rw------- 1 root root 149 Oct 29 18:45 .bash_history
-rwx------ 1 root root 29978 Oct 25 20:29 after_booting.sh
drwxr-xr-x 2 root root 2048 Jul 3 2009 bin
drwxr-xr-x 5 root root 7168 Oct 26 05:08 dev
drwxr-xr-x 4 root root 1024 Oct 26 05:09 e-data
lrwxrwxrwx 1 root root 8 Oct 25 20:31 etc -> /ffp/etc
drwxr-xr-x 14 root root 4096 Oct 25 20:33 ffp
drwxr-xr-x 4 root root 4096 Oct 25 20:31 home
drwxr-xr-x 3 root root 1024 Oct 26 05:08 i-data
drwxr-xr-x 4 root root 1024 Jul 3 2009 lib
drwxr-xr-x 2 root root 4096 Oct 25 20:33 mnt
dr-xr-xr-x 76 root root 0 Jan 1 1970 proc
drwxr-xr-x 2 root root 3072 Jul 3 2009 sbin
drwxr-xr-x 11 root root 0 Jan 1 1970 sys
drwxrwxrwx 16 root root 1024 Oct 29 18:48 tmp
drwxr-xr-x 9 root root 1024 Jul 3 2009 usr
drwxr-xr-x 10 root root 1024 Oct 26 05:08 var
-rw-r--r-- 1 root root 743 Oct 26 03:36 wget-log


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 6:52 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
sh-4.1# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
none /dev/pts devpts rw 0 0
/dev/mtdblock4 /zyxel/mnt/info jffs2 ro 0 0
/dev/sda1 /zyxel/mnt/sysdisk ext3 ro,data=ordered 0 0
/dev/loop0 /ram_bin ext2 ro 0 0
/dev/loop0 /usr ext2 ro 0 0
/dev/loop0 /sbin ext2 ro 0 0
/dev/loop0 /bin ext2 ro 0 0
/dev/loop0 /lib ext2 ro 0 0
/dev/ram3 /tmp ext2 rw 0 0
/dev/ram3 /var ext2 rw 0 0
/dev/ram3 /home ext2 rw 0 0
/dev/ram3 /mnt ext2 rw 0 0
/dev/ram3 /etc ext2 rw 0 0
/dev/ram3 /dev ext2 rw 0 0
/dev/ram3 /usr/local/etc ext2 rw 0 0
/dev/ram3 /usr/local/var ext2 rw 0 0
/dev/ram3 /usr/local/dmsf ext2 rw 0 0
/dev/mtdblock3 /etc/zyxel jffs2 rw 0 0
/dev/ram3 /i-data ext2 rw 0 0
/dev/ram3 /e-data ext2 rw 0 0
none /proc/bus/usb usbfs rw 0 0
/dev/md0 /i-data/0a2b3326 xfs rw,nouuid,usrquota 0 0
/dev/sdb1 /e-data/5089-A16E vfat rw,uid=99,fmask=0000,dmask=0000,codepage=cp437,iocharset=utf8,shortname=mixed 0 0
/dev/sdb2 /e-data/39ad54dd-a145-4571-b64b-50677200b879 ext3 rw,noatime,data=ordered 0 0
/dev/md0 /usr/local/zy-pkgs xfs rw,nouuid,usrquota 0 0
/dev/md0 /etc/zyxel/zy-pkgs xfs rw,nouuid,usrquota 0 0
/dev/md0 /usr/local/apache/htdocs/pkg xfs rw,nouuid,usrquota 0 0
/dev/ram3 /dev ext2 rw 0 0
/dev/ram3 /var ext2 rw 0 0
/dev/ram3 /tmp ext2 rw 0 0
/dev/loop0 /bin ext2 ro 0 0
/dev/loop0 /sbin ext2 ro 0 0
/dev/loop0 /lib ext2 ro 0 0
/dev/loop0 /usr ext2 ro 0 0
/dev/ram3 /e-data ext2 rw 0 0
/dev/sdb1 /e-data/5089-A16E vfat rw,uid=99,fmask=0000,dmask=0000,codepage=cp437,iocharset=utf8,shortname=mixed 0 0
/dev/sdb2 /e-data/39ad54dd-a145-4571-b64b-50677200b879 ext3 rw,noatime,data=ordered 0 0
/dev/ram3 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/dev ext2 rw 0 0
/dev/ram3 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/var ext2 rw 0 0
/dev/ram3 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/tmp ext2 rw 0 0
/dev/loop0 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/bin ext2 ro 0 0
/dev/loop0 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/sbin ext2 ro 0 0
/dev/loop0 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/lib ext2 ro 0 0
/dev/loop0 /e-data/39ad54dd-a145-4571-b64b-50677200b879/ffproot/usr ext2 ro 0 0
/dev/ram3 /i-data ext2 rw 0 0
/dev/md0 /i-data/0a2b3326 xfs rw,nouuid,usrquota 0 0
/dev/ram3 /ffp/etc/original ext2 rw 0 0
/dev/mtdblock3 /ffp/etc/zyxel jffs2 rw 0 0
none /proc proc rw 0 0
/dev/md0 /usr/lib/locale/locale-archive xfs rw,nouuid,usrquota 0 0
none /sys sysfs rw 0 0
sh-4.1# ls -la /ram_bin/
ls: cannot access /ram_bin/: No such file or directory
sh-4.1#


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 6:58 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
In the Beginning was the firmware 4.40 (afd.1) then was trying to upload firmware 3.20 but the NSA rejected. Without cleaning the browser cache (here probably is the beginning of the problem) attempt to upload firmware 4.40 (afd.2) then page is suspended


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 7:04 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
OK, the kernel is dated July 4, 2009, and the initramfs is dated July 3, 2009. I suppose we can safely presume it's firmware 3.20.

Now the rootfs. /ram_bin/ is not reachable due to the FFP chroot. But the contents of /usr/ should be part of the roots. So
Code:
ls -la /usr/sbin/


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 7:09 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
sh-4.1# s -la /usr/sbin/
sh: s: command not found


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 7:10 pm 
Offline

Joined: Wed Oct 24, 2012 8:45 pm
Posts: 14
sorry

sh-4.1# ls -la /usr/sbin/
total 11925
drwxr-xr-x 2 root root 1024 Jul 3 2009 .
drwxr-xr-x 9 root root 1024 Jul 3 2009 ..
-rwxr-xr-x 1 root root 6720 Jul 3 2009 apcaccess
-rwxr-xr-x 1 root root 98588 Jul 3 2009 apcupsd
-rwxr-xr-x 1 root root 14204 Jul 3 2009 app_wd
-rwxr-xr-x 1 root root 7004 Jul 3 2009 bin2ram
-rwxr-xr-x 1 root root 228836 Jul 3 2009 cupsd
-rwxr-xr-x 1 root root 5644 Jul 3 2009 diagnosed
-rwxr-xr-x 1 root root 3522064 Jul 3 2009 dservice
-rwxr-xr-x 1 root root 277040 Jul 3 2009 e2fsck.new
-rwxr-xr-x 1 root root 102320 Jul 3 2009 fadd
-rwxr-xr-x 1 root root 14764 Jul 3 2009 fw_unpack
-rwxr-xr-x 1 root root 26344 Jul 3 2009 groupadd
-rwxr-xr-x 1 root root 21568 Jul 3 2009 groupdel
-rwxr-xr-x 1 root root 21696 Jul 3 2009 groupmod
-rwxr-xr-x 1 root root 611476 Jul 3 2009 httpd
-rwxr-xr-x 1 root root 21772 Jul 3 2009 lpadmin
-rwxr-xr-x 1 root root 101428 Jul 3 2009 lsof
-rwxr-xr-x 1 root root 137316 Jul 3 2009 mke2fs.new
-rwxr-xr-x 1 root root 315396 Jul 3 2009 mkfs.xfs
-rwxr-xr-x 1 root root 110648 Jul 3 2009 mkntfs
-rwxr-xr-x 1 root root 114348 Jul 3 2009 msmtp
-rwxr-xr-x 1 root root 98512 Jul 3 2009 nduagent
-rwxr-xr-x 1 root root 987348 Jul 3 2009 nmbd
-rwxr-xr-x 1 root root 40908 Jul 3 2009 ntpdate
-rwxr-xr-x 1 root root 8696 Jul 3 2009 ntpdate_agent
-rwxr-xr-x 1 root root 243116 Jul 3 2009 pppd
-rwxr-xr-x 1 root root 28024 Jul 3 2009 pppoe
-rwxr-xr-x 1 root root 26908 Jul 3 2009 quotatool
-rwxr-xr-x 1 root root 9284 Jul 3 2009 ram2bin
-rwxr-xr-x 1 root root 10508 Jul 3 2009 rbm
-rwxr-xr-x 1 root root 91844 Jul 3 2009 resize2fs
-rwxr-xr-x 1 root root 3326204 Jul 3 2009 smbd
-rwxr-xr-x 1 root root 95868 Jul 3 2009 syslog-ng
-rwxr-xr-x 1 root root 7732 Jul 3 2009 uam-notify
-rwxr-xr-x 1 root root 10760 Jul 3 2009 uam-query
-rwxr-xr-x 1 root root 72948 Jul 3 2009 uamd
-rwxr-xr-x 1 root root 53772 Jul 3 2009 usermod
-rwxr-xr-x 1 root root 492260 Jul 3 2009 xfs_db
-rwxr-xr-x 1 root root 581364 Jul 3 2009 xfs_repair
-rwxr-xr-x 1 root root 60864 Jul 3 2009 zic
-rwsr-xr-x 1 root root 27676 Jul 3 2009 zylog_mailman
-rwxr-xr-x 1 root root 38632 Jul 3 2009 zylogd
-rwsr-xr-- 1 root nobody 33704 Jul 3 2009 zylogger


Top
 Profile  
 
PostPosted: Mon Oct 29, 2012 7:28 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
Hm. The rootfs is clearly also Juli 3, 2009. Which means all software parts are v3.20. So theoretically the only problem could be an incompatible configuration. The configuration should have been deleted by the factory reset, but we can also do it manually.

First backup the configuration:
Code:
mkdir /ffp/backup
cp -a /ffp/etc/zyxel/* /ffp/backup/
Now go into the configuration directory:
Code:
cd /ffp/etc/zyxel/
pwd
If pwd does not output /ffp/etc/zyxel, don't go any further!
Next, delete the configuration:
Code:
rm -rf *
and reboot
Code:
reboot


BTW, you can also use the edit button instead of creating messages shortly after each other.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 22 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group