Data Recovery Case File · Solid State & Flash · Test It Natively First
The Adapter Is Part of the Test
His enquiry states the symptom precisely and includes the qualifier that matters. A 128GB solid-state drive "that was working completely fine until it died suddenly, and since then the drive does not show up at all when connected via a USB" adapter. Sudden death without warning is characteristic of this class of drive, so the conclusion is probably right. But "not detected through USB" and "not detected" are different statements, and the difference costs nothing to establish — because the adapter between the drive and the computer is a component with its own limitations.
| Media | 128GB solid-state drive — failing abruptly during normal operation; not enumerated when connected through a USB adapter |
| Reported situation | Drive functioning normally until abrupt failure · no preceding symptoms · not detected when connected through a USB adapter · native connection not yet attempted · contents required |
| Fault class | To be established — adapter compatibility and supply to be eliminated before controller failure is concluded |
| Equipment used | Drive assessed on a native connection with the adapter eliminated · presence on the bus and initialisation state read directly · vendor technological and safe modes attempted (PC-3000 portfolio, SSD support) · firmware area and translation layer assessed |
The decode: what an adapter can hide, and what remains
Why the adapter deserves eliminating first: a USB caddy or cable adapter is not a neutral wire. It contains a bridge chip that translates between the drive's native protocol and USB, and bridges vary considerably. Inexpensive ones have real, documented limits: some do not handle drives above a certain capacity, some do not pass through the commands a solid-state drive needs to identify itself properly, and some cannot supply enough current under load. A bridge that has itself failed produces exactly the same symptom as a dead drive — nothing appearing at all.
What the free test is: connect the drive directly to a native port on a computer's motherboard, bypassing the adapter entirely. That takes the bridge, its cable and its power arrangement out of the question in one step. If the drive appears, the fault was never the drive. If it is still absent, the finding is now solid rather than provisional — and that is worth having before commissioning anything.
Why people skip it: because the adapter worked before. But a bridge chip that has been working can fail, and a drive that starts drawing abnormal current when it fails can take the bridge with it. "It worked yesterday" applies to both components.
What remains if the drive is absent natively: the drive's controller is not completing its own initialisation. These devices run their own firmware on start-up, reading internal structures before they can announce themselves; where those are damaged, or where the controller has failed electrically, the device never presents itself to the bus. Nothing above it can help, because there is nothing to communicate with.
Why the suddenness fits: he notes it was working completely fine until it died. That is the normal pattern for this class of drive rather than a surprise. Mechanical drives usually degrade audibly and gradually; solid-state drives typically go from entirely healthy to entirely inaccessible between one start-up and the next, with no warning at all.
The route, and the honest caveat: manufacturers build technological and safe modes into their controllers for precisely this, allowing the firmware area to be assessed, damaged modules repaired and addressing restored. That is tried first. Where the controller cannot be addressed at all, reading the memory past it is not the dependable fallback it is on a card, because the mapping and often the encryption live in the controller.
On the bench
The drive was assessed on a native connection with the adapter eliminated, since a bridge chip has its own capacity, protocol and current limitations and a failed bridge presents identically to a dead drive. Presence on the bus and initialisation state were read directly rather than inferred from a host that reports only presence or absence. Vendor technological and safe modes were attempted through the PC-3000 portfolio's SSD support, with the firmware area and translation layer assessed and damaged modules repaired until the drive addressed its media.
The outcome
The adapter eliminated on a native connection, the drive assessed directly and addressing restored in vendor modes where the controller could be reached. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone whose drive shows nothing through a caddy: eliminate the adapter first, because it is not a neutral wire. It contains a bridge chip with real limits on capacity, protocol support and current, and a failed bridge looks exactly like a dead drive. Connect natively to a motherboard port — free, and it turns a provisional finding into a solid one.
Drive not detected through a USB caddy
Connect it directly to a motherboard port before concluding anything — it's free and it eliminates a real variable. A USB adapter isn't a neutral wire: it contains a bridge chip that translates between the drive's own protocol and USB, and cheap ones have genuine limits. Some won't handle drives above a certain capacity, some don't pass through the commands a solid-state drive needs to identify itself, and some can't supply enough current. A bridge that has failed produces exactly the same symptom as a dead drive, which is nothing at all. And don't be reassured that the adapter worked before — a drive that starts drawing abnormal current when it fails can take the bridge with it. If the drive is still absent natively, you have a solid finding rather than a guess.
Try it natively first — then call Newcastle Data Recovery on 0191 406 1051; assessed on a native connection, initialisation state read directly, vendor technological modes attempted.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.