- Joined
- Feb 15, 2014
- Messages
- 20,194
Same root cause.From the watchdog timer issue, perhaps. I think they're still dropping dead from the failure of the voltage sensors though.
Same root cause.From the watchdog timer issue, perhaps. I think they're still dropping dead from the failure of the voltage sensors though.
Hm, just one third of them? Well, that's not a widespread issue. Might even be fixable with a mixture of resets and reflashes. Worked for me on my X10SLM+-F.Are you sure. The replacement board they gave me they reported was brand new from the factory and 1/3 of the voltage sensors don't work, or at least they don't report in IPMI server health.
Although fiber channel and infiniband do work (I believe) they are very far from the mainstream.
ATX
Larger motherboards are frequently needed due to memory requirements that cannot be met in a microATX form factor, either due to platform limitations (LGA 115x boards) or cost (Xeon-D). Compute is rarely the driving force behind the move to Xeon E5 platforms.
I'll take a look at it, don't remember what I recommended, exactly. The original version was indeed rushed.1) Really need to mention the E3-1230v3/4/5 either as E3-1230/1240 or instead of or as well as the 1240. For most people the 1230 is the sweet spot if you want quad core with hyperthreading. 1240 is circa 10% more expensive, for 4% more performance.
It's probably best to compare them to i5s/i7s, since that's what people who do not love their data use for servers and transcoding and stuff. :p) It might be worth while describing the 1220 as roughy equivalent to two Pentiums. and the 1230 as roughly equivalent to 2 i3s. Because its roughly true ;)
I might want to make it a bit clearer. I'll have to look at it.3) You make a jump here from ATX -> Xeon E5. Might want to preface with something about ATX normally means an E5 2011/2011-3 platform. And then explain why its necessary/not necessary etc.
I'm not too worried about strictly following section titles. As for expanded sections, that's probably something I'd like to avoid...4) "Pressing Hardware into service". This is under the "Advice what not to do" section. Its actually advice on what to do... Perhaps a slightly expanded section by itself, perhaps a "now that I've got the hardware..." ;)
...because this would make it take up even more of my time. If I can get help, I will definitely consider making a more comprehensive guide, sort of like the pfSense book without the absurd price model. It is not something I can do on my own, though. Hell, if iX thinks that they want something like that, I'd be glad to help if I could share the load with someone else.I know its a hardware recommendation guide, but it reads almost like a "everything you needed to know to install freenas" correctly.
It is? I had no idea.The hardware recommendation guide is locked behind the requirement of registration.
In my opinion it would be better to also offer it for those, that are not registered on the forum.
... no one should use atom cxxx anymore
Clearly you didn't look hard enough.Hi, I was looking in the forum but couldn't find anything about it, but no one should use atom cxxx anymore: https://www.theregister.co.uk/2017/02/07/intel_atom_failures_go_back_18_months/
Ok, the issue has been examined and guests should now be able to download the files.The hardware recommendation guide is locked behind the requirement of registration.
In my opinion it would be better to also offer it for those, that are not registered on the forum.
I disagree, a 8+ core CPU is great for VM workflows. No need to increase your power consumption by adding another. Now if you want 10vms running then maybe you need something bigger but at that point you should have a server just for vms.Just a small note. The guide tells us: " Most FreeNAS servers would not benefit from a second CPU." The first word here seems to be misplaced. If you want to use FreeNAS for media server of Docker container carrier, multiple CPUs will bring you great benefit in performance. Maybe this statement needs to be expanded into 2 small paragraphs for 2 different usage patterns (one is simple NAS with minimal additional functionality, and second is i.e. Docker container carrier or host system for multiple VMs).