Furthermore, your post only has shown how to verify that ECC is recognised through SSH/shell, and you have mentioned in your post that you're not doing the lengthy memtest for the RAM verification purposes at that time - I think that you could quickly check that whole RAM is actually usable/addressable by simply deploying VMs with total RAM assignment big enough to cover nearly 100% RAM as reported in the appliance control panel.
Given the example memory module you tested/used is a 32GB SO-DIMM and the device comes with 2 SO-DIMM slots, it stands to reason one could use 64GB ECC in total. However, as Qnap states that ECC is supported, and possibly there are some people out there who actually equipped/expanded/upgraded/replaced the manufacturer's SO-DIMMs with some ECC memory without issues as the proper way to use a file "server", I'd love to hear which specific memory SKUs/products have actually been successful in the long run. This is further visible since those new Qnap devices, as per information received from Qnap support are pretty finicky about memory, even without ECC taken into account. Furthermore, since both manufacturer produced base and high spec SKUs utilise non-ECC RAM solely, apparently even Qnap support does little to promote ECC memory in their little home/SMB desktop Ryzen boxes (h686 that uses full size DIMMs is possibly the cheapest officially with ECC).
However, everywhere I ask, whenever a retailer performs memory upgrade prior to selling the boxes to you or as an extra service, it seems non-ECC UDIMMs are in use, only non-ECC. The TS-X73A lines (and h973ax) of QNAP products all support ECC memory as per manufacturer product spec sheets and as per Ryzen V1500B spec sheets.
0 kommentar(er)
