Data Recovery Case File · Second Fixes & Trade Handoffs · The Correct Test, Correctly Read
He Booted From Something Else and Found the Drive Present and Silent
This enquiry came from a computer business handling a customer's laptop drive, and it describes exactly the right diagnostic. The customer reported the system hung and then displayed an error loading the operating system, so the shop "booted the laptop from a test disk; the faulty drive was shown but could not be accessed." That single test separates software from hardware, and the result places the fault precisely.
| Media | Laptop hard drive received from a third-party client — enumerating when the host is booted from external media; content regions not accessible |
| Reported situation | Drive received by a computer business from a client · client reporting the system hanging and subsequently failing to load the operating system · host booted from external media by the provider · drive present and identified · content not accessible · contents required |
| Fault class | Device enumerating with content regions failing — boot region readable to the point of loader reference; user data regions not returning |
| Equipment used | External boot result accepted as separation of software from device causes · Atola Insight Forensic error-rate assessment across the surface · imaged write-blocked under strict per-sector timeouts with retries capped · structures rebuilt from surviving copies · losses mapped per file |
The decode: why that test is the right one, and what it established
What booting from external media does: removes the drive from the start-up path entirely. The machine runs from something else, and the drive becomes an ordinary attached device to be examined rather than the thing the machine depends on.
Why that is the correct first step: a machine that will not start could be failing because its software is damaged or because its storage is. Those two require opposite responses — a repair in one case, a capture in the other — and nothing about the symptom distinguishes them. This test does, and it writes nothing.
What the result establishes: the drive is present and identifies itself, so it powers, spins, reads its own configuration and completes enumeration. The electronics and the mechanism are working, and the fault is in reading the regions holding content.
Why the original message fits: an error loading the operating system means the very beginning of the drive was read successfully — the boot region was found and the reference within it followed — and what it pointed at could not be read. So reading works at the outermost start and fails shortly after.
Why that pattern is characteristic: the regions read on every start-up are among the most heavily used on any drive, and developing faults surface where use is heaviest. A drive failing just past its boot region is a drive whose problems began in the busiest part of it.
What the hang before the failure adds: a system that hung and then would not restart is a system whose storage stopped answering. The hang and the boot failure are one fault at two moments, and the customer's account dates it precisely.
What must not happen, and a repair shop has the tools to do it: no consistency check and no boot repair. Both write, and both are the natural next step after a diagnosis like this — which is why the shop stopping here rather than proceeding is the right call.
What the capture approach is: capped per-sector timeouts so no single region consumes the session, healthy areas taken first at speed, and difficult regions revisited across later passes.
On the bench
The external boot result was accepted as separation of software from device causes — booting from other media removing the drive from the start-up path so it can be examined as an attached device, which distinguishes damaged software from failing storage without writing anything. The drive identifying itself confirms power, rotation, configuration reading and enumeration, placing the fault in content regions. Imaging ran write-blocked under strict per-sector timeouts with retries capped.
The outcome
The external boot result accepted as a separation, error rates measured across the surface, and the drive imaged under capped timeouts with losses mapped per file. 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: that was the right test. Booting from other media takes the drive out of the start-up path and writes nothing — and shown-but-not-accessible means the electronics work while the content regions do not.
Testing whether a fault is software or storage
Boot the machine from external media and look at the drive as an attached device — it takes minutes, writes nothing, and it separates two situations whose right answers are opposite. If the drive is present and reads reliably, the fault is software and a repair costs you nothing but time. If it's present and won't return content, the electronics work and the surface doesn't, which means capture before anything else. Don't follow it with a consistency check or a boot repair: both write, and both are the natural next step after exactly this finding. An error loading the operating system also tells you the very start of the drive read successfully.
Stop before any repair — call Easy Data Recovery on 028 9002 0144; external boot result accepted as a separation, error rates measured, imaged under capped timeouts with losses mapped per file.
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.