FreeNAS 11 build on Supermicro X11SSM-F with Xeon E3 1230 V6

[FFrederiksen]

Building a new FreeNAS for file sharing running Plex, Owncloud and Wordpress. Plex is transcoding 1-2 at the same time

Supermicro X11SSM-F motherboard
Intel Xeon E3 1230 v6 processor (Kaby Lake)
Cooler Noctua NH-L9i
1x Crucial 16GB DDR4-2400 ECC Unbuffered (CT16G4WFD824A)
Define R4 Black Pearl
SeaSonic X-650
SSD, and drives are taken from the existing FreeNAS

What do you think, and any caveats?

Thx
Frederik

 

[Stux]

Seems good to me.

You could get away without the Noctua perhaps as the CPU includes a box cooler, but running plex on the highest end Xeon E3, maybe its not a bad idea :)

Be sure to check your HD temps during a burnin or solnet-array-tester, and take steps if they are getting too high.

I think if you have BIOS v1.x then the v6 CPUs may not boot until you can do a BIOS upgrade.

 

[FFrederiksen]

Hi, Stux
Thx for your reply
Just realised there is an error in my setup. The DDR4-2133 is not supported with the Kaby Lake it need to be a DDR4-2400. Also I thought Intel removed the Box Cooler on the Kaby Lake processor...

 

[Stux]

Hi, Stux
Thx for your reply
Just realised there is an error in my setup. The DDR4-2133 is not supported with the Kaby Lake it need to be a DDR4-2400.

I suspect you'll find that 2133 works fine, but 2400 will be more performant, and normally is similarly priced. Not 100% sure though.

Also I thought Intel removed the Box Cooler on the Kaby Lake processor...

You might be right there, but I don't know.

 

[kamin]

Building a new FreeNAS for file sharing running Plex, Owncloud and Wordpress. Plex is transcoding 1-2 at the same time

Supermicro X11SSM-F motherboard
Intel Xeon E3 1230 v6 processor (Kaby Lake)
Cooler Noctua NH-L9i
1x Crucial 16GB DDR4-2400 ECC Unbuffered (CT16G4WFD824A)
Define R4 Black Pearl
SeaSonic X-650
SSD, and drives are taken from the existing FreeNAS

What do you think, and any caveats?

Thx
Frederik

Did Crucial memory (CT16G4WFD824A) workout for you? I have a similar build coming up and was going to cannibalize this memory from a previous build.