For anybody considering SM-X11 + Crucial-ECC:
I'm running SM+Crucial since summer now and it keeps sometimes crashing - not often, but ugly enough. It just reboots with no log entries. After the automatically following reboot is triggered another bug, this time SM BIOS, telling you "No RAM modules installed". I thought first that the "No RAM installed" is the cause of the FreeNAS crash somehow - but it's not. All the full MemTests were ok.
After a emailing with the SM support, it seems that the current SM BIOS (2.17.1254, 2016) has a bug in RAM detection after a warm reboot. And this warm-reboot is called after FreeNAS 9.10 crashes. So it seems to be quite unrelated: the FreeNAS crash bug only triggers the SM BIOS RAM detection bug - although it seems to be vice versa as some "RAM-MB combination problem => FreeNAS crash => you see, even POST can't see your bloody RAM". But it's not like that :o).
The support guy sent me a RC BIOS, but I somehow hesitate to burn it onto the board, until there is a final release and may be some patches/updates to the drivers. For now, I conclude it like this:
1. X11 is ok with Crucial ECC, although the MB after a warm-reset plays crazy
2. FreeNAS crashes sometimes, I can imagine it could be as of my second pool, where I mix 2x WD REDs with 1x ST (it's just "another free space" for me to use the unused disks I had around - if it goes, it's ok to me, but it shouldn't bring down the server!)
3. The soon coming SM BIOS2 will fix the dreadful "No RAM installed" message/beeping, which is very unpleasant after a FreeNAS crash, but should be harmless in reality
Anyway, FreeNAS should not crash - but as I'm not sure what is causing this, I can't fill in a bug.
Hope this helps somebody,
Andrej
I'm running SM+Crucial since summer now and it keeps sometimes crashing - not often, but ugly enough. It just reboots with no log entries. After the automatically following reboot is triggered another bug, this time SM BIOS, telling you "No RAM modules installed". I thought first that the "No RAM installed" is the cause of the FreeNAS crash somehow - but it's not. All the full MemTests were ok.
After a emailing with the SM support, it seems that the current SM BIOS (2.17.1254, 2016) has a bug in RAM detection after a warm reboot. And this warm-reboot is called after FreeNAS 9.10 crashes. So it seems to be quite unrelated: the FreeNAS crash bug only triggers the SM BIOS RAM detection bug - although it seems to be vice versa as some "RAM-MB combination problem => FreeNAS crash => you see, even POST can't see your bloody RAM". But it's not like that :o).
The support guy sent me a RC BIOS, but I somehow hesitate to burn it onto the board, until there is a final release and may be some patches/updates to the drivers. For now, I conclude it like this:
1. X11 is ok with Crucial ECC, although the MB after a warm-reset plays crazy
2. FreeNAS crashes sometimes, I can imagine it could be as of my second pool, where I mix 2x WD REDs with 1x ST (it's just "another free space" for me to use the unused disks I had around - if it goes, it's ok to me, but it shouldn't bring down the server!)
3. The soon coming SM BIOS2 will fix the dreadful "No RAM installed" message/beeping, which is very unpleasant after a FreeNAS crash, but should be harmless in reality
Anyway, FreeNAS should not crash - but as I'm not sure what is causing this, I can't fill in a bug.
Hope this helps somebody,
Andrej