I subscribe to the philosophy that each server should handle one thing. I’ve got a NAS that stores all data for all other servers other than boot drives. I’m using only spinning rust for data, so the network speed is never the bottleneck for my system. My NAS is a 24 bay chassis with the LSI card in IT mode. I got an LSI card that is powered from the PCIe port itself, and power usage for the card itself seems negligible, but spinning 24 drives takes a decent bit of power. I’ve got 20 drives in it now and it’s pretty loud, but substantially quieter than the dell r720 it replaced. It’s in my basement so it doesn’t bother me, but if sound is an issue, and you don’t need a ton of space, definitely go with SSDs. I’ve also got a media server that handles all media streaming (movies/TV/audiobooks/music/ebooks/comics/manga/roms). It reads/writes it’s data to the NAS. I’ve got another server running my personal cloud (nextcloud, password manager, testing new SH services). Again, the nextcloud data is on the NAS. Both servers store backups to the NAS, as well as a second local drive. I’ve also got a handful of raspberry pis running the smart house stuff, and one running the Ubiquiti Controller. All are running the PoE hat with the m.2 port on them for stable boot drives, and store their backups on the NAS. I’ve kind of stopped running proxmox + virtualization when I switched off of the r720, as I find that running Debian on bare metal with btrfs backups is simpler for me, and I run almost all of my services in Docker. I’ve had a motherboard go out on my media server, and was able to swap the motherboard and get everything back up and running in a little under 2 hours. Longest part was the motherboard swap itself.