How To Turn Old PC Into NAS | Fast NAS Setup No Fuss

How To Turn Old PC Into NAS means installing a NAS OS, adding storage drives, and sharing folders so every device can save and stream files.

An old desktop can make a solid NAS if it still boots, has steady power, and can take a couple of drives. You end up with one box that stores photos, videos, project folders, and phone backups, then serves them to your whole home network.

This walkthrough keeps things practical. You’ll check the hardware, pick a NAS operating system, install it, set up storage, then create shares you can reach from Windows, macOS, and phones.

What A NAS Does And Why An Old PC Works

A NAS is a computer that stays on and presents storage over your network. Most people use it for file sharing and backups, but it can also run a media library, sync folders between devices, and store camera uploads from phones.

Using an older PC has a couple of perks. You get real upgrade options, standard parts, and room for full-size hard drives. You also get a screen-and-input setup when something goes wrong, which can save a lot of frustration.

Centralize files — Put scattered folders from laptops, desktops, and phones into one set of shared folders.
Run automatic backups — Schedule backups from PCs and Macs so you don’t rely on memory.
Stream media — Serve videos and music to TVs, tablets, and media boxes on the same network.
Share with permissions — Give each person their own space, plus shared areas for family or work.

Hardware Check Before You Start

Start with a quick reality check. A NAS doesn’t need gaming horsepower, but it does need stability. If this PC blue-screens, locks up, or has random restarts, fix that first or pick different hardware.

Minimum hardware that feels good

Use a 64-bit CPU — Any mainstream Intel or AMD 64-bit chip from the last decade is fine for file sharing.
Have enough RAM — 8 GB is a comfortable starting point for most home file sharing; more helps with ZFS, apps, and caching.
Prefer wired Ethernet — Gigabit Ethernet is the baseline for smooth transfers; Wi-Fi adds hiccups and slower real-world speed.
Count SATA ports — Make sure you have enough ports for your data drives plus a separate boot drive.

Drives and connections to check

Plan for at least two storage drives if you care about uptime. One drive works, but a single disk is a single point of failure. A mirror (two drives with the same data) is the simplest way to keep the NAS running after a disk dies.

Choose CMR hard drives — Many SMR models slow down hard during rebuilds; CMR drives behave better in multi-disk arrays.
Add a small boot SSD — Install the NAS OS on a separate SSD so your storage drives stay dedicated to data.
Check the power supply — Old, low-quality PSUs can cause weird data corruption and random resets when drives spin up.
Think about cooling — Hard drives like steady airflow; a front intake fan makes a bigger difference than most people expect.

Simple power and noise tweaks

If this NAS will sit near a desk or TV, noise matters. A dusty case fan can turn a quiet build into a constant buzz. A NAS also runs longer hours than a normal PC, so clean airflow is worth the time.

Clean the case — Blow out dust from heatsinks, intake grills, and the power supply intake.
Swap loud fans — A modern 120 mm PWM fan can drop noise without hurting cooling.
Use rubber mounts — Drive vibration can travel through the case; rubber grommets help.
Set a sane fan curve — In BIOS, use a quiet profile that still ramps up under sustained drive activity.

Turning An Old PC Into A NAS With Free Software

Your software choice shapes the whole experience. Some NAS systems are “appliance style” with a web dashboard that controls storage, shares, and user accounts. Others are a normal Linux install where you add storage services yourself.

If you want a clean, dedicated NAS feel, start with one of the web-managed options. If you already like Debian and don’t mind setting things up by hand, an existing Linux install works fine too.

Option	Best For	Notes
TrueNAS SCALE	File shares plus apps	Linux-based, strong storage tools, runs apps and containers with a web UI.
TrueNAS CORE	Pure NAS use	FreeBSD-based, ZFS-first approach, great for straightforward shares and snapshots.
OpenMediaVault	Lightweight home NAS	Debian-based, flexible plugins, friendly web UI that works well on modest hardware.

