Data Recovery Case File · Legacy & Obsolete Media · Cloning Is a Full Read
A Clone Reads Every Sector, Which Is the Most Demanding Thing a Marginal Drive Can Be Asked
This enquiry has an unusual objective and a familiar sequence. A drive holding an early operating system and its installed programs, where "we tried to clone it, but it failed to clone and now the drive is no longer recognised" — and the goal is an image that can run in a virtual machine so the system is preserved. The clone attempt is very likely what finished it, because cloning asks a drive to read all of itself without stopping.
| Media | Hard drive holding an early operating system and installed applications — cloning attempted and unsuccessful; drive no longer recognised by its original machine; full disc image required for preservation |
| Reported situation | Legacy drive holding an early operating system and installed programs · cloning attempted for preservation purposes · clone operation failing · drive no longer recognised by its original machine afterwards · full image required for use in a virtualised environment · preservation of the installed system sought rather than individual files |
| Fault class | Drive not presenting following sustained full-capacity read — condition to be established by measurement; preservation objective requiring complete sector-level capture |
| Equipment used | Cloning attempt assessed as a sustained full-capacity read rather than as a neutral operation · drive addressed directly with imposed timeouts outside any host · current draw measured across the start-up cycle on a controlled bench supply · imaged sector by sector under strict per-sector timeouts with healthy regions taken first · image validated by booting in a virtualised environment |
The decode: why cloning is risky, and why the objective changes the method
What cloning asks a drive to do: read everything, in order, without pausing. Every sector from the first to the last, including regions no file has occupied for decades.
Why that is harder than ordinary use: ordinary use is selective. A machine in service reads the parts it needs, which on a legacy system is a small fraction of the capacity.
What happens when a clone meets a region that will not read: it waits. Ordinary cloning software has no imposed limit, so the drive retries indefinitely while the operation stalls.
Why those retries are the damage: each is mechanical work. A drive repositioning its heads thousands of times on one region is doing the most demanding thing it does, in the place least able to bear it.
Why the drive being unrecognised afterwards fits precisely: the reserved region suffered. Degradation reaching the area holding the drive's own configuration prevents it identifying itself at all.
Why this is worth saying without blame: the intention was correct. Making a copy before something fails is exactly right, and the method was the problem rather than the plan.
What should have been used instead: imaging with limits. Capture with imposed per-sector timeouts abandons a difficult region quickly, marks it, and returns later — the opposite of waiting.
Why the preservation objective raises the stakes on completeness: a running system needs all of itself. An image intended to boot must include boot structures, system files, configuration and registrations, not just documents.
Why that also makes a sector-level image the only acceptable form: file-level copying loses things. Attributes, hidden system areas and boot code are not reproduced by copying files.
Why the legacy hardware is a secondary problem and a real one: interfaces differ. A drive of that era attaches through a connection modern equipment does not carry, and is read through an adapter as a matter of course.
On the bench
The cloning attempt was assessed as a sustained full-capacity read rather than as a neutral operation — cloning requiring every sector to be read in order including regions unused for decades, while ordinary use reads a small fraction. Cloning software imposes no limit, so a difficult region is retried indefinitely, and thousands of repositioning operations in one place explain a drive that afterwards cannot read its own configuration. Imaging proceeded under strict per-sector timeouts.
The outcome
The clone attempt assessed as a sustained full read, the drive addressed outside any host, and a sector-level image taken under capped timeouts and validated by booting it. 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: your plan was right and the method was not. Cloning reads every sector without a time limit, so a marginal drive spends itself on the regions it cannot return.
Before cloning an old or uncertain drive
Use imaging with per-sector timeouts rather than a clone. Cloning reads every sector in order without any imposed limit, so when it meets a region that won't return, the drive retries indefinitely — thousands of head repositions in the one place least able to bear it. Ordinary use never does that, because it reads only the fraction it needs. If preservation is the goal, insist on a sector-level image rather than a file copy: boot code, hidden system areas and attributes aren't reproduced by copying files.
Stop cloning — call Cambridge Data Recovery on 01223 655015; the attempt assessed as a sustained full read, imaged sector by sector under capped timeouts, image validated by booting it.
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.