Building Your Own NAS Drive Server: A Comprehensive Guide

Building a home storage server, also known as a Nas Drive Server, can seem like a daunting task. However, with the right components and a clear guide, you can create a powerful and customizable system tailored to your specific needs. This article details the journey of building a 32 TB home nas drive server using open-source software, costing approximately $1,263. This price point is comparable to pre-built off-the-shelf solutions, but offers significantly more power and flexibility.

This guide will walk you through the entire process, from selecting parts and understanding key concepts like network-attached storage (NAS) and ZFS, to avoiding common pitfalls and optimizing your build. Whether you’re a seasoned tech enthusiast or just starting your homelab journey, this comprehensive walkthrough will provide valuable insights into creating your own nas drive server.


All components for the DIY NAS drive server project before assembly.


The completed DIY NAS drive server, ready for operation.

Understanding the Basics: Why a NAS Drive Server?

What is a NAS Drive Server?

NAS stands for Network-Attached Storage. Essentially, a nas drive server is a dedicated computer designed specifically for storing and sharing data across a network. Unlike direct-attached storage, a NAS is accessible to multiple devices on your network, making it ideal for centralizing files, backups, and media.

Benefits of a Dedicated NAS Drive Server

Why choose a dedicated nas drive server over simply using local storage on each computer? There are several compelling reasons:

  • Data Centralization: A NAS consolidates all your important data in one location, simplifying backup and management.
  • Data Sharing: Easily share files between multiple computers, devices, and users on your network.
  • Accessibility: Access your data from anywhere on your network, and even remotely with proper configuration.
  • Data Migration Simplified: Upgrading your primary workstation or laptop becomes less of a hassle as your data remains on the NAS, eliminating tedious data migrations.
  • Scalability: NAS systems are designed to be expandable, allowing you to increase storage capacity as your needs grow.
  • Customization: Building your own nas drive server gives you complete control over hardware and software, allowing for tailored performance and features.

For individuals and households with growing digital footprints, a nas drive server becomes increasingly valuable. From personal documents and photos to extensive media libraries and project files, a NAS provides a robust and accessible storage solution.

Homelab Context: Experimentation and Learning

The term “homelab” refers to a home-based environment for experimenting with IT hardware and software, mirroring setups found in offices or data centers. Building a nas drive server is a popular homelab project, offering a practical way to learn about server administration, networking, and data management.

Why Build a DIY NAS Drive Server?

While off-the-shelf NAS solutions from brands like Synology and QNAP are readily available, building your own nas drive server offers distinct advantages, especially for those seeking customization and deeper technical understanding.

If you are new to homelabs or PC building, starting with a pre-built NAS is advisable. Devices like the Synology DS412+ provide a user-friendly introduction to NAS concepts.


The Synology DS412+, a reliable pre-built NAS drive server, served as a starting point for exploring network storage.

However, pre-built NAS servers can have limitations:

  • Vendor Lock-in: Proprietary operating systems and storage formats can make data recovery and hardware upgrades challenging.
  • Limited Customization: Hardware and software options are restricted to the vendor’s offerings.
  • Repair Restrictions: User repairability is often limited, requiring full replacement even for minor component failures post-warranty.

Switching to open-source solutions like TrueNAS addresses these concerns. TrueNAS, based on FreeBSD and the ZFS file system, offers an open and powerful platform for building a nas drive server.

TrueNAS and ZFS: Open Source Power for Your NAS Drive Server

TrueNAS (formerly FreeNAS) is a leading open-source operating system specifically designed for storage servers. Its longevity and robust features make it a reliable choice for a DIY nas drive server.

At the heart of TrueNAS is ZFS, a powerful file system engineered for data integrity and scalability in storage servers. Unlike traditional file systems, ZFS manages the entire storage stack, from file-level logic down to disk I/O. This comprehensive control enables advanced features:

  • Storage Pooling: Aggregate multiple physical disks into a single, manageable file system.
  • Data Corruption Protection: Automatic detection and repair of data corruption, ensuring data integrity.
  • Snapshots: Create point-in-time snapshots for easy data recovery and versioning, similar to system restore points.
  • Data Compression and Encryption: Optional built-in compression and encryption to optimize storage and enhance security.

Planning Your NAS Drive Server Storage

