Printable View
We recently bought a Open-E 8TB DDS module. After fixing some troubles with a BIOS compatibility issue everyting seem to be running fine. Today we've got a power failure and after booting de Open-E DDS sytem NFS has the status failed. I've ran the fsck (on the console pressing ctrl+alt+x en chosing option 10) on the system. Errors were found and fixed. After the reboot NFS still showing 'NFS service - ON - FAILED' is there any way how we can determine why NFS has a failed status?
That is strange; only other way is to investigate the error or critical error logs. Also try to de select and re-select the NFS option in the NAS Settings of the GUI or try to re-flash the module.
error.log:
DRBD device for dssMw0-5Svx-57Sb-0xsH-B53q-N2Qi-xjIP3T does not exist.
[Fri Mar 13 21:14:41 2009] [error] [client 192.168.2.235] PHP Warning: Smarty error: unable to read resource: "file:" in /mnt/hda3/www/class/Smarty/Smarty.class.php on line 1095, referer: https://192.168.2.13/index.php?id=5.4
[Fri Mar 13 21:16:09 2009] [notice] SIGHUP received. Attempting to restart
apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.2.13 for ServerName
[Fri Mar 13 21:16:09 2009] [warn] RSA server certificate CommonName (CN) `pluto' does NOT match server name!?
[Fri Mar 13 21:16:09 2009] [notice] Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.7e PHP/5.2.6 configured -- resuming normal operations
[Fri Mar 13 21:25:42 2009] [error] [client 192.168.2.235] PHP Warning: Smarty error: unable to read resource: "file:" in /mnt/hda3/www/class/Smarty/Smarty.class.php on line 1095, referer: https://192.168.2.13/index.php?id=5.4
[Fri Mar 13 21:39:43 2009] [error] [client 192.168.2.235] PHP Warning: require_once(session.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in /mnt/hda3/www/css/IE/menuIEFix.css.php on line 2, referer: https://192.168.2.13/index.php?module=menu
[Fri Mar 13 21:39:43 2009] [error] [client 192.168.2.235] PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'session.php' (include_path='.:/usr/share/php') in /mnt/hda3/www/css/IE/menuIEFix.css.php on line 2, referer: https://192.168.2.13/index.php?module=menu
[Fri Mar 13 21:39:49 2009] [error] [client 192.168.2.235] PHP Warning: require_once(session.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in /mnt/hda3/www/css/IE/menuIEFix.css.php on line 2, referer: https://192.168.2.13/index.php?module=menu
[Fri Mar 13 21:39:49 2009] [error] [client 192.168.2.235] PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'session.php' (include_path='.:/usr/share/php') in /mnt/hda3/www/css/IE/menuIEFix.css.php on line 2, referer: https://192.168.2.13/index.php?module=menu
[Fri Mar 13 21:39:51 2009] [error] [client 192.168.2.235] PHP Warning: Smarty error: unable to read resource: "file:" in /mnt/hda3/www/class/Smarty/Smarty.class.php on line 1095, referer: https://192.168.2.13/index.php?id=5.4
/bin/ls: /sys/class/dma: No such file or directory
ls: /sys/class/dma/: No such file or directory
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc doesn't contain a valid partition table
/var/nasexe/sendlog: line 335: /var/nasconf/bacula/bacula.conf: No such file or directory
critical_errors.log:
2009/03/13 21:10:18|bonding: bond0: link status definitely up for interface eth0.
2009/03/13 21:10:18|bonding: bond0: link status definitely up for interface eth1.
We also did a deselect en select of the NFS service but that didn't solve the problem.
I think if the service failed or is still failing then there are XFS issues. Try running the Repair tool from the Extended tools once more and see if there are no more errors during the repair. Make sure that all tasks for the snapshots are disabled before running. If the service still is failing to run we may need to have run the Remote Support Service to remotely access the system to see why this is failing.