I would like to point people to the Odroid H4 series of boards. N97 or N355, 2*2.5GbE, 4*SATA, 2 W in idle. Also has extension boards to turn it into a router for example.
The developer hardkernel also publishes all relevant info such as board schematics.
And the best feature is they have in-band ECC, which can correct one-bit and detect two-bit errors. No other Alder Lake-N or Twin Lake SBC exposes this feature in UEFI.
There is the ASUS NUC 13 Rugged, which also exposes the in-band ECC, but it is both much more expensive and much slower (it uses either a 2-core or a 4-core Atom CPU, while ODROID uses either a 4-core or an 8-core CPU of the same Gracemont-based series).
Can you give a reference for ECC? I can not find anything about ECC support on the Odroid site.
The version using the 4-core CPU Intel N97, which is specified by Intel as an embedded CPU, certainly has in-band ECC, which was tested by some reviewers of this SBC.
I do not know whether the 8-core version (H4 Ultra) also enables in-band ECC, as for that CPU Intel does not specify embedded uses, so they may disable the ECC support in the factory.
See e.g.:
https://www.cnx-software.com/2024/05/26/odroid-h4-plus-revie...
However, looking right now at:
https://forum.odroid.com/viewtopic.php?f=171&t=48377
I see that someone has enabled successfully in-band ECC on the 8-core ODROID H4 Ultra and has run benchmarks with ECC disabled/enabled. Therefore it appears that in-band ECC support exists on all models.
The results of benchmarks with in-band ECC disabled/enabled may be not representative for real workloads. In-band ECC relies on caching the ECC bits in a dedicated ECC cache, in order to avoid excessive memory accesses. The effectiveness of the ECC cache can be very different for the benchmark and for the real workload, leading to misleading results. Usually for the real workload it is likely that the cache hit-rate will be higher, so the performance drop with in-band ECC enabled will be less conspicuous.
I can confirm that the Odroid H4 Plus also supports in-band ECC. If I remember right, Memtest86 showed different stats when I ran it with in-band ECC enabled/disabled though I didn't have a good way to test that an error was actually corrected.
Some systems allow forcing an ECC error, but assuming that's not available, if you can adjust memory voltages or timings, you can usually encourage errors that way and confirm memtest detects ECC corrections.
All CPUs with ECC support allow the forcing of ECC errors, but unfortunately in recent years the CPU vendors usually do not document how.
Only when they expose this feature in Linux EDAC drivers it becomes possible to do this. In the past Intel had maintained well its Linux EDAC drivers, but AMD had frequently great delays between the launch of a CPU and the update of the drivers. After the many lay-offs at Intel, it is unknown whether in the future their Linux support will remain as good as in the past.
I am building a NAS using the Odroid H4+ and a 3d printable case design. I selected the Odroid board for the in-band ECC and low power consumption: https://www.printables.com/model/1257966-odroid-h4-nas
Yep, I've had mine running for over a year now without issue. It idles at 34w with all 4 drives running. I ended up making a custom "case" for it: https://github.com/cbsmith402/storage-loaf
I also have an older Odroid HC4, it's been years it is running smoothly and not only I cannot use 1000$ for a NAS as the current post implied but the power consumption seems crazy to me for a mere disk-over-network usage (using a 500W power supply).
I like the extensive benchmark from hardkernel, the only issue is that any ARM-based product is very tricky to boot and the only savior is armbian.
> the power consumption seems crazy to me for a mere disk-over-network usage (using a 500W power supply).
The rated power supply spec is the maximum it can provide, not the actual consumption of the device.
I've had an H3 for a few years and it runs amazing. Very low power usage, small footprint and great stability. I run it with an M.2 ssd for power considerations.
Before that I had a full size NAS with an efficient Fujitsi motherboard, pico-psu, 12V adaptor and spinning HDD's. That required so much extra work for so little power efficiency gains vs the Odroid.