How to Convert an Old PC into a Custom NAS with TrueNAS
An old desktop can become a capable network-attached storage system with TrueNAS, a few reliable drives, and a careful setup. This approach can cost less than buying a prebuilt Synology or QNAP NAS while giving you greater control over storage pools, backups, media services, and network sharing.
A custom NAS is especially useful when an unused PC already has a suitable case, power supply, and expansion slots. However, age alone does not determine whether a computer is a good candidate. Drive compatibility, power consumption, noise, cooling, and long-term reliability matter just as much as processor speed.
TrueNAS SCALE is the most practical choice for many new builds because it combines the ZFS file system with a web interface, SMB sharing, snapshots, replication, and applications. The conversion process is straightforward, but storage planning should come before installation.
Choose The Right Donor PC
Almost any modern 64-bit desktop can run TrueNAS SCALE, but a machine that was acceptable for office work may not be ideal for continuous storage duties. A 64-bit processor with multiple cores is preferred, while 8 GB of RAM is a reasonable starting point for a basic system. For several drives, virtual machines, or applications, 16 GB or more provides a better margin.
Memory that supports error correction, or ECC, is valuable because ZFS checks data integrity as information moves through the system. ECC is not mandatory for a home NAS, particularly when reusing ordinary desktop hardware, but a compatible motherboard and processor can improve confidence in a business or always-on installation.
Check the number of SATA ports before buying disks. Older systems may have only four motherboard ports, while a PCIe Host Bus Adapter can add more connections. Use an HBA that can operate in IT mode, which passes individual drives directly to TrueNAS instead of hiding them behind a hardware RAID layer.
Power consumption also deserves attention. An old tower may draw substantially more electricity than a newer low-power platform. Replace damaged fans, clean dust from the heat sinks, and inspect the power supply for age-related problems. A failing power supply can corrupt data or cause unexplained drive dropouts.
Prepare Drives And Network Hardware
TrueNAS should have a dedicated boot device rather than sharing a disk intended for the storage pool. A small, reliable SSD is preferable to an old USB flash drive, which may wear out quickly under system updates and logging. The boot device does not need to be large, but it should be treated as an important component and backed up through the TrueNAS configuration export.
The data drives should be similar in capacity and performance when possible. Mixing disks is supported, but the smallest drive generally limits usable capacity in a redundant vdev. Avoid using disks with known bad sectors, excessive operating hours, or a history of disconnecting. Run manufacturer diagnostics before placing older drives into service.
Give the NAS a wired Ethernet connection. Gigabit networking is enough for general file storage, backups, and HD media streaming, while 2.5GbE or faster networking makes more sense when several computers move large video files or work directly from shared storage. Set a DHCP reservation on the router so the NAS keeps a predictable local address.
Do not connect the NAS to the internet by exposing its administration port. Remote access is safer through a VPN or a carefully configured private-access service. The TrueNAS dashboard should be reachable only from trusted networks.
Install TrueNAS SCALE
Download the current TrueNAS SCALE installer from the official source and write it to a bootable USB installer. During installation, select the dedicated boot SSD as the target. Every disk selected for installation can be erased, so disconnect or clearly identify important drives before proceeding.
After the first boot, TrueNAS displays an address for its web interface. Open that address from another computer on the same network, create a strong administrator password, and complete the initial network settings. Change the default system name to something recognizable, such as “HomeNAS” or “MediaVault,” so it is easy to identify among other devices.
Update TrueNAS before creating services or importing data. Then record the hardware layout, drive serial numbers, and network configuration. Export the system configuration and store a copy on a separate computer or cloud location. This backup does not contain the stored files, but it can make rebuilding the NAS much faster after a boot device failure.
The installation interface may offer several storage and application choices. Keep the first deployment simple. A stable file server with tested backups is more useful than an overloaded system running services that have not been configured or maintained properly.
Build A ZFS Storage Pool
ZFS organizes physical disks into virtual devices, commonly called vdevs, which are combined into a storage pool. A mirror uses two drives and tolerates one drive failure. RAIDZ1 uses at least three drives with single-drive parity, while RAIDZ2 generally requires four or more drives and can tolerate two failed drives.
Usable capacity is lower than the total advertised disk capacity because of parity, formatting, reserved space, and the recommendation to avoid filling a pool completely. Keeping roughly 20 percent free space helps maintain performance and gives ZFS room for normal operations. The exact usable figure depends on drive size and vdev layout.
| Storage Layout | Minimum Drives | Drive Failure Tolerance | Best Fit |
|---|---|---|---|
| Mirror | 2 | 1 per mirror | Small pools and easy expansion |
| RAIDZ1 | 3 | 1 per vdev | Moderate capacity with limited risk |
| RAIDZ2 | 4 | 2 per vdev | Valuable data and larger arrays |
| Single Disk | 1 | None | Temporary or noncritical storage |
Create datasets rather than placing every file directly in the root of the pool. Separate datasets for documents, media, computer backups, and applications allow different compression, sharing, snapshot, and quota settings. ZFS compression with a setting such as LZ4 is generally useful for documents and many general-purpose files, while it provides little benefit for already compressed videos, photographs, or archives.
Do not confuse redundancy with backup. A RAIDZ pool can remain available after a drive failure, but it cannot protect against accidental deletion, malware, theft, fire, or a serious hardware failure. Important data needs at least one additional copy outside the primary pool.
Configure Shares And Services
For Windows, macOS, and Linux computers, SMB shares are usually the simplest starting point. Create a dedicated user account for each person or service, assign access to the appropriate dataset, and avoid using the administrator account for routine file access. Clear permissions are easier to troubleshoot than a broad share that grants everyone access to everything.
Snapshots provide point-in-time versions of files and can help recover from accidental changes or ransomware. Set a schedule that matches the data: frequent snapshots for active documents and less frequent snapshots for media libraries. Snapshots consume space as changed blocks accumulate, so establish automatic retention limits.
TrueNAS can host applications such as Jellyfin, Plex, Syncthing, Nextcloud, and backup tools, depending on the current SCALE application ecosystem. Install only what the hardware can support. A media server may run comfortably on a modest processor for direct playback, but video transcoding can require considerably more CPU or a supported graphics processor.
SSD caching is often misunderstood. A cache drive does not automatically make every NAS workload faster, and it can add complexity or reduce available capacity. Improve the network, use adequate RAM, and organize datasets correctly before considering a special cache device. For many homes, mirrored SSD storage for frequently used virtual machines or applications offers more predictable benefits.
Protect And Maintain The NAS
Schedule regular SMART tests and configure alerts for drive health, temperature, pool status, and failed tasks. Short tests can run frequently, while extended tests can be scheduled less often when the NAS is not busy. Replace a suspicious disk before it becomes an active failure whenever possible.
A UPS is a worthwhile addition for a custom NAS. It gives the system time to shut down cleanly during a power outage and protects against short voltage interruptions. Connect the UPS through USB or a supported network protocol, then configure TrueNAS to react automatically when battery power reaches a defined threshold.
Test restoration, not just backup completion. Copy a selection of files back from the secondary location, verify permissions, and confirm that important applications can use the restored data. A backup that has never been recovered is an assumption rather than a proven safeguard.
Keep the operating system, applications, router firmware, and drive firmware maintained, but avoid making major changes immediately before an important trip or business deadline. Save configuration exports after significant changes, document the pool layout, and label drive bays so a replacement can be installed correctly.
Practical Build Recommendations
A reliable custom NAS is usually the result of conservative decisions rather than maximum specifications:
- Use a dedicated SSD for TrueNAS and keep a recent configuration backup offline.
- Select mirror or RAIDZ storage according to the value of the data, not simply the amount of capacity required.
- Connect the system by Ethernet and reserve its address in the router.
- Create separate datasets and user accounts for documents, media, backups, and applications.
- Add a UPS and maintain an independent backup that cannot be damaged by a failed NAS or ransomware.
When the hardware is old, begin with essential file sharing and monitoring before adding media servers, cloud synchronization, or virtual machines. This staged approach makes it easier to identify whether a problem comes from the operating system, a drive, the network, or an application.
A recycled PC can deliver impressive NAS performance, but its greatest advantage is flexibility. You can expand services, replace components, and tailor storage policies to your household or organization instead of accepting the limits of a fixed appliance.
Gather the donor PC’s specifications, test every drive, and map out your backup destinations before installing TrueNAS. With a deliberate ZFS layout, secure accounts, monitored hardware, and a tested second copy of important files, that unused computer can become a dependable central storage platform.