Slower RPM HDDs will generally be quieter than faster ones, and consumer drives will generally be quieter than enterprise drives at the cost of long term reliability and possibly write speed, but in general HDDs aren’t quiet, and no one specifically makes quiet HDDs.
Moving parts make noise. You’re more or less looking for something that doesn’t exist. Instead of looking for a quiet drive, look for ways to sound-isolate your drive.
I really like Seq. It supports tons of log types, including GELF, which means you can configure your docker hosts to send all container logs to Seq with just a couple lines in Docker’s daemon.json file.
Setup is pretty simple as a docker compose stack containing the Seq container and a container for ingesting each of the log types you plan to use.
If you wanted to try it out, I’d recommend setting up Seq with seq-input-gelf and seq-input-syslog, and setting up nginx to send access and error logs to syslog as detailed here.
I’d go option 2 and use some of the savings to max out the ram. I also like the extra PCIe slot on this one.
Option 3 is easily the worst deal in my opinion.
Long SMART test, dd if=/dev/urandom of=/dev/[new disk], long smart test. That’s pretty much it.
My first switch was a 4 or 5 port gigabit model that looked exactly like this back in 2005. Also my last Netgear device.
The only ports you need forwarded on your router are 80 and 443 to the local ip address NPM is hosted at, don’t forward ports to your services from the router. Your reverse proxy forwards traffic for each subdomain to the corresponding ip and port of your services.
One drawback of using replication instead of shared storage is that all data written since the last replication job will be lost during failover. Not ideal for mission critical services or anything that relies on a database. Otherwise it’s a good solution.
Have you tried to ssh into it?