IMPORTANT NOTICE
During the next period of time, the Thecus Wiki will migrate to a new site - the NAS Website. The migration is part of an improvement initiative, which includes giving the site a new look and making it more user friendly.
During the migration information may exist both at the old and new site, however slowly pages should start to be located mainly at the new site. Please see the NAS Website for details.
N5200 Troubleshooting
From Thecus Wiki
Contents |
Wan Access
I am having trouble accessing my Thecus 5100n device from a WAN address; from the LAN it works perfectly. The IP address of my Thecus device is a public IP address (full routable) that is completely accessible from the LAN but not from the WAN. From the WAN I cannot FTP, HTTP, SMB, or ping the thecus device. From the LAN I can FTP, HTTP, SMB, and ping the device.
I can see TCP/IP SYN packets crossing the network gateway and be directing via network switches to the device but the device does not send any SYN-ACK packets out regardless of how many SYN packets are sent to it using various TCP/IP protocols (FTP, HTTP, SMB, etc.).
I cannot find any sort of firewall settings within the thecus device and the odd part about it is that all of my local LAN clients have no trouble working with it.
Any suggestions on how I can resolve this issue would be appreciated.
--
I am having the same problem with the new N5200Pro - it was working but then stopped. The eth light on the front of the unit no longer lights up.
General
Q) My N5200 is stuck with a message of "Self testing" on the LCD
A) Sometimes this happens when you try and soft-reboot your NAS. Perform a hard-reboot by turning the power switch off for a few seconds and then turn it on again. (Switch is on the rear near where the power cord plugs in).
This however does not always fix the problem.
Note also - sometimes the unit will successfully finish a boot after sitting at "Self testing" for quite a while - considerably more than the 40 seconds or so implied by the docs. Suggest leaving it a good ten minutes... Supplementary info - we had this problem with a 5200 where the fifth disk was "dud". It was taking about 20 mins to boot, we presume it was trying FSCKs and stuff on the fifth disk before booting. Eventually it booted clean, mounted the raid, and reported four good disks. Fifth disk not even mentioned in reports. See also note under troubleshooting for the N3200. It appears a Very Long Boot Time is not unexpected under certain circumstances, up to several hours!
A) If you've used the web interface to start a "Filesystem Check" on your RAID array, you MUST then use the web interface to "Start" (or abort) the check after the system reboots. Until the check is started (or aborted), the system will not be available for use.
Q) Why can't I have multiple concurrent FTP sessions, using the same FTP account, from different computers accessing my Thecus N5200 device? That is, I want to be able to hand out a single FTP L/P and have multiple people use it at the same time. Is this not possible?
A) it looks like the 1.00.08 firmware fixes this.
Modules (firmware <= 1.00.05)
Q) When I SSH into my N5200 after installing the SSHD module, none of the usernames and passwords I have set up via the web interface work.
A) You need to install the SYSUSER module/patch and log in as sys with password sys.
Modules (firmware >= 1.00.06)
Please contribute...
Possible Solution
By running the following command from ssh: route add default gw 10.10.1.1 bond0 (where 10.10.1.1 is your router gateway) I managed to gain outside access to my device.
Let me know if this works for you. I am trying to setup a script to run that on boot but I am a linux n00b.