Estimating Storage Needs for Your NAS Drive Server

Accurate storage planning is crucial for building an effective nas drive server. Consider your current storage usage and future growth. A good strategy is to start with sufficient capacity for your immediate needs, with room for expansion.

For this build, the initial target was 20 TB of usable storage, expandable to 30 TB or more as needed.

While ZFS initially required creating a new pool to add drives, advancements are being made to allow adding disks to existing pools in future updates.

Update (2025-01-25): ZFS now supports adding drives to existing pools in the latest versions, though testing in TrueNAS is still recommended.

Choosing Disk Size and Quantity for Your NAS Drive Server

When planning your nas drive server, a key decision is whether to use many smaller disks or fewer larger disks to achieve your desired capacity.

ZFS utilizes disk pools and redundancy to protect against drive failures. The efficiency of storage utilization depends on the number of disks in the pool. For instance, two 10 TB drives in a mirrored ZFS pool only yield 10 TB of usable space, while five 4 TB drives can provide 14 TB of usable space from the same total raw capacity.

Smaller drives often have a lower cost per TB, but using more drives increases operational costs like electricity consumption. Opting for fewer, larger drives can minimize the physical footprint and potentially reduce power consumption, although larger drives might have a higher upfront cost.

RAIDZ Configuration: Balancing Redundancy and Capacity in your NAS Drive Server

ZFS offers different RAIDZ levels (RAIDZ1, RAIDZ2, RAIDZ3) for data redundancy, each providing varying levels of protection against drive failures.

  • RAIDZ1: Tolerates one drive failure.
  • RAIDZ2: Tolerates two simultaneous drive failures.
  • RAIDZ3: Tolerates three simultaneous drive failures.

Increased redundancy comes at the cost of usable storage capacity. With five 4 TB drives, the usable space varies significantly across RAIDZ levels:

ZFS Type Usable Storage % of Total Capacity
RAIDZ1 15.4 TB 77.2%
RAIDZ2 11.4 TB 57.2%
RAIDZ3 7.7 TB 38.6%

RAIDZ1 was chosen for this build, offering a balance of redundancy and usable space for a smaller disk array.

It’s crucial to remember that RAID is not a backup solution. While ZFS RAID protects against drive failure, it doesn’t safeguard against data loss from accidental deletion, malware, or other disasters. A robust backup strategy, such as using restic for encrypted cloud backups, is essential.

ZFS RAID primarily aims to maintain data availability in case of a drive failure, minimizing downtime and data recovery efforts. For larger disk arrays, considering RAIDZ2 or RAIDZ3 for enhanced fault tolerance is recommended.

Mitigating Concurrent Disk Failures in Your NAS Drive Server

While the probability of simultaneous disk failures might seem low initially, drives in close proximity, from the same batch, and under similar workloads are not statistically independent. If one drive fails, the risk for its neighbors increases. Furthermore, the stress of rebuilding a ZFS pool after a drive failure can put additional strain on surviving drives, potentially triggering further failures.

To minimize the risk of concurrent failures in this nas drive server build, drives from different manufacturers and models were chosen and purchased from separate vendors to reduce the likelihood of drives from the same manufacturing batch. While the impact of this strategy is hard to quantify, it adds a layer of precaution without significant cost increase.


Purchasing drives of the same model from different vendors can help mitigate risks associated with manufacturing batches.

Selecting Components for Your NAS Drive Server

Motherboard Choice for a NAS Drive Server

The motherboard forms the foundation of your nas drive server. Form factor is a primary consideration. A compact mini-ITX motherboard was chosen for this build, aiming for a smaller footprint similar to pre-built NAS units.

The ASUS Prime A320I-K was selected for its:

  • SATA Ports: Four SATA ports to directly connect up to four drives.
  • Integrated Graphics: Supports Radeon graphics, eliminating the need for a dedicated graphics card.
  • Affordability: Reasonable price point.


The ASUS Prime A320I-K motherboard, chosen for its mini-ITX form factor and integrated graphics capabilities.

Important Note: The ASUS Prime A320I-K motherboard choice later presented compatibility issues, highlighting the importance of BIOS compatibility with the chosen CPU. More details are discussed later in this article.

