You log into the Unraid web UI expecting your shares to be there, and instead the array is sitting in Stopped state with a Start button that either does nothing or is greyed out entirely. No Plex, no file shares, nothing. It is one of the more stressful moments in homelab life because it feels like your data is gone.
It almost never is.
The first time I hit this on my own box, a 6-drive setup running Unraid 6.12, I spent an hour convinced a drive had died. The real problem was a checkbox I had unticked three weeks earlier and forgotten about. That experience taught me to work through the causes in order instead of panicking, and the list below is roughly the order I check things in now.
1. A data or parity disk is missing
This is the single most common reason, and Unraid is deliberately strict about it. If the array had a parity disk and that disk is now showing as Not installed or a slot reads Missing, Unraid will refuse to auto-start to protect you.
Go to the Main tab and look at every slot. A healthy assigned drive shows its model and serial. A problem drive shows a blank dropdown, a different serial than before, or the words Wrong or Missing in red.
Nine times out of ten this is physical. A SATA power splitter that came loose, a cable that got nudged when you added RAM, or a drive that spun down and did not come back. Power the server down fully, reseat both the SATA data cable and the power connector on the affected drive, and boot again.
How to tell a loose cable from a dead drive
If the drive does not appear in the slot dropdown at all, it is not being detected by the controller, which points at cabling or the port. If it appears but is flagged red with a read error, the disk is detected but Unraid is unhappy with it. In that second case, check the SMART report before doing anything drastic. SMART attributes like reallocated sector count and pending sectors tell you whether the drive is genuinely failing.
2. Invalid configuration after a hardware change
Unraid remembers exactly which serial number belongs in which slot. Swap a drive, move disks between HBA ports, or replace a failed controller, and the serials no longer line up. The array then reports an invalid configuration and the Start button stays inactive.
You will usually see a specific slot flagged as Wrong with a red X, meaning the drive present does not match the one assigned.
If you know the swap was intentional and correct, assign the right drive to each slot from the dropdowns, then confirm. If a slot should hold a replacement disk, assign the new blank drive and Unraid will offer to rebuild it from parity once you start the array. That rebuild is normal and safe as long as parity is valid and only one disk changed.
3. Too many missing disks for parity to cover
Single parity protects against one disk failing at a time. Dual parity protects against two. If more disks go missing than your parity can rebuild, Unraid will not start the array, because starting it would risk emulating disks it cannot actually reconstruct.
This catches people after a power supply fault or a failed backplane that drops several drives at once. The drives are often fine, they just all lost power together.
The fix here is patience, not clicks. Shut down, reseat power to the whole drive cage or replace the failing PSU, and get all the disks detected again. Once the count of missing disks drops back within what parity can handle, the Start button returns.
4. An unmountable disk with a corrupt filesystem
Sometimes the array starts but a disk shows as Unmountable: not mounted or Unmountable: no file system. This is a filesystem problem, not a missing disk, and it usually follows an unclean shutdown, a power cut, or a kernel panic mid-write.
Do not format the drive. Formatting is the one button that will actually erase your data here, and Unraid words the prompt in a way that trips tired people up at 1am.
Instead, start the array in Maintenance mode from the Main tab, click the unmountable disk, and run the filesystem check tool. For an XFS disk that means running the check first in read-only mode, then, if it reports a problem, running it again with the repair flag to let it fix the log and metadata.
- XFS disks: run
xfs_repairfrom the disk's check page, read-only first, then with-Lonly if it asks you to clear the log. - BTRFS disks: use the BTRFS scrub and check tools, and check the cache pool separately since BTRFS is common there.
- Cache/pool devices: a full cache pool or a dropped pool member can block a clean start too, so do not overlook it.
5. A stale or unreadable USB flash drive
Unraid boots and licenses itself from the USB key, and the array configuration lives on that key too. If the flash drive is dying, if it silently dropped to read-only, or if the config files got corrupted, the array can refuse to start even when every disk is perfectly healthy.
Symptoms include the GUID not matching your license, config changes that do not save, or the whole thing behaving oddly after a firmware or version update.
The good news is that USB keys are cheap and replaceable. If you keep a backup of the config folder, and you should, you can restore onto a fresh key in about fifteen minutes. Limetech's own guidance on backing up and replacing the flash drive is worth reading before you ever need it, because the process involves transferring your license GUID.
6. The array is simply set to not auto-start
This is the checkbox that fooled me, and it fools a surprising number of people. Under Settings, then Disk Settings, there is an Enable auto start option. If it is set to No, the array will sit in Stopped state after every boot and wait for you to press Start manually.
Nothing is broken. The button works, you just have to click it.
People often disable auto start on purpose while troubleshooting something else, then forget they did it. If your array starts fine when you click the button but never comes up on its own after a reboot, this setting is almost certainly the reason.
Quick reference for what you are seeing
| What the UI shows | Most likely cause | First move |
|---|---|---|
| Slot blank or Missing | Disk not detected | Reseat power and SATA cable |
| Slot flagged Wrong (red X) | Serial mismatch after a swap | Reassign correct disk to slot |
| Unmountable: no file system | Corrupt filesystem | Maintenance mode, run repair |
| Start works but not after reboot | Auto start disabled | Enable auto start in Disk Settings |
| License or GUID errors | Failing USB key | Restore config to a new flash drive |
Work the list, keep your hands off the format button
Almost every stuck array I have seen traces back to one of these six, and the vast majority are cabling or a forgotten setting rather than lost data. The dangerous mistakes are the ones made in a hurry: formatting an unmountable disk, or running New Config with the wrong layout.
If you slow down, read the exact wording in each slot, and match it to the list above, you will usually have the array back within an hour. And once it is running, take that flash backup and that screenshot of your disk assignments. Future you, staring at a red slot at midnight, will be grateful.
Frequently asked questions
Why is the Start button greyed out in Unraid?
A greyed out or inactive Start button almost always means Unraid has detected an invalid configuration, such as a missing disk or more failed disks than parity can cover. Check the Main tab for any slot flagged as Missing or Wrong in red. Once the disk assignments are valid again, the button becomes clickable.
Will I lose data if my Unraid array won't start?
In most cases no. Unraid refuses to start specifically to protect your data, and the usual causes are loose cables, a serial mismatch, or a disabled setting. The real data loss risk comes from clicking Format on an unmountable disk or running New Config with the wrong layout, so avoid both until you understand the problem.
What does Unmountable: no file system mean in Unraid?
It means the disk is present and detected but its filesystem is corrupt, often after an unclean shutdown or power cut. Do not format it. Instead start the array in Maintenance mode, select the disk, and run the filesystem check and repair tool, using xfs_repair for XFS disks.
Can a bad USB flash drive stop the Unraid array from starting?
Yes. Unraid boots and stores its array configuration on the USB key, so a dying or read-only flash drive can block the array even when every disk is healthy. Watch for license GUID errors or config changes that will not save, and restore your flash backup onto a new key if needed.
My array starts when I click Start but not after a reboot. Why?
This is the auto start setting. Go to Settings, then Disk Settings, and set Enable auto start to Yes. When it is set to No, the array stays stopped after every boot and waits for you to press Start manually, which is expected behaviour and not a fault.
How do I know if it's a loose cable or a failed drive?
If the drive does not appear in the slot dropdown at all, the controller is not seeing it, which points to cabling or the port. If it appears but is flagged with a read error, check the SMART report for reallocated or pending sectors before assuming the worst. Reseating power and SATA cables fixes a large share of these cases.
