Upgraded to 2.1.03

[zeezow]

Now I can no longer access the Web UI.

I am able to successfully map to the NAS, I can make changes through the setup utility, everything seems to work fine except for the Web UI. Thanks in advance for any help.

[sigma]

Like zeezow I have much the same problem.

These are the details.
1. The original firmware was the first release (1.00). I went through the webgui interface to update to 2.1.03. This process went according to the description for updating including the final beep before executing the reboot button. The update was reported as being successful. On reboot, no webgui could be found.
2. The process for resetting to the factory settings (rebooting with the reset button pressed in for the required time) does not work.
3. I can see the unit using the setup utility. Within this utility I cannot fix the IP address to 192.168.1.x (192.168.y.x works if y is not equal to 1) but it allows a DHCP server to set the units IP address to 192.168.1.x Through this utility I can change the admin password, activate or inactive the ftp server, change the IP address as outlined above. I can ping to the unit. Also I can ftp to the unit but only as anonymous user - it won't authenticate with the admin password (no matter what it is). As an anonymous user I can create directories and copy files to the 2100 - but cannot delete files or folders.
4. Only 1 ethernet port works - the top one.

With this level of functionality is there any hope of recovery? eg using the ThecusWiki article "N2100 Recovering from a bad config change" - onbeat.dk/thecus/index.php/N2100_Recovering_from_a_bad_config_change

Many thanks for any suggestions.

(I have not done anything with Debian on the unit. I'm looking to recover the unit through Windows only - if possible)

[dbridges]

To both zeezow and sigma. Have you notified Thecus? Hopefully suggesting that they pull their firmware.

Their firmware development team managers aren't the brightest bunch and they probably never tested a single step firmware upgrade as opposed to progressive updates.

Unfortunately without the webgui you're pretty much stuffed

I can confirm that the "N2100 Recovering from a bad config change" is an extreme measure and not something that you want to do if you don't have to

However it will work but it's involved and you will need a linux machine.

Have you done an isolation test. Just your computer and the thecus with a single switch in between (or a crossover cable).

Have you tried https?

What do you get when you try to access the web gui. Anything? Nothing? Does it come up but you cant log in?

Also Thecus introduced a bug in their latest firmware relating to the setting of ip addresses...
thecususergroup.proboards106.com/index.cgi?board=installationissues&action=display&thread=1168996497

You'll need to be absolutely clear about which port you're using and what ip address you're using and that you're computer is on the same subnet. You'd be surprised how easy it is to mess things up when you're really frustrated.

Your unit should be under warranty and if thecus have screwed up then they should be the ones to fix it.

Don't resort to extreme measures which will void your warranty if you don't have to.

[sigma]

Many thanks dbridges for replying to my post.

This is a quick reply but I will follow up on all the points you raise.

The unit is no longer under warranty so there is room to move.

I had contacted Thecus about the failure after upgrading but they simply sent the instructions for the factory reset procedure. I have not contacted Thecus with the information I presented in my first post.

On the isolation test, I have connected to the unit by this method since the problem started. Details are: PC with 2 network cards one set to IP of 192.168.0.10 and connected directly to the 2100 with an IP of 192.168.0.20 I use a straight through cable rather than a cross over cable. I'm told the ethernet port on the 2100 can auto sense straight through or crossover. In any case I assume that one couldn't ping or ftp to the 2100 if the cable was no good.

With this setup I have been through the diagnostic flow chart as outlined in the user manual ie with no discs installed.
1. As mentioned the factory settings reset procedure does not work - by that I mean the setup program cannot find the 2100. If I then reboot normally the unit can be found by the setup program with the old IP address.
2. During normal bootup the busy lead flashes for 120 seconds and then the unit beeps. As mentioned can ping and ftp to the unit.

I'm not sure from the diagnostic flow chart whether the firmware is corrupted or the motherboard is bad (sic) or both. The busy lead does keep blinking but only for 2 minutes, not more than 3 minutes as mentioned. However, the admin webpage looks like it is not accessible.

But why can I ping and ftp to it?

With https I assume you mean 192.168.0.20 With this or the normal 192.168.0.20 the response is "Internet Explorer cannot display the webpage" from the browser.

I think I have the IP address issue okay. What information on ports should I know about?

[dbridges]

sigma said:

Many thanks dbridges for replying to my post.

This is a quick reply but I will follow up on all the points you raise.

The unit is no longer under warranty so there is room to move.

I had contacted Thecus about the failure after upgrading but they simply sent the instructions for the factory reset procedure. I have not contacted Thecus with the information I presented in my first post.

On the isolation test, I have connected to the unit by this method since the problem started. Details are: PC with 2 network cards one set to IP of 192.168.0.10 and connected directly to the 2100 with an IP of 192.168.0.20 I use a straight through cable rather than a cross over cable. I'm told the ethernet port on the 2100 can auto sense straight through or crossover. In any case I assume that one couldn't ping or ftp to the 2100 if the cable was no good.

With this setup I have been through the diagnostic flow chart as outlined in the user manual ie with no discs installed.
1. As mentioned the factory settings reset procedure does not work - by that I mean the setup program cannot find the 2100. If I then reboot normally the unit can be found by the setup program with the old IP address.
2. During normal bootup the busy lead flashes for 120 seconds and then the unit beeps. As mentioned can ping and ftp to the unit.

I'm not sure from the diagnostic flow chart whether the firmware is corrupted or the motherboard is bad (sic) or both. The busy lead does keep blinking but only for 2 minutes, not more than 3 minutes as mentioned. However, the admin webpage looks like it is not accessible.

But why can I ping and ftp to it?

With https I assume you mean 192.168.0.20 With this or the normal 192.168.0.20 the response is "Internet Explorer cannot display the webpage" from the browser.

I think I have the IP address issue okay. What information on ports should I know about?

Factory reset just sets your ipaddress back to 192.168.1.100 and resets the password and that's all.

It looks like your web config has become messed up.
As you're out of warranty there's nothing stopping you from using the serial connection to fix it.

The file that you need to clean up or replace is /app/etc/httpd/conf/httpd.conf

Does your serial ata backplane have the serial socket or just the holes???

If you want help with the instructions on the wiki then PM me.

DO NOT take a soldering iron to your n2100. It's not necessary.

A linux machine helps because you'll need a tftp server but it should be possible from windows. TFTP doesn't route so you must use a direct connection.

[sigma]

Thanks again dbridges for your reply.

Being one of the older units the serial pins are in place. I have a serial riser connector from an old PC that connected to com port pins (9) on the motherboard. Just need to get a null modem cable - I can make one if I need too.

I have a Windows version of tftp server.

This is going to get technical so I would like to accept your offer to PM you to work through details.

If I succeed then the procedure might be worth writing up.

Regards

[ktulaman]

zeezow and sigma:

Do you have ssh access to your broken N2100? If you do, fixing the "corrupted" web config is easier than the method using the null modem cable.

[dbridges]

I worked with sigma to resolve his problem.

His firmware upgrade wiped his app/etc/httpd/conf/httpd.conf
such that it had a filesize of zero.

The solution was to take the HDD and put it into a machine running systemrescuecd(?) and manually create a samba share with root permissions to the root (/) folder.

This allowed access to the apache config and it was all fixed.

zeezow probably got pissed off and returned his n2100.

SSH would have allowed it to be fixed with no hassles but unfortunately people dont install before they need it.

I've taken to recommending it as an automatic essential.