Data Recovery Case File · Desktop Externals & Aging Drives · Test the Thing They Share
Both Failed, Through the Same Reader
His enquiry describes a sensible piece of work with one variable left in it. Two hard drives, "one small and one large. Took them out of their shells and used a SATA to USB reader, but neither of them are recognised by the PC. Hoping to recover the data on them, hoping to start with the larger one as I have more data I need off there." Taking drives out of failed enclosures is the right move. But two drives failing to appear through one adapter is a statement about three components, and the cheapest of them has not been eliminated yet.
| Media | Two hard drives of differing capacities removed from external enclosures — neither enumerated when connected through a single SATA-to-USB adapter |
| Reported situation | Two drives removed from their enclosures · both connected through the same SATA-to-USB reader · neither recognised by the computer · larger drive prioritised by the owner · native connection not yet attempted |
| Fault class | To be established separately for each drive — shared adapter and supply to be eliminated before either is implicated |
| Equipment used | Adapter eliminated on a native connection before either drive was implicated · each drive assessed independently · current draw measured on a controlled bench supply · imaging sequenced to the prioritised drive first |
The decode: what the shared component means, and the free test
Why the adapter is the leading suspect: the probability of two separate drives failing independently and being discovered on the same afternoon is not high. The probability of one adapter having a limitation or a fault is considerably higher — and the adapter is the only thing both drives have in common. When two items fail through one shared component, the shared component is where to look first.
What SATA-to-USB adapters actually do wrong: they are not passive cables. Each contains a bridge chip translating between the drive's native protocol and USB, and inexpensive ones have specific, documented limits. Some do not support drives above a certain capacity — which matters here, since he has a small drive and a large one, and a capacity ceiling would affect the large one first. Many are bus-powered and cannot supply the current a 3.5-inch desktop drive needs to spin up, which is one of the commonest reasons a drive fails to appear through an adapter that works fine with laptop drives. And bridge chips fail like anything else.
The free test, and it takes minutes: connect each drive directly to a native port inside a desktop machine, with the machine's own power supply feeding it. That eliminates the adapter, its bridge and its power arrangement in one step. If a drive appears, the fault was never the drive.
Why the power point matters most for his large drive: a 3.5-inch drive draws substantially more current at spin-up than at any other moment, and considerably more than a 2.5-inch one. An adapter without its own mains supply frequently cannot provide it, so the drive attempts to start, stalls, and never reaches the point of announcing itself. That is indistinguishable from a dead drive and it is not one.
Why both should still be assessed separately: if the adapter turns out to be innocent, two drives failing together raises the same question as any simultaneous failure — what else did they share? Both came out of enclosures, so it is worth knowing whether those enclosures shared a power supply, a hub or a socket, since a supply fault that killed one enclosure can have reached the drive inside the other.
On prioritising the larger drive: naming which matters most is useful and it lets imaging be sequenced to reach that material first. It is worth doing for both drives rather than assuming size indicates importance.
On the bench
The adapter was eliminated on a native connection before either drive was implicated, since a single bridge shared by both is a likelier explanation than two independent failures — and bus-powered adapters frequently cannot supply the spin-up current a desktop drive requires. Each drive was then assessed independently, with current draw measured on a controlled bench supply to distinguish a drive receiving insufficient power from one failing to start. Imaging was sequenced to the prioritised drive first.
The outcome
The adapter eliminated first, each drive assessed independently and imaging sequenced by the owner's priority. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone testing several drives through one adapter: the adapter is the thing they share and the likeliest single explanation. Cheap bridges have capacity ceilings, protocol limits, and — most commonly — cannot supply the current a 3.5-inch drive needs to spin up, so the drive stalls and never announces itself. Connect each drive natively inside a desktop before concluding anything.
Two drives that won't appear through the same adapter
Connect each one directly inside a desktop machine before concluding anything — it's free and it eliminates the most likely explanation. Two separate drives failing independently on the same afternoon is far less probable than one adapter having a limitation, and the adapter is the only thing they share. SATA-to-USB adapters aren't passive cables: they contain a bridge chip with real limits. Some won't handle drives above a certain capacity, which would affect your larger drive first. And many are powered from the USB port alone, which often can't supply the current a 3.5-inch desktop drive needs to spin up — so it stalls and never announces itself, looking exactly like a dead drive. If the adapter turns out innocent, ask what else the two enclosures shared.
Try them natively first — then call Newcastle Data Recovery on 0191 406 1051; adapter eliminated before either drive is implicated, current draw measured on a controlled supply.
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.