A practical guide to monitoring Synology disk health
A Synology NAS can quietly protect family photos, business documents, media libraries, and backup copies for years, but reliable storage depends on early detection. Disk health monitoring is the process of finding warning signs before a drive failure becomes data loss, a degraded RAID volume, or an urgent replacement project.
DSM provides several useful tools, including S.M.A.R.T. information, storage pool alerts, bad-sector scans, and notifications. These features work best as part of a routine rather than as occasional checks after a warning appears. Good monitoring combines automated alerts with scheduled inspections and a tested backup strategy.
The same principles apply whether a NAS uses traditional hard drives, SSDs, SHR, RAID 1, RAID 5, RAID 6, or another configuration. Readers comparing storage hardware and backup features can use WhichNAS storage guides to evaluate how different Synology systems handle capacity, redundancy, and administration.
Understand what DSM is reporting
Synology DSM separates several related storage concepts. A physical drive may show a healthy or failing status, while the storage pool and volume have their own conditions. A drive can also report normal S.M.A.R.T. values while a RAID rebuild, filesystem error, or connection problem affects the volume.
S.M.A.R.T., or Self-Monitoring, Analysis and Reporting Technology, records attributes such as temperature, reallocated sectors, pending sectors, power-on hours, and error counts. These values are useful indicators, but they are not a guarantee that a disk will continue working. Some drives fail without giving much advance warning, while others accumulate concerning values gradually.
In Storage Manager, check HDD/SSD for the current condition of each installed drive. Review Storage Pool for degradation, repair activity, or critical status, and open Volume to inspect capacity and filesystem information. This distinction matters because replacing a drive based only on the volume screen may overlook another disk that is already developing problems.
Configure alerts before they are needed
A monitoring system is only useful when someone receives and acts on its warnings. In DSM, configure email, push notifications through the Synology mobile applications, or another supported notification channel. Confirm that alerts arrive by sending a test message rather than assuming the settings are correct.
Enable notifications for disk health warnings, abnormal temperatures, bad sectors, storage pool degradation, failed S.M.A.R.T. tests, and volume errors. Also monitor failed backups, insufficient capacity, and unexpected shutdowns. A healthy disk is less reassuring if the NAS has stopped sending backup copies or has no free space for a rebuild.
Use a mailbox or notification destination that is checked regularly. For a business NAS, send critical alerts to more than one responsible person, but avoid creating so much noise that important warnings are ignored. Keep a simple incident record with the date, disk bay, alert text, and action taken. This history can reveal recurring cabling, cooling, or power problems.
Schedule S.M.A.R.T. and surface tests
Quick S.M.A.R.T. tests are relatively short checks that can run regularly, often weekly or monthly depending on the workload. Extended tests read much more of the disk surface and take considerably longer. Schedule them during periods when the NAS is lightly used, since heavy activity can increase duration and reduce operational convenience.
A test result should be interpreted alongside its history. One completed test does not prove that a drive is permanently safe. Look for changes in reallocated sectors, pending sectors, uncorrectable errors, read errors, and temperature. A rising count is more important than a single isolated value, especially when it appears across multiple tests.
Surface checks and data scrubbing serve different purposes. A disk test examines drive behavior, while RAID or storage-pool scrubbing verifies data consistency and can identify mismatches that redundancy may repair. Schedule data scrubbing according to the storage pool and workload, allowing sufficient time for the operation to complete without disrupting critical services.
Track temperature, capacity, and operating conditions
Temperature is an important part of NAS disk health. Sustained heat can accelerate wear, while sudden temperature changes may indicate a failing fan, blocked ventilation, or an unsuitable installation location. Keep the NAS away from enclosed cabinets with poor airflow, dust buildup, radiators, and direct sunlight.
Check drive temperatures during normal use and during demanding tasks such as large transfers, indexing, video conversion, backup jobs, and RAID repairs. A brief rise may be normal, but a persistent increase deserves investigation. Clean vents carefully, confirm that fans are operating, and make sure cables are not obstructing airflow.
Capacity also affects reliability. Maintain enough free space for snapshots, temporary files, package updates, and RAID rebuild operations. A nearly full volume can make maintenance slower and reduce flexibility during a disk replacement. If the NAS hosts surveillance recordings or a media server, review retention policies before storage pressure becomes an emergency.
Recognize warning signs and replace drives safely
Common warning signs include increasing bad sectors, repeated S.M.A.R.T. failures, unusual clicking, slow response, frequent disconnections, read-only volume behavior, and a storage pool that becomes degraded. A single warning does not always identify the exact cause, since a faulty cable, backplane, power supply, or controller can produce similar symptoms.
When DSM marks a drive as failing, verify the alert and review recent logs, but do not postpone replacement while waiting for a complete failure. Confirm the correct bay, serial number, capacity, interface, and compatibility of the replacement. For a redundant array, use a drive that is at least as large as the member being replaced; apparent capacity differences can matter because manufacturers quote decimal sizes while DSM uses usable binary capacity.
Before removing anything, confirm that current backups are available and readable. Follow Synology’s replacement procedure for the specific RAID or SHR arrangement. After installation, monitor the repair or rebuild continuously enough to notice a second failure, abnormal temperature, or expanding error count. Avoid unnecessary heavy workloads during this vulnerable period.
| Monitoring area | What to check | Useful frequency | Action when abnormal |
|---|---|---|---|
| Quick S.M.A.R.T. test | Overall result and changing attributes | Weekly or monthly | Investigate trends and schedule replacement if values worsen |
| Extended disk test | Surface-read and error behavior | Every few months | Back up immediately and replace a suspect drive |
| Drive temperature | Sustained heat and unusual differences | Weekly review, plus alerts | Improve airflow and inspect fans or room conditions |
| Storage pool | Degraded, critical, or repairing status | Automated alerts and weekly review | Stop nonessential work and follow the recovery procedure |
| Data scrubbing | Consistency of redundant data | Scheduled by workload | Review errors, backups, and pool condition |
| Backup jobs | Completion, version history, and restore ability | Every job with periodic restore tests | Repair the backup process before relying on it |
Pair disk monitoring with independent backups
RAID and Synology Hybrid RAID improve availability, but they are not backups. They can protect against some drive failures while leaving files exposed to accidental deletion, ransomware, theft, fire, filesystem damage, or a failed NAS chassis. A robust plan keeps at least one copy separate from the primary device.
Use a layered approach when practical: another NAS, an external USB device, cloud storage, or an off-site location. Apply versioning so that corrupted or deleted files can be recovered from an earlier point in time. Encrypt portable and cloud-based copies, and restrict administrative access to backup destinations.
Restores are the real test of a backup. Periodically recover individual files, folders, and, where relevant, application data. Record how long recovery takes and whether permissions, names, and metadata are preserved. When documenting equipment stored at a property, older maintenance references—such as facility service records—can also help establish who is responsible for checking power, cooling, and physical access around the NAS.
Create a routine that fits the NAS
A small home NAS may need only automated alerts, monthly health reviews, and regular backup verification. A business system with multiple storage pools, virtual machines, surveillance workloads, or demanding media services needs more formal ownership. Assign a person to review alerts and define the response time for critical, warning, and informational events.
Keep firmware, DSM, drive compatibility information, and package updates under review, but schedule updates carefully. Read release notes, verify backups, and avoid making several major changes during an active rebuild. Monitoring is easier when the system has a clear baseline for temperature, capacity, workload, and normal test duration.
Actions worth adding to the maintenance calendar
- Enable email or push alerts and test every notification destination.
- Run recurring quick and extended S.M.A.R.T. tests during low-use periods.
- Review storage pools, volumes, temperatures, and capacity at least monthly.
- Schedule data scrubbing and record any consistency or repair errors.
- Test file restores and confirm that replacement drives match the array requirements.
Treat every disk-health alert as information that requires a decision, not as an inconvenience to dismiss. Open DSM, identify the affected drive or pool, confirm the latest backup, and document the next action. A short, repeatable review performed throughout the year can turn an unexpected disk failure into a controlled maintenance task.