Data Recovery Case File · Solid State & Flash · The Copy Is the Diagnostic
A Copy That Fails at the Same Place Has Found Something and Is Reporting It
His enquiry treats a recurring error as an obstacle to work around. An external solid-state drive being backed up to a larger drive, where "I keep getting the same error code" — and he asks about both completing the backup and repairing the fault so future backups work. The error is not preventing the backup so much as describing why it cannot finish: something on the source cannot be read, and the copy is where that becomes visible.
| Media | External solid-state drive being copied to a larger destination drive — copy terminating repeatedly with an identical read error |
| Reported situation | External solid-state drive in service · backup attempted to a larger external drive · copy terminating with the same error code on each attempt · owner seeking both completion of the backup and correction of the underlying fault · content required |
| Fault class | Localised read failure on the source revealed by a full copy — repeatable termination indicating a specific unreadable region; source not suitable for continued service |
| Equipment used | Repeatable failure point treated as a located fault rather than a copy problem · source removed from service before capture · imaged write-blocked under strict per-sector timeouts with readable regions taken first · unreadable regions revisited across later passes · recovered content validated and delivered to new media |
The decode: what the repeatability tells us, and what the request should be
Why a copy failing is informative rather than merely annoying: a file-level copy reads every occupied region of the source. It is the only routine operation that touches all of it, so it finds regions that ordinary use never reaches.
What an identical error each time establishes: the fault is at a fixed location. A random failure would move; a repeatable one is the same region failing the same way, which means it has been found rather than encountered.
What that class of error generally reports: the system asked for data and did not receive it in a usable state. It is a read failure, reported at the level of a specific file — which usefully names the item sitting on the bad region.
Why that matters practically: the failing file can be identified and set aside. Copying everything except that item frequently succeeds, which secures the bulk immediately rather than after any repair.
Why the second half of his request cannot be answered as asked: he wants the fault repaired so future backups work. An unreadable region on a solid-state drive is not repaired — the controller already substitutes spare capacity for regions that fail, and one becoming visible means that mechanism has been exhausted or bypassed.
What that implies about the drive's future: it should not have one. A drive showing user-visible read failures has passed the point where its own error handling copes, and further failures are likely rather than possible.
Why that reframing is the useful answer: the objective is not a working backup routine on this drive. It is getting the content onto something else and retiring the source, which is cheaper and more certain than any repair would be.
Why an ordinary copy is nevertheless the wrong tool now: it stops at the failure. Each attempt spends time reaching the same point and stopping, and repeated attempts on a degrading region can make a marginal read a permanent one.
What is done instead: the drive is imaged with capped timeouts so no region absorbs the available time, readable areas captured first at full speed, and difficult ones revisited across later passes — which secures everything reachable before anything difficult is attempted.
What must not happen: no further backup attempts, and no repair or optimisation utility. Utilities of that kind write to the drive, and writing is what a failing device handles worst.
On the bench
The repeatable failure point was treated as a located fault rather than a copy problem — a file-level copy reading every occupied region and therefore reaching areas ordinary use never touches, with an identical error on each attempt indicating a fixed location rather than a transient condition, reported at file level and so naming the item on the failing region. Imaging ran write-blocked under strict per-sector timeouts with readable regions taken first.
The outcome
The repeatable failure treated as a located fault, the source removed from service, and readable regions captured first under capped timeouts. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the copy found the fault rather than causing it. An identical error each time means a fixed region — and a drive showing read failures at user level has already exhausted its own error handling.
A backup that fails at the same point every time
Stop retrying it and change the objective. Repeatability is informative: a random failure would move, so an identical error each time means a specific region is failing the same way, and the error usually names the file sitting on it. That file can be set aside and the rest copied, which secures the bulk immediately. But don't aim at repairing the drive so future backups work — a solid-state controller already substitutes spare capacity for failing regions, so a failure you can see means that has been exhausted. Get the content onto new media and retire the source.
Stop retrying — call Manchester Data Recovery on 0161 871 0788; repeatable failure treated as a located fault, imaged under capped timeouts with readable regions first, difficult areas revisited across passes.
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.