FreeNAS 11.1 issue

[SilentStrike]

Hello,

There seems to be an issue with FreeNAS 11.1 (U1 or U2) with my system. I tried as much as I could to figure out what the issue is, but I'm here now. Here is a rundown of my hardware.

Motherboard: Supermicro X9SCL+-F
CPU: Intel Xeon E3-1240 V2
RAM: 4x 8GB Samsung MEM-DR380L-SL02-EU16
HBA: LSI 9211-8i

This is every SATA device plugged. "da" into my HBA, "ada" into my motherboard.
WDC WD1001FALS-4 da0
WDC WD1001FALS-4 da1
WDC WD1001FALS-4 da2
ST31000524NS da3
ST31000524NS da4
ST31000524NS da5
ST31000528AS da6
ST4000DM001-1FK1 da7
KINGSTON SVP200S37A120G ada0
KINGSTON SV300S37A120G ada1
ST5000DM000-1FK178 ada2
ST3000VN000-1HJ166 ada3
HL-DT-ST DVD+-RW GS40N cd0

I get the error in the screenshot everytime I launch FreeNAS. I've tried to see if it was a device in question causing issues (As this is a new system) but everything runs fine and smooth on 9.10.
That being said, if I unplug ada1, ada2 and ada3, it boots.

ada1 is my mirror boot drive, ada2 and ada3 are random HDDs. I tried unplugging these individually, but they really need to be unplugged, all 3. If I don't, then FreeNAS gets stuck in a reboot loop. Getting this error every single boot, then rebooting.

Anyone have any idea what could be causing this?

Thanks!

 

[Alecmascot]

How about you search the forums for trap 12 issues.......

 

[SilentStrike]

How about you search the forums for trap 12 issues.......

Trust me, I have. I've seen many trap 12 issues, but haven't seen one I can relate to. And if there is, I don't understand what I'm seeing. And that's precisely why I'm here posting for help :)

 

[nightshade00013]

You limited yourself then. If you can't find something on FreeNAS then search FreeBSD since that is the base OS involved.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223770

Long story short try:

Code:

kern.cam.scsi_delay="5000"

or

Code:

kern.cam.boot_delay="5000"

or

Code:

kern.cam.boot_delay="10000"

In the tunables as a loader.

Something in the timing is causing an issue so putting a delay in may fix it. If the first doesn't work then try the second but don't try them all in one shot.

 

[SilentStrike]

So I tried what you suggested, and it still won't boot. Got a new error I'll start looking into now.

Here are the different tunable scenarios I tried.

kern.cam.scsi_delay="5000" alone.
kern.cam.boot_delay="5000" alone.
kern.cam.boot_delay="10000" alone.
kern.cam.scsi_delay="5000" with kern.cam.boot_delay="5000".
kern.cam.scsi_delay="5000" with kern.cam.boot_delay="10000".

Only result that differed was the last one. sci_delay with 10000 boot_delay. That actually allowed me to boot, but always into 9.10. It's like my update wasn't recognized with that option.