Unraid Hardware Requirements: CPU, RAM, Storage & Network
Quick Answer
Unraid is deliberately hardware-agnostic. For a storage-focused server, use a modern 64-bit CPU, enough RAM for the services you plan to run, direct access to SATA/NVMe drives, and at least Gigabit Ethernet. For a new DIY build, 8–16 GB RAM and 2.5GbE are practical starting points; use 16–32 GB or more when Docker, VMs, GPU passthrough or heavier application workloads are part of the plan.
Unraid’s official setup still starts with compatible boot media, while current Unraid 7.3 documentation also supports onboarding to selected internal boot devices.
Key Takeaways
· Unraid itself does not require a high-end CPU; applications and VMs determine CPU size.
· Use HBA/AHCI-style direct disk access rather than hardware RAID hiding individual drives.
· 8–16 GB RAM is practical for storage and light apps; VMs usually justify 16 GB or more.
· SSD/NVMe storage is valuable for application data and VM disks.
· 2.5GbE is a strong default; 10GbE is useful for fast arrays and demanding clients.
CPU: Size It for Docker, VMs and Transcoding
A storage-only Unraid system can run on modest modern hardware. The CPU becomes important when the server also handles Plex/Jellyfin transcoding, multiple Docker containers, databases, VMs or GPU passthrough.
For a simple NAS, prioritize low power and platform stability. For a home-lab server, add cores and clock speed according to the applications you want to run. If VMs are part of the plan, verify hardware virtualization support. If you need PCIe device passthrough, IOMMU support (Intel VT-d or AMD-Vi) matters as well.
Unraid’s current VM documentation lists a 64-bit 4-core 2.4 GHz+ CPU as a minimum for VM use and recommends more capable 8+ core hardware for heavier VM and passthrough scenarios. See the official VM system preparation guide.
RAM: There Is No Single Number for Every Unraid Server
Unraid’s base storage services are lightweight compared with a full VM host, so RAM should follow the services installed on top.
A useful planning range is:
|
Workload |
Practical RAM |
|
File storage and parity array |
8 GB |
|
Storage + several Docker apps |
8–16 GB |
|
Media server + databases + apps |
16 GB |
|
One or more VMs |
16–32 GB+ |
|
GPU passthrough / heavier lab |
32–64 GB+ |
The VM documentation lists 8 GB as the minimum when running VMs and recommends 16 GB or more. If the server is only storing files, you may not need the same amount.
Boot Device: Follow Current Unraid Guidance
Unraid historically boots from a USB flash device tied to a unique GUID. The official getting-started guide calls for a high-quality named-brand USB device with a unique GUID and at least 4 GB capacity. Current Unraid 7.3 documentation also describes an onboarding flow that can move supported systems to internal boot storage.
Whichever method you use, the boot device stores configuration information, so back it up and avoid treating it like ordinary disposable media.
Storage Controllers: Expose Individual Drives
Unraid is designed to manage disks itself. Configure onboard SATA controllers in AHCI mode and add-on controllers in HBA/JBOD-style mode when possible. The current deployment checklist explicitly recommends HBA rather than RAID mode.
This matters because the operating system needs to see individual disks, serial numbers and health information. Hardware RAID can hide those details and complicate recovery.
The CWWK NAS hardware collection includes boards with onboard SATA, M.2 and PCIe expansion for different Unraid drive counts.
SSD and NVMe Are Best Used for Fast Application Data
HDDs remain efficient for bulk capacity, but Docker application data, databases and VM disks benefit from SSD or NVMe latency. A mixed Unraid server often uses HDDs for the main array and SSD/NVMe for application pools or high-performance data.
Do not assume every M.2 connector can run at maximum speed simultaneously. Check PCIe lane sharing on the motherboard, especially if you also plan to install a faster NIC or HBA.
Networking: Start at 2.5GbE for a New Build
Gigabit Ethernet remains functional, but 2.5GbE is now a sensible baseline for a new NAS if the switch and clients support it. A raw 2.5GbE link can carry about 312.5 MB/s before overhead, which is enough for many HDD arrays.
Use 10GbE when you have multiple SSDs/NVMe, several clients, large media/project files or VM storage. Unraid’s VM guidance also lists 2.5/10GbE as the preferred range for demanding VM workloads.
Practical Unraid Build Profiles
|
Use Case |
CPU |
RAM |
Storage |
Network |
|
Backup / file server |
Low-power 64-bit CPU |
8 GB |
HDD array |
1/2.5GbE |
|
Home server + Docker |
4+ capable cores |
16 GB |
HDD + SSD/NVMe app pool |
2.5GbE |
|
Media + VMs |
6–8+ capable cores |
32 GB |
HDD + NVMe |
2.5/10GbE |
|
Heavy home lab |
8+ cores, IOMMU |
32–64 GB+ |
NVMe VM pools + capacity storage |
10GbE |
FAQ
Does Unraid need ECC RAM?
No. ECC can be useful for a long-running storage server, but it is a platform choice rather than an Unraid requirement.
Does Unraid require a USB boot drive?
USB remains a supported and common boot method. Current 7.3 documentation also supports an onboarding path to selected internal boot devices; follow the documentation for the version you install.
Can I use a RAID controller with Unraid?
Prefer HBA/JBOD or AHCI-style direct disk access. Hardware RAID that hides individual drives works against Unraid’s normal disk-management model.
Is 2.5GbE enough for Unraid?
Yes for many HDD-based home servers. Use 10GbE when the storage pool or multiple clients can exceed 2.5GbE.

