Clone software says source disk error – what’s really going on

Quick answer

Use ddrescue on Linux or Macrium Reflect’s “Ignore bad sectors” checkbox in Windows. The error means the software hit a bad sector and stopped – you need a tool that skips those and retries later.

Why this happens

Disk cloning software like Clonezilla, Acronis True Image, or Macrium Reflect reads every single sector from the source drive. When your hard drive has a few bad sectors – from age, a power spike, or physical damage – the software hits a read error and throws “source disk error.” It’s not a bug. The software is designed to stop because it assumes you want a perfect bit-for-bit copy. But most users just need the data, not the bad spots.

I see this most often on 5+ year old mechanical drives that were dropped or run hot. SSDs rarely cause this – they fail differently. But with spinning drives, bad sectors are common after 3-4 years of daily use.

The real fix is to use software that skips bad sectors on the first pass, then retries them later. This gives you a clone of the good data, missing only the bad parts. You lose a few files, but you keep the drive working.

Fix steps – the main method

Step 1: Stop using the source drive

Every read attempt stresses the head and can spread damage. If you hear clicking or grinding, power off the PC and don’t try cloning yourself – send it to a recovery lab. Otherwise, proceed.

Step 2: Choose the right software

• Windows users: Download Macrium Reflect Free (version 8 or 8.1 works fine). During the clone wizard, check “Ignore bad sectors when reading” and set retries to 1. This tells the software to skip unreadable blocks and try once more.
• Linux users: Use ddrescue from the terminal. It’s built for this. The command:

  sudo ddrescue -d -r1 /dev/sda /dev/sdb rescue.log

  where /dev/sda is the source, /dev/sdb is the target. The -d flag does direct disk access (faster), -r1 does one retry.

Step 3: Run the clone

With Macrium, the clone starts and you’ll see a progress bar. It might pause at bad sectors – that’s normal. Let it run. It can take 1-2 hours for a 500GB drive with a few hundred bad sectors. ddrescue gives you a status display showing how many errors it found.

Step 4: Test the clone

Boot from the cloned drive. If it works, you’re done. If Windows chkdsk runs on first boot, that’s normal – it fixes filesystem issues from the skipped sectors. Let it finish.

Alternative fixes if the main one fails

Option A: Use a live Linux USB and ddrescue

If the source drive doesn’t show up in Windows at all, boot from a Linux USB (Ubuntu or SystemRescue). ddrescue can sometimes read drives that Windows completely ignores. The command is the same as above.

Option B: Freeze the drive (risky, but works)

If the drive fails to read even with ddrescue, put the drive in a sealed plastic bag and freeze it for 2 hours. The cold contracts the metal parts and can free a stuck head. This is a last resort – it works about 30% of the time for mechanical failures. After freezing, you have maybe 10-15 minutes of reliable reads before it warms up and fails again. Run ddrescue immediately.

Option C: Replace the controller board (advanced)

If the drive clicks but the platters are fine, swap the controller board from an identical donor drive. You need a screwdriver set and the exact model number printed on the drive’s label. This is for people who’ve done it before – it’s easy to short out the board.

Prevention tip

Bad sectors don’t appear overnight. Run chkdsk /r on your drives every 3 months. Windows will mark bad sectors in the filesystem, so if they grow, your backup software can skip them. On Linux, use fsck -c to scan. The key is catching them early – before the drive fails completely.

Also: never rely on a single clone. Keep two backups. One clone for fast recovery, one file-level backup in a cloud or external drive. When a clone fails, the file backup saves you.