I'm revising this build a bit over the following weeks/months. The plan is to basically convert it to an ESXi based FreeNAS AIO, very similar to my
baby version pilot system
I'll be upgrading the RAM, fans, adding a PCIe SSD for SLOG, adding some SATA SSDs for boot/l2arc etc, adding 10gbe and adding a 36 port SAS expander.
I'm using the SAS expander because I need to be able to pass through all drives/controllers into FreeNAS, and that means I can't really use the on-board SATA any more. I could add another HBA, but then I'd be out of PCIe slots, or I'd be bottlenecking various devices... and I have plans for the 16x slot already.
The 36 port expander means I can dual-link up to 28 bays off a single HBA and reclaim a PCIe3 x8 slot, and reclaim an HBA too... and I have other things to do with a spare HBA :)
And the 36 port expander was pretty much the same price as two HBAs... so its even.
All the parts have now arrived :)
Have already upgraded memory to 128GB using 4x 32GB RDIMMs, and already have the Intel X550-T2 10gbe adapter installed and tested. I was delayed by a few weeks due to RMA on the 10gbe card.
The Intel RES2CV360 arrived recently, so I wanted to test its functionality and begin to map out where it will be installed...
View attachment 20764
Think I will mount it around about here. Between the motherboard and fan bulkhead. I've already pulled one of the molex connectors back out from the drive bay section and it will reach the power input on the SAS expander nicely. The heat sink gets hot, so being in the air flow path is not a bad thing. Unfortunately the short cables that come with the expander won't be much good.
Haven't really worked out how I'm going to secure the expander. I think some plastic insulator sheet of some sort might be in my future.
While testing/setting up, I found that this section from the RES2CV360
manual
Is fairly important. If you don't cable the drive bays A->F (and presumably G) then the slot# in
sas2ircu <#> display
gets confused.
If you do, then you get a nice display with the sasexpander and connected drives, listed with increasing slot numbers and enclosure number. (each HBA is an enclosure and each Expander seems to be an "enclosure"), so 0 and 1 for my two HBAs, and then the expander is Enclosure 2 connected to enclosure 1.
So, the next thing to do is test if I can set a drive to boot off the expander...
Which apparently works fine. Need to ensure the HBA has its option rom installed, that option roms are enabled for the PCIe slot its installed for, you can then configure the HBA boot order in the avago bios utility, and then you can select any of the devices attached to the entire sas topology (apparently) from the SM bios' boot screen, under HD disk priority.
Sweet. This means I'll be able to fallback to direct booting off the HBA, or should be able to simply pass it in to boot with ESXi. Won't even need a VMDK for FreeNAS. I think.