Unraid Setup Guide: How to Install and Configure Your First Array

Unraid is a NAS operating system that boots from a USB flash drive and combines mixed-size hard drives into a parity-protected array while also running Docker containers and virtual machines on the same machine.

This Unraid setup guide walks through every step we use when commissioning a new archive server: choosing hardware, building reliable boot media, configuring BIOS, assigning parity, and creating the first shares. The goal is a machine you can trust with a growing collection of large datasets, public domain archives, and lossless media for years.

Unraid earned its place in the home lab because it does not demand identical drives. You can start with two disks and add one more next month without rebuilding anything, which matches how most archives actually grow.

Budget roughly 30 to 45 minutes of hands-on work, plus several unattended hours for the first parity sync. Keep a monitor, keyboard, and a spare flash drive nearby before you begin.

Plan the Server and Storage Layout

Ten minutes of planning saves a weekend of rebuilding. Decide how much capacity you need in two years, how many drives your case and power supply can feed, and whether a fast pool device will sit in front of the spinning disks.

Decide Whether Unraid Fits Your Archive Goals

Unraid OS suits collections that grow one drive at a time and sit mostly idle. Files live whole on individual disks, so only the drive holding a requested file needs to spin up, which keeps power draw and noise low.

If you need maximum sequential throughput across every disk at once, a striped pool or a different NAS operating system may serve better. For long-term preservation in a home lab, flexibility usually beats raw speed.

Understand the Difference Between an Unraid Array and RAID

Traditional RAID stripes data across identical members, so losing more disks than your redundancy level destroys the whole set. An Unraid array stores each file entirely on one disk and keeps a separate parity calculation.

That design has a practical consequence we appreciate every time something goes wrong: if the array suffers an unrecoverable failure beyond parity coverage, the surviving disks still mount and their files remain readable.

Choose Hardware, Drives, and a Cache Drive

Any 64-bit x86 machine with ECC or non-ECC memory works, but the case you put it in matters just as much — see our NAS case comparison for hot-swap options that make drive swaps painless. Our baseline hardware recommendation:

Avoid hardware RAID cards and SMR drives, especially for parity. Both cause slow, painful rebuilds.

Compare Starter and Unleashed Licensing Before Installation

Unraid moved to tiered licensing, and the tier you pick caps how many storage devices the server can attach.

• Starter: small builds, currently capped around six attached storage devices, includes one year of OS updates
• Unleashed: unlimited attached devices, one year of OS updates, upgradeable later
• Lifetime: unlimited devices plus perpetual OS updates

Count the boot flash drive, every array disk, and every pool SSD when estimating. Starter licenses can be upgraded to Unleashed by paying the difference, so a two-drive test build is a low-risk starting point.

Unraid Setup Guide: Create Reliable Boot Media

The flash drive is the license anchor, the config store, and the boot device all at once. Spend a few dollars on a decent name-brand stick and label it, because a corrupted boot drive is the single most common failure we see in new builds.

Select a Compatible USB Flash Drive With a Unique GUID

Unraid requires a flash device of at least 4 GB that exposes a unique GUID. That serial is what your license is tied to, so drives without one will refuse to register.

Sweet spot in practice: an 8 GB to 32 GB USB 2.0 stick from a mainstream brand. Larger, faster drives offer no benefit and often run hotter in a rear panel port.

Use the Unraid USB Flash Creator on Windows, Mac, or Linux

The official USB creator is the fastest route. Download the USB Flash Creator for Windows or Mac, insert the drive, choose the Unraid OS release, name the server, and let the tool write and flag the volume as bootable.

Two details matter. Leave the drive label as UNRAID, and pick UEFI or legacy boot to match how your motherboard is configured.

Prepare a Manual FAT32 Boot Device When Needed

When the USB flash creator cannot see your drive, the manual method still works. Format the stick as FAT32 with the volume label UNRAID, extract the Unraid OS archive to the root of the drive, then run the included make_bootable script as administrator on Windows or the equivalent script on Mac and Linux.

Verify that bzimage, bzroot, and the EFI folder sit at the top level, not inside a subfolder.

Avoid Counterfeit and Unreliable SanDisk USB Drives

