Data Recovery Case File · Portable Drives · He Stopped at the Right Moment
Disconnecting on a Change in Sound Preserved What a Completed Transfer Might Not Have
His enquiry describes a session that began well and was ended deliberately. An old drive with "a bit dodgy" connection history, unused for years, which he "successfully connected to last night" — and then, "before I could transfer the majority of files, it began making an intermittent beep so I disconnected it." Two things follow from that: some files did transfer and should be checked, and stopping when the sound changed was the correct call.
| Media | Portable hard drive of some age, unused for years — connected successfully for one session; transfer commenced and interrupted by the owner on a change in audible behaviour |
| Reported situation | Portable drive with a history of intermittent connection · drive unused for a period of years · drive connecting successfully on a recent attempt · file transfer commenced · intermittent audible signal beginning during the transfer · owner disconnecting the drive at that point · transfer incomplete · photographic content of a recently deceased family member sought |
| Fault class | Degradation presenting during sustained access after prolonged idleness — partial transfer completed; audible change indicating the working session was ending |
| Equipment used | Prompt disconnection on audible change credited as limiting further demand · partial transfer contents established before recovery scope was set · no further connection permitted · current draw measured across the start-up cycle on a controlled bench supply · imaging under capped timeouts with untransferred regions prioritised |
The decode: what to check first, and why stopping was right
Why the partial transfer comes before anything else: some files arrived. Whatever was copied before he disconnected is already saved, and establishing what that covers may reduce the work substantially.
Why that is worth doing before any figure is discussed: it costs nothing. A list of what reached the computer defines what still needs recovering.
Why the order in which files transfer matters: it is rarely the order of importance. A transfer proceeds through folders in the order the system lists them, so what arrived is arbitrary rather than chosen.
Now the decision to disconnect, which was correct: a change in sound during access is a warning. A drive that begins signalling while being read is reporting that something has altered under load.
Why continuing would have been the natural response: the transfer was working. Interrupting a successful copy to avoid a hypothetical problem is counterintuitive, and most people push on.
What pushing on would have risked: the remainder of the session. A drive that has begun to struggle under sustained reading may not survive the rest of a large transfer.
Why the years of idleness are relevant here: the first return to service is demanding. A drive standing for years faces its greatest load when asked to run again, and sustained reading immediately afterwards compounds it.
Why the earlier dodgy connection history fits: it was already marginal. A drive with intermittent connection before being set aside was showing signs then.
Why the successful session is nonetheless encouraging: it read. A drive that mounted and transferred files has demonstrated that its content is reachable, which most enquiries cannot show.
What must not happen now: no attempt to resume. The temptation to reconnect and continue is strong and the session that ended was the window.
On the bench
Prompt disconnection on audible change was credited as limiting further demand, and the partial transfer contents established before recovery scope was set — files copied before disconnection being already saved, with transfer order following system listing rather than importance. A drive standing for years faces its greatest load on returning to service, compounded by sustained reading, and an audible change under access indicates alteration under load. Untransferred regions were prioritised during imaging.
The outcome
Disconnection credited as limiting demand, partial transfer contents established before scoping, and untransferred regions prioritised. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: check what already reached your computer first — it costs nothing and may reduce the work considerably. And unplugging when the sound changed was the right call, however counterintuitive it felt.
When a transfer is interrupted by a change in sound
Check what already arrived before doing anything else — it costs nothing and defines what still needs recovering, though don't expect the files that transferred to be the ones you'd have chosen, since a copy proceeds in whatever order the system lists. Stopping was right, even though continuing feels natural when a transfer is working: a drive that begins signalling under sustained reading is reporting a change under load, and it may not survive the rest of a large copy. Don't reconnect to resume.
That was right — call Cambridge Data Recovery on 01223 655015; partial transfer established before scoping, disconnection credited as limiting demand, untransferred regions prioritised during capture.
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.