Data Recovery Case File · Desktop Externals & Aging Drives · Authorised to Open It
The test that came back negative — and settled everything: why a bare-drive connection eliminates the enclosure, what "still not recognised" narrows the fault to, and the recovery that began where his elimination ended
Most enquiries arrive with a mystery; his arrived with a completed experiment. A 2TB G-Technology USB drive, "not being recognised by Mac" — and then the sequence that makes this a case file worth writing: "the drive is still under warranty. They authorised me to disassemble the drive and use a USB-to-SATA cable. Did not work." Two things deserve immediate credit. First, asking the manufacturer for written authorisation before opening a warrantied enclosure is exactly the right instinct — it preserved his cover while allowing the one test that matters. Second, the result he reports as a failure is nothing of the kind: "did not work" is a diagnostic finding, and a valuable one. It removes the enclosure, its bridge board and its power path from suspicion in a single move, and points the whole case at the drive itself — which is where this page picks up: what that negative result narrows the fault to, and why a USB-to-SATA cable is the right test but never a treatment.
| Media | 2TB G-Technology external hard drive — unrecognised by the host Mac; enclosure opened under manufacturer authorisation; bare drive connected via USB-to-SATA cable with no result |
| Reported situation | Drive fails to appear on the Mac · warranty-sanctioned disassembly performed · direct connection also unrecognised · data recovery sought |
| Fault class | Drive-side non-enumeration — enclosure and bridge eliminated by the owner's own test; firmware-area, head or board fault indicated |
| Equipment used | Atola Insight Forensic power-on and current-signature diagnostics · PC-3000 Express with Data Extractor — technological-mode access to firmware areas, module regeneration as required · head-mapped imaging; volume verified from the image and delivered |
The decode: what the negative proves, what a cable can't do, and the three suspects left
Why "still not recognised" is worth so much: an external drive is two devices in one shell — a hard drive, and a bridge board translating between its native connection and USB. When such a drive vanishes, the first question is always which half died, and the definitive answer comes from bypassing the bridge: connect the bare drive on a native path and see whether it enumerates. His authorised test did precisely that, and the drive stayed silent — so the bridge, the enclosure's power circuitry and the USB cabling are all acquitted. This is the most common happy ending in this archive's enclosure cases, and it did not happen here: the fault travelled with the drive.
What a USB-to-SATA cable is, and isn't: a small honest correction to a widespread hope. Such a cable supplies power and a data path — that's all. It cannot stabilise a drive that resets, cannot budget timeouts, cannot manage a mechanism that stalls, and cannot reach the drive's service modes. As a test it is exactly right, and it gave a clean result. As a treatment it has no capability at all — which is why the correct response to his negative result was to stop testing, not to try further cables, adapters or Macs.
The three suspects that remain: a drive that spins yet never announces itself on a native connection has narrowed itself to a familiar trio. Firmware-area damage: the drive's internal service data — translation tables, adaptive parameters — corrupted so the controller cannot complete start-up and therefore never identifies. Head trouble: an assembly unable to read the service areas it must calibrate against, producing the same silence. Board fault: a failure in the drive's own electronics, sometimes as unglamorous as a blown protective component. All three are professional-tier work; all three are routine at that tier; and none of them means the platters have lost anything. Determining which requires the drive's power-on behaviour to be read electrically, not relayed by a host's shrug — and once named, each has an established road: firmware access and module repair through technological modes, head service under filtered air, or board-level attention, followed in every case by the same next step — image first, ask questions of the copy afterwards.
On the bench
The drive arrived already stripped of its shell — his authorised test having removed the enclosure question permanently — and went straight onto the Atola Insight Forensic, where the power-on current signature told the story the Mac could only decline to tell: which of the three suspects was answering, and how much life the mechanism had to spend. From there the road followed the finding: PC-3000 Express access to the drive's technological modes, firmware areas read and the damaged service structures regenerated until the drive would identify and address its own media again — and then, immediately, imaging under Data Extractor on a per-head map, the two terabytes banked before anything else was asked of it. The volume was rebuilt from the image, verified by opening, and delivered on fresh media — the drive itself returned with its warranty intact and its authorisation letter still valid.
The outcome
The 2TB recovered following firmware-level access and head-mapped imaging, verified and delivered — the owner's own elimination having saved the assessment its first hour. Free assessment, one fixed written figure including VAT, no recovery, no fee. The method, posted for every owner of a warrantied external: ask the manufacturer in writing before opening anything — many will authorise it, as his did; connect the bare drive natively once, because that single test cleanly separates enclosure faults from drive faults; read a negative result as a finding rather than a failure; and then stop, because a USB-to-SATA cable is a diagnostic instrument and never a repair. When the fault travels with the drive, the next hands it meets should be holding something better than another cable.
External drive unrecognised — wondering whether to open the case
Ask the manufacturer first: if the drive is in warranty, request written authorisation to open the enclosure and test the bare drive — many grant it, and it protects your cover. Then run the one test that matters, once: connect the drive directly on a native path. If it appears, the enclosure was the fault and you've had a lucky escape; if it stays silent, you've proved the fault is in the drive — a firmware, head or board problem, all of which are ordinary professional work and none of which means your files are gone. Don't keep cycling through cables, docks and computers after a clean negative, don't leave the bare drive powered while you think, and don't be tempted by utilities: the next step is diagnosis on instruments that can read the drive's own start-up behaviour, then an image.
That's your answer, and it's a workable one — call Leeds Data Recovery on 0113 322 3083; power-on diagnostics, firmware-level access, head-mapped imaging, verified out — one written figure, no recovery, no fee.
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.