Drive and bay diagnostics
A missing drive in Synology DSM can be caused by the disk itself, a drive slot, an expansion connection, power or intermittent I/O. Synology’s current diagnostic method is deliberately comparative: determine whether the error follows the suspected drive when it is moved to a known-good bay, or whether a healthy drive develops errors in the original bay. That test is useful only after the storage state is safe enough to move hardware.
Quick answer
Do not swap drives until you know the pool can tolerate it
If the storage pool is already degraded or crashed, an unnecessary drive move can remove the wrong member and increase risk. Record bay order, serial numbers and current status before touching the chassis.
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
The decisive clue is whether the problem follows the drive or stays with the slot
A fault that follows the disk points toward media or drive electronics. A fault that remains in the same bay with another healthy drive points toward the bay, backplane or NAS hardware. Expansion-unit systems add cable and expansion compatibility as another layer.
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.
Record the exact DSM message first
Cannot be detected by controller, Drive slot disabled, repeated plugged-in or plugged-out events and I/O command timeouts are different clues. Save screenshots and logs before reseating anything so the diagnostic evidence does not disappear after a reboot.
For a missing-drive investigation, record the exact dsm message first should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Confirm whether the pool is already vulnerable
A healthy redundant pool can tolerate controlled testing more safely than a degraded pool with no remaining fault margin. If the system already reports Degraded or Crashed, prioritize data protection and the supported repair procedure over exploratory hardware swaps.
For a missing-drive investigation, confirm whether the pool is already vulnerable should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Power and seating problems can imitate a dead drive
A partially seated carrier, vibration, connector contamination or power instability can make a healthy disk vanish intermittently. Power down when the model and procedure require it, reseat carefully and avoid repeated hot swaps simply to see whether the drive returns.
For a missing-drive investigation, power and seating problems can imitate a dead drive should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Expansion units add another connection to test
When the missing drive sits in a DX expansion unit, verify that the expansion model is supported, the cable is secure and the expansion unit itself is stable. A disappearing expansion link can make several drives look suspicious at once.
For a missing-drive investigation, expansion units add another connection to test should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
The drive-versus-slot test needs a controlled baseline
Synology recommends moving the suspected disk to a functioning empty slot or swapping it with a healthy disk on multi-bay systems. The result matters only when you can identify which disk is which afterward, so label bays and serial numbers before the test.
For a missing-drive investigation, the drive-versus-slot test needs a controlled baseline should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
If the error follows the drive, replace the drive
When the suspected disk continues to report errors in a known-good slot while the healthy disk works normally elsewhere, the drive becomes the leading cause. Confirm compatibility for the replacement and follow the storage-pool repair procedure appropriate to the RAID type.
For a missing-drive investigation, if the error follows the drive, replace the drive should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
If the error stays with the slot, suspect the NAS
A healthy disk that starts producing the same errors in one specific bay points toward the slot, backplane or chassis. Synology’s guidance is to back up data and consider replacing the NAS when the slot itself is faulty rather than repeatedly sacrificing drives to the same connection.
For a missing-drive investigation, if the error stays with the slot, suspect the nas should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
SMART data can support but not replace the swap test
A disk can fail intermittently without an obvious SMART threshold, and a controller path can produce I/O errors while SMART looks clean. Combine drive health data with physical-location behavior instead of treating either source as definitive on its own.
For a missing-drive investigation, smart data can support but not replace the swap test should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Do not initialize an unexpectedly missing array member
A drive that reappears as uninitialized after a fault should not be casually added to a new pool. Confirm the original array state and recovery procedure first because initialization writes metadata that can destroy evidence of the previous layout.
For a missing-drive investigation, do not initialize an unexpectedly missing array member should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Check logs after the system is stable
DSM 7.2 and later expose drive-related entries through Log Center. Look for recurring I/O errors, reconnection events and timeouts tied to a bay or serial number. A timeline often reveals whether the disappearance was sudden or part of a longer deterioration.
For a missing-drive investigation, check logs after the system is stable should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Replacement drives should solve the actual capacity requirement
When a disk truly failed, replacement is also an opportunity to check minimum size rules and planned expansion. Do not buy a smaller nominal drive that cannot satisfy the existing RAID member size, and verify exact-model compatibility before installation.
For a missing-drive investigation, replacement drives should solve the actual capacity requirement should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Preserve a backup before a chassis diagnosis
A suspected bad bay can worsen unpredictably. If the data remains accessible, complete an independent backup before extended hardware testing or migration. Chassis diagnostics are easier when the only copy of the data is no longer sitting on the unstable system.
For a missing-drive investigation, preserve a backup before a chassis diagnosis should be tied to a physical identity: bay number, drive serial, expansion location and the exact controller message. Photograph the original arrangement before reseating anything. A useful diagnostic step must distinguish whether the failure travels with the disk or remains attached to the chassis path, while avoiding an extra member removal from a vulnerable array. If this checkpoint cannot be performed without sacrificing remaining redundancy, stop the experiment and secure the dataset before continuing hardware isolation.
Questions people ask
Synology Drive Not Detected questions
Why is my Synology drive not detected?
Possible causes include a failed disk, bad bay or backplane, expansion connection problem, power issue or intermittent I/O. The error location and swap behavior help separate them.
A drive-detection answer should preserve bay order and array safety first; only then should controlled swapping be used to separate disk failure from slot failure.
Should I move the missing drive to another bay?
Only after confirming the pool state and recording bay order. A controlled swap can identify whether the error follows the drive or remains with the slot.
What does Cannot be detected by controller mean?
DSM cannot communicate reliably with the drive through the controller path. The fault can be the disk or the connection to that bay.
Can a bad Synology bay make a good drive look failed?
Yes. If a known-good drive produces errors in the same bay while the suspect disk behaves normally elsewhere, the slot or chassis becomes the likely cause.
Should I reboot first?
A reboot may temporarily change the symptom but can erase useful timing evidence. Record the status and logs first, and avoid repeated reboots on unstable storage.
Can SMART be healthy while the drive is still bad?
Yes. Some intermittent failures do not immediately cross SMART thresholds, and controller-path issues can also generate errors. Use multiple signals.
What if several expansion-unit drives disappear together?
Check the expansion connection and unit health before assuming several disks failed simultaneously.
Can I initialize the missing drive when it reappears?
Do not initialize it casually. Initialization writes metadata and can damage recovery options if it belonged to the original pool.
What replacement size should I buy?
Use a drive that satisfies the existing pool’s minimum member size and Synology compatibility requirements. Equal or larger capacity is generally safer than smaller nominal capacity.
When should I replace the NAS instead of the drive?
When errors consistently stay with a specific slot using healthy disks, Synology treats the slot or chassis as suspect and recommends backing up before replacing the system.
Official references and methodology
Verify the live DSM state before any destructive recovery step
This detection guide separates physical presence, controller visibility, DSM recognition and storage-pool membership. The recommended checks start with cabling, bays and safe reseating conditions, then use Synology's drive-versus-slot isolation logic when a controlled swap is appropriate. No destructive storage action should be taken merely because a drive is absent from one screen.
- 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.