Alternatives like the B450 chipset motherboards offer similar features but often at a higher price, with benefits like improved overclocking capabilities, which are generally not necessary for a nas drive server.

CPU Selection for a NAS Drive Server

CPU requirements for a nas drive server, especially running TrueNAS and ZFS, are generally modest. ZFS itself is not heavily CPU-bound in typical NAS workloads. Initial testing with a basic TrueNAS installation on a low-power Dell OptiPlex confirmed low CPU utilization.

The primary CPU criterion for this build was integrated Radeon graphics support to leverage the motherboard’s HDMI output and avoid a discrete GPU.


The AMD Athlon 3000G CPU, selected for its integrated graphics and cost-effectiveness.

The AMD Athlon 3000G was chosen, offering a balance of cost-effectiveness and integrated Radeon graphics. Its CPU benchmark performance is adequate for NAS duties.

Case Selection for a NAS Drive Server

Case selection for a nas drive server balances aesthetics, functionality, and drive capacity. Fractal Design cases are known for their quality and thoughtful design.

The Fractal Design Node 304 Black mini-ITX case was chosen for its compact cube-like design and capacity to house up to six drives.


The Fractal Design Node 304 Black case, a compact mini-ITX option capable of holding six drives.

Data Drives for Your NAS Drive Server

For data storage in a nas drive server, hard disk drive (HDD) selection is critical. Starting with four 8 TB drives was planned for this build, aiming for approximately 22.5 TB of usable space in RAIDZ1. The six-bay case allows for future expansion.

While faster drives (10k RPM) exist, 7200 RPM drives are sufficient for most NAS applications as network bandwidth often becomes the bottleneck. Higher RPM drives also increase noise and power consumption without significant performance gains in a typical NAS setup.

Reliability is paramount. While Backblaze drive stats are insightful, focusing solely on the lowest failure rates can lead to disproportionately expensive drive choices. Balancing cost and reliability is key.

Avoid Shingled Magnetic Recording (SMR) drives when building a ZFS-based nas drive server. SMR drives are known to perform poorly with ZFS. Choose drives with Conventional Magnetic Recording (CMR), often labeled as such, for optimal ZFS compatibility.

Toshiba N300 and Seagate IronWolf 8 TB drives were selected, both receiving positive reviews in TrueNAS communities. These drives offered a good balance of price and performance for NAS applications.


The Toshiba N300 8TB HDD, a reliable option for NAS drive servers.


The Seagate IronWolf 8TB HDD, another popular choice for NAS drive servers.

OS Drive for Your NAS Drive Server

TrueNAS requires a dedicated OS drive. However, the OS drive workload is minimal after initial boot. A small, inexpensive solid-state drive (SSD) is sufficient.


The Kingston A400 M.2 SSD, a cost-effective OS drive for NAS drive servers.

A Kingston A400 120 GB M.2 SSD was chosen for its low cost and compact M.2 form factor, simplifying installation and cable management.

Memory (RAM) for Your NAS Drive Server

RAM requirements for ZFS-based nas drive servers are often debated. The “1GB of RAM per 1TB of storage” rule is considered a myth by ZFS developers for basic NAS usage. While data deduplication and other advanced ZFS features can be RAM-intensive, basic file serving and RAID functionality operate efficiently with moderate RAM.

Choosing RAM involved:

  1. Compatibility Check: Verifying RAM compatibility with the ASUS A320I-K motherboard.
  2. Capacity Selection: Opting for 32 GB or 64 GB kits using two DIMMs for potential future expansion.
  3. Brand Preference: Selecting reputable brands (Corsair, Crucial, etc.).
  4. Price Consideration: Filtering for options within a reasonable budget.

The CORSAIR Vengeance LPX 32GB (2x16GB) DDR4 kit was selected, offering a good balance of capacity, compatibility, and price.


The CORSAIR Vengeance LPX 32GB RAM kit, providing ample memory for the NAS drive server build.

Power Supply Unit (PSU) for Your NAS Drive Server

Power supply selection involves ensuring sufficient wattage and efficiency. PCPartPicker estimated a system power requirement of only 218W. While a 300-400W PSU would suffice, semi-modular options were limited in that range.

The EVGA 110-BQ-0500-K1 500W semi-modular PSU was chosen. While potentially over-capacity, it offered semi-modularity for cleaner cable management.


