NAS Hardware Guide 2026: What to Look For by OS and Filesystem
· Last verified July 2026
Most hardware guides hand you a parts list and hope it fits your plans. The trouble is that the right parts depend almost entirely on the software you are going to run, because a ZFS box on TrueNAS asks for very different things than an Unraid array or a lightweight OpenMediaVault file server. This guide flips the usual order: you decide the operating system and filesystem first, then let each of them tell you what to look for in memory, in the disk controller, in the network card and in the case. Learn the criteria once and you can price any build with confidence, instead of copying a stranger's shopping cart and hoping it survives its first rebuild.
Pick the OS and filesystem first, then the parts follow
The single biggest fork in a NAS build is not the CPU or the case, it is the filesystem, because that choice decides how the machine uses memory, how it wants to see your disks, and how much room you have to grow. ZFS trades RAM and a little rigidity for end-to-end checksums that catch silent corruption, whereas Unraid's array trades raw speed for the freedom to mix drive sizes and add one disk at a time; ext4 or Btrfs on a plain Linux box sits somewhere in between. If that comparison is new to you, our ZFS vs ext4 vs Btrfs breakdown lays out what each one protects and what it costs, and the Unraid vs TrueNAS vs OpenMediaVault comparison maps those filesystems onto the operating systems people actually install.
Once you have named the OS, the hardware questions almost answer themselves, so the rest of this guide is organised the same way: what ZFS demands, what Unraid needs and skips, when a lighter system is the smarter call, and finally the criteria that apply no matter which route you take. Settle the software first and every later decision, from how much RAM to buy to whether you need an add-in disk controller, stops being guesswork.
What ZFS wants (TrueNAS and Proxmox)
ZFS is the reason people reach for "server" hardware, and it earns that reputation in three places: memory, the disk controller, and the PCIe lanes that feed both. Start with RAM, because ZFS borrows whatever free memory it can find and turns it into a read cache called the ARC, so more memory mostly buys you faster reads rather than headroom you will never touch. A long-standing rule of thumb suggests roughly 1 GB of RAM for every TB of pool, though in practice it is a loose guideline rather than a hard floor; 16 GB is a comfortable starting point for a home pool, and TrueNAS publishes its own hardware guidance if you want to cross-check before you buy.
The ECC question is where the internet gets loudest, so here is the honest version. OpenZFS itself describes ECC memory, which quietly corrects the single-bit flips that ordinary background radiation causes, as highly recommended rather than mandatory, and the widely repeated "a scrub without ECC will eat your pool" story is a myth. ECC is genuinely worth it on a build whose whole reason to exist is data integrity, because it closes the one gap ZFS checksums cannot cover, the moment data sits in RAM before it is written; on a casual media box it is a nice-to-have you can skip. We walk through the whole debate, and which platforms actually support it, in ECC RAM for NAS and ZFS.
The disk controller matters just as much, and this is where a lot of first builds go wrong. ZFS wants to see each drive directly, so OpenZFS advises against hardware RAID controllers and notes that SATA port multiplier support is inconsistent, which rules out both motherboard fake-RAID modes and the cheap port-splitter boards that promise eight drives from two ports. When you run past the four to six SATA ports a typical board offers, the reliable answer is a host bus adapter such as the Broadcom (LSI) 9300-8i, a PCIe x8 card flashed to IT mode that hands eight drives straight to ZFS. If the difference between an HBA and a RAID card is fuzzy, our hardware RAID vs software RAID guide explains why the pass-through approach is the one modern ZFS builds want. For a machine you will not sit next to, a proper server board with ECC support and IPMI, a baseboard controller that lets you power-cycle and reinstall the box remotely, turns a headless NAS from a chore into a set-and-forget appliance. The takeaway: budget for RAM, plan an HBA the moment you cross six drives, and prefer a board that supports ECC even if you populate it later.
The PCIe lane budget, where cheap boards quietly run out
PCIe lanes are the part nobody warns first-time builders about, and they are exactly where an ambitious ZFS build collides with a consumer motherboard. A lane is one of the CPU's limited fast connections to the rest of the system, and a mainstream desktop CPU only breaks out a couple dozen of them; the motherboard chipset adds a few more, but it funnels all of them through a single shared uplink, so they are not free capacity. The concept is worth understanding before you spend, and the PCI Express overview is a good primer if the term is new.
The problem is that a serious NAS asks for lanes from every direction at once. An eight-port HBA wants a full x8 slot, a 10GbE network card wants four to eight lanes of its own, and every NVMe SSD you add for a boot drive, an SLOG or a cache device quietly claims four more. Add those up on a budget board and you find the second x16 slot silently drops to x8 the moment the first is populated, or an M.2 slot disables a pair of SATA ports, and suddenly the build you sketched does not physically fit. This is the real reason ZFS builds drift toward workstation and server platforms, an Intel Xeon E or an AMD Ryzen with a workstation chipset, which simply expose more lanes so an HBA, a fast NIC and a couple of NVMe drives can coexist without fighting.
For the more technical crowd: some boards support PCIe bifurcation, which splits one physical x16 slot into four independent x4 links so a single slot can carry four NVMe drives on a passive adapter. It is a genuinely useful trick for squeezing more storage out of a lane-starved platform, but it only works if both the board and its firmware advertise it, so check the manual before you count on it. The plain takeaway for everyone else: if your wishlist includes an HBA plus 10GbE plus NVMe, add up the lanes on paper first, and step up to a platform that has them rather than discovering the shortfall after the parts arrive.
What Unraid wants, and what it lets you skip
Unraid is the friendly opposite of a ZFS build, and understanding one thing about how it reads data explains most of its relaxed hardware needs. Unlike a striped array, an Unraid array reads each file from a single drive rather than spinning up the whole set in parallel, which means you do not need matched disks, striping-class throughput or a fast disk controller to keep it fed. That single design choice is why mixed drive sizes are not just tolerated but expected, so the shelf of odd-capacity disks that traditional RAID would waste becomes a perfectly good Unraid array.
The one firm rule to remember when you shop is about parity: in Unraid the parity drive must be at least as large as your largest data drive, which the official storage documentation spells out and which our tool below enforces for you. In practice that means you buy your single biggest disk to be parity first, then fill the data slots with whatever mix of smaller drives you already own or can find cheaply. Because there is no ARC to feed, RAM needs are light: 8 GB is plenty for pure file serving, and you only climb toward 16 GB or more once you start stacking Docker containers and virtual machines. Two more conveniences round it out, since Unraid boots and licenses from a humble USB stick so the OS never costs you a drive bay, and an NVMe cache pool absorbs incoming writes at flash speed before a scheduled "mover" migrates them to the slower array overnight.
The takeaway is that Unraid lets you spend the money you would have poured into ECC, a big HBA and a lane-rich board on the drives themselves instead, so it is the natural pick for a media library that grows unpredictably one disk at a time.
When a lighter system or an appliance is the smarter call
Not every NAS needs to be a ZFS fortress, and pretending otherwise is how people overspend on their first build. OpenMediaVault is the lightweight middle ground: a Debian-based system that runs happily on a low-power mini-PC or even a Raspberry Pi, gives you ext4 or Btrfs with optional SnapRAID for parity, and leaves you in a normal Linux shell rather than a walled appliance. It is the sensible choice when you want simple, cheap and quiet, and when the checksums and RAM appetite of ZFS would be effort you never cash in.
Further down the effort curve are the sealed appliances from Synology, QNAP and Ugreen, and they exist for a real reason. When you weigh the parts, the assembly, the OS setup and the fact that a DIY box makes you your own warranty and support desk, a turnkey two-to-four-bay unit is often the smarter buy for a first NAS, and you trade flexibility for a machine that arrives working. Our Synology vs QNAP vs DIY comparison weighs those platforms head to head, and if you are still deciding between building and buying at all, the honest verdict lives in the DIY parts-list companion to this guide, linked in the recommendation below. The takeaway: match the ambition of the hardware to the ambition of the workload, because an appliance that fits is worth more than a DIY build that intimidates.
The criteria that apply to every build
Whichever OS you land on, a handful of decisions carry across every NAS, and getting them right matters more than chasing the last few percent of any single spec. These are the parts you live with longest and the ones most likely to bite later if you cut the wrong corner, so it helps to weigh them together rather than one at a time.
- Case and bays: pick the chassis for your planned drive count plus at least one spare bay, and favour a purpose-built NAS case with hot-swap trays and airflow over the drive cage rather than squeezing disks into a leftover tower. Sanity-check capacities against real models in our NAS drives database before you commit to a bay count.
- PSU headroom and quality: a rack of spinning drives draws a real surge at spin-up, so a quiet, efficient 80 Plus unit with headroom beats a bargain PSU that browns out a six-drive array, and pairing it with a UPS protects an in-flight write from a power cut, as covered in best UPS for NAS.
- Cooling and noise: drives last longest with steady front-to-back airflow, and a NAS that lives in a living room needs quiet fans and calmer drives, a trade we quantify in our NAS noise levels guide.
- CPU: file serving is light work, but if you plan to run Plex or Jellyfin, an Intel chip with Quick Sync hardware transcoding handles several streams while barely touching the processor, so an efficient N100 covers a light media server and you only step up to an i5 or Ryzen for many simultaneous transcodes or heavy virtualization.
- Network card: 2.5GbE is the sensible floor in 2026 because it saturates a couple of spinning drives and runs on the cabling you already have, while 10GbE only earns its price alongside NVMe or a wide array and a switch to match.
- Boot device: the OS belongs on its own small SATA or NVMe SSD (or a USB stick on Unraid), never on the pool it manages, and a cheap 128 to 256 GB drive is plenty.
The takeaway: bays, power, cooling and the network are the decisions you cannot easily undo once the machine is racked, so spend your attention there before you argue about drive brands.
Example hardware these criteria point to
This is deliberately not a prescriptive shopping list, it is a short set of parts the criteria above tend to land on, so treat them as anchors and price the rest of the build around your OS choice and drive count.
Recommendation
If data integrity is the whole point, build for ZFS on TrueNAS: a board that supports ECC (ideally a server board with IPMI), 16 GB or more of RAM, an HBA in IT mode once you pass six drives, and enough PCIe lanes that a 10GbE card and an NVMe device do not fight it. If you are pooling a pile of mismatched drives for a media library, go Unraid: a modest CPU, 8 to 16 GB of ordinary RAM, your largest disk as parity, an NVMe cache pool and a USB boot stick, with the money saved going straight into disks. And if you want simple, quiet and cheap, or you would rather not be your own support desk, run OpenMediaVault on a small machine or buy a prebuilt appliance outright; the best NAS is the one whose hardware matches how much of your weekend you actually want to spend on it.
Related articles
NAS Motherboard Guide: SATA Ports and PCIe Lanes Decoded
Buying a NAS in 2026: Ugreen, Synology, QNAP or DIY?
NAS Power Consumption: What Your NAS Actually Costs Per Year
HDD vs SSD in NAS: When Does Each Actually Pay Off?
NAS Cooling 2026: Drive Temperature Done Right
ZFS Hardware Requirements 2026: RAM, ECC, HBA and SLOG