Skip to content

Installing Unraid for the First Time

Unraid is a home server operating system that can act as a NAS, Docker host, and VM host. It is managed mostly from a browser, so you do not need to be a Linux expert to get started.

Updated for Unraid 7.3.x

This guide was written for the current Unraid 7.3.x setup flow as of June 2026. Unraid 7.3 introduced the onboarding wizard and optional internal boot support. Always confirm the latest stable release in the official Unraid Version Archive.

Official references

Topic Official documentation
What Unraid is What is Unraid?
Create boot media Create your bootable media
First boot and onboarding Deploy & configure Unraid OS
Internal boot Internal Boot FAQ (7.3+)
Array setup Configure your array
Post-install essentials Complete your post-setup essentials
Community apps Community Applications

What you need

Item Notes
Server hardware A 64-bit x86_64 PC or server with a wired network connection is recommended.
Boot device For a typical install, use a quality USB 2.0 flash drive between 4 GB and 32 GB with a unique GUID.
Storage drives At least one data drive is needed to start using storage. At least one parity drive is strongly recommended for protection.
Another computer Used to create the Unraid boot device and access the WebGUI.
Unraid account Used for trial activation, licensing, and license management.

Unraid is not a backup

Parity can help recover from a failed data drive, but it does not protect against accidental deletion, file corruption, ransomware, theft, or fire. Important data should still follow the 3-2-1 backup method.

1. Create the boot device

The easiest method is the official Unraid USB Flash Creator.

  1. Go to the official Create your bootable media page.
  2. Download the USB Flash Creator for Windows, macOS, or Linux.
  3. Insert your USB flash drive.
  4. Select the latest stable Unraid release.
  5. Choose a server name, such as tower, unraid, or nas.
  6. Use a static IP or DHCP and reserve IP via DHCP server (most likely your router).
  7. Write Unraid to the USB drive.
  8. Safely eject the USB drive when finished.

Use a simple server name

A short name like unraid or nas is easy to remember. You can usually access the WebGUI later at http://unraid.local or http://nas.local, depending on the name you choose.

2. Configure BIOS/UEFI settings

Insert the Unraid USB drive into the server and enter the BIOS/UEFI settings.

Recommended settings:

Setting Recommendation
Boot order Set the Unraid USB drive as the first boot device.
Secure Boot Disable it. Unraid does not support Secure Boot.
SATA mode Use AHCI mode.
RAID mode Disable motherboard RAID. Use AHCI or HBA mode instead.
Virtualization Enable Intel VT-x / AMD-V if you plan to run VMs.
IOMMU Enable Intel VT-d / AMD-Vi if you plan to pass hardware through to VMs.

Note

If the server does not boot, try changing between UEFI and Legacy/CSM boot modes. Some motherboards also list USB devices under a separate hard drive boot order menu.

3. Boot Unraid and open the WebGUI

After the server boots, open Unraid from another computer on the same network.

Try one of these addresses:

http://tower.local
http://tower
http://SERVER-IP-ADDRESS

Replace tower with the server name you chose in the USB Flash Creator.

If the name does not work, check your router's DHCP client list and look for the server's IP address.

4. Set the root password

On first login, Unraid will ask you to create a password for the root user.

Use a password that is:

  • Unique to this server
  • At least 12 characters if possible
  • Stored in a password manager

Do not expose the WebGUI to the internet

Do not port forward the Unraid WebGUI directly to the internet. For remote management, use a VPN-style option such as WireGuard or Tailscale, or follow Unraid's official remote access guidance carefully.

5. Complete the Unraid 7.3 onboarding wizard

On Unraid 7.3 and newer, new installs start with an onboarding wizard.

In the wizard, review:

Step What to choose
Server settings Confirm server name, description, language, theme, and time zone.
SSH Leave disabled unless you know you need command-line access.
Boot option Most beginners should keep the default flash boot option.
Internal boot Optional in Unraid 7.3+. Only use it if you understand the device count and recovery differences.
Plugins Preinstall only what you know you need. You can install more later.

About internal boot

Unraid 7.3+ can boot from an internal SSD, NVMe, eMMC, or supported internal device. This is optional. Internal boot devices can count toward your attached storage device limit, so review the official Internal Boot FAQ before choosing it.

6. Register or start a trial

In the WebGUI, use the Get Started section to sign in or create an Unraid account. A trial key can be installed automatically during setup.

You can review licensing later at:

Tools → Registration

Note

The Unraid license is tied to the boot device or licensing method. Keep a backup of your boot device configuration after setup.