The EVGA 110-BQ-0500-K1 500W PSU, providing reliable power with semi-modular cabling.

90-Degree SATA Cables for NAS Drive Server Assembly

90-degree SATA cables are often necessary in compact builds to manage tight spaces between components.


90-degree SATA cables are essential for tight spaces in mini-ITX NAS drive server builds.

Standard SATA cables were found to be too bulky in the mini-ITX case, leading to the adoption of slim 90-degree SATA cables to ensure proper connections.


90-degree SATA cables provide the necessary clearance in constrained spaces.

Components Intentionally Omitted from the NAS Drive Server Build

Certain components were deliberately excluded from this initial build to optimize for cost, space, or complexity, but could be considered for future upgrades.

Graphics Card (GPU)

A dedicated graphics card was omitted, leveraging the integrated Radeon graphics of the chosen CPU and motherboard to conserve space, power, and cost.

Host Bus Adapter (HBA)

A Host Bus Adapter (HBA) expands the number of drive connections beyond the motherboard’s native SATA ports. While useful for larger drive arrays, an HBA was initially skipped to simplify the build and utilize the motherboard’s four SATA ports. The PCI slot was left available for future HBA addition if needed.

ECC RAM

Error-Correcting Code (ECC) RAM is often discussed for data integrity in servers. However, for a home nas drive server, standard consumer-grade RAM was deemed sufficient. While ECC RAM is beneficial for critical enterprise environments, its necessity for home use is debatable.

SLOG Disk

A Separate Intent Log (SLOG) SSD can improve write performance in ZFS by providing a fast write cache. However, due to port and bay limitations in this build, a SLOG disk was initially omitted to prioritize drive capacity.

NAS Drive Server Parts List and Costs

Category Component Price Paid
CPU AMD Athlon 3000G $105.13
Motherboard ASUS Prime A320I-K* $97.99
Graphics Integrated Graphics (Motherboard) $0
Disk (OS) Kingston A400 120GB $31.90
Memory CORSAIR Vengeance LPX 32GB CMK32GX4M2A2400C14 (2 x 16GB) $127.99
Power EVGA 110-BQ-0500-K1 500W 80+ Bronze Semi-Modular $44.99
Case Fractal Design Node 304 Black $99.99
SATA cables Silverstone Tek Ultra Thin Lateral 90 Degree SATA Cables (x2) $22.30
Subtotal (excluding storage drives) $530.29
Disk (Storage) Toshiba N300 HDWG480XZSTA 8TB 7200 RPM (x2) $372.79
Disk (Storage) Seagate IronWolf 8TB NAS Hard Drive 7200 RPM (x2) $359.98
Total NAS Drive Server Cost $1,263.06

* Motherboard Caveat: BIOS compatibility issues were encountered with the ASUS Prime A320I-K and AMD Athlon 3000G, requiring a BIOS update. Details are provided later in this guide.

DIY NAS Drive Server vs. Off-the-Shelf Solutions

Comparing the DIY nas drive server build to commercially available pre-built NAS solutions reveals compelling advantages in terms of performance and customization for a similar price.

Product 2022 Budget NAS (DIY) Synology DS920+ QNAP TS-473A-8G-US
Disk Bays 6 4 4
RAM 32 GB 4 GB 4 GB
Max RAM 32 GB 8 GB 8 GB
CPU Benchmark 4479 3002 4588
Price (Excluding Drives) $530.29 $549.99 $549

For a comparable price to pre-built NAS units, the DIY build offers significantly more RAM and avoids vendor lock-in associated with proprietary operating systems.

Building the NAS Drive Server: Assembly Process


All components laid out before assembly.


Motherboard installation into the Fractal Design Node 304 case was straightforward.


M.2 SSD installation is clean and simple, requiring no cables.


PSU installation in the case.


Routing SATA cables before PSU installation simplifies cable management.


Tight space highlighting the necessity of 90-degree SATA cables.


Motherboard with CPU, RAM, and power connections complete.


The finished NAS drive server build, ready for deployment.

Using TinyPilot for NAS Drive Server Management

For remote server management during the build process, TinyPilot Voyager 2 was utilized, eliminating the need for physical keyboard, mouse, and monitor connections.


