Data Recovery Case File · Formatted & Logical Faults · Two Faults One Event Can Cause
An Abrupt Power Loss Can Break a Connection or the Drive Behind It
His enquiry pairs a cause with a symptom and a round of troubleshooting that missed the point. Power to the computer was cut accidentally, and on restart "a message appeared saying there was no contact with the hard drive. The supplier's helpdesk talked me through turning it on and off, and removing and refitting a wire." An abrupt power loss can dislodge or damage a connection, or it can damage the drive — and reseating a cable addresses only the first, while the on-off cycling risks the second.
| Media | Internal hard drive — host reporting no communication following an uncontrolled power loss; connection reseated without resolution |
| Reported situation | Power to the computer interrupted accidentally · host reporting no contact with the drive on restart · helpdesk-directed power cycling performed · data and power connection removed and refitted · no resolution · contents required |
| Fault class | Communication failure after uncontrolled power loss — connection disturbance or drive-side damage; repeated power cycling contraindicated pending assessment |
| Equipment used | Connection and drive-side causes separated before further power cycling · drive removed and assessed independently on a controlled bench supply · service area and enumeration read under strict timeouts · laminar flow bench inspection where rotation was affected · imaging in one supervised session |
The decode: what the event could have done, and why the fixes were wrong
What "no contact with the hard drive" means: the machine's firmware tried to communicate with the drive and got no answer. Communication requires the connection to be intact and the drive to be alive and responding — and a failure could come from either side.
The first possibility — the connection. An abrupt power loss on a desktop can be accompanied by a knock, a surge, or simply the disturbance of the event, and a cable can be dislodged or a contact disturbed. This is the benign case, and it is what the helpdesk was addressing.
Why reseating the wire was a reasonable first thing: if a connection had worked loose, refitting it would resolve it, and it costs nothing. As a single step it was fine — the problem is what surrounded it.
The second possibility — the drive. An uncontrolled power loss while a drive is running is exactly the event that damages drives. The supply is cut mid-operation, the heads fall back on their emergency retract, and a board or a head can be harmed — and if that is what happened, no amount of cable-reseating will help, because the drive itself is not answering.
Why the on-off cycling was the wrong instruction: if the drive was damaged by the first power loss, repeatedly powering it on and off is repeating the harmful event. Each cycle is another abrupt start and stop on a drive that may already be injured, and a helpdesk script aimed at a working machine does not account for that.
Why the two must be separated before anything else: the safe response to a connection fault and the safe response to a damaged drive are opposite. One invites you to power-cycle freely; the other requires you to stop immediately — and until you know which you have, the cautious course is to stop.
How they are told apart: the drive is removed and assessed on its own, on a controlled supply, away from the machine. That establishes whether it powers, spins and responds — which the in-machine message cannot distinguish from a loose cable.
Why the helpdesk cannot be blamed and should not be followed further: their remit is a working computer and their script suits one. For a possible drive fault it is the wrong script, and continuing it risks the data.
On the bench
Connection and drive-side causes were separated before further power cycling — a no-communication message following uncontrolled power loss arising either from a disturbed connection, which reseating addresses, or from drive-side damage, which it cannot, with the harmful event being repeated by directed on-off cycling. The drive was removed and assessed independently on a controlled bench supply, establishing power, rotation and response, with the laminar flow bench used where rotation was affected.
The outcome
Connection and drive-side causes separated before further cycling, the drive assessed independently on a controlled bench supply, and imaging performed in one supervised session. 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: an abrupt power loss can dislodge a connection or damage the drive. Reseating the cable addresses only the first — and the on-off cycling you were talked through repeats the very event that may have caused the second.
No-communication message after a power cut
Stop power-cycling it until the cause is known. A "no contact with the drive" message after an uncontrolled power loss has two possible causes: the connection was disturbed, which reseating a cable would fix, or the drive itself was damaged by the abrupt loss, which it wouldn't. Reseating the wire once was reasonable. But being talked through turning it on and off repeatedly is the wrong step if the drive is injured, because that repeats the exact event — a sudden start and stop — that may have caused the damage. A helpdesk script suits a working machine, not a possibly-faulty drive. Have the drive assessed on its own.
Stop cycling the power — call Easy Data Recovery on 028 9002 0144; connection and drive-side causes separated first, drive assessed independently on a controlled bench supply, imaged in one supervised session.
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.