Scott Pandorf
Cadet
- Joined
- Oct 14, 2016
- Messages
- 1
I am preparing a new environment, FreeNAS build FreeNAS-9.10.1-U2 (f045a8b)
This is running on a Dell PowerEdge T110 with a single NIC
Platform: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
Memory: 6105MB
Frequently when I come in on Monday, the server is locked up, i.e. server is running, server is ping-able, the console responds but I am unable to access from the web and the shares are not available. I am forced to reboot the machine, once I do this everything is good.
I have started to transfer files from another Samba share on the network and it will also lock up, this just happened after the transfer had been running for 3+ hours. (Transfers using windows robocopy to move files from old Samba/Ubuntu share to new FreeNAS share).
Looking at the log there are no events that would concern me.
Oct 18 15:15:03 glpcshare autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot -r -o freenas:vmsynced=Y "FreeNASPool@auto-20161018.1515-2w"
Oct 18 15:15:04 glpcshare autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "FreeNASPool@auto-20161004.1515-2w"
... Transfer crapped out somewhere between these two ...
Oct 18 15:42:50 glpcshare shutdown: reboot by root:
Oct 18 15:42:51 glpcshare syslog-ng[1471]: I/O error occurred while writing; fd='28', error='Input/output error (5)'
Any suggestions about what I can look into / do to try to diagnose this problem? I sure can't implement on FreeNAS if it is going to be DOA every Monday morning.
Thanks, Scott.
This is running on a Dell PowerEdge T110 with a single NIC
Platform: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
Memory: 6105MB
Frequently when I come in on Monday, the server is locked up, i.e. server is running, server is ping-able, the console responds but I am unable to access from the web and the shares are not available. I am forced to reboot the machine, once I do this everything is good.
I have started to transfer files from another Samba share on the network and it will also lock up, this just happened after the transfer had been running for 3+ hours. (Transfers using windows robocopy to move files from old Samba/Ubuntu share to new FreeNAS share).
Looking at the log there are no events that would concern me.
Oct 18 15:15:03 glpcshare autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot -r -o freenas:vmsynced=Y "FreeNASPool@auto-20161018.1515-2w"
Oct 18 15:15:04 glpcshare autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "FreeNASPool@auto-20161004.1515-2w"
... Transfer crapped out somewhere between these two ...
Oct 18 15:42:50 glpcshare shutdown: reboot by root:
Oct 18 15:42:51 glpcshare syslog-ng[1471]: I/O error occurred while writing; fd='28', error='Input/output error (5)'
Any suggestions about what I can look into / do to try to diagnose this problem? I sure can't implement on FreeNAS if it is going to be DOA every Monday morning.
Thanks, Scott.