Data Recovery Case File · Formatted & Logical Faults · The Loop Is Writing

Switch It Off — Each Cycle Is Another Repair Attempt

Her enquiry describes a machine stuck in a state that looks passive and is not. "I accidentally let the battery drain completely while using my laptop, which caused it to go into a loop of constantly preparing an automatic repair. I believe this happens due to a corrupt drive. I have bought a new lap"top. The drive is very likely fine. But that loop is not the machine waiting — it is the machine repeatedly trying to fix a filesystem it cannot reconcile, and every attempt writes.

The decode: what the loop is doing, and why it must stop

What caused it: a complete power loss while the system was running. Everything the machine had outstanding — writes queued in memory, structures mid-update, files open — was lost at that instant, and the filesystem was left in a state it could not be sure of. On the next start-up the system noticed and did what it is designed to do: attempt a repair.

Why it is looping rather than finishing: the repair is not completing. It starts, works on structures it cannot reconcile, fails or hangs, and the machine restarts into the same routine. That cycle can continue indefinitely, and to somebody watching it looks like a machine waiting for something.

Why that is the damaging part, and it is the reason to act now: a repair is a write. It reads the filing structures, decides what they should be, and writes that conclusion back. So a machine looping through repair attempts is writing its conclusions to the volume over and over — each time from information it has already partly altered. Every cycle is another chance to discard entries it cannot verify, which on this kind of fault are precisely the files that were open or recently modified.

So the instruction is simple: hold the power button until it switches off, and leave it off. Not restart it to see whether it gets further, not let it run overnight in the hope of completing. The loop achieves nothing and costs something on every pass.

Why the drive is probably fine: a power loss does not damage a drive. It damages the coherence of what was being written at that moment, which is a logical fault on undamaged hardware. Her guess about a corrupt drive is understandable and the word doing the work is corrupt rather than drive.

What she did right: bought a replacement machine, which means the affected one can come out of service entirely rather than being needed and therefore repeatedly restarted. Most people in this position keep trying because they have no alternative computer.

What is done instead: the drive is removed and read independently, imaged before any reconstruction, and the structures rebuilt against the copy — where a wrong conclusion costs nothing and can be repeated. Filesystems keep backup copies of their key structures at known positions, and where the automatic repair has already rewritten the primary set, those copies are frequently what returns files with folders and names intact.

On the bench

The machine was powered down immediately and not restarted — an automatic repair being a write operation, so a looping machine writes its conclusions to the volume on every pass, each time from information it has already partly altered. The drive was removed and read independently of the host, imaged write-blocked before any reconstruction, and pre-repair structures located from their surviving backup copies, since the repair cycle rewrites the primary set while duplicates elsewhere survive. Files were validated by opening.

The outcome

The machine stopped from cycling, the drive read independently and pre-repair structures recovered from their surviving copies. 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 loop is not the machine waiting. An automatic repair reads your filing structures, decides what they should be, and writes that back — so a machine cycling through it is rewriting the volume on every pass and discarding entries it cannot verify. Hold the power button and leave it off.

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.