If you’re new to NAS builds, TrueNAS SCALE is a common first pick because it bundles storage tools and a modern web interface. The official TrueNAS install steps are clear and worth a quick read before you start.

For OpenMediaVault, the official installer flow is also well documented, especially if you’re installing from an ISO and want the cleanest path.

TrueNAS install instructions
and
OpenMediaVault ISO install steps
are the two reference pages that match the setup below.

Install The NAS OS Step By Step

This section uses the common “install from USB” flow that works for TrueNAS and OpenMediaVault. The screens differ, but the rhythm is the same.

Back up anything you care about — Installing a NAS OS can erase drives if you pick the wrong target, so copy off any files you want to keep.
Download the installer ISO — Grab the ISO from the project’s official download page, then save it on your main PC.
Write the ISO to a USB stick — Use a tool like Rufus (Windows) or balenaEtcher (Windows/macOS/Linux) to make a bootable installer.
Plug the NAS into your router — Use Ethernet, not Wi-Fi, so setup and later transfers are stable.
Boot from the USB installer — In BIOS/UEFI, set the USB drive first in the boot order, then restart.
Install to a dedicated boot drive — Pick a small SSD for the operating system. Leave your storage drives untouched for now.
Reboot and find the web dashboard — After install, the screen shows an IP. Type it into a browser on your main PC.

BIOS settings that prevent headaches

Most old PCs boot fine with default BIOS settings, but a couple toggles can save time. If your board has both legacy and UEFI boot, stick to UEFI when the installer offers it.

Enable AHCI — SATA in AHCI mode is the expected choice for most NAS systems and makes drive behavior predictable.
Turn off Fast Boot — This makes it easier to reach the boot menu and spot USB devices.
Disable overclocks — A NAS benefits from stability more than speed, so run stock settings.
Set power loss behavior — Use “Restore on AC power loss” if you want the NAS to come back after an outage.

Create Storage And Shared Folders

Once the web dashboard loads, slow down for a minute. Most mistakes happen here, not during install. Storage settings decide how your data is laid out and how hard drive failure is handled.

Pick a layout that matches your risk tolerance

If you only have one data drive, you can still build a NAS, but treat it like a single external drive on the network. If you have two or more drives, you can trade raw capacity for the ability to survive a drive failure.

Use a two-drive mirror — Two drives store the same data, so you can keep going if one dies.
Use RAIDZ1 with three or more drives — This is closer to RAID5; you get more usable space than a mirror but rebuilds take longer.
Use RAIDZ2 with four or more drives — This tolerates two drive failures and is a calmer choice when using big disks.
Keep one disk for backups — A separate backup drive, even if it’s smaller, beats “no backup” every time.

Create datasets and shares with clean permissions

Many NAS systems let you break a pool into datasets or shared folders with their own rules. This makes it easier to keep family photos separate from work files, or keep a media folder readable by everyone while locking down personal documents.

Create a storage pool — Select your data drives and your chosen layout, then create the pool.
Create datasets or shared folders — Make top-level folders like Media, Backups, and Private.
Create user accounts — Add one user per person, not one shared login for the whole house.
Set ownership and permissions — Give each user access only to the folders they need, then test before you move files.
Create SMB shares — SMB is the usual choice for Windows and works well on macOS too.

Test from a laptop before migrating everything

Do a small test transfer while your folders are empty. If permissions are wrong, it’s painless to fix when you only copied a few files. Once it works, then start moving your main data.

Map the share in Windows — In Windows file browser, map a network drive to the SMB share and sign in with your NAS user.
Connect from macOS — In Finder, use “Connect to Server” and enter smb://NAS-IP/ShareName.
Try a phone upload — Use a file manager app that can log into SMB, then upload a photo album to test real-world use.

Protect Data With Backups And Routine Checks

A mirror or RAIDZ keeps the NAS online during a drive failure. It does not protect you from accidental deletes, ransomware on a PC, or a bad power event that damages multiple drives. Backups still matter.

