bigphil
Patron
- Joined
- Jan 30, 2014
- Messages
- 486
I would appreciate a little help trying to find the cause of random reboots on a FreeNAS system.
9.2.1.2 Release
i5-2400S
Intel DQ67EP motherboard
8gb non-ecc
intel pro/1000 nic's
I understand that the hardware is not the greatest here, and if its a hardware issue, so be it...I would bet on memory. I would just like a little assistance to see if there is anything in the logs that could point to any other possible issues. The reboots are usually random in nature, but almost guaranteed to happen when I perform a Veeam backup over NFS from an ESXi 5.5 host. The system will reboot almost immediately after the job starts and then it comes back up and continues on its way without any issue until the next backup job runs. I have syslog going to the .system dataset and have looked at the logs but nothing seems obvious to me. The latest crash was 6am on the nose this morning, but no Veeam job runs then. I've attached some logs if anyone with knowledge on this would care to look at them. Also...is there any additional logging I may turn on that could assist in tracking this down? Thanks!
9.2.1.2 Release
i5-2400S
Intel DQ67EP motherboard
8gb non-ecc
intel pro/1000 nic's
I understand that the hardware is not the greatest here, and if its a hardware issue, so be it...I would bet on memory. I would just like a little assistance to see if there is anything in the logs that could point to any other possible issues. The reboots are usually random in nature, but almost guaranteed to happen when I perform a Veeam backup over NFS from an ESXi 5.5 host. The system will reboot almost immediately after the job starts and then it comes back up and continues on its way without any issue until the next backup job runs. I have syslog going to the .system dataset and have looked at the logs but nothing seems obvious to me. The latest crash was 6am on the nose this morning, but no Veeam job runs then. I've attached some logs if anyone with knowledge on this would care to look at them. Also...is there any additional logging I may turn on that could assist in tracking this down? Thanks!