Downgrade from 4.2.31 to 4.2.30?

Ok.  So there's no point in truncating logs, etc. since the OS partition isn't filling.

Do you only have one network connection active?

If so, you could do the brute-force method (back up data, factory reset, rebuild NAS, restore data), as that is guaranteed to deal with anything wrong in the OS partition.  

Perhaps back up the data, and then try an OS-reinstall first.  That is non-destructive, but will reset the network interface to use DHCP and the password to netgear1.

Reinstall done - that went pretty quick.

Now, the web interface is totally down (I get a connection refused error on the new IP address).

However, the shares seem solid now (no network error copying files to the unit...yet). I will continue to pound on it to see if the network stays up, but no idea why the web interface is dead.

Ugh - a factory reset may be the way to go.

I hope its not a hardware issue! Is there a log I can get via telnet that would show information about why the web server is hung or if there are hardware failures? I can get the logs via the web interface, so I need to go the SSH route to get them.

Thanks for all your help-

Dave

This sounds like a corrupted OS partition to me (not hardware).  Even if you get past the web server startup, there might be other things broken that aren't as obvious.  So I think the factory default (painful though it is) is the best approach.

You could look through /var/log and see if there are any issues related to apache.

You could also try manually restarting the service and see what happens.

apache-ssl -f /etc/frontview/apache/httpd.conf -k restart