Hardware fault isolation
A Synology NAS can report a drive as missing or unstable when the real problem is the disk, the bay, the backplane, an expansion connection or power. Synology’s current diagnostic procedure focuses on one high-value observation: after data is protected and the storage state is safe for testing, does the error move with the suspected disk or remain tied to the physical slot?
Quick answer
The error path is more useful than one health badge
If the suspect drive remains faulty in a known-good slot, replace the drive. If a healthy drive develops the same error in one bay, the slot or chassis becomes the leading suspect.
Current Amazon listings
Replacement and migration DiskStation options
Product cards are supporting purchase references only; they do not determine whether your failed drives are recoverable or whether a specific migration pairing is supported.
Technical decision
Do not perform the swap test casually on an unhealthy array
A controlled diagnostic requires known bay order, adequate redundancy or backup, and a clear plan for putting drives back. On a crashed or critically degraded array, preservation takes priority over experimentation.
Interactive recovery tool
Drive vs Bay Diagnostic
This tool routes the symptoms you select to a safer next step. It does not issue destructive commands. Before initializing a disk, deleting a pool, reinstalling DSM or moving the only copy of important data, verify the exact live Synology procedure for your model and DSM build.
Recovery safety checklist
Four rules before you change a failing Synology system
Preserve readable data first
If unique files can still be opened, copy or back them up before changing storage metadata, reinstalling DSM or running stressful diagnostics.
Record drives and bays
Capture drive serial numbers, bay positions, health states and DSM messages before swapping disks or moving them to another chassis.
Match the action to the failure layer
A degraded pool, crashed volume, failed system partition, bad drive and failed bay have different supported recovery paths.
Keep a rollback path
During migration or recovery, do not erase the source system until the destination data, permissions, applications and backups have been verified.
Start with a map of disks to bays
Write down every bay number, drive serial, capacity and current DSM status. A physical swap without this map can create confusion later about which drive originally belonged to which slot.
During drive-versus-slot isolation, start with a map of disks to bays becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Review the error types before moving hardware
Drive slot disabled, controller detection failures, repeated connect/disconnect logs and I/O timeouts all support a path-related diagnosis. A pure SMART media warning points more strongly toward the drive itself.
During drive-versus-slot isolation, review the error types before moving hardware becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Verify the storage pool can tolerate a swap
If redundancy is already exhausted, removing another member can make the volume inaccessible. Back up first and use Synology’s supported repair or recovery procedure instead of diagnostic swapping when the pool is unstable.
During drive-versus-slot isolation, verify the storage pool can tolerate a swap becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Use an empty known-good bay when available
Moving the suspect drive to a functioning unused bay gives a cleaner test because no healthy array member has to be disturbed. Monitor whether the same drive continues to produce errors in the new location.
During drive-versus-slot isolation, use an empty known-good bay when available becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
A healthy-drive swap can expose a bad slot
When there is no empty bay, Synology documents swapping the suspect disk with another healthy one on multi-bay systems after appropriate preparation. If the healthy disk now fails in the original bay, the physical slot becomes suspect.
During drive-versus-slot isolation, a healthy-drive swap can expose a bad slot becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
An error that follows the disk points toward the disk
A drive that remains unstable regardless of which known-good bay it occupies likely has an internal media, electronics or connector problem. Replace it with a compatible drive and restore pool redundancy.
During drive-versus-slot isolation, an error that follows the disk points toward the disk becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
An error that stays in the bay points toward the NAS
When different healthy drives show faults in one specific bay, stop blaming the disks. Backplane, connector or chassis issues can damage reliability and may justify replacing the NAS rather than continuing to rotate drives through the bad path.
During drive-versus-slot isolation, an error that stays in the bay points toward the nas becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Expansion units require cable isolation too
DX units add a cable and expansion controller between DSM and the disks. If several drives in the expansion unit disappear together, validate the expansion connection before assuming several simultaneous disk failures.
During drive-versus-slot isolation, expansion units require cable isolation too becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
SMART evidence should travel with the serial number
Save health results by drive serial, not by bay label. After moving a disk, Drive 2 may no longer refer to the same physical device, while the serial number remains stable.
During drive-versus-slot isolation, smart evidence should travel with the serial number becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Temperature can reveal chassis-level problems
A failed fan or restricted airflow can make multiple disks in one region run hot and unstable. Compare temperatures across bays and check fans before concluding that several drives independently failed.
During drive-versus-slot isolation, temperature can reveal chassis-level problems becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
A slot failure turns migration into the safer repair
If the chassis path is unreliable, replacing individual disks does not solve the root cause. A planned migration to another Synology NAS with verified backup gives the data a stable platform and reduces repeated rebuild exposure.
During drive-versus-slot isolation, a slot failure turns migration into the safer repair becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Finish with a stable-state verification
After replacing the bad component, confirm the pool returns to Healthy, drive logs stop accumulating errors and backups complete normally. Fault isolation is only complete when the symptoms do not return under ordinary workload.
During drive-versus-slot isolation, finish with a stable-state verification becomes meaningful only after the original disk map has been written down and a safe comparison path exists. Keep the suspected drive's serial number separate from the bay label, because those two identities diverge as soon as hardware is moved. The diagnostic goal is simple: determine whether the symptom follows the physical disk or remains with one chassis position. If the array cannot tolerate that movement, the correct outcome for this checkpoint is to postpone the test and protect data first.
Questions people ask
Synology Drive Failure vs Drive Slot Failure questions
How do I tell if the Synology drive or bay is bad?
After protecting data, move the suspect disk to a known-good bay or place a healthy disk in the suspect bay. See whether the error follows the disk or remains with the slot.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
What if the error follows the drive?
The drive is the leading suspect. Replace it with a compatible disk and repair the storage pool according to the RAID or SHR procedure.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
What if the error stays with the slot?
The slot, backplane or chassis is likely faulty. Back up the NAS and consider replacing the system.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Can SMART prove the bay is good?
No. SMART describes the drive's internal health and cannot fully test the NAS connection path.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Should I swap drives in a degraded pool?
Only when the pool can safely tolerate it and you understand the recovery state. Backup and supported repair take priority.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Can an expansion cable cause missing drives?
Yes. A failing or loose expansion connection can affect several drives in a DX unit.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Should I preserve drive order?
Yes. Record bay locations and serial numbers before any swap so the original array membership remains clear.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Can heat cause bay-specific errors?
Poor cooling can affect drives or regions of the chassis. Check fan operation and temperatures as part of hardware diagnosis.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Do I need a new NAS for one bad bay?
Synology recommends backing up and replacing the storage system when the fault is tied to the drive slot rather than the disk.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
How do I know the problem is solved?
The pool should return to Healthy, the affected drive or replacement should stay stable, and drive logs should stop showing recurrent I/O or connection errors.
Drive-versus-slot diagnosis depends on controlled comparison. If the pool is unsafe for a swap, recovery comes before fault isolation.
Official references and methodology
Verify the live DSM state before any destructive recovery step
This diagnostic page is built around fault isolation. It uses Synology's controlled cross-check: observe whether the same drive fails in a known-good bay and whether a healthy drive fails in the suspect bay. The method should only be used when the storage state and redundancy make a swap safe; otherwise the correct outcome is to preserve data and escalate rather than create a second fault during testing.
- Synology: Determine whether errors come from the drive or slot
- Synology: Repair a storage pool
- Synology: S.M.A.R.T. test FAQ
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Failure states, DSM behavior, migration compatibility and recovery options can change by model and DSM build. Preserve readable data and verify Synology's current Knowledge Center instructions before initializing drives, deleting pools, reinstalling DSM or changing the only copy of important data.