FreeNAS 11.1 U5 - Fatal Trap 12 error

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
My FreeNAS box keeps getting this error and reboots by itself every 5-10 minutes. I have tried re installing FreeNAS but get the same issue.

System Config:
Motherboard - X10SRH-CLN4F with onboard LSI 3008 flashed to P14
CPU - E5-1620 V4
RAM - Hynix 2 x 16GB DDR4 22400 ECC
NIC - Mellanox CX3 40GB
Chassis - SC846 with BPN-SAS3-846EL1
OS Boot disk - 2x Apacer SATADOM (mirrored)
DATA Disks - 20x WD Red (8TB)


123.jpg
 

EffrafaxOfWug

Radioactive Member
Feb 12, 2015
1,394
511
113
Are there any entries in the IPMI log to suggest memory problems, and have you tried a run under memtest?
 

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
There are no issues in the ipmi log. Freenas 10.4 was running in an aio without issues till 2 days ago. Issue started after converting freenas to baremetal.
 

Jeggs101

Well-Known Member
Dec 29, 2010
1,529
241
63
Convert to Proxmox. In other words:

I was afraid. I was petrified.
Kept thinking I could never live without FreeNAS by my side
But then I spent so many nights thinking how FreeNAS did me wrong
And I grew strong
And I learned how to get PVE along

Losing the ZFS GUI wasn't a big deal for me once I learned it.
 

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
Memtest ran successfully for 4 hrs. Found a post in the freenas forums where 11.1 had issues with having mirrored rpool on sata SSDs.

Will try with different SSD or USB flash once I'm back.
 

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
This seems to be an issue with FreeNAS 11.1 U5.

I got the same error after replacing almost everything in the system. Proxmox was stable as well as running FreeNAS / OmniOS in a VM on this system. Tried U5 in another system with a X10SDV-2C-7TPF board and got the same error.

Did a clean install of 11.1 U4 and it has been stable for a week now.
 

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
SMH.

I may have spoken too soon. I had a backup job running and got the same error now. There is nothing in the logs to indicate that something went wrong. Is there anything else I can do to troubleshoot? I've pretty much eliminated the physical hardware. The only other possibility could be the zpool itself. It was originally created in omnios with Napp-It. If all else fails, I have to figure out if it's worthwhile to re-create the pool and restore the data ( >︹<)
 

realtomatoes

Active Member
Oct 3, 2016
251
32
28
44
sorry to hear that.
well, if your data is critical, i'd start your data recovery/restore process, then recreate that pool in freenas from scratch.
 

K D

Well-Known Member
Dec 24, 2016
1,439
320
83
30041
Yeah! This is a backup server. I just kicked off scrubs on my main boxes. Once they finish, Once they are done, I’ll do that. 52TB :(
 

Rand__

Well-Known Member
Mar 6, 2014
6,626
1,767
113
But it makes no sense that this should not have occurred in the VM if it indeed was a pool issue

There was a thread somewhere here that mentioned having issues with MLX Card and Freenas but I can't find it. Not sure its related at all but worth checking.