How to update the NAS540 firmware from the serial terminal?

Matteo

Question as per subject. Here below the background.

I successfully connected the usb serial adapter to the NAS540 since I wanted to play with NAS540 and install debian and OMV. It was quite sometime since I used that last time and got no access to the web interface of the original zyxel firmware. Reviewing the bootlog I found that the FW 5.11 is still in there and want to update the FW to the latest version.

Should somebody be able to tell me what is wrong with the installed FW, that would be great as well.

Here attached the bootlog. Note that I run that with no HDD attached.

Thank you in advance for you support.

Ciao,
   Matteo

#NAS_Jan_2019

Mijzelf

I still don't see a clear reason why the webserver isn't started. AFAIK it is not started directly or indirectly by /etc/init.d/rcS, and so it's hard to find reasons why it wouldn't start.

Have you already  tried a factory reset?

Matteo

That's the solution! The factory reset solved the problem. 


For the sake of the completion of this question, I did not find a way to upgrade the firmware from the serial port but I was able to manage a full update to the latest FW.

Thank you for the support.

lodiabai

even reboot, you still can't access web interface?

if accessible, then you can try to create a volume and do firmware upgrade through web interface.

Matteo

Yes it happens at every boot.
Should that be useful I can send the bootlog with the HDDs connected.

Yes the Point is exactly that: boot to the web interface and update the FW. 

Thanks for the support, 
   Matteo 

Mijzelf

The boot looks normal. Maybe you assigned a fixed IP?

Matteo

Not to my knowledge.

How can I set the IP as dynamic? From the console I mean. 

Thanks you all for the help.

Regards, 
   Matteo 

Mijzelf

You can see the current used IP by executing

ifconfig

You can request an ip address by dhcp by executing

dhcpcd egiga0

or

dhcpcd egiga1

depending on the port you used.

Matteo

Thank you for the quick reply.

From the ifcong, no ip assigned.
---8<---
/ # ifconfig  
egiga0    Link encap:Ethernet  HWaddr 5C:F4:AB:5B:AB:6C   
         inet6 addr: fe80::5ef4:abff:fe5b:ab6c/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:5 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000  
         RX bytes:300 (300.0  TX bytes:468 (468.0

egiga1    Link encap:Ethernet  HWaddr 5C:F4:AB:5B:AB:6D   
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000  
         RX bytes:0 (0.0  TX bytes:238 (238.0

lo        Link encap:Local Loopback   
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0  
         RX bytes:356 (356.0  TX bytes:356 (356.0
---8<---

activating the ip returns:
---8<---
/ # dhcpcd egiga0
Jan 25 18:50:16 NAS540 dhcpcd[2927]: dhcpT1value is 21660 sec
Jan 25 18:50:16 NAS540 dhcpcd[2927]: dhcpT2value is 37905 sec
2019/01/25 18:50:16 [ipnotify] : detect a new IP and execute /sbin/ipnotify_exec.sh
Jan 25 18:50:16 NAS540 avahi-daemon[1598]: Joining mDNS multicast group on interface egiga0.IPv4 with address 192.168.1.120.
/ # [ipnotify_exec.sh]: ******** detect egiga0 new IP********
Jan 25 18:50:16 NAS540 avahi-daemon[1598]: New relevant interface egiga0.IPv4 for mDNS.
Jan 25 18:50:16 NAS540 avahi-daemon[1598]: Registering new address record for 192.168.1.120 on egiga0.IPv4.
Jan 25 18:50:18 NAS540 httpd[2845]: [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
Jan 25 18:50:19 NAS540 httpd[2843]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Jan 25 18:50:19 NAS540 httpd[2843]: [warn] RSA server certificate CommonName (CN) `NAS540' does NOT match server name!?
Jan 25 18:50:19 NAS540 httpd[2843]: [error] mod_auth_zyxel: initialized.
---8<---

 I can successfully ping it from my laptop 
---8<---
ping 192.168.1.120
PING 192.168.1.120 (192.168.1.120) 56(84) bytes of data.
64 bytes from 192.168.1.120: icmp_seq=1 ttl=64 time=3.89 ms
64 bytes from 192.168.1.120: icmp_seq=2 ttl=64 time=2.05 ms
64 bytes from 192.168.1.120: icmp_seq=3 ttl=64 time=1.55 ms
64 bytes from 192.168.1.120: icmp_seq=4 ttl=64 time=2.30 ms
64 bytes from 192.168.1.120: icmp_seq=5 ttl=64 time=2.38 ms
^C
--- 192.168.1.120 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 10ms
rtt min/avg/max/mdev = 1.553/2.434/3.885/0.781 ms
---8<---

accessing 192.168.1.120 from chromium on the laptop I have:
---8<---

This site can’t be reached

192.168.1.120 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

---8<---

Mijzelf

Hm. You can start the webserver with

/etc/init.d/httpd.sh restart

Matteo

Update:
Thanks to your advise I  successfully started the web server and updated the firmware to the latest version. So the original question on how to update, is no longer a point.

The point is that now the NAS boots with the network up but the web server is not working. I can again start the server with the command "/etc/init.d/httpd.sh restart" via serial port, but it is not the most appropriate way to use the NAS.

Here attached is the log of the boot that I have now. I see some errors, but unable to find an appropriate solution so far. Here below one example.
[27/Jan/2019:18:08:23]  [network_main_model_front.py.pre](apache_config_setting)(627): There is no statement '#WebService Start#' in httpd_zld.conf.

Thank you,
   Matteo.

Mijzelf

I can see you have both Entware and ffp installed. Is it possible that one of them kills the webserver?

Matteo

I uninstalled both of them. Same situation.

Here attached the bootlog of today after that.

I am still reviewing that file looking for a solution.

Thank you,
   Matteo