7. Assign your array and pool devices

Go to the Main tab to assign storage devices.

Basic roles:

Role Purpose
Parity Protects the array from a failed data drive. It does not store normal files.
Data Stores your files and shares.
Pool / cache Usually SSD or NVMe storage used for Docker, VMs, appdata, and faster writes.
Boot device Holds Unraid OS and configuration.

Recommended beginner layout:

Drive type Suggested use
Largest HDD Parity drive
Other HDDs Array data drives
SSD/NVMe Pool/cache for Docker, VMs, and appdata

Parity drive size

The parity drive must be at least as large as the largest data drive in the array. If you plan to add larger drives later, consider using a larger parity drive from the start.

Avoid SSDs in the main array

Unraid's official docs still note that SSD support in the array is experimental. SSDs and NVMe drives are usually better used as pools/cache devices.

8. Start and format the array

After assigning drives:

  1. Review every disk assignment carefully.
  2. Click Start under Array Operation.
  3. New drives will show as unformatted.
  4. Check the format confirmation box.
  5. Click Format.

Formatting erases data

Formatting a disk deletes the existing filesystem. Make sure you are formatting only the drives you intend to use with Unraid.

After the array starts, Unraid will begin parity sync if a parity drive is assigned. The server can run during this process, but it is best to wait for parity sync to finish before copying important data.

9. Create your first shares

Shares are folders that appear on the network, such as media, backups, or documents.

Go to:

Shares → Add Share

Suggested starter shares:

Share Use
media Movies, TV, music, photos, or other media files.
backups Backups from computers or other devices.
documents Personal files that need controlled access.
appdata Docker container configuration. Usually created automatically when Docker is enabled.

For sensitive data, use Private share security and create user accounts instead of relying on public guest access.

10. Back up the boot device

After the first setup is complete, back up the boot device.

Go to:

Main → Boot Device → Boot Device Backup

Store the backup somewhere other than the Unraid array, such as your main computer, cloud storage, or another backup location.

Tip

Back up the boot device again after major changes, such as changing disk assignments, network settings, Docker paths, or licensing.

11. Install Community Applications

Community Applications adds the Apps tab, which works like an app store for Docker containers and plugins.

  1. Go to the Apps tab.
  2. Click Install when prompted to install Community Applications.
  3. Refresh the page after installation.
  4. Search for apps from the Apps tab.

Be selective with apps

Community Applications is curated, but you should still review each app's description, support link, repository, and required paths before installing it.

12. First settings to review

Before loading the server with data, review these areas:

Setting area Where to find it What to check
Date and time Settings → Date & Time Set the correct time zone and NTP settings.
Network Settings → Network Settings Confirm IP, gateway, DNS, and bonding/bridging choices.
Management access Settings → Management Access Review HTTP/HTTPS settings and remote access options.
Disk settings Settings → Disk Settings Review spin-down, filesystem defaults, and array auto-start.
Docker Settings → Docker Enable Docker after your pool/cache is configured.
Notifications Settings → Notifications Configure email, browser, or agent notifications.
Users Users Create users for private shares.

13. Quick troubleshooting

Problem What to try
Server will not boot from USB Check boot order, UEFI/Legacy mode, Secure Boot, and whether the USB is listed under hard drives.
tower.local does not load Find the IP address from your router and use http://SERVER-IP.
No drives appear Check SATA/SAS cables, power cables, HBA mode, and BIOS storage settings.
Array will not start Confirm your license supports the number of attached storage devices.
WebGUI looks broken Try another browser, private window, or clear browser cache.
Very slow first writes Parity sync may be running. Wait for it to finish before judging performance.

Final checklist

  • [ ] Boot device created with the official USB Flash Creator
  • [ ] BIOS/UEFI boot order configured
  • [ ] Secure Boot disabled
  • [ ] WebGUI reachable from another computer
  • [ ] Strong root password set
  • [ ] Onboarding wizard completed
  • [ ] Trial or license installed
  • [ ] Array and pool devices assigned correctly
  • [ ] Array started and formatted intentionally
  • [ ] First shares created
  • [ ] Boot device backup saved outside the array
  • [ ] Community Applications installed
  • [ ] Notifications configured

Next steps

Once the base install is stable, continue with:

  • Setting up shares and SMB access
  • Installing Docker containers from Community Applications
  • Configuring appdata backups
  • Setting up UPS monitoring
  • Planning a real backup strategy
  • Reviewing Unraid security fundamentals before enabling any remote access