Quick Summary (TL;DR): For a reliable DIY NASPriceAliExpress price, install the stable TrueNAS Community Edition 25.10.x on a dedicated internal SSD, connect the storage disks through native SATA ports or a genuine pass-through HBA, and create a ZFS mirror or RAIDZ pool only after confirming every disk by model and serial number. As of 10 October 2026, 25.10.7 is the current maintenance release listed by TrueNAS; TrueNAS 27-RC.1, released on 6 October, is pre-release software, not the default choice for irreplaceable files. A practical four-bay starting point is four equal-capacity CMR NASAliExpress price HDDs in RAIDZ2 if two-disk fault tolerance matters, or two mirrored pairs when small-file performance and simpler incremental expansion are priorities. Keep the boot device separate from the data disks, create datasets rather than sharing the pool root, configure alerts and backups, and test a restore. ZFS redundancy is not a backup.
Before You Start: Which TrueNAS Edition and Release?
This guide covers bare-metal TrueNAS Community Edition, the Linux-based platform formerly known as TrueNAS SCALE. It does not describe legacy TrueNAS CORE, installing TrueNAS as a Proxmox guest, or building an Unraid array. Those are different projects with different disk-access assumptions.
The version matters. TrueNAS’s software status page lists 25.10.7, dated 2 September 2026, as the maintenance release for the established 25.10 line. TrueNAS announced on 5 October that the development line previously called 26 would be renamed TrueNAS 27; the 27.0.0-RC.1 release followed on 6 October. An RC is intended for evaluation, not a conservative family-photo or business-backup NASAliExpress price. Check the software status page again when installing, rather than blindly using the largest version number.
For a first build, download the supported Community Edition installer from the official TrueNAS site and use the documentation matching the release actually installed. Menu names and pool-wizard options can change between releases.
| Decision | Recommended starting point | Why |
|---|---|---|
| Software | Stable TrueNAS 25.10 maintenance build | Documented, maintained production branch as of 10 October 2026 |
| Installation | Bare metal | Direct visibility of controllers and individual drives |
| Boot | Separate 120–256GB SATA or NVMe SSD | Widely available sizes; avoids wasting an HDD bay on the OS |
| Memory | 16GB for a modest new build; 8GB is the documented minimum | Leaves more headroom for ARC, sharing and routine services |
| Storage connection | Motherboard AHCI SATA or suitable HBA in IT/pass-through mode | ZFS needs reliable access to individual disks and errors |
| Data pool | Mirror, RAIDZ1 or RAIDZ2 chosen for the actual risk | Layout affects fault tolerance, capacity and future expansion |
| Backup | Independent local/off-site copy | Protects against deletion, theft, malware and pool-level failure |
The 16GB recommendation is a practical planning choice, not a claimed TrueNAS minimum. The official 25.10 hardware guide specifies a 64-bit x86 processor, at least 8GB RAM and a 16GB SSD boot device. A consumer 120GB or 240GB SSD is simply easier to source and leaves space for boot environments. Buying a 1TB boot SSD will not turn the remaining space into a normal data-pool drive.
Hardware Checklist: What Actually Matters for ZFS
A DIY NAS is not just a PC with lots of disks. Before installing, check the entire storage path: motherboard chipset, SATA controller, PCIe slot, backplane, power supplyPrice, cables and drive model. A CPU that supports virtualisation or a board advertised as having six SATA sockets tells you little about how those sockets are wired.
| Component | Practical choice | Check before buying or installing |
|---|---|---|
| CPU/motherboard | Supported x86-64 Intel or AMD board | BIOS support, NIC driver, available PCIe lanes, actual SATA controllers |
| RAM | 16GB or 32GB for most four-to-eight-bay home builds | ECC only if CPU, board and memory configuration all support it |
| Boot SSD | One internal SATA/NVMe SSD; optional mirrored boot SSD | Dedicated device, free port/slot, firmware boot support |
| Data HDDs | Identical-capacity CMR drives preferred | Exact model/recording method, warranty, workload and bay cooling |
| SATA/SAS path | Onboard AHCI or HBA presenting each disk directly | No RAID virtual volume; SMART, serial numbers and error reporting work |
| Case/backplane | Bays with unobstructed airflow | Hot-swap wiring, drive vibration, fanPrice control, SATA/SAS connector type |
| PSU | Quality unit sized for disk spin-up and CPU peak | 12V/5V connectors, SATA power leads and headroom; not just idle watts |
| Network | Reliable 1GbE or 2.5GbE to start | Real NIC support, switch port speed, cable, fixed/reserved IP |
| UPS | Appropriately sized UPS with supported shutdown path | Runtime at measured load and USB/network monitoring compatibility |
ECC memory: ECC is an additional protection against memory errors, not a prerequisite for ZFS to function. Do not assume a Ryzen or Xeon processor guarantees ECC end-to-end: check the motherboard QVL, firmware and memory type. If the choice is between an untested ECC combination and a well-supported non-ECC platform with a real backup plan, prioritise a reliable, supported build and backups.
CMR versus SMR: TrueNAS advises against shingled magnetic recording (SMR) drives for normal ZFS pools because sustained rewriting and resilver operations can behave poorly. Confirm the exact drive model with the manufacturer; product-family names alone do not guarantee recording technology. Mixing SSDs and HDDs inside the same data VDEV is generally a poor way to accelerate a home NAS.
Drive ports: Some M.2 sockets share lanes with SATA ports and disable particular ports when populated. Other inexpensive NAS boards connect multiple SATA ports through a PCIe-to-SATA bridge. Neither is automatically unusable, but you must know which controller and link you are buying. For the broader hardware trade-offs, see our DIY NAS motherboard comparison.
SATA Controller, HBA or Hardware RAID?
Use direct disk access. On a normal consumer motherboard, configure the SATA controller in AHCI mode rather than an Intel RST/RAID mode that hides drives behind a virtual array. For additional bays, choose an HBA supported by the installed TrueNAS/Linux kernel and flashed/configured for IT (initiator target) or equivalent pass-through mode. An LSI/Broadcom SAS HBA can be suitable, but its exact chip, firmware, cooling, PCIe slot and connector breakout cables matter.
| Storage path | TrueNAS suitability | Common trap |
|---|---|---|
| Chipset SATA in AHCI mode | Good default for 2–6 drives | SATA ports disabled by an M.2 slot or shared lane |
| Well-supported SATA expansion card | Can work for modest arrays | Weak bridge, flaky power management or poor error recovery |
| SAS HBA in IT mode | Good for many drives when properly supported | Wrong firmware, missing airflow, incompatible cables |
| Hardware RAID virtual disk | Avoid for ZFS data disks | TrueNAS sees a virtual device, not each physical disk |
| USB multi-bay enclosure | Not a preferred primary pool | Bridge resets, changing disk identities, SMART limitations |
Do not rely on a RAID controller’s battery-backed cache to compensate for opaque disk access. ZFS already manages checksums, redundancy and recovery; it benefits from seeing the real disks. The installer can succeed even with an unsuitable controller, so successful installation is not proof that the storage topology is sound.
Plan the Pool Before You Install Anything
ZFS groups disks into virtual devices (VDEVs) and groups VDEVs into a pool. A mirror VDEV duplicates blocks across drives; a RAIDZ VDEV stores data plus parity across its member drives. When a pool contains multiple data VDEVs, loss of any one whole data VDEV can lose the entire pool. That is why the redundancy of each VDEV matters more than a reassuring overall drive count.
| Layout using equal-size disks | Approximate nominal data capacity | Disk-failure tolerance within VDEV | Typical reason to choose it |
|---|---|---|---|
| 2 × 8TB mirror | 8TB | One of the two drives | Simple first pool; good random I/O |
| 4 × 8TB as two mirrored pairs | 16TB | One disk per mirror; not any two | Expand later by adding another mirror VDEV |
| 4 × 8TB RAIDZ1 | 24TB | One drive | More capacity, but narrower failure margin |
| 4 × 8TB RAIDZ2 | 16TB | Any two drives | More fault tolerance during rebuilds |
| 6 × 12TB RAIDZ2 | 48TB | Any two drives | Capacity-oriented six-bay home NAS |
Capacity figures are decimal, simplified planning numbers, not what the TrueNAS dashboard will display. For example, 16TB decimal is about 14.55TiB before ZFS metadata, reserved space, filesystem overhead and practical free-space headroom. Do not promise that a 4 × 8TB RAIDZ2 pool will hold 16TB of files. Compression also makes actual usable capacity workload-dependent.
Mirror or RAIDZ2 for a four-drive NAS?
For important home data and four equal HDDs, RAIDZ2 is a sensible fault-tolerance-first default: it can survive any two drive failures in that VDEV. Two mirrored pairs can provide better small random I/O characteristics and let you add another mirror VDEV later; however, the wrong pair of two failed disks can still destroy the pool. RAIDZ1 offers more nominal capacity, but one drive failure leaves no further disk-failure margin during replacement. None of these protects against accidentally deleting an entire dataset.
A single-disk stripe is useful only for disposable data or a lab. Never interpret the ability to create a pool with one disk as a recommendation to store your only copy of valuable files there.
Can you expand RAIDZ later?
Yes, modern TrueNAS supports RAIDZ VDEV expansion by adding a disk to an existing RAIDZ VDEV. This is an important improvement over older advice that a RAIDZ width can never change. It does not increase parity level: expanding RAIDZ1 still leaves one-disk fault tolerance. Existing data can retain the original parity-width efficiency until rewritten, so expanded capacity may not equal a freshly created, wider RAIDZ VDEV. Check the pool’s health and backup before starting any expansion. See the TrueNAS 25.10 pool-management guide.
Step 1: Assemble and Inspect the Hardware
Install the boot SSD and data drives with the power disconnected. Fit the motherboard, PSU and fans; check the SATA power connectors are fully seated and avoid overloaded splitter chains. Route cables away from fans. If you are using a SAS HBA, ensure it receives airflow: server HBAs often assume a strong front-to-back chassis fan stream that a quiet desktop case may not provide.
Before first boot, record the serial number, physical bay and cable/controller port of each HDD. A simple label such as bay1 → serial XYZ... saves substantial time when TrueNAS later reports a failed drive. Do not identify disks by Linux names such as /dev/sda alone; these can change after a reboot or controller rearrangement.
Power on and enter UEFI/BIOS. Confirm all installed disks appear with expected capacities. Check that the boot SSD is separate from the data HDDs, and that SATA is in AHCI/direct-access mode. Disable Secure Boot or select the board’s compatible ‘Other OS’ setting if required by the TrueNAS installer. Use UEFI boot where supported. Update motherboard/HBA firmware only from trusted vendor instructions, preferably before populating the pool.
Step 2: Download and Verify the TrueNAS Installer
Download the stable Community Edition ISO from TrueNAS. Verify the file’s published SHA-256 digest when supplied by the download page; do not copy a hash from an unrelated blog. Keep a note of the exact version and installer filename in your build log.
On Linux, you can calculate a checksum with:
sha256sum TrueNAS-*.iso
On Windows PowerShell, use:
Get-FileHash -Algorithm SHA256 .\TrueNAS-*.iso
Compare the output to the official checksum for that exact download. A matching checksum checks integrity; it does not replace downloading from a trusted source.
Write the ISO to a temporary installer USB stick using a reputable image-writing tool. The installer USB is not the permanent boot device. If using Linux dd, identify the entire target USB device carefully with lsblk first: a wrong of= path can erase a data disk. A GUI writer with a clear removable-device selection is often safer for a first installation.
Step 3: Install TrueNAS on the Dedicated Boot SSD
- Disconnect any disks containing existing data you cannot afford to erase. For a new build, consider temporarily disconnecting the blank data HDDs as well; this makes choosing the boot target much less error-prone.
- Boot from the installer USB in the firmware boot menu.
- Select Install/Upgrade and choose the intended boot SSD by model and capacity. The selected destination will be erased.
- Follow the prompts to create the administrative user (in the documented 25.10 installer,
truenas_admin) and a strong unique password. Do not reuse a normal file-share account as your administrator. - Select the correct UEFI/legacy option for your hardware. Complete installation, shut down/reboot and remove the installer USB.
- Reconnect the data HDDs if you disconnected them. Set the permanent boot SSD as the first boot device.
Do not install TrueNAS on a member of the planned storage pool. The OS boot device is managed separately and cannot be casually reused as a normal data disk. TrueNAS can support mirrored boot devices, but a second boot SSD is an availability choice, not a substitute for saving the system configuration. A single reliable SSD plus a secure configuration backup is often a reasonable home setup.
After the first boot, the console should display the system’s management address. If it does not, check the network cable, NIC detection and DHCP server. Keep the monitor/keyboard connected until you have verified web access.
Step 4: Secure the Management Network
From another device on the same trusted LAN, open the address shown by the TrueNAS console. Sign in with the administrator created during installation. Use the exact scheme/address shown by the installed version and heed any certificate warning only after confirming that it is your own NAS.
A DHCP reservation on your router is often the simplest way to keep a stable NAS address; alternatively configure a static address in TrueNAS with the correct gateway and subnet. Do not set a static address that conflicts with the router’s DHCP pool. Write down the management IP, host name, gateway and DNS settings before changing them, because a wrong setting can lock you out remotely.
Never forward the TrueNAS web administration port directly from the public internet. Use a secure VPN for remote administration and keep management separate from guest/IoT networks where practical. Apply supported maintenance updates after checking the release notes and saving the configuration.
Step 5: Confirm the Disks TrueNAS Can Actually See
Open the Storage/Disks views (labels may vary slightly by release) and inspect every physical drive’s model, capacity and serial number. Confirm the data disks appear individually, not as one virtual RAID volume. Compare the on-screen serial numbers with your bay map. Look for unexpected small capacities, duplicate identifiers, missing drives or SMART information that cannot be read.
For a new disk, a baseline health check is worthwhile. Inspect SMART information, temperatures and error counts; consider a long SMART self-test or manufacturer-supported surface validation before trusting it with your only copy of data. Such tests take time and may stress a failing drive. Do not run destructive burn-in tools against a drive with existing data. The TrueNAS UI and supported SMART tools can help identify suspect disks, but passing a test cannot guarantee a future failure-free life.
If disks intermittently disappear, stop before creating the pool. Investigate SATA power, data cables, controller firmware, HBA temperature and backplane connections. Creating a pool over an unstable link makes later troubleshooting far harder.
Step 6: Create the First ZFS Storage Pool
Open Storage → Create Pool (or the equivalent Storage dashboard action for your release). Choose a short, descriptive name such as tank or vault; pool names should be planned because renaming is not a routine button-click operation. For a four-drive home NAS, the following is a safe example only if the four HDDs are blank and intended for the new pool:
- Choose the four matching 8TB HDDs by serial number. Do not select the boot SSD.
- Select RAIDZ2 as the data VDEV layout. Confirm the wizard shows four HDDs in the same RAIDZ2 data VDEV.
- Leave deduplication disabled unless you have a measured, specialist requirement. Ordinary compression can be useful, but it does not justify optimistic capacity assumptions.
- Leave optional special metadata, cache (L2ARC), log (SLOG), spare and dedup VDEVs out of the first build. They are not required to make a safe basic pool; misconfiguring a special VDEV can create additional pool-level risk.
- Review the drive list and redundancy again. The creation action erases the selected disks. Confirm only when you have verified the layout and backup situation.
- Wait for creation to finish and check that the pool is ONLINE and the expected drives appear in its VDEV view.
The TrueNAS wizard distinguishes pool, data VDEV and optional supporting VDEVs. A second RAIDZ2 VDEV added to the same pool is not a ‘backup RAIDZ2’: ZFS stripes across data VDEVs and the pool depends on all of them. Do not add an unprotected single-disk data VDEV to a redundant pool merely to gain space.
What about encryption?
Decide before filling the NAS with data. If you need encryption at rest, follow TrueNAS’s current guidance on encrypted datasets, key storage and recovery. A strong encryption key that exists only on the NAS is a single point of failure. Save and test the required keys/recovery material off the NAS, securely. Encryption does not protect against accidental deletion while the dataset is unlocked.
Step 7: Create Datasets, Not a Share of the Pool Root
The root of a pool is a management boundary, not a good general-purpose shared folder. Create separate datasets for different uses so you can control permissions, snapshots, quotas and replication independently.
| Dataset example | Purpose | Suggested preset / consideration |
|---|---|---|
vault/family | Personal documents and photographs | SMB dataset; restricted user/group ACL |
vault/media | Films, music and media-library files | SMB if shared to clients; avoid broad write access |
vault/backups | Client-computer backup targets | Dedicated credentials, quota and retention policy |
vault/apps | Application data if using supported apps | Apps preset where appropriate; separate from media |
In the 25.10 interface, open Datasets, select the parent pool and choose Add Dataset. For Windows/macOS file sharing, use the appropriate SMB preset, which configures suitable ACL/case-sensitivity defaults. For application storage, follow the application’s own dataset requirements. Some dataset choices, including case sensitivity, are difficult or impossible to change in place after creation.
Do not turn on every ZFS feature because it exists. Keep recordsize and other tuning at defaults until a workload demonstrates a need. In particular, do not disable synchronous writes to make benchmarks look better: that changes durability guarantees when power fails.
Step 8: Make a Small SMB Share and Test It
A first share is a practical end-to-end test of disks, pool, permissions and networking. Create a normal non-admin user with SMB access enabled; built-in TrueNAS administrator accounts are not general SMB file-sharing identities. Create a share pointing to vault/family, configure the dataset ACL to grant the intended user/group access, and start the SMB service when prompted.
From Windows File Explorer, connect using \\NAS-IP\family (substitute the actual share name and IP). On macOS, use Finder’s Connect to Server with smb://NAS-IP/family. Copy a small folder, read the files back, rename one file and test that a user without permission is denied. A share that appears in network discovery but refuses access usually has an ACL/user issue, not a ZFS pool problem.
Keep the first SMB configuration simple. Do not enable guest/anonymous write access as a shortcut. Avoid opening the SMB port to the internet. When using Windows, confirm the NAS and client negotiate a modern SMB dialect rather than trying to resurrect SMB1.
Step 9: Set Up Protection Before Moving Your Real Data
A healthy RAIDZ2 pool is only the first layer. Put snapshots, alerts, backups and a recovery test in place before migrating your photo archive.
| Protection | What it catches | What it does not catch |
|---|---|---|
| ZFS mirror/RAIDZ redundancy | A defined number of failed disks in the same VDEV | Deletion, ransomware, theft, fire, pool-wide failure |
| ZFS checksums and scrub | Detects corruption; repairs it when valid redundant copies exist | Loss beyond available redundancy; deleted data |
| Snapshots | Previous states of datasets; useful against accidental edits/deletion | NAS theft, all disks failing, compromised snapshot retention |
| Independent backup/replication | Data recovery after source loss when configured correctly | Errors that are never detected/tested, insufficient retention |
| UPS and clean shutdown | Reduces interruption risk | Storage failures, human error, malware |
Configure alert delivery and verify it by sending a test notification. Review the pool’s scrub schedule rather than assuming the default is right for your disks and workload. In current 25.10 documentation, TrueNAS provides a scheduled scrub mechanism; the threshold-days setting prevents a scrub running on every scheduled trigger. Allow heavy scrubs and SMART long tests to run at sensible times.
Create a snapshot task for each important dataset, with retention that matches how often the data changes. For example, hourly snapshots retained for a day plus daily snapshots retained for several weeks can help with ordinary mistakes; these are illustrative retention choices, not a universal rule. Snapshots on the same pool do not count as an independent backup.
Replicate or back up to a second NAS, a rotated external disk or a trusted off-site target. Protect backup credentials and retention from the same account that can delete production files. Finally, restore several real files to a different location and open them. A backup job reporting success is not proof that the restore procedure works.
Step 10: Save the TrueNAS Configuration and Recovery Information
Download a system configuration backup using the installed version’s configuration/export facility. This is not a backup of the files in your pool: it preserves system settings and helps rebuild the boot environment after SSD failure. Store the configuration securely outside the NAS, along with your pool layout, serial-to-bay map, network settings, any encryption recovery keys and the software version.
If the configuration export offers a password-secret seed or related sensitive key material, understand the security implications before including it. A backup containing decryptable secrets must be protected like credentials. Test that you can locate your recovery information without logging into the NAS that may have failed.
After any major change—new users, SMB shares, networking, replication tasks or application configuration—take a fresh configuration backup. Avoid storing the only copy of that backup on the pool it is meant to help recover.
Common First-Install Problems and What to Check
| Symptom | Most likely areas to inspect | Safer next step |
|---|---|---|
| Installer USB will not boot | Wrong UEFI entry, Secure Boot, faulty USB image | Recheck ISO checksum and firmware boot options |
| Installer cannot see boot SSD | BIOS storage mode, NVMe slot support, disabled SATA port | Verify device in BIOS; do not choose a data HDD instead |
| TrueNAS boots but no web UI | No DHCP, unsupported NIC, wrong VLAN/subnet | Read console IP and router lease table; test a direct LAN route |
| Only one large ‘disk’ appears | RAID controller exposing a virtual volume | Stop; configure proper pass-through before creating a pool |
| HDD vanishes under load | Cable, power splitter, controller reset, HBA heat | Inspect hardware and logs; do not keep rebuilding blindly |
| Pool capacity is lower than expected | TB versus TiB, parity, ZFS overhead | Compare against the actual VDEV layout and reserve headroom |
| SMB share visible but access denied | User lacks SMB access or dataset ACL rights | Check SMB user, share path and dataset permissions separately |
| Pool says DEGRADED | Drive/controller error or missing member | Identify disk by serial; check backups before replacement |
| Slow copying over 1GbE | Network link or client, not necessarily disks | Check negotiated link speed and compare wired local transfers |
| Cannot expand as expected | VDEV topology, version, disk size, free bays | Review documented RAIDZ extension or add a compatible VDEV |
Do not initialise, wipe or replace a disk just because its /dev/sdX name changed. Match serial numbers and pool membership first. A wrong-disk replacement can turn a recoverable degraded pool into an unrecoverable one.
A Sensible First-Build Cost and Power Budget
TrueNAS Community Edition does not require a normal software licence purchase for this installation, but the complete NAS certainly is not free. A fair build comparison includes the case, motherboard/CPU, RAM, boot SSD, data HDDs, PSU, fans/cables, optional HBA/networking, UPS, backup media and electricity. Your labour, warranty route and replacement drives also matter. See our DIY versus prebuilt NAS ownership comparison for the purchasing decision rather than treating this setup guide as a product ranking.
For power, calculate average measured wall draw, not CPU TDP. At an illustrative electricity rate of £0.25/kWh, a NAS averaging 50W continuously uses 0.050 × 24 × 365 = 438kWh/year, costing £109.50/year or £547.50 over five years before tariff changes. A 70W average raises that illustrative five-year electricity cost to £766.50. The £219 difference is real arithmetic, but neither wattage is a benchmark for any particular DIY board.
A useful ownership worksheet is: case + board/CPU + RAM + boot SSD + (number of HDDs × price per HDD) + PSU/cooling/cables + controller/NIC + UPS + independent backup + electricity + expected replacements. Fill it with current UK quotes and measured or credibly estimated wall consumption. If you already own a suitable chassis or drives, distinguish sunk cost from new spending, but do not omit the cost of protecting the data.
Final Pre-Migration Checklist
- The installed release is a stable, supported TrueNAS Community Edition build, not an experimental RC used by mistake.
- The boot SSD is separate from the ZFS data pool and its configuration is backed up.
- Every HDD is visible by unique serial number and mapped to a physical bay.
- The chosen mirror/RAIDZ layout has the fault tolerance you intended.
- The pool is ONLINE; disk health and alert delivery are checked.
- You have created child datasets with sensible SMB/user permissions.
- Snapshots and an independent backup are scheduled.
- You have successfully restored sample files to another location.
- The management UI is reachable only through your trusted LAN/VPN, not an exposed internet port.
If you have reached this point, you have a defensible foundation for a home NAS. Add applications, more demanding network services or advanced ZFS devices only after the basic storage and recovery path has proved reliable. For component expansion decisions, revisit our Intel N150 vs Core i3 vs AMD NAS motherboard guide.
Official Documentation and Further Reading
- TrueNAS Software Status and release recommendations — check the supported stable version before installation.
- TrueNAS 25.10 Hardware Guide — minimum requirements, memory, drives and storage considerations.
- TrueNAS 25.10 installation guide — boot media, firmware settings and installer steps.
- TrueNAS 25.10 pool creation and storage setup — VDEVs, datasets and pool wizard.
- TrueNAS 25.10 pool management and RAIDZ expansion — growth and disk-management caveats.
- TrueNAS 25.10 SMB sharing — SMB users, ACLs and share access.
- TrueNAS 27 renaming announcement (5 October 2026) — explains why the 27-RC.1 release is not the same as a stable 27.0 release.