Black Friday mini PC deals are live, checked daily through Cyber Monday. See the deals guide
← All Guides
intermediate

TrueNAS SCALE Setup Guide: Building Your First NAS

A first-NAS walkthrough for TrueNAS: hardware that actually works, pool and vdev layout before you commit, datasets, SMB shares, snapshots, scrubs, and getting your data off the box.

Budget Homelab ·
hardwarestoragehow-toself-hosting

This guide contains affiliate links. If you buy through them, I earn a small commission at no extra cost to you.

You have already decided you want a separate storage box, and you have picked TrueNAS over the alternatives. If either of those is still open, start with TrueNAS vs Unraid vs OpenMediaVault for the OS decision and NAS vs DAS for whether you need a networked box at all. The short version of the OS decision is that TrueNAS wants matched drives and real RAM, and gives you ZFS integrity for free in exchange.

This guide covers the part those comparisons do not: getting a working NAS out of a pile of drives. The hardware that matters, the pool layout decision you should make on paper before you touch the installer, and the configuration that turns a file server into something you can trust. If you are still choosing between buying a finished unit and building one, prebuilt vs DIY covers that trade-off.

One naming note before anything else, because it causes real confusion when you go looking for downloads. TrueNAS SCALE is now called TrueNAS Community Edition. iXsystems merged the old FreeBSD-based CORE and the Linux-based SCALE into one product with the 25.04 Fangtooth release. The current release line is 25.10, codenamed Goldeye. Everyone still says SCALE, the docs URLs still say SCALE, and the thing you download is the same thing. Grab the current stable release from truenas.com rather than any version number written in a guide, including this one.

What You Need First

TrueNAS publishes real minimums, so there is no need to guess at them:

ComponentTrueNAS documented minimumWhat to actually plan for
RAM8 GB16 GB if you want apps or a VM on the box
CPU2-core 64-bit Intel or AMD x86_64Almost any desktop CPU from the last decade
Boot device16 GB SSDA small SATA or NVMe SSD, not a USB stick
Data drivesnot specifiedAt least two, ideally the same size
Storage controllernot specifiedMotherboard SATA, or an HBA in IT mode

A few notes on where first builds go wrong:

For the drives themselves, a CMR NAS drive is the thing you want, and drive choice is mostly independent of the OS. The Seagate IronWolf 4TB is the common homelab pick in that class; check current price, because spinning disks move around a lot. If you also want a fast drive for apps and VM storage so containers are not competing with your spinning pool for I/O, a Crucial P3 Plus 2TB NVMe is a reasonable special-purpose drive; check current price. Homelab storage options goes deeper on the drive side.

Decide Your Pool Layout First

This is the one part of a TrueNAS build that is genuinely hard to undo, so do it before the installer, not during it.

ZFS groups physical drives into a vdev, and a pool is made of one or more vdevs. Redundancy lives at the vdev level. The practical layouts for a first NAS:

LayoutDrivesUsable capacitySurvivesGood for
Mirror2One drive’s worth1 drive failureFirst builds, small pools, simple growth
RAIDZ13-4Total minus one drive1 drive failureBest capacity-per-dollar at small scale
RAIDZ26+Total minus two drives2 drive failuresLarger pools, bigger drives
Striped2+All of itNothingScratch data you can lose

How I would pick: with two drives, mirror. With three or four, RAIDZ1. With six or more, or with drives large enough that a rebuild will take a long and nervous day, RAIDZ2. Striped with no redundancy is a real option for genuinely disposable data, and a trap for everything else.

The thing to internalize is that vdev layout is fixed once created. You cannot turn a mirror into RAIDZ1 in place. Historically you grew a ZFS pool by adding another full vdev, and while recent OpenZFS releases added RAIDZ expansion, it remains slower and more constrained than Unraid’s add-any-drive model. If your plan is to buy one drive every few months, that is a genuine argument for a different OS, and the comparison article makes the case honestly.

Step 1: Write the Installer and Boot It

Download the current stable 25.10 image, then write it to a USB stick:

# Linux or macOS, replace /dev/sdX with your USB device
sudo dd if=TrueNAS-SCALE-25.10.x.iso of=/dev/sdX bs=4M status=progress conv=fsync

On Windows, Balena Etcher does the same job. Double-check the target device; dd will happily overwrite the wrong disk without asking.

Connect the data drives before booting, so the installer can see everything, but be clear in your own head which device is the boot target.

