Data Recovery Case File · Formatted & Logical Faults · It Did Not Break the Other Machine
A Failing Drive Can Stop a Working Computer
His enquiry describes a test that produced an alarming result. A laptop that will not boot, reporting that the disk does not exist: "I removed it from my laptop and inserted it into another laptop, and unfortunately the latter does not boot either. There was no physical damage and the only thing that changed wa"s the drive. It looks as though the fault has spread. It has not — the second machine is fine, and what he has actually done is confirm the diagnosis more thoroughly than he realises.
| Media | Laptop internal drive — host reporting the disk as absent; second host also failing to complete start-up with the same drive fitted |
| Reported situation | Original laptop failing to boot and reporting that the disk does not exist · drive removed and fitted to a second laptop · second laptop also failing to boot · no physical damage to either machine · drive identified as the only changed variable |
| Fault class | Drive stalling during host initialisation — enumeration blocking start-up on any host; second machine unaffected once the drive is removed |
| Equipment used | Second host confirmed serviceable with the drive removed · drive assessed on a direct connection under strict timeouts · initialisation state read directly · imaging on restored readiness |
The decode: why a drive can hold a machine hostage
What happens before an operating system loads: the firmware enumerates the hardware attached to the machine. For each storage device it sends an identification request and waits for a reply — because it cannot proceed without knowing what is there. That wait has a timeout, but on many machines it is generous, and some firmware retries several times before giving up.
What a drive stalling during that exchange does: holds the process. A drive that has failed cleanly reports nothing and the firmware moves on quickly. A drive that is partly alive — powering up, beginning to respond, and then failing to complete — can leave the firmware waiting through every retry on every attempt. The machine appears frozen, or takes minutes to reach a menu, or simply never starts.
Why that produces exactly what he saw: the second laptop is not broken. It is waiting for a device that will not finish answering. Remove the drive and it will boot normally within seconds — which is worth doing immediately, both for reassurance and because leaving it in place achieves nothing.
Why this is genuinely useful confirmation: the fault travelled with the drive and reproduced on independent hardware. That eliminates the original laptop entirely — its board, its power, its firmware, its connector — and places the problem in the drive with no ambiguity at all. Most people cannot narrow a fault that cleanly, and he has done it without meaning to.
Why it is worth saying plainly that he has damaged nothing: the natural reading of "I put my drive in another machine and now that one won't boot either" is that something contagious has happened. Nothing has. No fault transfers between machines through a storage device, and the second laptop is in exactly the condition it was in before.
What the drive is actually doing: failing partway through its own initialisation — powering, starting to respond, and not completing the sequence that would let it announce its capacity and geometry. That is a device-level fault, most often in the controller or in reading the drive's own configuration.
What must not happen: no further attempts to boot from it, since each is another stalled initialisation on a drive that cannot complete one.
On the bench
The second host was confirmed serviceable with the drive removed, a machine held at firmware enumeration by a partly responsive device booting normally within seconds once it is taken out — and confirming that nothing was damaged. The drive was assessed on a direct connection under strict timeouts rather than through a host that waits generously, with initialisation state read directly to establish which stage of start-up was failing, and imaging on restored readiness.
The outcome
The second machine cleared, the drive assessed on a direct connection under strict timeouts and imaged on restored readiness. 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: you have not broken the second laptop. Before an operating system loads, firmware asks each storage device to identify itself and waits for the reply — and a drive that powers up, begins responding and never finishes leaves the machine waiting through every retry. Take the drive out and it will boot in seconds.
Failing drive that stops another machine booting
Take the drive out of the second machine and it will boot normally within seconds — you haven't damaged anything, and no fault transfers between computers through a storage device. What's happening is that before any operating system loads, the firmware asks each attached drive to identify itself and waits for a reply, because it can't proceed without knowing what's there. A drive that has failed cleanly reports nothing and the machine moves on. One that's partly alive — powering up, starting to respond, never finishing — leaves the firmware waiting through every retry, so the machine appears frozen or never starts. Your test was actually valuable: the fault travelled with the drive and reproduced on independent hardware, which clears the original laptop completely.
Remove it and they'll boot — call Guildford Data Recovery on 01483 901310; second host confirmed serviceable, drive assessed on a direct connection under strict timeouts, imaged on restored readiness.
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.