Data Recovery Case File · Second Fixes & Trade Handoffs · What the Test Cannot Reach
A Built-In Diagnostic Can Only Report on a Drive That Answers It
This trade enquiry describes a thorough process that produced nothing. A failed laptop drive where "we ran the inbuilt diagnostics and placed the drive in an external reader to view as a USB drive, but nothing is recognised." Both steps were correct and both have the same blind spot — a diagnostic and a reader can each only report on a drive that responds, and a drive that never announces itself is invisible to both.
| Media | 500GB laptop hard drive from a business machine — not recognised by host firmware diagnostics or through an external adapter; occupied capacity unknown |
| Reported situation | Laptop drive failed in a business machine · built-in diagnostics run · drive placed in an external reader · not recognised by either route · quantity of user data unknown · recovery quotation sought |
| Fault class | Device not completing identification — invisible to host diagnostics and adapters alike; fault below the level either can observe |
| Equipment used | Diagnostic and adapter results interpreted as absence of identification rather than absence of fault detail · current draw measured on a controlled bench supply · service area and firmware state read under strict timeouts · laminar flow bench inspection where rotation was affected · imaging in one supervised session |
The decode: the blind spot both tests share
What a built-in diagnostic does: asks each attached drive to identify itself, then requests its health data and runs tests against it. Every one of those steps assumes the drive is answering — the diagnostic is a conversation, and it needs a participant.
Why it reports nothing useful here: the drive never identifies itself, so the diagnostic has nothing to test. That is not a clean result and not a fault report; it is the absence of a subject — which is easy to read as inconclusive when it is actually informative.
What that absence does tell you: the fault sits below the level at which any software operates. Identification happens before health data, before partitions, before any filesystem, so a drive failing at that point has a device-level problem and everything above it is eliminated in one observation.
Why the external reader was the right next step: it changes the machine, the port, the controller and the cabling all at once. Getting the same nothing through an entirely different path is a clean elimination of the original computer — good practice, and it narrows things properly.
Why the reader has the same limitation: an adapter presents a drive to a computer; it does not make a silent drive speak. If the drive is not completing its identification, it will not complete it through an adapter either, so the second test confirms the first rather than adding to it.
What remains to be established, and it needs different equipment: whether the drive powers, whether it reaches speed, and what it does during the moments before it should identify itself. Those are electrical and mechanical observations rather than software ones, and no diagnostic run from a computer can make them.
What the likely causes are: a board fault leaving the drive unable to initialise; a firmware region the drive cannot read, so it never completes start-up; or a mechanical fault preventing the platters reaching speed. Each is addressed differently, and current draw and rotation distinguish them quickly.
Why the unknown data quantity does not affect the assessment: the work is reaching the drive, not the volume it holds. Occupied capacity becomes visible once the drive can be read, and it is not something the owner needs to establish first.
What must not happen meanwhile: no repeated power cycles to see whether it appears. Where the cause is mechanical, each start attempt is the harmful event repeated.
On the bench
Diagnostic and adapter results were interpreted as absence of identification rather than absence of fault detail — a built-in diagnostic requesting identification before any health data or testing, so a drive that never identifies itself provides no subject to test, while an adapter changes host, port and cabling without enabling a silent drive to respond. Current draw was measured on a controlled bench supply and service area and firmware state read under strict timeouts, those being electrical and mechanical observations unavailable to software.
The outcome
The results read as absence of identification, draw measured on a controlled bench supply, and firmware state read under strict timeouts. 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: both tests share a blind spot. A diagnostic and an adapter can only report on a drive that answers, so a drive that never identifies itself is invisible to both — which places the fault below anything software can observe.
When diagnostics and an external reader both show nothing
Read that as informative rather than inconclusive — it places the fault below the level any software can reach. A built-in diagnostic asks a drive to identify itself before it can test anything, so a drive that never answers gives it no subject, and an adapter changes the host and cabling without making a silent drive speak. Together they eliminate the computer, the port and everything above the device in one go. What's left needs different instruments: whether the drive draws current, whether it reaches speed, and what happens in the moments before identification. Stop power-cycling it in the meantime, since a mechanical cause makes each attempt harmful.
That narrows it — call Easy Data Recovery on 028 9002 0144; results read as absence of identification, draw measured on a controlled bench supply, firmware state read under strict timeouts.
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.