Quick Answer / Summary: The seven fixes in order: (1) try another USB port and skip hubs, (2) verify full conductor continuity on the USB link, (3) check power arrangement for the drive class, (4) look in Disk Management – present-but-uninitialised and present-without-letter are different problems, (5) test the drive on another machine or adapter to isolate bridge vs drive, (6) update bridge firmware where the platform supports it, (7) read SMART – a drive that powers but never mounts may be a failed board, not a failed adapter.
The adapter that worked yesterday shows nothing today – or the new adapter never shows the new SSD at all. ‘Not detected’ has a short list of causes, and the fastest path is working them in order of probability, cheapest fix first. This guide is that list, with the reasoning behind each step so you stop at the right one.
Fixes 1-3: The Physical Layer
Port: rear motherboard USB 3.0 ports first – front-panel headers, monitors’ hubs and keyboard passthroughs are the most common silent culprits, and hubs add their own negotiation. Link: a USB 2.0-wired cable on a 3.0 head still enumerates flash-class devices but can starve a 2.5-inch drive’s spin-up; use the adapter’s own cable or a known-good 3.0 cable. Power: a 2.5-inch drive on a weak port may draw enough to enumerate but not to mount – the Y-cable or a powered hub isolates that. Three physical checks, two minutes, and roughly half of all ‘not detected’ tickets close here.
The Sound Tells
Listen: a healthy drive spins up with one smooth whir and a soft unpark click. Click-spin-repeat means underpower or failing drive. Total silence on an SSD is normal (no moving parts) – SSDs give no audio evidence, which is why the OS-level checks come next.
Fix 4: Present But Not Visible
Disk Management (Windows) or Disk Utility (macOS) tells you which of three worlds you are in: (a) the drive appears uninitialised – a brand-new SSD’s normal state, and initiating it (GPT) makes it appear; (b) the drive appears with no letter – assign one, done; (c) the drive does not appear at all – the problem is physical or electronic, go to fix 5. Windows’ ‘uninitialised’ state on a previously-working drive is also the classic bridge-firmware hiccup symptom, which is why fix 6 exists.
Never Initialise a Drive With Data
Initialising writes partition structures. On a drive that should contain data, that prompt is a trap – decline it, and treat the state as a symptom to diagnose (firmware, bridge, or genuine corruption), not a setup step.
Fixes 5-7: Isolating Bridge From Drive
Swap test: the same drive on a different adapter/machine, and the same adapter on a known-good drive – four combinations isolate which element failed. Firmware: JMS567-class and similar platforms have update utilities; a bridge that mispresents the drive’s capacity or sector emulation often recovers with a firmware pass. Health: SMART through a working chain reads the drive’s own opinion – a drive with a dead controller never enumerates anywhere and has no SMART to read, which is the honest signal that the drive, not the adapter, is the patient.
When It Is the Drive
The drive that powers, spins (if HDD), and never appears on any adapter-any machine combination has a PCB or firmware fault. Recovery moves to specialist territory (board swaps, chip-off) – beyond adapter troubleshooting, and exactly why the swap test is worth running before spending on recovery.
Not-Detected: Cause-to-Fix Matrix
| Symptom Detail | Likely Cause | Fix | Order |
|---|---|---|---|
| Nothing, any port | Port/hub issue | Rear motherboard port | 1 |
| Enumerates, drops under load | Weak power | Y-cable or powered hub | 2-3 |
| In Disk Mgmt, uninitialised | New SSD (normal) or firmware hiccup | Initialise (empty) / firmware | 4/6 |
| In Disk Mgmt, no letter | Missing mount | Assign letter | 4 |
| Same drive fails everywhere | Drive board/firmware | Specialist recovery | 5/7 |
| Same adapter fails all drives | Bridge fault | Replace under warranty | 5 |
Real-World Application Scenarios
A help desk pins this list inside its ticketing template; ‘adapter not detected’ tickets close in minutes with a consistent order. A refurbisher trains every new technician on the swap test specifically – the four-combination isolation ends the guess-and-swap hour. A cautious home user prints the matrix; the drawer’s next mystery drive gets method instead of frustration.
Recommended Internal Resources
(1) FAQ – https://zh-zong.com/faq/ (anchor: extended troubleshooting for adapters and drives); (2) Product cluster – https://zh-zong.com/productlist/ (anchor: adapters on firmware-disciplined bridge platforms with update support); (3) Contact – https://zh-zong.com/contact/ (anchor: bridge firmware and warranty support requests).
- extended troubleshooting for adapters and drives
- adapters on firmware-disciplined bridge platforms with update support
- bridge firmware and warranty support requests
Related Reading in This Series
- USB to SATA Cable: Reading Specs That Actually Matter in 2026
- Hard Drive Reader: Turn Any Bare Drive Into a Readable Disk
- SATA to USB Adapter: The Complete Buying Guide for 2.5 and 3.5 Drives
Frequently Asked Questions (FAQ)
Q: Why does my SSD show as uninitialised?
A: Brand-new SSDs ship uninitialised – initialising (GPT) is the correct setup step. A previously-working drive showing this state is a firmware or corruption symptom; do not initialise it with data aboard.
Q: Can a bad cable cause not-detected?
A: Yes – a 2.0-wired cable or a damaged pair can starve spin-up while passing enough for enumeration. The adapter’s own cable or a known-good 3.0 cable is the control.
Q: How do I know if the drive or the adapter is dead?
A: The swap test: each element against a known-good counterpart. Two combinations per element, four total, and the fault is isolated with certainty.