RAIDiator 4.1.13 - update failed

Something went very wrong with the filesystem on the OS partition on this system.

It was the 2 GB OS partition not the data volume (checking the data volume briefly it was only 30% full with 1% of the inodes used up) that was full and the inodes were all used up.

Presumably it was almost full before the update and the new files added led to all the remaining inodes being used up and hanged the system.

However on checking to see what was using up the space and after removing some stuff the inodes on the OS partition were still almost all used up.

As a result I had no choice but to format the OS partition and reload the OS. All the users, settings and other configuration data is gone, but the data volume is still there.

The system should now be back to normal with plenty of free inodes.

Thank you for your help

Just to add I had to install Host name fix

It is all back running normally again

Hi, I received the same email as "dmsims" and followed the provided link which failed, but anyway I managed to download the correct file (http://www.downloads.netgear.com/files/GDC/RND2110/RAIDiator-V4.1.13.zip) for my "sparc" based machine and everything went well except for one thing, the web interfaces for "admin" and "shares" are not available (port 80), the other web interfaces running on other ports (ports 8080 & 3689) are fine though.

I managed to log in using an ssh account I had enabled on the ReadyNAS device and I have found that the "apache-ssl" process is failing to start. When I executed the "/etc/frontview/addons/bin/PHP5/restart_apache.sh" command it failed with the message following message:

  nas:~# /etc/frontview/addons/bin/PHP5/restart_apache.sh 
  apache-ssl: no process killed
  apache-ssl: Could not reliably determine the server's fully qualified domain name
  nas:~#

So I added "ServerName nas.XXXXXX.XXX" to the "/etc/frontview/apache/httpd.conf" file and the error went away, however the apache-ssl process still continues to fail.

I do not have an admin web interface, so how can I either fix this issue or downgrade to radiator 4.1.12 from the command line?

Rick

The problem for dmsims was not doing a remote update. The problem was probably already present on his system.

What version of the PHP5 add-on do you have installed? There is a known compatibility issue with 4.1.12+ and certain versions of the PHP5 add-on. All you likely need to do is install the latest PHP5 add-on from the command line once or twice. And maybe do likewise for one or two other add-ons. I wouldn't edit apache configs.

The PHP version I have was purchased from RNXtras.com and is 5.3.27 specifically for the ReadNAS sparc box. I am chasing them up for any suggestions they may have re: 4.1.13 and I shall keep this thread posted on any positive outcome from them.

As for this issue, maybe I should try to disable PHP and see how I go, any suggestions / comments?

However I have disabled PHP from the apache2 config files and apache-ssl still behaves exactly the same way. I suspect that this is not a PHP5 issue, but I could still be proved wrong.

I said not to mess with that. The problem is almost certainly that PHP needs to be installed again.