The storage question trips up almost every first home server build, because the honest answer is that you want both kinds of drive doing different jobs. The right home server drive setup pairs a fast SSD or NVMe for the operating system, containers and databases with larger spinning hard drives for bulk media and backups. Mixing them lets you buy speed where it matters and cheap capacity where it does not, instead of overpaying for one or crippling the other.

Quick Answer

For a self-hosting home server, put the OS, Docker volumes and databases on an SSD or NVMe drive, and use HDDs for media and backups. SSDs handle hundreds of thousands of random operations per second where spinning drives manage around 150, while HDDs deliver cheap capacity, so the split gives you a fast, responsive system at a sane cost.

Why you mix drive types

A home server has two very different storage workloads. The operating system, your containers and any databases hammer the disk with small, random reads and writes. Media files, photo libraries and backups are large, sequential, and rarely touched. Those workloads want opposite things.

SSDs crush random I/O. An NVMe drive can handle hundreds of thousands of random operations per second, while a hard drive manages roughly 150. That gap is why a server running its OS and Docker stack from a hard drive feels sluggish, while the same setup on an SSD feels instant. But SSDs cost several times more per terabyte, which is exactly the wrong tool for storing terabytes of media you stream occasionally.

The SSD layer: OS, containers and databases

NVMe or SATA?

NVMe is several times faster than a SATA SSD for random work, and the price difference between the two has narrowed to almost nothing at smaller capacities. For a boot and application drive, NVMe is the sensible default if your board has a slot for it.

That said, be realistic about where the speed shows up. NVMe's advantage is real for the OS, databases and container activity. It does not help file serving over a typical home network, because a 1 or 2.5 gigabit link cannot move data fast enough to stretch even a SATA SSD's legs. Spend the NVMe budget on the drive that actually does random work.

Sizing the boot and app drive

A 500GB to 1TB SSD is plenty for the operating system, your Docker images and volumes, and several databases, with room for a few virtual machines. Reliable TLC drives have far more write endurance than a home server will ever use, so you do not need an enterprise-grade part to start. You can compare suitable small-form-factor machines and drives in the mini PC and home server range at Evetech.

The HDD layer: bulk media and backups

For the large, sequential, rarely-changed data, hard drives win on cost and they win clearly. Once your storage needs pass roughly 8TB, HDDs become the obvious choice because the price per terabyte is a fraction of flash. A pair of large drives gives you a media library plus a backup target without the cost of an all-flash array.

Watch out for SMR

When you buy hard drives for a server, choose CMR (conventional magnetic recording) rather than SMR (shingled). SMR overlaps tracks to cram in capacity cheaply, but it badly hurts predictable performance during rewrites and especially during RAID rebuilds, which is precisely the situation a server eventually hits. CMR drives are the safer foundation for any setup where data integrity and rebuilds matter.

NAS-rated drives for always-on use

Beyond CMR versus SMR, consider whether the drive is rated for always-on operation. Standard desktop drives are not designed to spin 24/7, and the mechanical stress shows up in failure rates over time. NAS-rated drives from the major manufacturers are built for continuous duty and are the right choice for any server that never sleeps. They cost a little more than desktop equivalents but last considerably longer in a server context, making the premium worthwhile over a multi-year run.

Software stack and what it asks of the drives

Which self-hosting software you run shapes your storage choices. Proxmox VE, which is the most common open-source hypervisor for home lab builds, boots and runs its OS comfortably from a 500GB NVMe, with an optional ZFS mirror across two small NVMe drives if you want boot redundancy. Attaching bulk SATA HDDs as a separate storage pool gives Proxmox virtual machines dedicated space without touching the OS drive. TrueNAS SCALE takes a different angle: it uses all drives in a pool and is fussiest about drive quality, making CMR drives even more important than on Proxmox. Either way, mixing a fast NVMe tier with a large HDD tier is the approach most home lab guides now recommend, as it stops the OS from competing with media transfers for the same drive heads.

A sensible starter layout

A clean first build looks like this: one NVMe or SATA SSD of 500GB to 1TB for the OS, containers and databases, plus two CMR hard drives for media and backups, sized to your library with headroom to grow. Keep at least one copy of anything irreplaceable on a separate drive, because a server is not a backup until the data exists in two places.

This split scales gracefully. Add more spinning capacity as your library grows, and only move to all-flash bulk storage if you genuinely need silent, low-power, high-speed access to everything. Many local self-hosters build exactly this kind of machine from the best-selling PCs and components at Evetech and expand the HDD tier over time.

Frequently Asked Questions

Can I just use one big SSD for everything?

You can, but it is expensive once you store real amounts of media. An all-flash server is fast and silent, yet you pay several times more per terabyte than a hybrid setup that uses HDDs for bulk data.

Does NVMe make my file server faster?

Only for the OS, databases and container work. File transfers over a normal home network are limited by the network, not the drive, so NVMe gives no real-world speed gain there over a SATA SSD.

What is the problem with SMR hard drives?

SMR drives overlap data tracks to lower cost, which slows sustained rewrites and can severely degrade RAID rebuilds. For a server, choose CMR drives so performance stays predictable when it matters most.

How much SSD space do I need for the OS and Docker?

A 500GB to 1TB SSD comfortably holds the operating system, container images and volumes, and several databases with room for virtual machines. Most home servers never fill it.

Do I still need backups if I run RAID?

Yes. RAID protects against a drive failing, not against deletion, corruption or theft. Keep a separate backup copy of anything you cannot afford to lose, ideally on a different drive or location.

Planning your first self-hosting box? Build it around a fast SSD for the OS and HDDs for bulk storage, and source the hardware from the mini PC and component range at Evetech so every drive lands in the right job from day one.