SanDisk sticks have long been community favorites, but marketplace listings are flooded with counterfeits, and some genuine current models report a blank or duplicated GUID. Either problem blocks licensing.

Buy from a retailer you trust, and keep the receipt. If the server rejects the drive during registration, swap brands rather than fighting it. Once booted, take an immediate flash backup so a replacement takes minutes instead of an evening.

Boot the Server and Complete First-Time Configuration

First boot is mostly firmware work. Get the boot order right, turn on the virtualization features you will want later, then move to the browser and lock down access before touching a single disk.

Set the USB Flash Drive as the Boot Device

Plug the stick into a rear USB 2.0 port on the motherboard, ideally an internal header port if your case has one. Enter firmware setup, then set the flash drive first in the boot order.

Disable Secure Boot, and enable CSM if you wrote the drive for legacy boot. Save, exit, and you should reach the Unraid boot menu within seconds.

Adjust BIOS Settings for Virtualization and IOMMU

Even if virtual machines are not in your plans today, enable them now to avoid a second reboot later:

• Intel: VT-x and VT-d
• AMD: AMD-V (SVM Mode) and AMD-Vi / IOMMU
• Both: Above 4G Decoding for GPU passthrough, and SR-IOV if present

Also set power state after power loss to “Last State” or “On” so the server recovers unattended, and turn off aggressive ErP settings that kill USB power.

Find the Server on Your Network and Secure the Web Dashboard

With the server on Ethernet, open a browser and go to http://tower.local or the IP address shown on the console. The first prompt asks for a root password, so use a long unique passphrase from your password manager.

Then reserve a DHCP address for the server in your router, and keep the dashboard off the public internet. Remote access belongs behind a VPN tunnel such as WireGuard or Tailscale, a point the privacy guides on datahoarder.io repeat for good reason.

Start a Trial or Apply a License

Register the free 30-day trial from the Tools or registration page, or paste the activation code from your purchase. The trial is fully featured, including Docker and virtual machines.

Test everything during the trial: drive detection, temperatures, noise, network speed. If the trial expires while you are still evaluating, extensions are available before you commit money.

Build and Protect Your First Storage Array

Assignment order matters here, and a mistake can wipe data. Read the drive serials carefully on the Main tab, assign parity deliberately, then start the array and let the first sync finish before you copy anything valuable.

Assign Data and Parity Drives Correctly

On the Main tab you will see Array Devices, Pool Devices, and unassigned devices. Assign your largest drive to the Parity slot, then fill Disk 1, Disk 2, and onward with data drives.

Match by serial number, never by size alone. If a drive already contains files you want, do not assign it to parity, because Unraid overwrites parity members completely.

Understand Parity Protection, Drive Failures, and Its Limits

Single parity survives one failed drive; dual parity survives two simultaneous failures. Unraid rebuilds the missing disk by calculating from every remaining member.

Parity is not a backup. It does nothing about accidental deletion, ransomware, a bad power supply frying several drives, or fire and theft. Treat parity as uptime insurance and keep a real copy of anything irreplaceable somewhere else.

Format New Drives and Start the Array Safely

Click Start under Array Operation. New disks appear as unmountable, and a Format checkbox appears once you confirm the device list.

Check the serials one final time, then format. XFS is the sensible default for array disks; enable encryption only if you have a plan for storing the key. Parity sync now begins, roughly two hours per terabyte on typical drives, and the array stays usable while it runs.

Configure the Cache Drive and Mover Schedule

Create a pool from your NVMe SSD and name it cache. Shares set to use the cache accept writes at SSD speed, and mover relocates those files to the array on schedule, by default nightly.

Two habits we stick to: keep appdata and VM images pinned to the pool so containers never wake the disks, and use two mirrored SSDs for that pool, since a single-device pool has no redundancy.

Create Shares for Archives and Network Access

Shares are how the array becomes usable over the network. A little structure now keeps container paths clean, permissions tight, and archival data separated from the churn of working files.

Design Shares for Archival Data, App Data, and Backups

We start every server with four shares:

• archive: long-term preservation of large datasets and public domain collections, array only
• data: working area for active projects and container output
• appdata: container configuration, cache pool only, excluded from mover
• backups: copies from workstations and phones

