Quick Summary (TL;DR):
For a first Unraid server, build around one parity HDD, two data HDDs and a separate mirrored SSD pool. A practical example is 3 × 12TB CMR HDDs (one parity plus two data disks, giving approximately 24TB decimal array capacity) and 2 × 1TB SSDs in a properly configured mirror for application data. Choose a case with spare bays, direct SATA/HBA disk access, 16GB RAM for a modest Docker workload, reliable cooling and wired Ethernet. Install the current Unraid 7.3 stable release using the official USB Creator or installer; 7.3 also supports selected internal boot devices, so USB is no longer the only option. Assign the largest HDD to parity, verify serial numbers before formatting, allow the initial parity sync to finish, create private SMB shares and keep Docker/VM data on protected SSD storage. Parity is not backup: add an independent, preferably offline/off-site copy and test a restore. Starter, Unleashed and Lifetime licences differ primarily by device allowance and update entitlement, not by Docker features.
The First-Build Layout We Recommend
Unraid is particularly useful when you want to add HDDs of different capacities over time without replacing a whole striped RAID set. Its traditional parity-protected array stores each file on an individual data disk, while optional Btrfs or ZFS pools handle fast SSD workloads. These are different storage mechanisms: an Unraid parity array is not a conventional RAID 5 set, and a ZFS pool is not automatically protected by the array parity drive.
| Component | Starter configuration | Why |
|---|---|---|
| Chassis | 4–6 or more 3.5-inch bays with filtered airflow | Leave room to expand without rebuilding |
| CPU/platform | Modern 64-bit x86-64 platform with supported Ethernet | Enough for SMB and modest Docker workloads |
| Memory | 16GB as a sensible planning target | Headroom for filesystem caching and a few containers |
| Array | 1 × 12TB parity + 2 × 12TB data | ~24TB decimal data capacity with single-drive fault tolerance |
| Fast pool | 2 × 1TB SSD/NVMe configured as a mirror | ~1TB effective SSD capacity; protects against one pool-device failure |
| Boot | Quality USB flash or supported 7.3 internal boot device | Holds Unraid configuration; boot path depends on hardware |
| Network | Wired 1GbE minimum; 2.5GbE if useful | Stable file transfer and local management |
| Power | Reliable PSU plus a compatible UPS | Avoid abrupt outages and unsafe shutdowns |
This five-storage-device example fits within the current Starter six-device limit before any additional counted drives. Unraid counts attached storage devices, including pool and unassigned devices, with specific exceptions described in its licensing FAQ. An internal boot SSD/NVMe does count toward the licence device limit, while the licensing FAQ currently excludes one USB device and one eMMC device. Check the live count before purchasing; do not assume only array disks count.
Choose the Right Parts Before Buying Drives
Case, bays and airflow
Buy the case for the future number of disks, not just the three you install today. Three 3.5-inch HDDs in a compact enclosure may be easy to cool; six tightly packed drives need a credible intake path and fans that push air through the drive cage. Check the actual supported 3.5-inch mounting positions, SATA backplane connections, PSU form factor, HBA clearance and available fan headers. “Eight-bay” marketing can hide the fact that some positions require optional cages or that the motherboard has only four usable SATA ports.
Hot-swap trays are convenient but not essential. A conventional tower case with secure drive mounts can be cheaper and easier to repair. For a component-level cost comparison, see our DIY NAS vs prebuilt NAS ownership guide.
CPU and motherboard
A modest modern processor is sufficient for SMB file sharing and routine backups. CPU choice changes when you add several VMs, media transcoding, camera analytics or heavy encryption. An Intel processor with a supported integrated GPU can be useful for Plex/Jellyfin hardware transcoding, but verify the exact CPU, kernel and application support rather than assuming that every Intel-labelled board offers the same acceleration. Unraid does not make a weak CPU powerful by adding SSDs.
- Prefer a motherboard with enough native SATA ports or a known-good HBA path. SATA controllers should expose individual disks, not hide them behind hardware RAID.
- Check the Ethernet controller against the Linux kernel in the Unraid release you intend to install; a known Intel NIC is often straightforward, but specific models and firmware still matter.
- For VM use, confirm CPU virtualisation and IOMMU/VT-d/AMD-Vi support in both hardware and BIOS.
- Check RAM type and maximum capacity. DDR5 on-die ECC is not the same as end-to-end ECC memory protection; do not claim ECC without board/CPU validation.
- Ensure there is room for at least one NVMe SSD and preferably two if you want mirrored fast storage.
HDDs, SSDs and storage controllers
Use NASAliExpress price-appropriate CMR hard drives for parity and frequently written array disks. Drive-managed SMR may perform poorly during sustained parity synchronisation or rebuilds. Verify the exact manufacturer model number, not merely a product-family name. For an HBA, favour supported IT/HBA-mode disk presentation; avoid a hardware RAID virtual disk. An HBA also adds cabling, power and heat, so motherboard SATA ports are perfectly reasonable for a small first build.
Keep SSDs in pools rather than the classic Unraid parity array. Unraid documentation warns that TRIM/Discard is not supported in the traditional array as it is for pools. A mirrored SSD pool protects against a single SSD failure but still requires backups, especially for databases, Docker appdata and VM images.
Understand Unraid Parity Before You Format Anything
In the traditional Unraid array, data disks remain individually formatted and files are stored on one data disk at a time. The parity disk stores calculated protection information rather than normal user files. A single parity disk protects against failure of one data disk; two parity disks protect against two disk failures, subject to a healthy array and successful reconstruction. Parity capacity must be at least as large as the largest data disk.
| Example layout | HDDs purchased | Parity | Approx. array data capacity | Failure tolerance |
|---|---|---|---|---|
| Starter three-disk | 3 × 12TB | 1 × 12TB | 24TB | Any one array disk |
| Mixed-size three-disk | 12TB + 12TB + 8TB | 12TB | 20TB | Any one array disk |
| Four-disk single parity | 4 × 12TB | 1 × 12TB | 36TB | Any one array disk |
| Four-disk dual parity | 4 × 12TB | 2 × 12TB | 24TB | Any two array disks |
These are decimal manufacturer capacities, before filesystem overhead; the OS may display lower binary TiB figures. Unlike RAID 5, Unraid does not stripe every file across all HDDs, so a single large file is usually read from one data disk. That helps mixed-size growth but does not deliver the aggregated sequential speed of a striped RAID set. Parity-protected writes can be slower than writes to an SSD pool, especially with small files.
Important: Do not select a parity drive smaller than the largest data disk. Do not confuse format with rebuild: formatting a failed or emulated data disk writes a new empty filesystem and can destroy recoverable data. Always identify disks by serial number and stop when the array reports an unexpected missing or disabled disk.
Choose an SSD Pool: Single Drive or Mirror?
A single 1TB SSD gives about 1TB of fast storage but no disk redundancy. Two 1TB SSDs configured as a Btrfs RAID1 or ZFS mirror provide roughly 1TB usable and can tolerate one SSD failure. Merely inserting two SSDs does not guarantee the intended profile; verify the pool filesystem, profile and actual usable capacity in the Unraid interface before storing anything important.
| SSD arrangement | Approx. usable from 2 × 1TB | Protection | Good for |
|---|---|---|---|
| Single 1TB SSD | 1TB (only one drive used) | None | Testing, replaceable temporary files |
| Two-device Btrfs RAID1 | ~1TB | One SSD failure | Docker appdata, everyday containers |
| Two-device ZFS mirror | ~1TB | One SSD failure | VM disks, snapshots and protected appdata |
| Two separate 1TB pools | ~2TB total, separate | None unless backed up | Distinct scratch/workload volumes |
For a beginner, mirrored Btrfs is a sensible option because it integrates with the normal Unraid pool workflow. ZFS is worth considering when you specifically want ZFS features and understand its expansion and administration rules. This article is about building a working Unraid server, not reproducing the complete ZFS design guide.
Unraid Licensing in October 2026: Count All Your Drives
Unraid is paid software with a full-featured 30-day trial. As checked against Unraid’s published pricing and licensing documentation in October 2026, the normal US-dollar list prices are Starter $49, Unleashed $109 and Lifetime $249. Prices, tax, regional checkout totals and upgrade terms may change; verify at purchase. The July 2026 summer sale is over and should not be treated as current pricing.
| Licence | Published USD price | Attached storage allowance | OS update entitlement |
|---|---|---|---|
| Starter | $49 | Up to 6 counted storage devices | 1 year included; optional paid extensions |
| Unleashed | $109 | Unlimited by licence tier; hardware/OS limits remain | 1 year included; optional paid extensions |
| Lifetime | $249 | Unlimited by licence tier; hardware/OS limits remain | Updates for product lifetime |
Starter and Unleashed licences are perpetual: your installed version keeps running after the included update period. The optional update-extension fee is currently listed as $36 per year in the official licensing FAQ, but verify the checkout/account portal before budgeting. Lifetime is attractive if you expect to keep updating for years; Unleashed is usually the sensible route when you expect to exceed six storage devices but are unsure about long-term software commitment.
The six-device limit is easy to hit: three array HDDs plus two mirrored SSDs equals five; adding a fourth array HDD reaches six. Another SSD, a permanently attached USB backup drive or other counted storage may require a tier change. One USB device and one eMMC device are excluded under the licensing FAQ’s current counting rule; do not assume every USB device is excluded. For a trial, check the current activation and internet requirements before building an isolated server.
Step 1: Assemble the Hardware and Check BIOS Settings
- Install the CPU, cooler, RAM and motherboard, then fit the PSU and fans. Keep SATA power connectors free from excessive splitter chains.
- Mount the HDDs securely, label each bay with its serial number and connect each drive to a separate SATA/HBA port. Connect the SSDs and verify cooling airflow.
- Attach a monitor/keyboard for the first boot, wired Ethernet and your chosen boot media. Disconnect any unrelated external storage during installation.
- Enter BIOS/UEFI: use AHCI for SATA, HBA/IT mode for supported disk controllers, and disable Secure Boot (not supported by Unraid). Set the chosen boot device first.
- If you plan to use VMs, enable Intel VT-x/VT-d or AMD-V/IOMMU as supported. Leave overclocking disabled until the server has passed stability tests.
- Boot the hardware diagnostics or firmware page and verify that every disk, RAM module and NIC is detected before writing the OS.
Do not enable motherboard RAID or create a RAID volume for the HDDs. Unraid must see the physical devices and their serial numbers. If a new HBA is not detected, inspect PCIe slot sharing, power, cable orientation and firmware rather than assuming Unraid is at fault.
Step 2: Create the Boot Media — USB or Internal Boot
The old “Unraid must always boot from USB” advice is now incomplete. Since Unraid 7.3.0 (12 May 2026), Unraid supports booting from selected internal devices as well as conventional USB flash. The official USB Creator remains a straightforward path for a first build, and the installer can prepare an internal boot target. An internal boot SSD/NVMe counts as a storage device for licensing, and internal boot support and TPM-based licensing depend on the system and release; check the official internal boot FAQ before selecting a device.
- On a separate PC, download the official Unraid USB Creator from Unraid, not a third-party ISO mirror.
- Insert a good-quality USB flash drive. Verify its device identity: creating the boot media erases the selected device.
- Use the USB Creator to download the stable Unraid release and write the flash drive. Confirm the device has a suitable unique GUID if you intend to retain USB boot.
- Boot the server from that drive and follow the Unraid 7.3+ onboarding wizard. Select flash boot or supported internal boot as appropriate.
- If choosing internal boot, carefully confirm the target disk(s) and any mirrored boot-pool option; the installer will erase the chosen target. Keep a configuration backup after onboarding.
As of 8 October 2026, Unraid’s published 7.3.3 release notes describe a security-fix stable update. The 7.4 beta line is not a sensible default for a first storage server. Use the latest stable download available when you actually install, rather than blindly copying a version number from an old tutorial.
Step 3: Open the WebGUI and Complete Onboarding
After the first successful boot, access the Unraid WebGUI from another computer on the same trusted LAN. The documented default hostname is often tower.local; use the IP address shown on the server console if name resolution fails. The 7.3 onboarding wizard lets you configure the hostname, time zone, boot mode and related first-run options. Set a strong administrator password promptly and do not expose the management UI directly to the public internet.
- Confirm the server has a valid LAN IP, gateway and DNS. Consider a DHCP reservation on your router rather than guessing a static address.
- Review the trial/licence status under registration. Activate a valid trial or purchased licence as prompted.
- In Main, compare every detected HDD and SSD serial number with your physical labels. Do not use disk position alone to identify a drive.
- Set notification delivery (email or another supported method) so failed disks and parity errors do not remain invisible.
- Back up the boot device configuration once initial setup is complete; store that backup outside the server.
Step 4: Assign Parity, Data Disks and SSD Pool
Go to Main and assign your array drives. For the example 3 × 12TB HDD build, put one 12TB drive in the Parity slot and the other two in data slots. If you mix capacities, the parity disk must be at least as large as the biggest data disk. Then create a named SSD pool such as fast or cache, assign both SSDs and explicitly configure/verify the intended mirrored profile.
- Identify each physical drive by model, capacity and serial number; double-check there is no data you need on it.
- Assign parity and data slots, then assign the two SSDs to the named pool. Check that the total number of attached devices is within your licence.
- Review array and pool filesystem selections. XFS is a common default for HDD data disks; Btrfs or ZFS is appropriate for SSD pools depending on your design.
- Start the array only after the device map is correct. New unformatted disks may need formatting; this erases their contents.
- Let the initial parity sync complete before treating the array as protected. Avoid importing irreplaceable data during this initial unprotected period.
- After the sync, verify parity status, pool profile, available capacity and disk temperatures on the Main/Dashboard pages.
Important: A new array and an existing array with failed/missing drives are different situations. Never follow first-install formatting instructions on a populated array you are trying to recover. Do not click “Parity is valid” or “New Config” as a shortcut when an existing array is degraded.
Step 5: Create Shares with Deliberate Storage Placement
Unraid shares are logical folders presented over SMB/NFS or to containers. Since Unraid 6.12, shares use Primary storage, optional Secondary storage and a directional Mover action. A cache pool does not magically accelerate every share: you must decide where new files land and where Mover sends them.
| Share | Primary storage | Secondary storage | Mover action | Reason |
|---|---|---|---|---|
| media | SSD pool | HDD array | Pool → array | Fast incoming copies, bulk media eventually on HDDs |
| family-backups | HDD array | None | Not applicable | Avoid filling SSD with large backup sets |
| appdata | Mirrored SSD pool | None | Not applicable | Keep live container databases on protected fast storage |
| domains (VMs) | Mirrored SSD pool | None | Not applicable | Fast VM disks; still back up VM images |
| isos | HDD array or SSD pool | None | Not applicable | Mostly read-only installation images |
In Shares → Add Share, create a media share. Choose the mirrored SSD pool as Primary, the HDD array as Secondary, and Mover direction from pool to array if you want completed media files to settle on HDDs. Set a sensible minimum-free-space threshold: Unraid recommends a floor at least as large as the largest expected file, preferably more. A 50GB file and a 5GB free-space floor are a predictable recipe for failed copies.
For appdata and domains, use only the protected SSD pool unless you deliberately design a different placement strategy. Mover should not shuttle open Docker databases between devices. If changing an existing share’s storage settings, stop Docker and VMs before moving live application files, follow the official mover procedure and confirm the files are where you expect.
Step 6: Configure Private SMB Access
Create a non-administrator user for ordinary file access, then configure SMB export for the shares you actually need. Use private or securely restricted access rather than opening family backups to anonymous guests. On Windows, open File Explorer and use \\server-name\media (substitute the actual hostname and share); on macOS, use Finder → Go → Connect to Server with smb://server-name/media.
- Create a regular user with a strong password and appropriate share permissions.
- Enable SMB export only on intended shares. Use private/security settings to limit write access.
- From a client PC, create a disposable test file, read it back, rename it and delete it.
- Check that you cannot access restricted shares using an unauthorised account.
- Record the share names and credentials in your password manager; never place administrator passwords in automation scripts.
Do not port-forward SMB (TCP 445) or the Unraid WebGUI to the internet. For remote access, use a properly secured VPN/overlay solution and apply updates; remote exposure should be a separate security decision, not part of the default first-day setup.
Step 7: Add One Docker Application Without Breaking Storage
Unraid can run Docker containers and VMs, but get storage and backup working first. The Community Applications catalogue is an optional discovery and installation interface for containers and plugins. Install it from the Apps tab if prompted, and check the maintainer and source of each application. A community template is not an official security review of its container image.
- Confirm
appdataandsystemare on the intended SSD pool and that the pool is protected. - Enable Docker under Settings after checking the storage path. The Docker image/container layer should not be your only copy of application state.
- Choose one low-risk application (for example, a dashboard) from a trusted maintainer and read its container documentation.
- Map persistent configuration to an appdata path, not to an ephemeral container filesystem. Use the least privileged host paths and ports required.
- Start the container, open its UI only on the LAN and verify that settings survive a container restart.
- Record how to back up its persistent data and test a restore before adding more services.
For media applications, keep large libraries on the HDD array and their metadata/databases on the SSD pool when supported. For surveillance or VM-heavy workloads, reconsider CPU, RAM, GPU/detector and pool endurance before treating the basic build as sufficient. This is a starter NASAliExpress price, not a promise of high-performance transcoding or multi-VM capacity.
Step 8: Make Backups Before Trusting the Server
Unraid parity handles a particular HDD failure scenario. It does not undo ransomware, mistaken deletion, a corrupted application database, theft, fire, PSU damage, or a catastrophic SSD-pool failure. Mirroring the SSD pool improves availability, not independent recovery. You need separate copies of both data and configuration.
- Export and store a boot-device/configuration backup outside the Unraid server, and repeat it after important settings changes.
- Back up the SSD appdata/VM data to independent storage using an application-aware method; stop or quiesce databases/VMs where required for consistent copies.
- Back up irreplaceable array shares to a second NASAliExpress price, removable HDD or suitable cloud service, with version retention and an off-site/offline copy.
- Test restoring one document, one application configuration and, if using VMs, a VM backup. A green backup-job status is not a restore test.
- Set notifications for disk SMART alerts, parity errors, backup failures, SSD-pool errors and UPS events. Schedule parity checks and pool maintenance at sensible times.
Our RAID protection guide explains why redundancy is not backup. The same distinction applies to Unraid’s parity-protected array and to mirrored SSD pools.
How Much Does a First Unraid Server Really Cost?
Do not compare a bare motherboard price with a finished NASAliExpress price appliance. The following is an illustrative budget worksheet, not a live retailer quote or a claim that these parts are currently available at the assumed prices. Substitute your own checkout totals and electricity tariff. The example uses three 12TB HDDs, two 1TB SSDs and a UPS, plus a separate backup target.
| Cost item | Illustrative assumption | What to verify |
|---|---|---|
| Case, board/CPU, RAM, PSU, fans and cables | £350 | SATA ports, warranty, NIC and cooling |
| Three 12TB CMR HDDs | 3 × £220 = £660 | Exact CMR SKU, warranty and return policy |
| Two 1TB SSDs | 2 × £70 = £140 | Endurance, form factor, mirror compatibility |
| UPS | £120 | Actual wattage, runtime and USB/NUT support |
| Boot media | £12 | USB quality or internal boot provision |
| Independent backup target | £230 | Enough capacity and off-site rotation |
| Hardware/backup subtotal | £1,512 | Before OS licence, taxes/delivery changes or labour |
| Unraid Starter licence | $49 USD list price | Separate currency; checkout tax and FX apply |
At a hypothetical measured average of 45W running 24/7 and a hypothetical electricity rate of £0.25/kWh:
0.045 kW × 24 h/day × 365 days = 394.2 kWh/year
394.2 kWh × £0.25 = £98.55/year
Five years = £492.75 electricity
Illustrative five-year subtotal:
£1,512 hardware/backup + £492.75 electricity = £2,004.75
PLUS Unraid licence (USD converted at checkout),
replacement batteries/drives, optional update extensions,
network upgrades, shipping/tax differences and your time.Power consumption is not a published measurement for this configuration. Measure your actual server at the wall once it is built; idle HDD spin-down, background parity checks, workload, PSU efficiency and network cards can all change average watts. Every additional constant 10W adds 87.6kWh per year: at £0.25/kWh that is £21.90 annually, or £109.50 over five years. A “free” older desktop can therefore be expensive to leave on continuously.
Common First-Install Problems and the Right Fix
| Symptom | Likely cause | Safe first check |
|---|---|---|
| USB boot not detected | UEFI/legacy mismatch, boot order, poor flash media | Check BIOS boot list and official USB Creator output |
| Internal boot option unavailable | Unsupported device/controller or platform requirements | Review Unraid 7.3 internal boot FAQ and supported drivers |
| A drive is missing | Cable/power/HBA firmware or slot sharing | Inspect BIOS and drive serials; do not initialise unknown disks |
| Array will not start | Licence count exceeded or missing assigned device | Check registered tier, device count and exact assignments |
| Parity sync takes hours | Full-disk sequential work, HDD/controller bottleneck | Check disk health and progress; avoid assuming a fixed completion time |
| SSD pool shows unexpected size | Profile not mirrored or pool configuration mismatch | Inspect Btrfs/ZFS profile before adding important data |
| Share fills SSD | Wrong Primary/Secondary or Mover direction | Inspect share settings and minimum free space |
| Docker is slow or appdata missing | Appdata on HDD or files moved while services running | Stop services, inspect paths, restore from backup if needed |
| SMB login fails | Wrong share security, account or name resolution | Use LAN IP, confirm credentials and permissions |
| Disk reported unformatted after a failure | Wrong assignment or damaged filesystem | Stop; preserve evidence and follow recovery guidance—never format to rebuild |
Should You Start with Unraid, TrueNAS or a Prebuilt NAS?
Unraid is a strong fit when you value incremental HDD expansion, a familiar WebGUI, Docker/VM support and the ability to reuse mismatched disks within parity constraints. It is less compelling when your main requirement is maximum throughput from a single striped pool, an all-flash ZFS appliance or the lowest possible software cost. TrueNAS may suit a ZFS-first storage design; OpenMediaVault suits some simpler Linux-based NASAliExpress price builds; a prebuilt NAS reduces assembly and platform-support effort. Do not buy Unraid just because a tutorial shows attractive Docker dashboards—choose it for the storage model you actually want.
For broader ownership trade-offs, compare our DIY vs prebuilt NAS guide before spending money on the chassis and software. If you already own suitable hardware, the Unraid trial is a practical way to validate compatibility without purchasing a licence first.
First-Weekend Acceptance Checklist
- All HDD and SSD serial numbers match the physical drive labels and intended assignments.
- Parity disk is at least as large as the largest array data disk; initial sync has completed without errors.
- SSD pool really has the intended mirror profile and expected usable capacity.
- Shares use deliberate Primary/Secondary placement and Mover direction; appdata remains on the fast pool.
- A non-admin SMB user can access permitted shares and cannot access restricted ones.
- At least one Docker container retains its settings after a restart, if Docker is in scope.
- SMART, parity, pool and backup alerts reach a monitored destination.
- An independent backup has completed, and at least one file and one configuration have been restored successfully.
- The boot-device backup is stored off-server and the licence/device count has room for the next planned drive.
Frequently Asked Questions
Can I use different-sized HDDs in an Unraid array?
Yes. Data disks can differ in size, but no data disk can be larger than the smallest assigned parity disk. For example, one 12TB parity disk can protect a 12TB data disk and an 8TB data disk. This is a central benefit of the traditional Unraid array compared with many conventional striped RAID layouts.
Is one SSD enough for a first Unraid server?
Yes for learning or replaceable workloads, but it is a single point of failure for any live data stored there. For Docker appdata, databases and VM disks you care about, a correctly configured two-device mirrored pool plus an independent backup is a more robust starting point.
Does Unraid 7.3 still need a USB flash drive?
Not for every final boot configuration. Unraid 7.3 introduced supported internal boot devices and TPM-based licensing where possible. The USB Creator remains the straightforward route and may be used to start onboarding before selecting internal boot. Check your exact hardware and the current official instructions.
Is Unraid parity the same as a backup?
No. Parity can reconstruct a failed array disk under the supported failure conditions, but cannot recover files deleted, encrypted or overwritten by software. A separate, versioned backup—ideally including an offline or off-site copy—is essential.
Do I need Unleashed instead of Starter?
Count all attached storage devices that Unraid licensing counts, not only the data HDDs. A three-HDD array plus two SSDs already uses five counted devices in a conventional USB-boot build. If expansion will take you beyond six, compare Unleashed or Lifetime before buying Starter.
Related esp32.co.uk/ Guides
- DIY NAS vs Prebuilt NAS: Complete Build and Running Costs — compare the true price of a custom system.
- RAID 1 vs RAID 5 vs RAID 6 for a Home NAS — understand failure tolerance and backup limitations.
Official Sources and Documentation
- Unraid 7.3.3 release notes (8 October 2026) — stable security/maintenance release context.
- Unraid: Create an Unraid USB drive — official USB Creator and manual boot-media guidance.
- Unraid: Deploy and configure OS — first boot, onboarding and BIOS settings.
- Unraid: Configure your array — parity/data assignments, formatting and pool guidance.
- Unraid: Arrays and cache pools — parity design and SSD placement.
- Unraid: Cache pools — Mover, minimum free space and pool considerations.
- Unraid: Licensing FAQ — counted devices, perpetual licences and extension terms.
- Unraid: Official pricing — confirm the latest checkout price and regional tax.
- Unraid: Post-setup essentials — configuration backups and ongoing care.
- Unraid: Community Applications — Docker templates and plugin caveats.