NAS storage emergency · September 10, 2026
A NAS that says “Degraded” may still open every shared folder, but that does not mean it is safe to keep working as usual—or safe to pull the first drive with a red light. The first job is to preserve evidence, identify the exact pool and failed member, verify a separate backup, and then follow the procedure for that NAS model and RAID layout.
Guidance checked September 10, 2026, at 3:41 p.m. Eastern / 19:41 UTC against current Synology DSM and QNAP QTS documentation. Menu names, hot-swap support, replacement-drive rules, and fault tolerance vary by model, operating-system version, storage-pool design, and RAID type.
The short version: keep the NAS powered and stable unless there are signs of physical distress; photograph the alert, record the chassis and drive-slot map, confirm which pool and drive the management interface identifies, copy irreplaceable current data to a separate destination, then use the exact vendor repair workflow. Synology and QNAP both distinguish a degraded but accessible protected array from a healthy one.[1][2]
Why a degraded NAS can become an expensive emergency
RAID can keep a service available after a permitted number of drive failures, but the array has lost some or all of its remaining fault tolerance. QNAP says a degraded RAID group can remain accessible when the failures are within that RAID type’s tolerance.[2] That useful uptime window is for controlled backup and repair—not proof that another drive, cable, power supply, controller, or filesystem problem cannot finish the outage.
A NAS can hold company files, QuickBooks exports, camera recordings, project archives, family photos, and computer backups. A wrong-slot pull, incompatible replacement, sudden shutdown, or rebuild started without a current backup can turn a manageable single-drive event into a recovery case. The risk is highest when more than one disk reports trouble, the pool is no longer mounted, the NAS is clicking or repeatedly rebooting, or the data exists nowhere else.
Stop condition: Do not initialize, format, erase, create a new pool, change RAID type, force-assemble an array, run an unknown repair command, or remove multiple drives. If the pool is crashed or unmounted, two or more members are missing or failing, a drive is making unusual mechanical sounds, the enclosure is unstable, or the only copy is irreplaceable, stop ordinary DIY repair and preserve the system for model-specific support or professional recovery.
The safe response ladder
Freeze the scene before touching hardware
Photograph the front of the NAS, every bay and status light, the exact warning, and the storage-pool screen. Record the NAS model, serial number, operating-system version, pool name, RAID type, volume status, failed-drive slot, drive model/capacity, and time the alert began. If bays are not already numbered clearly, make a written left-to-right map without moving anything.
Classify the state: degraded, crashed, read-only, or physically distressed
“Degraded but accessible” is a different situation from “Crashed,” “Not mounted,” or repeated boot failure. Synology describes a degraded protected pool as one where one or more drives are defective while the pool remains accessible because the RAID layout has not yet lost data.[1] QNAP similarly says data remains accessible when failures stay within the RAID type’s tolerance.[2] If your state is worse than that description, do not treat a generic drive-swap checklist as permission to proceed.
Verify the failed member in software—not by LED color alone
Open the storage manager and identify the pool, RAID group, and member disk the system marks as defective or missing. Synology’s repair guidance explicitly sends administrators to the HDD/SSD page to confirm which drive is defective before removal.[1] Match the reported slot to the chassis map twice. In an expansion enclosure, confirm which enclosure the slot number belongs to.
Prove a separate backup before starting a rebuild
Open several important files from a destination that is not the affected storage pool, including one current file and one older version. If no current separate copy exists and the pool is still readable, prioritize a controlled copy of the hardest-to-replace data before a rebuild. Synology warns that even a multi-version local copy on the same NAS can still be lost to RAID crash or hard-drive failure, and documents external, remote-NAS, file-server, and cloud destinations.[3]
A backup job marked “successful” is not enough: verify the destination, date, file count or protected scope, and an actual restore sample. Do not use the suspect replacement disk as the only new backup destination if the repair process will erase it.
Check the exact model’s hot-swap and replacement-drive rules
Do not assume every multi-bay NAS supports hot-swapping. Synology says to power off models that do not support hot-swap before removing or installing drives.[1] Also verify interface type, capacity, sector format, vendor compatibility list, and the array’s sizing rule. Synology notes that the acceptable replacement size depends on RAID or SHR layout and warns that data already on the replacement drive will be erased.[1]
Replace only the confirmed failed member
Label the removed drive with the NAS, date, and slot, and keep it untouched until the array is healthy and the backup has been retested. Insert only the reviewed replacement in the confirmed bay. Do not shuffle healthy members, reuse a disk with uncertain history, or replace a second drive while the first rebuild is incomplete.
Use the vendor’s repair command and monitor the whole rebuild
In Synology DSM, the documented path is to select the degraded pool and use Repair after installing an eligible replacement.[1] In QNAP QTS 5.1, the documented path selects the degraded RAID group and uses Rebuild RAID Group; QTS determines how many free disks are required.[2] Your interface may differ, so use the documentation for the installed version rather than copying another model’s buttons.
During rebuild, avoid firmware upgrades, shutdowns, cable work, storage expansion, large migrations, and unnecessary heavy workloads. Watch temperatures, new disk errors, and rebuild progress. If another member reports errors or the pool drops offline, stop and reassess.
Verify health, then verify the backup again
Completion means more than a progress bar reaching 100%. Confirm the pool and volume are healthy, all expected shares mount, critical files open, scheduled jobs run, alerts are delivered, and a backup restore still works. Keep the removed drive and incident notes until the repaired system has remained stable through a backup cycle and the business owner accepts the result.
Affected, not affected, and needs-more-checking
Phone readers: swipe the table left to see every column.
| Situation | What it suggests | Safest next move |
|---|---|---|
| One drive failed; RAID 1, 5, 6, 10, SHR, or another protected layout is degraded but readable | A controlled repair may be possible within the layout’s fault tolerance | Preserve evidence, verify backup, confirm the exact member and model rules, then follow the matching vendor repair workflow.[1][2] |
| RAID 0, JBOD, Basic, or a single-drive pool reports failure | There may be no redundancy to rebuild from | Do not assume another disk contains a complete copy; use the exact layout documentation and recovery plan. |
| Two or more disks are missing, warning, or failing | The array may be at or beyond its fault tolerance | Stop drive swaps and seek model-specific assistance, especially when no verified backup exists. |
| Pool is crashed, unmounted, or asks to initialize | This is not the ordinary degraded-and-readable case | Do not initialize or create a new pool. Preserve screenshots and the original disk order. |
| NAS is healthy but one drive shows warning sectors or predicted failure | Proactive replacement may be available | Verify backup and use the vendor’s preventive-replacement workflow for that model; do not wait for a second fault. |
| The “backup” is another folder or snapshot on the same pool | It may help with deletion but not pool loss | Create and test a copy on a different device or service.[3] |
Good response versus dangerous shortcuts
Good approach
- Photograph warnings, bays, and drive order.
- Confirm the failed member in the management interface.
- Verify a separate restore before the rebuild.
- Check model-specific hot-swap and disk requirements.
- Replace one confirmed member and monitor the full rebuild.
- Retest shares, alerts, and backups afterward.
Bad approach
- Pull the first blinking drive without matching the slot.
- Remove several disks to “reseat everything.”
- Initialize a pool because a wizard promises repair.
- Use a smaller or unverified replacement disk.
- Start a firmware update during degraded operation.
- Treat same-pool snapshots as the only backup.
Two realistic examples
The safe, boring win
A four-bay office NAS reports one degraded RAID 5 group but all shares still open. The owner photographs the bays, confirms Disk 3 in the management interface, restores current payroll exports from an off-device backup, verifies that the model supports hot-swap, installs a compatible equal-or-larger drive in Bay 3, and uses the documented rebuild command. The old drive stays labeled and untouched until the new backup cycle passes.
The costly wrong turn
A user sees two red LEDs, pulls both drives, then reinserts them in different bays and accepts an initialization prompt. The original member order and evidence are now harder to reconstruct, and the write may overwrite metadata needed for recovery. The safer move was to stop at the multiple-failure boundary, preserve the exact layout, and get model-specific help before any write.
Related safeguards
- If an external disk is missing, use our external-drive “do not initialize” diagnostic ladder.
- A green backup dashboard is not proof of recovery. Run our one-file restore test.
- If ransomware is already visible, switch to the first-15-minutes containment checklist rather than starting a storage rebuild.
FAQ
Does “Degraded” mean my files are already gone?
Not necessarily. Synology and QNAP both document degraded states in which a protected array remains accessible.[1][2] It does mean you should treat the remaining availability as a limited repair window, verify a separate backup, and avoid unnecessary changes.
Can I keep using the NAS during a rebuild?
Some platforms keep data online, but a rebuild adds sustained disk work and the array has reduced protection. Minimize nonessential load, do not combine the rebuild with upgrades or migrations, and follow the model’s official guidance.
Can I replace the bad disk with any larger drive?
No. Capacity is only one requirement. Interface, sector format, model compatibility, RAID layout, and vendor rules matter. Synology’s documented minimum-size rule changes with RAID and SHR layout, and it warns that the replacement disk will be erased.[1]
Should I shut down before pulling the failed drive?
Only after checking the exact model. Synology says systems without hot-swap support must be powered off before drive removal or installation.[1] An unplanned shutdown also carries risk, so do not guess.
Is RAID itself a backup?
No. RAID availability and backup are different controls. Synology says a local multi-version copy on the same NAS can still be lost to RAID crash or hard-drive failure and points users to different backup destinations.[3]
Your next 10 minutes
- Photograph the warning, front bays, and current storage screen.
- Write down the NAS model, software version, pool, RAID type, and reported slot.
- Open one current and one older file from a separate backup destination.
- Download the repair and hardware guide for the exact model and software version.
- If there is more than one failed member, no verified backup, physical noise, or an unmounted pool, stop before touching a drive.
Treasure Coast help: The IT Guys can help identify the pool, preserve the slot map, verify backups, and plan a model-specific repair for homes and small businesses in Port Saint Lucie, Jensen Beach, Fort Pierce, and Vero Beach. Do not send passwords, encryption keys, customer records, or private file listings through an ordinary contact message.
Sources
- Synology Knowledge Center — Repair a Storage Pool.
- QNAP QTS 5.1.x — Recovering a RAID group with a Degraded status.
- Synology Knowledge Center — How can I back up my Synology NAS?.
Evidence boundary: These sources describe vendor-specific degraded-array, repair, and backup behavior. They do not identify your failed bay, prove your backup, guarantee a rebuild, or make one vendor’s steps safe on another system. Check the exact model, software version, and storage layout before changing hardware.