TinyPilot Voyager 2 simplifies remote management of the NAS drive server.

TinyPilot allowed for BIOS access, OS installation media mounting, and remote troubleshooting directly from a web browser.


TrueNAS installation via TinyPilot, mounting the ISO image remotely.

BIOS updates using TinyPilot presented a minor limitation as direct file sharing for .CAP BIOS files was not yet supported. A USB drive was temporarily used for this step, highlighting a potential future enhancement for TinyPilot.

Troubleshooting BIOS Compatibility Issues

Initial power-on resulted in no video output, indicating a potential BIOS incompatibility between the ASUS Prime A320I-K motherboard and the AMD Athlon 3000G CPU.

Despite ASUS’s compatibility list indicating BIOS version 2203 support, the system failed to boot with the Athlon 3000G.

Borrowing a compatible Ryzen 7 CPU and GPU from a previous build allowed booting into BIOS and performing a BIOS update to the latest version (5862).


Initial BIOS version 2203, which was supposedly compatible but caused boot issues.


ASUS compatibility list indicating Athlon 3000G support from BIOS version 2203.

Even after updating the BIOS, boot issues persisted until the HDMI cable was correctly connected to the HDMI port instead of the DisplayPort output – a simple user error.


Correcting the display output connection resolved the boot issue.

The root cause remains unclear – whether it was a genuine BIOS incompatibility or a user error compounded by confusing port placement. Ultimately, the system booted successfully after BIOS update and correct HDMI connection.


Successful boot screen with the Athlon 3000G CPU after resolving the display issue.

NAS Drive Server Performance Benchmarks

Benchmarking NAS performance can be challenging. Standard benchmarking tools often focus on local disk I/O, not reflecting real-world network usage. A rudimentary benchmark was devised using file transfers over the network to assess read and write speeds.

The test involved transferring two datasets (20 GiB of 1 GiB files and 3 GiB of 1 MiB files) using robocopy between a desktop and the nas drive server, comparing performance to an older Synology DS412+.

Networking limitations were evident, with performance topping out around 1 Gbps (111 MiB/s), suggesting the 1 Gbps Ethernet ports on the network devices were the bottleneck.

Read Performance


Unencrypted read performance comparison between DIY NAS and Synology DS412+.

Surprisingly, the older Synology DS412+ outperformed the DIY nas drive server in unencrypted read speeds.


Encrypted read performance comparison, showing TrueNAS significantly outpacing Synology.

However, Synology’s performance plummeted with encryption enabled, while TrueNAS maintained consistent read speeds. On encrypted volumes, TrueNAS significantly surpassed Synology in read performance.

Write Performance


Unencrypted write performance comparison, with TrueNAS showing faster small file write speeds.

In unencrypted write tests, TrueNAS demonstrated faster small file write performance compared to Synology.


Encrypted write performance comparison, highlighting TrueNAS’s superior performance.

With encryption enabled, TrueNAS exhibited significantly superior write performance, outperforming Synology by a large margin.

Power Consumption

Power consumption was measured using a Kill A Watt meter.

NAS Drive Server Synology DS412+ 2022 DIY NAS
Idle Power 38 W 60 W
Load Power 43 W 67 W

The DIY nas drive server consumed approximately 60% more power than the Synology DS412+, likely due to component choices and PSU efficiency at lower load levels.

Final Thoughts and Lessons Learned from the NAS Drive Server Build

Motherboard Reflections

The ASUS Prime A320I-K motherboard presented compatibility and BIOS update challenges. The BIOS update utility was unreliable, requiring manual updates. The 32 GB RAM limit was also a minor drawback.

Realtek Networking Driver Issue and Fix

The Realtek NIC on the motherboard exhibited occasional instability under heavy network load. A workaround involving loading the official Realtek driver in TrueNAS was implemented:

  1. Navigate to System > Tunables in the TrueNAS web UI.

  2. Add the following tunables:

    Variable Value Type
    if_re_load YES loader
    if_re_name /boot/modules/if_re.ko loader

Case Feedback

The Fractal Design Node 304 case, while aesthetically pleasing, proved less user-friendly during assembly compared to other Fractal Design cases. Documentation was minimal, and some case mechanisms were not intuitive. Mini-ITX form factor limitations may have contributed to some of the assembly challenges.

