Yes, I do have a motherboard :)
It's a Supermicro twin box, 6026TT-HTRF. The motrherboard is
X8DTT-HF+
I'm not one for updating software unless there's a problem - while there is no mission critical data on the server at the moment, it does cause a bit of disruption when the box is rebooted.
The box is a bit older, so it could very well be a hardware problem. It did crash hard on me once with an ECC error, but I've replaced the ram since then. In addition, that hard crash was a hard stop- no auto reboot. So this feels different. I'm just trying to figure out where to diagnose in 'BSD as all of my general purpose servers are linux these days and I've forgotten most of my BSD tricks from years gone by (and most of them would likely be 10 years out of date by now anyway)
Interesting that one says don't use autotune, one says to do so.
Attached is a screenshot of the variables it set - any comments (especially obvious problems) most appreciated. My main concern is to max out the ARC as this system has limited # of drives available to it. As it's not yet heavily used, it took about a week to fill up the arc. This is why I noticed that it was approaching full utilization the day before it died.
After it rebooted, I got the following email:
freenas.xxx kernel log messages:
> SMP: AP CPU #12 Launched!
> SMP: AP CPU #10 Launched!
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #15 Launched!
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #13 Launched!
> SMP: AP CPU #6 Launched!
> SMP: AP CPU #14 Launched!
> SMP: AP CPU #11 Launched!
> Timecounter "TSC-low" frequency
1400076204Hz quality 1000
> uhub1: 2 ports with 2 removable, self powered
> uhub2: 2 ports with 2 removable, self powered
> uhub3: 6 ports with 6 removable, self powered
> ukbd0: <Keyboard Interface> on usbus1
> kbd2 at ukbd0
> vboxdrv: fAsync=0 offMin=0x2eb offMax=0x3301
-- End of security output --