RAID degraded/offline — what NOT to do before sending it to a lab

RAID “Degraded”/offline — why it is a high-risk state

The “Degraded” message means the array is operating in emergency mode (redundancy is missing or one of the copies is inconsistent). In this state, one careless step can overwrite metadata and make reconstruction much harder. If your data matters, the priority isstopping all writesand securing read access. In the case of arrays and NAS systems, the safest path is to move toRAID/NAS array reconstruction(with no blind rebuilds).

What you absolutely must NOT do before handing it over to a laboratory

• Do not startrebuild/re-sync“just to see what happens”.
• Do not re-initialise the array and do not create new volumes.
• Do not update the controller/NAS firmware during the incident.
• Do not change the disk order or swap drives blindly.
• Do not run file-system repair tools on the volume; they can change the structure permanently.

What to do instead (safe checklist)

• Stop services that are writing data (VMs, databases, shares) and perform a controlled shutdown.
• Take photos/screenshots: array status, error messages, bay order, models and serial numbers.
• Label the drives (slot 1/2/3/…) and do not start them individually in an operating system.
• If possible, prepare the configuration details (RAID level, stripe size, controller model).

When to report the case

If the array is in “Degraded” state, read errors appear, the volume disappears, or the NAS will not boot, the safest option is to move toRAID/NAS data recovery. In the laboratory, we start with imaging the drives (including cases where the array uses SSDs:SSD/NVMeor traditional spinningHDD), and only then do we reconstruct the volume on the copy.

Reporting the case:describe the error messages and the NAS/controller model — you will receive a safe action plan.Request form.