Cloud storage subscriptions keep creeping upward and hard drive prices are climbing too, which is why more people are building their own network-attached storage box instead of renting space by the terabyte forever. TrueNAS Scale, now called TrueNAS Community Edition by iXsystems after SCALE reached feature parity with CORE, is the free and open-source NAS operating system most homelab builders reach for in 2026. Its BSD-based sibling, TrueNAS CORE, was marked legacy with zero active development as of May 2026, according to TrueNASGuide, leaving Community Edition as the actively developed line. It runs on ordinary PC hardware, protects data with ZFS (a filesystem built specifically to catch and repair the silent data corruption that regular file systems miss), and, with the 25.10.7 point release reported as the latest stable release on October 19, bundling Linux kernel 6.12.99 on top of 25.10.6 fixes for Fibre Channel crashes and an NFS hang, runs Docker containers directly, so the same box that stores your files can also run Plex, a Pi-hole instance, or a handful of self-hosted apps.
This tutorial walks through building a real NAS from scratch: picking hardware that won’t bottleneck you, installing the current TrueNAS Scale release, setting up a ZFS pool that survives a drive failure without losing anything, sharing that storage to Windows and Mac machines, and deploying your first containerized app. Budget 90 minutes for the initial build and setup, plus however long the initial ZFS resilver takes in the background afterward.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why Build a NAS Instead of Using Cloud Storage in 2026
A self-built NAS pays for itself differently than a cloud subscription. You pay once for drives and a small PC, and after that the marginal cost of storing another terabyte is close to zero, versus a recurring monthly bill that scales with every gigabyte you add. It also solves problems cloud storage can’t: local network transfer speeds are limited only by your Ethernet, not your ISP’s upload cap, and you keep full control over your data rather than trusting a third party’s retention policy and pricing changes.
Run the numbers and the gap is stark for anyone storing more than a couple terabytes long-term. A four-bay NAS built around 8TB WD Red Pro drives in RAIDZ2 lands around $700-900 all-in for roughly 16TB of protected, self-healing storage, a one-time cost. The equivalent 16TB on a consumer cloud storage plan runs well into hundreds of dollars a year indefinitely, with no cap on how long that bill keeps arriving. The breakeven point typically lands somewhere between year one and year two, and every year after that is close to free beyond electricity, which is why homelab and self-hosting communities treat a NAS build as one of the higher-value projects available to anyone comfortable with a screwdriver and a web browser.
The tradeoff is that a NAS is not automatically a backup. RAID and ZFS protect against a drive dying, not against a house fire, ransomware, or an accidental deletion that syncs to every connected device. The right mental model, and the one this guide follows, is that your NAS is your primary storage and one leg of a proper 3-2-1 backup strategy, with an off-site copy on a service like Backblaze B2 or another object storage provider covering the “off-site” leg.
Network-attached storage, as a category, is defined by the Storage Networking Industry Association as a file-level storage device connected to a network that provides shared access to multiple clients, the key distinction from a simple external drive being that a NAS is its own small server, with its own OS, filesystem intelligence, and the ability to run background services rather than just holding files. That’s exactly what TrueNAS Scale turns a spare PC into.
Prerequisites: Hardware and Software You Need
TrueNAS Scale’s hardware bar is low enough that a retired office PC can run it, but the specs below reflect what actually makes a NAS usable rather than just bootable.
- Operating system: TrueNAS Scale 25.10 “Goldeye” (current stable release as of September 2026, iXsystems shipped 25.10.7 that month per the TrueNAS Software Status page, following 25.10.6 in August 2026 with Linux kernel 6.12.99, 25.10.5 in July 2026 with kernel 6.12.95, and 25.10.4, the recommended general-release build, in June 2026 with kernel 6.12.91), the Debian-based Community Edition that replaced the older Kubernetes-based apps system with Docker
- CPU: any 64-bit x86 processor with hardware virtualization support; a quad-core chip is comfortable if you plan to run apps or transcode media, a dual-core is the bare minimum for storage-only use
- RAM: per the official TrueNAS hardware guide, 8GB is the stated minimum for up to eight drives, but 16GB is a realistic floor for a comfortable home NAS and 32GB is worth budgeting for if you’ll run several Docker apps alongside storage, ZFS uses RAM as a read cache (called ARC), so more memory directly means faster repeated reads
- ECC RAM: recommended but not mandatory; ZFS checksums data on every read and write, and ECC memory prevents the rare case of memory errors corrupting data before ZFS ever sees it. Non-ECC RAM works fine for most home builds where budget is the deciding factor
- Boot drive: a dedicated 20GB-or-larger SSD, separate from your data drives, do not boot from a spinning hard drive or share the boot device with a storage pool
- Data drives: at least two identical-capacity drives for a mirrored pool, four or more for a RAIDZ2 pool; use CMR (conventional recording) NAS-rated drives, not SMR (shingled) drives, which perform poorly under ZFS’s write patterns
- A USB flash drive (8GB or larger) to create the TrueNAS Scale installer
- Balena Etcher or Rufus to write the installer image to the USB drive
Picking a Case, Motherboard, and Power Supply
The single biggest hardware decision after drives is whether to repurpose an existing PC or buy dedicated NAS hardware. A retired office desktop or a used SFF (small-form-factor) machine works well if it has enough SATA ports for your drive count, but most consumer motherboards only expose four to six SATA ports, which caps how far a build can grow before you need an add-in HBA (host bus adapter) card. On the “buy dedicated hardware” side, iXsystems sells its own rack-mountable R-Series appliances preloaded with TrueNAS, and added the R60 as its newest model in March 2026, a turnkey option worth pricing against a DIY build if you’d rather skip sourcing a case and HBA yourself. If you’re buying new for a DIY build instead, look specifically for a case with hot-swappable drive bays, it turns a future drive replacement from a full teardown into a five-minute job, which matters more than it sounds like it should the first time you’re doing it at 11pm after a drive alert.
An HBA card flashed to “IT mode” (pass-through mode, as opposed to the card’s native hardware RAID mode) is the standard way to add SATA or SAS ports beyond what your motherboard offers, and it’s a requirement rather than an option if you’re using a RAID controller card at all, TrueNAS needs direct, unmediated access to each physical disk to manage ZFS correctly, and a hardware RAID card sitting in between breaks that. Used LSI-based HBA cards (the 9207-8i and similar models turn up regularly on the secondhand market) are the community-standard choice and typically cost well under $50.
For power supply sizing, a four-to-six-drive spinning-disk NAS rarely draws more than 100-150W under load, so almost any modern 80 Plus-rated PSU in the 400-550W range has ample headroom, the bigger consideration is a PSU with enough SATA power connectors (or a splitter) for your drive count, and ideally one rated for continuous 24/7 operation rather than a budget unit designed for intermittent desktop use. If your build will also run Docker apps with any GPU-accelerated transcoding, budget additional wattage and confirm the case has room for a low-profile graphics card or that your CPU’s integrated GPU (Intel QuickSync is the most common choice for this) covers your transcoding needs without one.
Why ZFS Instead of a Traditional RAID Filesystem
ZFS, the filesystem underneath every TrueNAS pool, exists to solve a problem traditional RAID controllers don’t even detect: silent data corruption, sometimes called bit rot, where a bit on a drive platter flips without the drive itself reporting an error. A conventional hardware RAID array has no way to know which copy of a mirrored block is the corrupted one if only one bit differs, it just serves whichever copy it reads first. ZFS checksums every block of data as it’s written and verifies that checksum on every read, so it can detect corruption immediately and, on a mirror or RAIDZ pool, automatically repair the bad block using a known-good copy from another drive.
That self-healing behavior is why homelab communities treat ZFS as meaningfully more trustworthy than the ext4-plus-mdadm RAID stack many older NAS operating systems still use. The OpenZFS project documentation covers the technical details of how checksumming, copy-on-write, and pool scrubbing work together, but the practical takeaway for this build is simpler: run a scheduled scrub (covered in the Advanced Tips section below), and ZFS will find and fix corruption long before it becomes a problem you notice by a corrupted photo or a file that won’t open.
Step 1: Choose Your NAS Hard Drives
Drive selection determines both your usable capacity and how long your NAS lasts before a failure. The three NAS-rated drive families that dominate 2026 buyer guides are Seagate IronWolf Pro, WD Red Pro, and Toshiba N300, all CMR drives rated for 24/7 operation.
| Drive Family | Best For | Workload Rating | RPM | Warranty |
|---|---|---|---|---|
| Seagate IronWolf Pro | Home NAS with heavy multi-user load | 300 TB/year | 7200 | 5 years |
| WD Red Pro | Best overall reliability for 24/7 NAS | 300-550 TB/year | 7200 | 5 years |
| Toshiba N300 | Budget-value NAS drive | 180 TB/year | 7200 | 3 years |
| WD Red Plus | Light home use, 1-8 bay | 180 TB/year | 5400 | 3 years |
For a first build, four matched drives is the sweet spot: enough to run RAIDZ2 (tolerates two simultaneous drive failures) while keeping the parity overhead reasonable. Our full IronWolf Pro vs WD Red Pro vs Toshiba N300 comparison breaks down pricing and performance in more depth if you’re still deciding between families. Whatever you choose, buy from at least two different retailers or batches when possible, drives from the same manufacturing batch tend to fail in clusters, which defeats some of the protection RAID is supposed to provide.
Step 2: Understand ZFS Pool Types Before You Build
ZFS pool layout is the single decision hardest to change after the fact, so get it right before you write any data. Three layouts cover almost every home NAS use case.
- Mirror: two (or more, in pairs) drives holding identical copies of everything. Simple, fast to resilver after a failure, but only gives you 50% usable capacity from your total raw storage.
- RAIDZ1: parity striped across three or more drives, tolerating one drive failure. Cheaper on capacity than mirroring, but current guidance increasingly steers larger, high-capacity arrays away from RAIDZ1 toward RAIDZ2, since a second drive failing during the long resilver window after the first failure would mean total data loss.
- RAIDZ2: parity striped across four or more drives, tolerating two simultaneous drive failures. This has become the default recommendation for a 4-6 drive home NAS in 2026, trading a bit more usable capacity for meaningfully better protection during the vulnerable resilver period.
For four 8TB drives, a RAIDZ2 pool gives you roughly 16TB of usable space (two drives’ worth of capacity spent on parity), versus about 24TB usable if you ran the same four drives as RAIDZ1, but with meaningfully less protection during a rebuild. For most home users, that trade is worth it.
Step 3: Create the TrueNAS Scale Installer
Download the current TrueNAS Scale 25.10 “Goldeye” ISO, the line went general availability on October 28, 2025, per endoflife.date, with OpenZFS 2.3.4 under the hood, and iXsystems has kept shipping point releases since: 25.10.0.1 on November 14, 2025, 25.10.1 on December 17, 2025, 25.10.2 on February 18, 2026, then 25.10.2.1 later that February fixing NIC-bonding disruptions, 25.10.4 became the recommended general-release build on June 3, 2026, 25.10.5 followed in July 2026, 25.10.6 (fixing Fibre Channel crashes and an NFS hang) shipped August 12, 2026, and 25.10.7 arrived in September 2026 as the current build, from the official TrueNAS site, then write it to your USB drive.
Creating the installer (Windows/Mac/Linux):
1. Download TrueNAS-SCALE-25.10.6.iso from truenas.com
2. Open Balena Etcher (or Rufus on Windows)
3. Select the downloaded ISO as the source image
4. Select your USB flash drive (8GB+) as the target
5. Click Flash, this erases everything on the USB drive
6. Wait for the write and verify pass to complete (~5-10 minutes)Step 4: Install TrueNAS Scale on the Boot Drive
Physically install your boot SSD and data drives into the NAS chassis, plug in the installer USB, and boot from it (you may need to change the boot order in BIOS, see our BIOS settings guide if you’re not familiar with your motherboard’s boot menu). The installer walks through a short menu-driven process.
TrueNAS Scale installation steps:
1. Boot from the USB installer, select "Install/Upgrade"
2. Choose your dedicated boot SSD as the install target
(WARNING: do not select a data drive here, it will be wiped)
3. Set a root/admin password when prompted
4. Choose UEFI or Legacy boot mode to match your motherboard
5. Confirm and wait for installation (5-10 minutes)
6. Remove the USB drive, reboot into TrueNAS Scale
7. Note the IP address shown on the console screen, you'll use
this to reach the web UI from another computerStep 5: Access the Web Interface and Complete Initial Setup
From any other computer on the same network, open a browser and navigate to the IP address shown on the TrueNAS console (for example, http://192.168.1.50). Log in with the root credentials you set during installation. The setup wizard will prompt you to confirm your timezone, hostname, and whether to enable automatic updates, leave automatic updates off for a production NAS and apply updates manually after reading the release notes, since a Docker backend migration or major version jump is not something you want happening unattended.
Step 6: Build Your Storage Pool
In the TrueNAS web UI, navigate to Storage and click Create Pool. Select your data drives (not the boot SSD, which won’t appear in this list), choose RAIDZ2 as the vdev type if you have four or more drives, and give the pool a name like tank or storage. TrueNAS will show you the calculated usable capacity before you confirm, double-check it matches your expectations from Step 2’s math before proceeding, since changing the layout later means destroying and rebuilding the pool from scratch.
Click Create, confirm the warning about data on the selected drives being erased, and wait for the pool to initialize. This step is close to instant since ZFS doesn’t need to pre-format drives the way traditional RAID controllers do.
Step 7: Create Datasets and Set Up SMB/NFS Shares
Datasets are ZFS’s version of folders with their own independent settings for compression, quotas, and permissions. Create at least one dataset per logical use case, for example, separate datasets for Media, Backups, and Documents, rather than dumping everything into the pool’s root.
Setting up an SMB share (for Windows and Mac access):
1. Storage -> select your pool -> Add Dataset -> name it "media"
2. Shares -> Windows Shares (SMB) -> Add
3. Select the "media" dataset as the path
4. Name the share (this is what appears on the network)
5. Enable the SMB service under System Settings -> Services
6. Create a dedicated user account under Credentials -> Local Users
(avoid sharing the root account for daily file access)
7. Grant that user permission on the dataset under
Storage -> pool -> dataset -> Edit Permissions
Setting up an NFS share (for Linux/Unix clients):
1. Shares -> Unix Shares (NFS) -> Add
2. Select the dataset path, set allowed networks/IPs
3. Enable the NFS service under System Settings -> ServicesOn a Windows machine, map the share by entering \\[NAS-IP-address]\[share-name] in File Explorer’s address bar. On macOS, use Finder’s Connect to Server (Cmd+K) with smb://[NAS-IP-address]/[share-name].
Step 8: Deploy Your First App With Docker
TrueNAS Scale’s Apps backend moved from Kubernetes to Docker starting with the 24.10 “Electric Eel” release, first shipped December 17, 2024. iXsystems kept patching that line well into 2025, 24.10.2.1, released April 3, 2025, fixed a batch of OpenZFS issues and became, per iXsystems, the most widely used build of the release, before Electric Eel’s security support ended and the line closed out at its terminal 24.10.2.4 maintenance update on August 7, 2025. The next stable line, 25.04 “Fangtooth,” had shipped April 15, 2025 and ran through a 25.04.2.6 maintenance update on October 30, 2025, per endoflife.date, before handing off to 25.10 “Goldeye.” By the current 25.10 “Goldeye” release, custom app deployment via a Docker Compose YAML file is a first-class, guided option, a meaningful simplification over the older Kubernetes-based system, which was frequently cited as the most confusing part of running TrueNAS Scale.
Deploying an app from the built-in catalog:
1. Apps -> Discover Apps -> browse or search (e.g. "Pi-hole", "Plex")
2. Select the app -> Install
3. Configure the storage path (point it at a dataset from Step 7)
4. Set any required ports or environment variables
5. Click Install and wait for the container to pull and start
Deploying a custom app via Docker Compose:
1. Apps -> Discover Apps -> Custom App -> Install via YAML
2. Paste your docker-compose.yml configuration
3. Map volumes to your ZFS datasets, not to arbitrary paths
4. Click Save, TrueNAS handles the underlying Docker Compose
invocation and keeps the app under Apps -> Installed for
start/stop/update management through the web UIA Pi-hole container is a popular first app for exactly this setup, see our Pi-hole setup guide for the DNS-side configuration once the container is running. A password manager like Vaultwarden is another common second app; our Vaultwarden setup tutorial covers that deployment in more detail. The full list of what changed in the Docker migration, including which older Kubernetes-based app configurations require manual re-creation rather than automatic migration, is documented in the TrueNAS 25.04 “Fangtooth” release notes, worth a skim if you’re migrating an existing older TrueNAS Scale install rather than starting fresh.
Step 9: Set Up Scheduled Snapshots
Snapshots are ZFS’s built-in, near-zero-cost protection against accidental deletion and ransomware-style file corruption, they capture the state of a dataset at a point in time without duplicating unchanged data. Navigate to Data Protection → Periodic Snapshot Tasks and create a schedule for each important dataset.
Recommended snapshot schedule for a home NAS:
- Hourly snapshots, kept for 24 hours (catches same-day mistakes)
- Daily snapshots, kept for 2 weeks (catches slower-to-notice issues)
- Weekly snapshots, kept for 2 months (long-tail recovery window)Snapshots are not a substitute for off-site backup, since they live on the same pool and won’t help if the whole NAS is stolen, flooded, or catches fire. Pair them with a replication task to a second TrueNAS box or a cloud target for genuine disaster recovery.
Step 10: Configure Email Alerts and Monitor Drive Health
A NAS that silently loses a drive and nobody notices for six months is a NAS running on borrowed time. Under System Settings → General → Email, configure an SMTP relay (Gmail’s app-password SMTP works fine for personal use) so TrueNAS can notify you of pool degradation, failed SMART tests, or resilver events. Under Data Protection → S.M.A.R.T. Tests, schedule a short SMART test weekly and a long SMART test monthly on every drive, SMART tests catch developing mechanical issues well before a drive fails outright.
Complete Worked Example: A 4-Bay RAIDZ2 Home NAS Build
Here is a full build combining every step above into one concrete, current-2026 example.
PROJECT: 4-bay home NAS with TrueNAS Scale 25.10 "Goldeye"
Hardware:
- Repurposed mini-PC, quad-core x86_64, upgraded to 32GB non-ECC RAM
- 1x 500GB SATA SSD (boot drive, dedicated)
- 4x 8TB WD Red Pro (data drives, matched capacity)
- 1x 8GB USB flash drive (installer only, removed after setup)
Build steps:
1. Flashed TrueNAS-SCALE-25.10.6.iso to USB with Balena Etcher
2. Installed to the 500GB boot SSD, left data drives untouched
during install
3. Logged into web UI at http://192.168.1.42, set timezone,
disabled automatic updates
4. Storage -> Create Pool -> selected all 4x WD Red Pro drives
-> RAIDZ2 -> pool named "tank"
Result: ~16TB usable from 32TB raw
5. Created datasets: tank/media, tank/documents, tank/backups
6. Configured SMB share for "tank/media" and "tank/documents",
created a dedicated non-root user "homeuser" with share access
7. Deployed Pi-hole and Plex from the Apps catalog, storage
mapped to tank/media
8. Set hourly/daily/weekly snapshot schedule on all three datasets
9. Configured Gmail SMTP relay for alert emails
10. Scheduled weekly short SMART tests, monthly long SMART tests
on all 4 drives
Result: fully functional NAS, tolerant of 2 simultaneous drive
failures, running 2 self-hosted apps, backing up automatically
via snapshots, alerting on any drive health issue.Common Mistakes to Avoid
- Using SMR drives instead of CMR. Shingled Magnetic Recording drives are cheaper per terabyte but perform poorly during ZFS resilver operations and have been linked to failed rebuilds. Always confirm a drive is CMR before buying for a NAS build.
- Sharing the boot drive with a storage pool. TrueNAS requires a dedicated boot device separate from your data drives. Trying to combine them isn’t supported and risks losing your configuration if a data drive needs to be replaced.
- Skipping RAIDZ2 to save capacity on a 4+ drive array. RAIDZ1’s single-drive fault tolerance looks fine until a second drive fails during the hours-long resilver window that follows the first failure, a genuinely common failure pattern with drives from the same batch.
- Treating snapshots as a full backup strategy. Snapshots protect against file-level mistakes on the same physical box. They do nothing if the NAS itself is lost to theft, fire, or flooding, you still need an off-site or cloud copy of anything irreplaceable.
- Mixing drive capacities in a single vdev. ZFS pools built from mismatched drive sizes waste the excess capacity on the larger drives, since a vdev’s usable size is capped by its smallest member. Buy matched drives for each pool.
Troubleshooting Common TrueNAS Scale Problems
Problem: The pool creation wizard doesn’t show my data drives. Confirm the drives are properly connected via SATA/SAS and recognized by the motherboard’s BIOS before booting TrueNAS. If using a RAID controller card, it must be flashed to “IT mode” (pass-through) rather than running its own hardware RAID, TrueNAS needs direct access to each disk.
Problem: SMB shares are visible but Windows won’t connect. Confirm the SMB service is running under System Settings → Services, and that the user account has both a password set and explicit permissions granted on the dataset, not just the pool root. If you’re seeing ACL-related permission errors on an older install, note that iXsystems’ 24.10.1 maintenance update (December 18, 2024) raised the maximum SMB ACL entries per share from 64 to 1024, per Tweakers, worth confirming your build is past that point before digging further.
Problem: Transfer speeds are far below your network’s rated speed. Check whether your NIC is actually negotiating at its rated speed (a 2.5GbE port sometimes falls back to 1GbE with the wrong cable category), and confirm the client machine’s network adapter matches. Spinning HDDs in a small pool can also simply not saturate a 10GbE link, sequential throughput scales with the number of drives in a vdev, and even though 25.10 “Goldeye” added support for networking hardware up to 400GbE, per iXsystems’ February 2026 roadmap, a handful of spinning drives in a small vdev will bottleneck long before a link anywhere near that fast becomes the limiting factor.
Problem: A Docker app won’t start after installation. Check Apps → Installed → [app name] → Logs for the container’s startup output. Most failures trace back to a storage path pointing at a dataset the app’s assigned user doesn’t have permission to write to.
Problem: The pool shows “Degraded” status. One or more drives have dropped out or failed a health check. Check Storage → your pool for which specific drive is flagged, replace it, and TrueNAS will automatically begin resilvering onto the new drive once it’s added back to the vdev.
Problem: RAM usage sits at 80-90% constantly. This is normal, not a leak, ZFS’s ARC cache deliberately uses most available RAM to speed up reads, and releases it automatically if another process needs memory. Don’t interpret high RAM usage on a ZFS system the way you would on a typical desktop.
Problem: SMART tests keep reporting “Pre-fail” on a specific attribute. Treat this seriously even if the drive still appears functional, a Pre-fail SMART attribute is a strong predictor of failure within weeks to months. Order a replacement drive and plan a proactive resilver rather than waiting for the drive to fail outright.
Problem: Can’t remember the web UI’s IP address after a reboot. Connect a monitor and keyboard directly to the NAS, the console displays the current IP address at the login prompt. Setting a static IP reservation in your router’s DHCP settings avoids this recurring after every reboot.
Advanced Tips
Once the base NAS is stable, a few refinements matter for long-term reliability. Enable ZFS’s automatic scrub schedule (Data Protection → Scrub Tasks) to run monthly — a scrub reads every block in the pool and verifies its checksum, catching silent data corruption (“bit rot”) before it spreads to your backups. If your motherboard supports it, add a small NVMe SSD as an L2ARC read cache or SLOG write-log device to meaningfully speed up either read-heavy or write-heavy workloads without touching your main pool layout, and for anyone pooling storage across multiple boxes, 25.10 “Goldeye” also added NVMe-oF support, per iXsystems’ February 2026 roadmap, letting a remote NVMe device be shared over the network with much of local-NVMe latency intact.
For anyone running low on drive bays, TrueNAS supports expanding a RAIDZ vdev by adding drives to it directly in the 25.10 “Goldeye” release line, a capability that used to require destroying and rebuilding the entire pool in older versions — and it’s about to get more flexible still: iXsystems’ preview builds have been moving fast, with 26-BETA.1 landing in April 2026, 26-BETA.2 (versioned 26.0.0-BETA.2 in the release metadata) following in June 2026, and 26-BETA.3 on August 20, 2026, further updating the Linux kernel and OpenZFS and adding dRAID spare support ahead of the next major line. iXsystems’ February 2026 roadmap confirmed that upcoming line drops the old “25.04.2.6”-style versioning for simpler “26.1” numbering and moves SCALE onto Linux kernel 6.18 LTS. And if the RAM market stays tight, remember TrueNAS’s rule of thumb — roughly 1GB of RAM per terabyte of storage as a starting point for planning, adjusted upward if you’re running memory-hungry apps alongside file serving.
Finally, set up remote access carefully rather than by opening ports directly on your router. Exposing the TrueNAS web UI or SMB directly to the internet is a well-documented way to get a NAS compromised, since both have been targeted by ransomware campaigns in past years. A VPN back into your home network, or a reverse proxy with proper authentication in front of specific apps, is the safer route if you need access away from home — treat the TrueNAS management interface itself as something that should never be reachable from outside your LAN.
TrueNAS Scale vs Unraid vs Synology: Which Fits a Home NAS Build
TrueNAS Scale’s biggest advantage is that it’s free, open-source, and built on ZFS, widely regarded as the most robust filesystem available for protecting against data corruption. Unraid, a commercial alternative with a one-time license fee, trades some of ZFS’s protection guarantees for more flexible mixed-capacity drive pooling, you can add drives of any size to an Unraid array without matching capacities, something TrueNAS’s ZFS vdevs don’t support as cleanly. Synology sits at the opposite end: a fully packaged hardware-plus-software appliance with the friendliest interface of the three, at a meaningfully higher cost per terabyte than building your own box.
| Platform | Cost Model | Filesystem | Mixed-Capacity Drives | Best For |
|---|---|---|---|---|
| TrueNAS Scale | Free, open-source | ZFS | Not within a vdev | Best data protection per dollar, DIY builders |
| Unraid | One-time license ($59-$149) | XFS/BTRFS per-drive + parity | Yes, any size | Flexible expansion, mixed old drives |
| Synology (DSM) | Hardware appliance, $300-$1,500+ | Btrfs | Limited (SHR pools) | Easiest setup, least hands-on maintenance |
For anyone comfortable following a step-by-step build like this one, TrueNAS Scale on repurposed or budget PC hardware delivers the best storage-protection-per-dollar of the three options, which is why it remains the default recommendation across homelab communities heading into the back half of 2026.
Frequently Asked Questions
Do I need ECC RAM for TrueNAS Scale?
No. ECC RAM is recommended because ZFS’s checksumming works best when the memory holding data before it’s written is itself error-corrected, but TrueNAS runs perfectly well on standard non-ECC RAM. Most home builds use non-ECC RAM without issue; ECC becomes more valuable as pool size and the amount of irreplaceable data grow.
How much RAM do I actually need?
TrueNAS’s official minimum is 8GB for up to eight drives, but 16GB is a more realistic comfortable floor for home use, and 32GB is worth targeting if you plan to run several Docker apps alongside file storage. A rough planning guideline is 1GB of RAM per terabyte of storage, though this scales down for storage-only setups without app workloads.
Can I use TrueNAS Scale on old, repurposed hardware?
Yes, and it’s one of the most common ways homelab builders get started, any 64-bit x86 machine from roughly the last decade with virtualization support will run it. Just make sure it has enough SATA ports (or an add-in HBA card) for your planned drive count, and enough RAM slots to grow into if you add apps later.
Is RAIDZ2 overkill for a small home NAS?
For a 2-drive setup, RAIDZ2 isn’t possible (it needs at least four drives), use a mirror instead. For four or more drives, RAIDZ2 is the current default recommendation because it protects through the vulnerable resilver window after a first drive failure, when a second failure would otherwise mean total data loss on a RAIDZ1 array.
What happened to TrueNAS Scale’s Kubernetes-based apps?
The Apps backend switched from Kubernetes to Docker starting with the 24.10 “Electric Eel” release. iXsystems kept shipping fixes throughout the line’s life, a 24.10.0.2 update on November 9, 2024 addressed a high-impact SMB memory management bug, and a 24.10.2.2 maintenance release followed on May 13, 2025, before Electric Eel reached end of life. By the current 25.10 “Goldeye” line, Docker Compose YAML deployment is a fully guided, first-class option in the web UI. This resolved one of the most commonly cited pain points from earlier TrueNAS Scale versions.
Does a NAS replace the need for cloud backup?
No. A NAS is excellent primary storage and, with snapshots, protects well against accidental deletion and drive failure, but it lives in one physical location. Pair it with an off-site or cloud backup target for anything you genuinely can’t afford to lose, see our comparison of IDrive vs Backblaze for options.
How does the current RAM price situation affect a NAS build budget?
DRAM pricing has stayed elevated through 2026, which pushes the cost of hitting the recommended 16-32GB RAM targets higher than it was a year or two ago. Budget builders should treat 8-16GB as an acceptable starting point for storage-only use and add RAM later once prices normalize, rather than delaying the build entirely, see our coverage of the ongoing DRAM price crisis for the broader context.
Can I mix TrueNAS Scale storage with Plex or media server apps on the same box?
Yes, this is one of the most common home NAS configurations. Deploy Plex (or Jellyfin) as a Docker app pointed at your media dataset, and make sure your CPU supports hardware transcoding (Intel QuickSync or an equivalent) if you’ll be streaming to devices that need on-the-fly format conversion.
How much does it cost to run a NAS 24/7 in electricity?
A typical four-to-six-drive spinning-disk NAS built on a repurposed office PC or small-form-factor board draws roughly 40-70W at idle and up to 100-150W under heavy load, translating to somewhere in the range of $5-15 per month depending on local electricity rates and how much of the time it spends idle versus active. Spinning the drives down during idle periods (configurable under Storage → your pool → Edit → HDD Standby) trims that further, though frequent spin-up/spin-down cycling adds mechanical wear, so it’s a genuine tradeoff rather than a free win.
