Running FreeNAS 9.1.1 from an 8GB USB drive (Kingston DTSE9H/8GBZ). The system consists of an Intel S5000PSL motherboard with 2 Xeon E5345 processors and 32GB of Kingston ECC RAM. I have a 3ware RAID controller (9650se-12ML) with 6 x 4TB (Seagate ST4000NM0033) hard drives connected. These drives are in one raidz2 volume giving me roughly 14.5TB. This is all in a SuperMicro CSE-846TQ-R900B chassis with 900watt redundant power supplies. I am using one of the on-board gigabit ethernet connectors with a static ip- appears to be an 82563EB chipset. There is one Unix (NFS) share and one Windows (CIFS) share on the system. There are a handful of CentOS 6.4 machines that access the NFS share and one Windows 2008 machine that touches the CIFS share. Not very high volume in my opinion, maybe 250mb per hour being read or written (mostly written).
Here is my problem: Several times per day the system becomes unresponsive. You can not read or write to the shares from Windows or CentOS. The web interface is sometimes accessible during this time but usually is not. You can ping the IP address of the system during this time. The only way I have found to get it to start back up (other than rebooting) is to start an SSH session with the system from PuTTY. You don't have to login, just start the SSH sessions so that it prompts for a username. Then all of the shares come back, the processes that are reading and writing to the shares from either Windows or CentOS continue, and the web interface comes up. The other peculiar thing that happens is if you go look at the 'Reporting' tab in the web interface there are gaps in all of the graphs for the time period that the system was unavailable.
The issue seems very similar to the problem raised here: http://forums.freenas.org/threads/nfs-dies-under-load.14346/ but there really is no good solution mentioned and it does not seem to be the exact same issue.
I'm not sure where to go from here. The hardware is mostly new. The used parts were pulled from a machine that was previously running Windows without any problems. The system is in a large data center that is climate controlled and has very reliable power. I'm not sure what to do other than try running an older release like 8.3.2.
I would appreciate any suggestions. Please let me know if I can provide any other information that may help.
Here is my problem: Several times per day the system becomes unresponsive. You can not read or write to the shares from Windows or CentOS. The web interface is sometimes accessible during this time but usually is not. You can ping the IP address of the system during this time. The only way I have found to get it to start back up (other than rebooting) is to start an SSH session with the system from PuTTY. You don't have to login, just start the SSH sessions so that it prompts for a username. Then all of the shares come back, the processes that are reading and writing to the shares from either Windows or CentOS continue, and the web interface comes up. The other peculiar thing that happens is if you go look at the 'Reporting' tab in the web interface there are gaps in all of the graphs for the time period that the system was unavailable.
The issue seems very similar to the problem raised here: http://forums.freenas.org/threads/nfs-dies-under-load.14346/ but there really is no good solution mentioned and it does not seem to be the exact same issue.
I'm not sure where to go from here. The hardware is mostly new. The used parts were pulled from a machine that was previously running Windows without any problems. The system is in a large data center that is climate controlled and has very reliable power. I'm not sure what to do other than try running an older release like 8.3.2.
I would appreciate any suggestions. Please let me know if I can provide any other information that may help.