NAS SETUP, MAINTENANCE & RECOVERY
More capacity should mean one clearly identified new disk, not a reshuffle of every drive in the server. Before expanding an Unraid array, separate three jobs that look similar on the Main page: adding an empty data disk, replacing an existing disk, and expanding a cache pool. This walkthrough covers the first job and explains where to stop if the screen describes something else.
Quick answer
Back up important files and record the current disk assignments. Stop the array, install the new disk with the server powered down, and assign it to an unused data slot. Confirm its serial number and parity size limits. Let Unraid clear the new disk where required, then format only that intentionally empty addition. Never format an existing disk merely because it becomes unmountable.
Steps to follow
-
Establish a clean starting point
Open Main and save a screenshot showing each slot, model, serial number and parity assignment. Download a fresh boot-device configuration backup using the supported backup facility for your installation. Keep that backup somewhere outside the server. Copy irreplaceable files to a separate destination and open several copies there. A screenshot helps reconstruct assignments; it does not contain the files themselves.
If an existing data disk is disabled, parity is invalid, or a filesystem is already unmountable, postpone expansion. Those are recovery problems. Adding hardware now makes it harder to tell whether a new cable, a changed slot or the original fault caused the next warning. Resolve the existing condition and record the result before starting this capacity change.
-
Check the new disk against the actual array
Read the new drive's label and compare its capacity with both parity devices if dual parity is present. A data disk cannot exceed the smaller parity disk. A larger drive therefore needs a separate parity-upgrade plan first. Check physical clearance, connectors, available power and airflow too; a free SATA socket alone does not establish that the enclosure can support another disk reliably.
Assume everything on the new disk will be erased. If it came from a desktop or another NAS, copy off anything wanted before assignment. An old folder structure is not imported by dropping that drive into an ordinary array data slot. Label the drive with its intended role so another person cannot confuse it with a backup disk during installation.
-
Install and assign one deliberate addition
Stop applications writing to the array, stop the array through the interface, and shut the server down normally before opening it. This is the straightforward approach when hot-swap support has not been positively established. Fit the drive, secure its connections, restart, and compare the original assignments with your screenshot. Existing disks should still occupy their original logical slots.
Choose the new serial number in an unused data slot. Do not select a parity slot or overwrite an existing data assignment. Read the pending-operation message before starting. If it describes a rebuild, missing disk or unexpected configuration change, stop and reconcile that difference. For a normal addition to a protected array, Unraid prepares the new disk through clearing unless a recognised preclear already satisfies that requirement.
-
Finish preparation and test a share
Wait for preparation to complete. Formatting is appropriate for this new, intentionally empty disk after its identity has been checked. Read the entire list of disks that the format confirmation covers: if any established data disk appears, cancel. A format request is not permission to erase every unmountable item shown on the page.
After the new filesystem mounts, write a modest test folder through an intended user share. Reopen the files from a second client if possible. Inspect that share's allowed disks, allocation policy and minimum-free-space setting if the new capacity is not being used. Adding a disk provides capacity; it does not automatically rebalance the old files across all drives.
Detailed guidance
Clearing, formatting and copying have different purposes
Clearing prepares an added disk for a parity-protected array. Formatting creates the chosen filesystem. Copying imports your documents into that filesystem afterwards. Treat these as separate checkpoints, with the serial number checked before either destructive preparation step. Optional preclear testing can help evaluate an empty drive, but it is not a substitute for a backup and is not required simply because a guide mentions it.
Choose a filesystem based on the features you actually need and the support available in your installed Unraid release. Do not use a capacity expansion as an unplanned filesystem conversion. Keeping this change limited to one new disk makes the outcome easier to verify and leaves a clear maintenance record for the next upgrade.
Shares can hide the reason capacity looks unchanged
A share may exclude the new disk explicitly, favour a pool, or follow allocation rules that do not choose the emptiest disk immediately. Examine those settings before moving existing folders manually. Pool and array capacity are separate resources, so a full application pool will not necessarily be relieved by adding an array disk unless the relevant share placement and Mover direction permit it.
For example, a media archive can gain another data disk while the downloads share remains on a small SSD pool. The archive has expanded, but downloads still need their own capacity policy. Document which storage location is expected to grow so that the first post-upgrade test measures the intended result rather than just the total shown on the dashboard.
Keep the expansion reversible until verification ends
Retain your assignment screenshot, diagnostics and copied files until the array has completed its normal checks without new errors. Watch temperatures and connection errors under load. If faults appear only after installing the disk, inspect the changed power and data path before assuming that every warning proves a defective drive.
A useful completion record lists the new serial number, slot, filesystem, usable capacity and successful test folder. Add the new storage to your backup selection if the backup job uses explicit paths or disk lists. Otherwise an apparently successful expansion can create a quiet gap: the new files are available on the NAS but absent from the separate recovery copy.
Compare the options
| Situation | Recommended action | Check before continuing |
|---|---|---|
| Unused data slot and healthy array | Add the new empty disk after checking parity limits | Confirm serial number and erasure intent |
| Replacing a disabled data disk | Use the replacement and rebuild procedure | Do not clear or format the recovery target |
| Full cache pool | Plan a pool-specific expansion or migration | Array capacity does not automatically enlarge the pool |
Frequently asked questions
Will Unraid distribute my old files onto the new drive?
Not automatically as part of adding it. Share allocation governs future writes, while existing files generally remain where they were. Avoid an unnecessary mass move until backups and the new disk have been verified.
Can I add a disk that already contains files?
An ordinary array addition is destructive to the assigned disk. Preserve its files elsewhere first, add and prepare the disk deliberately, then copy the wanted files into the finished array. Use a separate import workflow if you need to read the old disk before erasing it.
Official documentation
This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.