Set the archive share’s allocation method to High Water so files spread predictably, and leave split level generous enough that related folders stay on one disk.

Configure an SMB Share With Least-Privilege Access

Create individual accounts on the Users tab rather than sharing root. For each SMB share, set Export to Yes and Security to Private, then grant read/write only where it is needed.

Everyday laptops get read-only access to the archive share. One dedicated account holds write permission for ingest. That single choice has saved us from more accidental deletions than any other setting.

Use Consistent Paths for Containerized Archive Workflows

Map one parent path into your containers, such as /mnt/user/data, and let each app see subfolders below it. Shared parents allow instant, atomic moves and hardlinks instead of slow duplicate copies.

Mixed mappings like /downloads and /library pointing at different shares force full copies and double your write load. Fix the layout before you accumulate terabytes.

Separate Fast Working Data From Long-Term Storage

Point active processing at the cache pool and let finished, verified files land on the array. Unpacking and verification hammer the disk with random writes, work that SSDs absorb far more gracefully.

Once files are checksummed and organized, mover shifts them into parity-protected storage overnight. Spinning disks stay asleep during the noisy part of the job.

Add Self-Hosted Services and Maintain the Server

The Community Apps plugin turns Unraid into a home lab platform in a few clicks. Add services intentionally, keep their permissions narrow, and put monitoring in place before the collection grows past what you can re-acquire.

Deploy Docker Containers With Deliberate Permissions

Install Community Apps from the Apps tab, then add Docker containers one at a time. Set PUID and PGID to a non-root user, map only the paths a container genuinely needs, and avoid host networking unless required.

Automation tools like SABnzbd and NZBGet run well here for pulling Linux distributions and public domain archives. If you feed those clients from Usenet, a premium provider with long retention, SSL, and generous connection counts, such as Newshosting or Easynews, makes far more difference to completion rates than any container tweak.

Use Plex and Jellyfin as Archival Data Organizers

Both act as catalog front ends for large collections of high-resolution and lossless media you own or that sits in the public domain. They index folders, generate thumbnails, and give family members a searchable browser view of the archive.

Point the libraries at read-only mounts of your archive share. Jellyfin appeals if you prefer fully open-source software; Plex wins on polished client apps.

Run Vaultwarden and Other Privacy-Focused Home-Lab Services

Vaultwarden is our first non-storage container on every build, giving the household a self-hosted password vault. Put it behind HTTPS via a reverse proxy, and back up its data directory on a schedule you actually verify.

Other worthwhile additions: AdGuard Home or Pi-hole for network-level filtering, Home Assistant for automation, Syncthing for peer-to-peer file replication between your own machines, and Uptime Kuma for service checks.

Enable Virtual Machines Only When They Serve a Clear Need

Virtualization is powerful and expensive in RAM. A Windows or Linux VM makes sense for testing software, running a Windows-only utility, or isolating a workload, and GPU passthrough needs working IOMMU groups.

For most archive servers, containers cover the workload with a fraction of the overhead. Skip VMs until a specific requirement demands one.

Test Backups, Monitor Drive Health, and Plan Recovery

Turn on notifications immediately so SMART warnings and parity errors reach your inbox or chat client. Watch reallocated and pending sector counts, and schedule a monthly correcting parity check.

The routine we run:

1. Automatic flash backup so the boot device is reproducible
2. A 3-2-1 copy of irreplaceable data, including one offsite target
3. Quarterly restore tests, pulling real files back from backup
4. A written recovery note listing drive serials, license details, and share layout

An untested backup is a hope, not a plan.

Next Steps After Your First Array

Once your first array is up and shares are working, a few follow-up guides cover the pieces most builders add next: our parity vs cache drive explainer if you’re deciding how to allocate additional drives, setting up Tailscale for secure remote access without opening ports, Docker Compose on Unraid for running your automation stack, and GPU passthrough for Plex if you want hardware transcoding.

Guides in this series

• Choosing and adding a parity drive
• ZFS hybrid pools and NVMe cache
• Docker Compose on Unraid
• Remote access with Tailscale
• GPU passthrough for Plex
• Best Unraid plugins
• Unraid vs TrueNAS
• Unraid vs Synology
• SnapRAID vs Unraid

Frequently Asked Questions