Here is how to add a drive to Unraid array storage, in six steps: confirm the new disk is no larger than your smallest parity disk, stop the array and power down, install the drive, assign it to an empty data slot on the Main tab, start the array so Unraid clears it, then format it. Existing data disks are never touched.
The clear is the slow part. Unraid writes zeros across the whole new disk so parity stays valid, the array stays online while it runs, and the new disk is unusable until it finishes. The rest of this is the detail that separates a quiet evening from a weekend spent reading old forum threads at 1 a.m.
Who this is for, and who should skip it
This is for anyone with a working array, a free bay and room on their license. Three situations need a different procedure:
- Replacing a failed or disabled disk. That is a rebuild, not an add. Read what Unraid’s red X actually means before buying anything, because the culprit is often a cable.
- The new disk is bigger than your parity disk. It goes in as parity first. That has its own section below.
- You are at your license limit. Unraid’s licensing FAQ caps Starter at 6 attached storage devices in total, parity included, while Unleashed and Lifetime allow up to 30 array devices (28 data plus 2 parity). Every storage device present before the array starts counts, apart from one eMMC and one USB device, so the cache SSD is on the tab too.
Before you touch a screwdriver
Make sure the array is healthy. If any disk is disabled or emulated, fix that first. Adding a disk to an array that is already running without full protection stacks two jobs, and the new disk helps with neither.
Sort out power and cabling. A new drive hung off the end of a daisy-chained SATA power splitter is a reliable way to earn CRC errors and, eventually, a disabled disk that was never faulty. The first-build hardware guide covers PSUs and HBAs, and the CMR drive picks cover what goes in the bay.
Write down the serial number. You need it at the format step, which is the worst possible moment to be guessing.
The six steps, in order
- Confirm the parity rule. Unraid’s documentation on adding disks is blunt: a new data disk must be the same size or smaller than your current parity disks. If yours is larger, skip to the parity section below.
- Stop the array and power down. The Stop button lives under Array Operation on the Main tab. Docker containers and VMs stop with the array, so pick a time when nobody is halfway through a film. The docs note that hot-swap hardware lets you skip the power-down, but the array still has to be stopped to change slot assignments.
- Install the drive and power back on.
- Assign it to an empty data slot. On the Main tab, open the next free Disk slot’s dropdown and pick the new drive by model and serial. New array disks default to XFS, with ZFS and BTRFS available from the file system dropdown. XFS is the boring, correct answer for most array disks; choose something else only if you know why.
- Start the array. Unraid begins clearing the disk. Zeros contribute nothing to parity, which is why the array stays protected and online while this runs, but the new disk is not usable until the clear completes. A disk with an intact pre-clear signature skips this step. You can add several disks at once, though none become usable until all are cleared and formatted.
- Format it. When the clear finishes, the disk shows as unmountable and Unraid prompts you to format it. Check the serial against the one you wrote down, tick the confirmation box and click Format. It takes a few minutes, after which the disk shows as mounted and its capacity joins the array.
On an array with no parity disk the procedure is the same minus the clear: the disk goes straight to unmountable and waits for a format.
Clear or pre-clear?
Use the built-in clear for drives you already trust and a pre-clear for drives you don’t. The pre-clear comes from the Unassigned Devices Preclear plugin and, per Unraid’s docs, runs a pre-read to find bad sectors, zeros the disk, then verifies it with a post-read. That is three full passes instead of one, with the disk outside the array the whole time.
| Built-in clear | Pre-clear (plugin) | |
|---|---|---|
| Purpose | Ensures basic disk compatibility | Tests drive health and prepares for use |
| Speed | Fast | Significantly slower |
| Array impact | Background operation | Disk offline required |
| Best for | Quick expansions | Preparing and checking new drives |
The comparison is Unraid’s own. A reasonable rule: anything new, shucked, refurbished or second-hand gets a pre-clear; a drive that has lived in this server for years doesn’t need one. The disk replacement docs note that many users pre-clear to test new drives and help prevent early failure.
Afterwards, open the drive’s SMART report by clicking its name on the Main tab. Unraid’s SMART guidance reads a reallocated sector count (attribute 5) above zero as a drive starting to fail, uncorrectable sectors (198) as lost data, and a rising UDMA CRC count (199) as a cable to reseat. A new drive showing anything but zero on 5 or 198 goes back to the seller now, not after it holds your photos.
One trap: do not format a pre-cleared disk before adding it. The docs warn that formatting removes the clearance signature, so Unraid clears it all over again. That costs hours rather than data, but it is an irritating way to lose a day.
What if the new drive is bigger than parity?
Make it your new parity disk. Stop the array, assign the larger drive to the parity slot in place of the old one, start the array and let parity rebuild onto it. When that completes, the old parity disk is free to join the array as a data disk using the six steps above, clear included.
Three cautions from Unraid’s docs:
- Keep the old parity disk untouched until the new parity build finishes. If a data disk fails mid-build, it is your way back.
- With single parity, your data is unprotected until the rebuild completes.
- If a data disk has already failed, don’t do this at all. Use the Parity Swap procedure, where the new large disk becomes parity and the old parity disk replaces the failed data disk. The replacement docs warn the array isn’t available during its copy phase, which can take many hours.
Do the upgrade as two separate operations rather than one clever reshuffle. Saving a few clicks is not worth giving up the fallback.
Adding a parity disk instead
A parity disk needs no clear. Assign it to the parity or parity 2 slot, start the array, and Unraid builds parity across it while your files stay accessible, if slower. Single parity must be at least as large as your largest data drive; with dual parity each parity disk must meet that rule, though the two can differ in size. Building a fresh array? The docs’ order is data disks first, then parity, which means those data disks skip clearing entirely.
After it mounts, make sure your shares use it
A mounted disk is not the same as a disk your shares will write to. If a share has an Included Disks list, Unraid’s shares documentation says only the listed disks are considered for new files, so a fresh disk5 sits empty indefinitely until you add it. Check each share’s settings and the Global Share Settings page.
There is no rebalancing to do. Unraid writes whole files to individual disks rather than striping them, as covered in how the array, parity and pools work, so an empty disk is simply another place for new files to land. Under the default high-water allocation, which fills disks using switch points based on half the largest drive’s capacity, the new disk won’t necessarily take the next write. That is expected, not a fault.
Mistakes that turn this into a weekend
- Clicking Format while another disk is unmountable. The checkbox reads “Format will create a file system in all Unmountable disks.” If an existing data disk is unmountable because of filesystem corruption, a community expert on the Unraid forums spells out the result: it erases the drive and its parity representation. Run a filesystem check on that disk instead, and format only when the new disk is the sole one listed.
- Using Tools, New Config to “add” a disk. It isn’t needed, and the array health docs warn that New Config clears the array history required for a rebuild.
- Dropping a data disk into a parity slot. A parity build writes every sector, so whatever was on that disk is gone.
FAQ
does unraid need to clear a new drive before adding it
Yes, if the array has a parity disk. Unraid fills a new data disk with zeros so parity stays valid, and runs that clear in the background while the array stays online. Arrays without parity skip it, parity disks never need it, and a disk with an intact pre-clear signature is accepted without clearing again.
can i add a drive to unraid without losing data
Yes. Adding a data disk never writes to your existing data disks; the clear only touches the new drive, and parity stays valid because zeros don’t change it. The real risks are formatting the wrong disk, assigning a data disk to a parity slot, or running New Config when you meant to rebuild a disk.
how long does it take to add a drive to unraid
The hands-on part takes minutes; the clear takes hours. Unraid’s docs describe the built-in clear as adding storage “in just a few hours,” but it writes every sector, so time scales with capacity. A pre-clear reads, writes and reads the whole disk, so budget considerably longer and start it before you need the space.
can i add a used drive with data to my unraid array
Yes, but its contents will be wiped. On a parity-protected array Unraid zeros the disk before it joins, and the format step erases it regardless. If you want the files, mount the drive with the Unassigned Devices plugin first, copy everything into a share, then add the empty disk.