Backup patterns that work at home

A simple rule is one extra copy that is not always plugged in. An external USB drive you connect weekly is a solid start. If you pay for off-site storage, add a cloud backup job.

Schedule a USB backup — Plug in an external drive, run a nightly or weekly backup task, then unplug it when done.
Use snapshots for quick rollbacks — Snapshots let you restore older versions of files after a mistake.
Keep a second copy of photos — Photos are hard to replace, so store them in two places you trust.
Write down your restore plan — Note where backups live, what tool created them, and how to restore a folder.

Health checks that catch drive trouble early

Most NAS dashboards can run SMART tests, send alerts, and schedule pool checks. Turn these on early so you don’t notice a dying disk only after it fails.

Run SMART short tests — Set a weekly short test to catch obvious issues without heavy load.
Run SMART long tests — Schedule a long test monthly on each drive to scan the surface.
Schedule scrubs — For ZFS pools, a scrub reads data and checks checksums so silent corruption is more likely to get caught.
Set email alerts — Use an inbox you check so warnings don’t sit unseen.

Power protection that saves frustration

A small UPS gives the NAS time to shut down cleanly during an outage. Even a short dip can cause file system repairs on reboot. A clean shutdown keeps drives from being hammered by sudden power loss.

Use a UPS with USB signaling — Pick a model that can tell the NAS when battery is low so it can shut down.
Enable automatic shutdown — Set a low-battery threshold that triggers a graceful power off.
Keep the router on the UPS — If the router stays up, laptops can still reach the NAS during the outage window.

Make Access Fast And Smooth On Every Device

Once shares work, polish the everyday experience. A little naming and network setup now saves “where did the NAS go?” moments later.

Give the NAS a stable IP

If your router changes the NAS IP, saved bookmarks and mapped drives break. Fix it by setting a DHCP reservation in your router or setting a static IP in the NAS network settings.

Reserve the NAS IP in the router — Tie the NAS MAC to one IP so it stays the same after reboots.
Set a clear hostname — A name like HOME-NAS is easier than a string of numbers.
Keep DNS simple — Use the router as DNS for most home networks so name resolution stays consistent.

Use the right share protocol for the job

SMB is the default for mixed-device homes. NFS can be great for Linux boxes and some media players. Many NAS systems let you run both.

Use SMB for Windows and Macs — It integrates cleanly with Windows file browser and Finder.
Use NFS for Linux clients — NFS can feel snappy for Linux-to-Linux file access.
Use SFTP for remote file grabs — SFTP is handy when you need to pull a file from outside your home network.

Remote access without exposing shares to the internet

Don’t forward SMB ports to the public internet. Use a VPN or a private tunnel so file shares stay off the open web.

Use a VPN — Connect your phone or laptop to your home network, then access shares as if you were local.
Use read-only accounts — If a device only needs to stream media, don’t give it write access.
Turn on two-factor login — For web dashboards, enable two-factor if your NAS OS offers it.

First Week Checklist After Your NAS Goes Live

Once the NAS is running, spend a week with light use before you trust it with everything. You’ll spot permission quirks, noisy fans, and slow links while the stakes are low.

Copy a small folder set — Move a few gigabytes first and confirm everything opens correctly from each device.
Watch transfer speed — On gigabit Ethernet, large file copies should feel steady; if speed jumps up and down, check cables and switch ports.
Confirm sleep and wake behavior — If you want the NAS on 24/7, check temps after an overnight run. If you prefer scheduled on/off, test the schedule twice.
Test a restore — Delete a test file, then restore it from a snapshot or backup job so you know the process works.
Label drives and ports — A bit of tape with “Disk 1, Disk 2” helps when a dashboard reports an error on a bay.
Set update habits — Pick a monthly time to apply OS updates, then reboot when you’re home to verify services return.

After that first week, the NAS should feel boring in the best way. Add storage later if you need it.