Short answer: When a NAS becomes inaccessible, do not reset it, remove drives or recreate a storage pool until you know whether the fault is network, account, file service, DSM or storage. Record when it began, who is affected, indicator lights, previous IP and the latest backup. If a pool or volume is unhealthy, preserve the current state and involve qualified recovery help.
This is an initial business incident triage, not model-specific repair instructions. After containment, review Synology solutions and five NAS recovery mistakes to avoid increasing data loss risk.
Scope the outage before touching the appliance
If one workstation fails while others still connect, inspect that client’s network, VPN, DNS, SMB mapping and credentials. Do not declare a failed NAS. If everyone is affected, check power and UPS status, Ethernet and switch ports, IP and recent router or firewall changes. Use Synology-supported discovery on the local network. Record DSM access and SMB file access separately: a reachable login page does not prove shared folders work.
Pause potentially destructive sync when mass deletion or ransomware is suspected. Ask staff not to repeatedly guess passwords if account lockout applies. Capture the exact error, start time and affected users so logs can be correlated. Change one configuration at a time rather than making several blind adjustments.
If DSM is accessible: separate rights, service and storage
Check whether the account is locked or lost a group/shared-folder permission. Verify the file protocol in use, the share name and a known-good test client. If just one share fails, review its permissions before changing the whole NAS. Examine security and configuration events, but do not post sensitive logs publicly.
In Storage Manager, inspect the pool, volume, individual drives and free space. Capture degraded/crashed or warning/critical states before repair. Replace a drive or start Repair only after identifying the correct member, RAID layout, remaining tolerance, compatible replacement and a suitable data copy. Rebuilds add load. Never remove multiple drives or create a fresh pool as a troubleshooting experiment.
If DSM is unavailable: inspect hardware without wiping state
Synology’s troubleshooting begins with power supply, adapter, Power/Status/LAN indicators, cable and connection path. Distinguish an appliance that will not boot from one that boots under a changed DHCP address. If network settings appear wrong, read the exact vendor procedure for the model and DSM before using RESET; a reset can change IP, administrator access and configuration. It is not the first response to suspected data loss.
For beeps or an unresponsive NAS, record indicators and errors before any shutdown. Avoid repeated forced power cycles, mixing drive order, initializing drives on another computer or reinstalling DSM without an assessment and backup. Such actions can destroy evidence or overwrite recoverable data. Escalate when multiple drives or high-value data may be at risk.
Prove service and data recovery before closing
Once the fault is known, make one controlled fix and test using an actual user account. Check read/write rights, sample files, dependent applications, capacity and alerts. Correlate the incident with network, patch, permission or disk changes and log the approver. If backup is needed, choose a clean recovery point and perform a documented restore test before reconnecting bulk sync.
The incident record should state impact, root cause, downtime, known data loss, backup point, action taken and residual risk. Configure alerts for pool health, capacity, logins and backup failures. One successful login is not proof the storage system is safe again.
Frequently asked questions
Does a failed ping mean the drives failed?
No. Power, cable, switch, IP/DHCP or the client network may be responsible. Check the path before concluding a storage fault.
Should we press RESET after losing the IP address?
Only after supported discovery steps and reading the exact DSM/model procedure. Reset alters some settings and is unsuitable as a blind experiment during data risk.
What if the pool is degraded but accessible?
Protect important data, identify the correct failed drive and remaining fault tolerance, then follow the vendor or a qualified technician’s procedure.
Technical sources
Synology: local connection troubleshooting; Synology: unresponsive NAS; Synology: abnormal drive status. Apply to the actual model, DSM and device state.




