Looking for some confirmation before I buy… the compatibility page lists only a pair of 16GB modules which may or may not be ECC, but the online store has both a 16GB AND a 32GB module that is ECC. So, two questions:
Best to open a ticket with QNAP (as the product specs say 16GB max), but that is a LOT of RAM you want to put into this low performance ARM box.
Yeah, specs from release say 16, but the online store says this 32G module is compatible, sooo… And yeah, that is a lot of memory, but I plan on starting on a ton of low cpu hobby projects I keep putting off, so lots of services running all at once, but minimal “thinking” required (outside scheduled ClamAV scans, which themselves take a stupid amount of time to complete already).
ClamAV would be the first thing to permanently switch off on a NAS, The clients will have an AV (and the files are supplied by clients to and from a NAS).
No need for this outdated non realtime ClamAV engine to drag your CPU down.
No need for this outdated non realtime ClamAV engine to drag your CPU down.
Defense in depth.
Well you do not have the NAS CPU cycles to spare, I’d say have an external client scan the shares then (as ClamAV also only scans shares and not the NAS system folders or OS partitions)
Look, if you have nothing constructive to say about whether nor not the chips I linked are compatible, bugger off. I asked a straightforward technical question, not whether or not I’m doing things the “right” way according to your preferences.
Cool your jets or I cool them for you
I told you to open a ticket … topic closed
Regarding this issue, our internal team confirmed it was an error in the online store listing. Please always refer to the official compatibility list.
We sincerely apologize for any inconvenience this has caused!