Direkt zum Inhalt

Cloning corrupts ORIGINAL disk and clone

Thread needs solution

I have been using True Image to clone the original hard drives in a Win7 based video switching system as backups for my customers. Unbeknownst to me this has been corrupting the Linux based recovery partitions on both the cloned and the original disks.

Why is it even writing to the original disk in the first place?

The machines use Grub as a boot manager so that the user can boot a small Linux installation to re-image the Windows partition in the case of corrupted windows installation. Our clones were for use in the case of an actual drive failure.

I have verified this on three machines at this point but it probably has happened on dozens and dozens of them as I've been using True Image for over a year. These drives com configured from the manufacturer and I have no easy way of getting any technical info on how grub was configured etc.

Here is what I do know:

  • Using BCDEdit I see the 'recovery boot' (on a good machine) calls the path \windows\sysrst.mbr on a bad machine it calls the path \windows\sysrst.exe
  • \windows\sysrst.mbr exists
  • \windows\sysrst.exe does not exist
  • If I change the path on the bad machine (using BCDEdit) to \windows\sysrst.mbr I end up at a Grub prompt but it doesn't actually boot Linux.
  • Windows Still boots fine

Is there any way to repair this?

Why is it even writing to the original disk in the first place?

0 Users found this helpful

Hi Jeff,

This is a good question. We already know that many Acronis products actually deactivate GRUB and LILO on a destination after cloning operation is performed.

kb4974

kb1686

Since the articles above pertain to the destination disk, I would suggest contacting Acronis Customer Support in regards to your question.