Step 2: Install to a Dedicated Boot Device

Boot from the USB stick and work through the installer. The decisions it asks for:

  1. Install device. Pick your small boot SSD. Not a data drive. The installer wipes what it touches.
  2. Admin credentials. Newer releases create a local admin account rather than using root directly. Set a real password.
  3. Reboot. Pull the USB stick on the way down.

When it comes back up, the console prints the web UI address. If your network hands out DHCP, it will be something like http://192.168.1.50. Open that in a browser on the same network.

Step 3: Give It a Static Address

A NAS whose address moves is a NAS whose shares break. Set a static IP under Network, picking something outside your router’s DHCP range so nothing else gets handed the same address:

Address:  192.168.1.50/24
Gateway:  192.168.1.1
DNS:      192.168.1.1

TrueNAS applies network changes behind a rollback timer: if you lock yourself out, it reverts automatically after a short window. Use that deliberately. Apply the change, reload the UI at the new address, and only then confirm it permanently. If the reload fails, wait for the rollback rather than power-cycling.

Step 4: Create the Pool

Go to Storage and create a pool. Name it something plain, tank being the traditional choice.

Add your data drives into a single vdev with the layout you decided on earlier. The UI shows you the resulting usable capacity as you go, which is a good sanity check against what you expected. Leave the boot device out of it entirely.

Read the confirmation summary properly before you click through it. This is the point of no return for vdev layout.

Step 5: Create Datasets, Not Folders

New users often create a pool and start copying files into its root. Don’t. Create a dataset per purpose instead:

tank/media
tank/documents
tank/backups
tank/apps

Datasets are the unit that snapshot schedules, quotas, permissions, and share settings attach to. Splitting them by purpose means you can keep ninety days of snapshots on documents and seven on media, share one over SMB and not the other, and cap the one that would otherwise eat the pool. Doing it later means moving data between datasets, which is a copy, not a rename.

For a dataset that will be shared with Windows and macOS clients, choose the SMB share type when creating it so the permissions are set up sensibly from the start.

Step 6: Create a User and Share It

Create a non-root user under Credentials for daily access. Shares authenticated as root are a bad habit that is annoying to unwind later.

Then add an SMB share under Shares, point it at a dataset, and enable the SMB service when prompted. Mount it from a client to prove it works in both directions:

# Linux
sudo mount -t cifs //192.168.1.50/media /mnt/media -o username=youruser

# macOS: Finder, Cmd+K
smb://192.168.1.50/media

Write a file, read it back, delete it. “The share mounted” and “the share works” are different claims, and only one of them is worth trusting.

NFS is the better choice if the clients are Linux or hypervisors rather than desktops, and it is a separate share type in the same screen. If you are wiring this into a Proxmox host, VM vs LXC covers which side of that line your workloads belong on.

Step 7: Snapshots and Scrubs

Two scheduled tasks turn TrueNAS from a file server into something with actual guarantees.

Periodic snapshot tasks (under Data Protection) capture a dataset’s state on a schedule. They are near-free until data diverges, and they are the thing that saves you from your own mistakes. A reasonable starting point:

DatasetFrequencyRetention
documentsHourly2 weeks
mediaDaily2 weeks
appsDaily1 month
backupsDaily1 month

Restoring is per-dataset from the snapshot list, or per-file by browsing a previous version from an SMB client.

Scrub tasks walk the whole pool, verify every block against its checksum, and repair what they can from redundancy. TrueNAS schedules one by default; confirm it exists rather than assuming. A monthly scrub is the common cadence. This is the mechanism behind the claim that ZFS catches silent corruption, and it only catches it if the scrub actually runs.

Step 8: Alerts, Then Get the Data Off the Box

Configure an alert channel under System Settings so SMART warnings, failed scrubs, and degraded pools reach you somewhere you will actually look. A degraded pool nobody notices is a single drive failure away from a dead one.

Then build a real backup. This is where first NAS builds most often stop, and it is the step that matters most:

TrueNAS has built-in replication and cloud sync tasks, and both are good. If you would rather run the backup from a machine that is not the NAS, restic for homelab backups covers the encrypted-off-site pattern, which is the shape I would use for the data you cannot re-download.

What To Skip On A First Build

Things that look important and are not, yet:

Get the pool layout right, the snapshots scheduled, the alerts delivered, and a copy off the box. That is a NAS you can rely on, and it is most of the value TrueNAS has to offer.