Synology Reports Healthy but the Data Is Missing
DSM can show healthy drives and a normal system while the expected files are missing because SMART status does not validate the RAID, storage pool, volume, filesystem, snapshots, or shared-folder configuration.
Avoid creating new volumes or shares, running repair, or restoring data onto the same storage until the mounted volume and missing-data path are identified.
What this condition means
The system may have mounted a different or incomplete volume, the filesystem may be read-only or damaged, shared-folder configuration may no longer point to the expected path, or a storage-pool event may have separated the current DSM view from the original data.
A healthy label is useful, but it describes the layer DSM is checking. It cannot establish that the missing files were deleted or that the underlying blocks are intact.
What to record
- Synology model, DSM version, and recent updates
- Storage pool, volume, filesystem, and snapshot status
- Expected shared folders and when they were last visible
- Bay order and serial number of each member
- Migration, reset, repair, replacement, or restore history
What not to do
- Recreate missing shared folders immediately
- Initialize an offered disk or volume
- Run repair repeatedly
- Restore backups onto the affected pool
- Assume passing SMART tests rule out storage failure
How ADR evaluates it
ADR reviews the DSM storage layers, RAID assembly, volume metadata, filesystem, and share paths in sequence. The goal is to locate the existing data before any repair changes those layers.
If member reads are stable, diagnosis and recovery may be performed remotely. Unstable members are imaged first.
What happens next
Many healthy-but-empty Synology cases retain recoverable file data. The result depends on whether the data is merely unpresented, structurally damaged, deleted, or overwritten.