NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RND2000 Frontview Not Working After Removal of Failing Disk
Model: RND2000 Firmware: 4.1.16 RAIDar: v6.5.0 Scenario I have had the above RND for many years without significant difficulties. It is configured with 2 2TB disks, mirrored by XRAID. The roo...
I'm delighted to report that I'm back up and running! đ
On consideration of my previous post it struck me there were file(s) missing from the OS and RAIDiator software. This was seemed to apply to some of the Apache system too. I was hesitant to do a full factory reset (for which I had managed to answer most/all of the questions I was considering), and decided to go for a software reinstall. There was the chance that some of the config was missing/corrupt (along with some of my files!), but if that became apparant and I had to go for the full reset then that would have to be done. So here are the steps undertaken.
1. Backup the data over my network to a USB HDD on my PC.
2. Perform software re-install.
After this the system recovered. Frontview and the USB HDD were working again, along with the log emails.
3. Conduct a full check of config on Frontview - all seemed to be correct.
4. Backup up data to the directly connected USB drive.
5. Insert new HDD to replace previously faulty one.
This has been detected and automatically synced with the running disk.
How the system got into this mess I shall probably never know, but at least I know how to get out of it should it happen again, and if this thread is help to anybody else who gets into similar trouble I'm happy!
Thanks to StephenB for his helpful pointers.
I agree that's an option, but it's the option of last resort for which a number of other questions would have to be answered first. I really would like to try and get it back to full running without resorting to that if we can.
Now in the recesses of my mind I have a horrible feeling that the last time I was on Frontview I changed a setting that I probably ought not to have done. I can't recall exactly what that was so we will have to try and undo the effects to at least get Frontview back up and running so that I can resolve any settings issues.
From the ssh root access I have tried to stop and start the Frontview. As I expected Frontview isn't running. The stop command gives the following:
~# /etc/init.d/frontview stop
Stopping frontview: apache-sslNo /usr/sbin/apache-ssl found running; none killed.
Attempting to start Frontview gives another set of output indicating problems elsewhere:
~# /etc/init.d/frontview start
Starting frontview: apache-sslapache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.1.61 for ServerName
Can't locate strict.pm in INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/lib/perl/5.8/Config.pm line 5.
BEGIN failed--compilation aborted at /usr/lib/perl/5.8/Config.pm line 5.
Compilation failed in require at /usr/lib/perl/5.8/lib.pm line 6.
BEGIN failed--compilation aborted at /usr/lib/perl/5.8/lib.pm line 6.
Compilation failed in require at /frontview/bin/set_language line 7.
BEGIN failed--compilation aborted at /frontview/bin/set_language line 7.
Can somebody decode this and point me in the right direction, please?
I have a suspicion that apache2 isn't running either, which might well impact on the above. But I don't know what to do to try an d restart that.
Many thanks.
I'm delighted to report that I'm back up and running! đ
On consideration of my previous post it struck me there were file(s) missing from the OS and RAIDiator software. This was seemed to apply to some of the Apache system too. I was hesitant to do a full factory reset (for which I had managed to answer most/all of the questions I was considering), and decided to go for a software reinstall. There was the chance that some of the config was missing/corrupt (along with some of my files!), but if that became apparant and I had to go for the full reset then that would have to be done. So here are the steps undertaken.
1. Backup the data over my network to a USB HDD on my PC.
2. Perform software re-install.
After this the system recovered. Frontview and the USB HDD were working again, along with the log emails.
3. Conduct a full check of config on Frontview - all seemed to be correct.
4. Backup up data to the directly connected USB drive.
5. Insert new HDD to replace previously faulty one.
This has been detected and automatically synced with the running disk.
How the system got into this mess I shall probably never know, but at least I know how to get out of it should it happen again, and if this thread is help to anybody else who gets into similar trouble I'm happy!
Thanks to StephenB for his helpful pointers.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
