The clone runs well, then hangs at one point for hours, retrying the same sectors. That is not a software bug — the source disk is physically damaged there. Here is the strategy that actually saves the data.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ Rescue workflow
🎥 Watch the full video — HDD change and complete disk clone, step by step
When a clone fails halfway with read errors, the worst move is to run the same clone again. A failing drive has a limited amount of life left, and the job is to spend it copying healthy data — not hammering the damaged area. This is the rescue-first method technicians use.
Disk clone — the run that never finishes
Cloning Disk 0 → Disk 147%
Elapsed time2:41:07
Read error at sector 482,771,200RETRYING
Read error at sector 482,771,208RETRYING
Estimated time remaining-- : --
The classic pattern — the clone flies through healthy areas, then sits at one percentage for hours, retrying the same damaged sectors.
1
Recognise the Pattern — Errors at the Same Place Every Time
A healthy clone moves at a fairly steady speed. A clone hitting bad sectors behaves differently: it slows to a crawl or freezes at one percentage, the log fills with read errors at nearby sector numbers, and a mechanical HDD may start clicking, ticking or repeatedly spinning down and up. If every attempt fails at roughly the same point, the disk has physical damage in that area. Retrying the same normal clone will not heal it — it only keeps the dying drive working at maximum stress.
2
Stop the Normal Clone and Change Strategy
Cancel the clone. Do not run chkdsk /r or a full surface scan on a dying drive "to fix it first" — hours of head movement over damaged areas can finish the drive off.
If any files on this disk exist nowhere else, copy the most important folders off first with a plain file copy, starting with the smallest and most valuable.
Decide honestly how valuable the data is. If it is business-critical or irreplaceable and the drive is clicking, power it off and use a professional recovery service. Everything below is the do-it-yourself route for data you can afford some risk on.
3
Image the Drive with a Rescue Tool That Skips Bad Sectors
The correct tool for a failing source is not a normal cloner but a rescue imager. These tools copy the healthy areas first, keep a log (mapfile) of what is done, and only afterwards make careful extra passes at the damaged areas — so if the drive dies mid-job, you keep everything already copied and can even resume on another PC.
GNU ddrescue (on Linux live USBs, and included in recovery environments) is the reference tool: ddrescue -f -n /dev/sdX /dev/sdY rescue.log makes a first fast pass that skips bad areas; a second pass with -r3 retries the gaps up to three times.
Clonezilla has a rescue option in its advanced parameters that tells it to continue past read errors instead of aborting — acceptable for mild damage.
HDDSuperClone is another purpose-built option with a free version for this exact job.
Image to a healthy drive of equal or larger size. Work from the image afterwards, never repeatedly from the dying original.
4
Then Clone or Restore from the Image
Once the rescue image sits on a healthy drive, the rest is routine: restore or clone that image onto your new SSD, then boot-test it. Windows may want a disk check on first start — let it run. Files that lived exactly on the bad sectors will be missing or damaged; rescue tools fill unreadable areas with zeros, so a document from a damaged area may open with holes or not open at all. That is the honest limit of physics — those bytes no longer exist on the platter.
5
Know When to Stop
Clicking that gets louder, a drive that stops being detected, or a burning smell — power off immediately. Continued attempts can destroy the heads and the data surface together.
A sector-by-sector copy of a drive with bad sectors copies the damage map too; it is not a cleaner result than a rescue image, just a slower one.
After recovery, never trust the old drive again — not even as a scratch disk. A drive with growing bad sectors only gets worse.
🔴 Honest note: no software can read data from a physically destroyed area of the disk. Rescue tools recover everything that is still readable — often 95 percent or more — but anyone who promises 100 percent recovery from a clicking drive with free software is not telling you the truth.
🎥 Watch the Complete Video Guide
The full process on a real PC — changing the HDD and cloning the complete disk, step by step.
Can I just tell the cloning software to ignore errors?
Some tools allow it, and for one or two isolated bad sectors the result is usually fine. But ignoring errors on a heavily damaged drive can produce a clone full of silent holes, and the long retries still stress the disk. A rescue imager with a mapfile is the safer tool for anything beyond trivial damage.
Will chkdsk fix the bad sectors so the clone works?
chkdsk cannot repair physical damage. It can mark bad sectors so Windows avoids them, but running its full /r scan on a dying drive takes hours of heavy head movement — exactly the stress that can kill the drive before your data is copied. Image first, repair later on the copy.
The drive clicks. Is there any software fix?
No. Clicking means mechanical failure inside the sealed unit. Software can sometimes still read data between clicks, which is what the rescue method above is for — but if the data is critical, a professional lab with a clean room is the honest answer.
This guide is based on the Technical Anshu video on cloning a full disk to a new drive • Stuck on a step — ask in the video comments and the community will help 🙏