Data Recovery Case File · Mac & Apple Systems · The Copy Was the Load
A Backup Is the First Thing That Asks the Whole Drive to Work at Once
His enquiry places the failure inside a specific operation. A 3TB drive used for scheduled backups of a laptop which "stopped working while doing a backup, and now the laptop does not recognise it. The drive lights up intermittently and I can hear and feel its vibrations." A backup is far more demanding than ordinary use, and a drive with a developing fault frequently fails during exactly this task — which is not the backup's fault.
| Media | 3TB external hard drive used for scheduled laptop backups — failed during an active backup; rotation present, indicator intermittent, not enumerating |
| Reported situation | External drive used for scheduled backups of a laptop · drive ceasing to function during an active backup · laptop no longer recognising it · indicator illuminating intermittently · rotation audible and perceptible · substantial content held |
| Fault class | Failure under sustained load with rotation retained — drive spinning but not completing identification; intermittent indicator suggesting supply or initialisation instability |
| Equipment used | Failure during sustained transfer assessed as load-revealed rather than load-caused · rotation confirmed and current draw measured on a controlled bench supply · service area and enumeration read under strict timeouts · laminar flow bench inspection where indicated · imaging in one supervised session under capped timeouts |
The decode: why backups surface faults, and what the symptoms narrow to
What a backup asks of a drive that daily use does not: sustained, continuous work across a large portion of its surface. Ordinary use touches a small area repeatedly and leaves the drive idle most of the time, whereas a backup writes steadily for a long period without pause.
Why that surfaces problems: a marginal component, a weak supply stage or a region the drive struggles with may never be reached during light use. A sustained operation reaches all of it and holds the drive at full working demand for as long as the job takes, which is when something already weak gives way.
Why this must not be read as the backup causing harm: the alternative was a drive that failed later, during a restore, when it was needed. A fault revealed during a backup is a fault found at the least costly moment — and it is a strong argument for backing up more often rather than less.
What the retained rotation tells us: the motor works and the platters are turning, which he can hear and feel. That eliminates the stall faults — no seized bearing, no heads adhered holding the mechanism — and places the problem after rotation in the start-up sequence.
What remains once rotation is established: the drive must position its heads, read its own configuration, and identify itself. Failing at any of those produces a spinning drive that is not recognised, which is precisely his symptom.
What the intermittent indicator suggests: the drive is not settling into a stable state. A flickering indicator on a drive that is spinning points at repeated attempts to initialise — starting, failing, and starting again — rather than a device that has simply stopped.
Why that pattern is worth acting on quickly: a drive repeatedly attempting to initialise is a drive doing work. Each cycle is another attempt on whatever is failing, and leaving it connected lets that repeat indefinitely.
Why the backup content being on the drive raises the stakes: a backup drive holds the copy rather than the original, and the natural assumption is that it matters less. He says there is a lot of data on it he needs, which suggests it has become a store in its own right — a common and worth-noting drift, since a backup that holds the only copy of anything is no longer a backup.
What must not happen: no leaving it connected in the hope it settles, and no repeated reconnection. The drive should be disconnected now, which stops the cycle of initialisation attempts.
On the bench
Failure during sustained transfer was assessed as load-revealed rather than load-caused — a backup imposing continuous demand across a large portion of the drive whereas ordinary use touches a small area intermittently, so a marginal component or difficult region unreached in light use gives way under sustained work. Rotation was confirmed and current draw measured on a controlled bench supply, retained rotation excluding stall faults and placing the failure after spin-up in positioning, configuration reading or identification, with an intermittent indicator suggesting repeated initialisation attempts.
The outcome
The failure assessed as load-revealed, rotation confirmed on a controlled bench supply, and enumeration 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: the backup did not cause this, it found it. Sustained copying is the first thing that asks a whole drive to work at once — and your drive still spinning rules out the stall faults and places the problem after rotation.
A drive that failed during a backup
Disconnect it rather than leaving it plugged in hoping it settles — a flickering indicator on a spinning drive means repeated initialisation attempts, and each cycle is more work on whatever is failing. Don't read the timing as the backup causing damage: a backup is the first thing that asks the whole drive to work continuously, so a marginal component that light use never reaches gives way then. Finding a fault during a backup is finding it at the cheapest possible moment. If you can still hear and feel rotation, that's useful — it rules out a seized motor or adhered heads and places the fault later in the start-up sequence.
Disconnect it — call Easy Data Recovery on 028 9002 0144; failure assessed as load-revealed rather than load-caused, rotation confirmed on a controlled bench supply, enumeration 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.