CPU Performance and Power

The AMD Athlon 3000G CPU proved to be significantly overpowered for basic NAS duties, with consistently low CPU utilization. Its integrated graphics capability was valuable, eliminating the need for a discrete GPU.


CPU utilization graph from TrueNAS dashboard, demonstrating minimal CPU load.

Data Drive Noise and Performance

The chosen Toshiba N300 and Seagate IronWolf drives have performed reliably and quietly. Noise levels were generally inaudible except during benchmark testing, particularly during file deletion operations.

PSU Efficiency

The 500W PSU might be oversized, contributing to higher idle power consumption. A lower wattage, more efficiently sized PSU could potentially reduce power draw.

OS Drive Performance

The Kingston A400 OS drive has performed flawlessly, with minimal disk activity in TrueNAS, indicating it is more than sufficient for the OS workload.


Disk I/O graph for the OS drive, showing very low activity levels.

TrueNAS User Experience

TrueNAS, while powerful, presents a less user-friendly interface compared to Synology’s intuitive web UI. Basic tasks like volume creation and network sharing require navigating multiple menus with less clear guidance. Third-party app installation is also more complex in TrueNAS compared to Synology’s streamlined plugin system.


Synology’s user-friendly web dashboard.


TrueNAS’s more technical web dashboard.

Despite usability differences, TrueNAS’s open-source nature and platform flexibility remain key advantages. For users prioritizing ease of use, Synology remains a strong recommendation.

ZFS Feature Utilization

While ZFS offers advanced features like snapshots, data deduplication, and encryption, basic RAID functionality has been the primary feature utilized in this build. Encrypted snapshots present a potentially useful feature for secure backups without constant decryption.

Overall NAS Drive Server Experience

Building this DIY nas drive server has been a valuable learning experience. Prior experience with a pre-built Synology NAS provided a useful foundation for understanding NAS concepts. The DIY approach offers greater control and deeper technical insight, albeit with a steeper initial learning curve.

Video Walkthrough

[Link to Video – Replace with actual video link if available]

2.5-Year Update on the NAS Drive Server

After 2.5 years of operation (as of November 2024), the DIY nas drive server continues to be a valuable asset.

Continued Satisfaction

The nas drive server remains a functional and reliable storage solution. While Synology’s user experience is missed, the control and flexibility of TrueNAS are appreciated.

Disk Replacement

After 18 months, one Toshiba N300 drive began exhibiting clicking noises and was proactively replaced with a Seagate IronWolf drive. No further drive issues have occurred.

Rackmount Chassis Upgrade

The nas drive server was transitioned to a rackmount chassis (Sliger CX3701 10-bay) as part of a homelab rack setup. The Sliger CX3701 is recommended for users planning to utilize an HBA for expanded SATA ports, although mini-ITX motherboards limit PCI slot availability for other expansion cards if an HBA is used.

TrueNAS Scale Migration

A migration from TrueNAS Core (FreeBSD-based) to TrueNAS Scale (Debian-based) was performed. TrueNAS Scale’s web UI is considered slightly improved, and its Linux base is more familiar for users accustomed to Linux environments.

10 Gbps Network Upgrade

A 10 Gbps fiber NIC was added to the nas drive server to leverage a 10 Gbps network infrastructure. Initial NIC compatibility issues led to motherboard upgrades.

Motherboard Upgrade to Gigabyte B550I Aorus Pro

To resolve 10 Gbps NIC compatibility, the motherboard was upgraded to a Gigabyte B550I Aorus Pro AX. This motherboard resolved NIC compatibility and offered minor improvements in design and usability compared to the ASUS Prime A320I-K. However, the Gigabyte B550I Aorus Pro AX has a less intuitive M.2 slot design and slower BIOS boot times.

Mini-ITX Form Factor Regret for NAS Drive Server Expansion

The primary regret after long-term use is the choice of a mini-ITX form factor. Mini-ITX’s single PCI slot and limited SATA port count restrict expansion options. For future builds, a motherboard with more SATA ports or multiple PCI slots in a larger form factor (like micro-ATX or ATX) within a rackmount chassis with 6-8+ drive bays is recommended for greater expandability.

Thanks to the Blogging for Devs Community for providing early feedback on this article.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *