Aller au contenu principal

source drive registry corrupted when cloned - config.sys missing - system down completely

Thread needs solution

system crashed during the cloning and wont restart because of corrupted registry. I now see that it is not the first time this has happened. I operate a system on RAID 1 configuration because I cannot afford down time and this happens! I contacted live chat to be told that as it is 30 days past my subscription renewal they cant help me unless I pay!!!! Are you kidding??? You have just cost me a magazine cover! Who will pay me for that?

can someone tell me the fastest way to fix the registry - I am able to access the main drive by booting using BartPE - if one can get the system booted again, can we not just choose a restore point to get back previous registry settings?

0 Users found this helpful

After the Clone, did you reboot while leaving both drives connected? Windows won't allow two Active system drives, so it will render one of the unbootable. That is a Windows limitation, not an Acronis issue. Perhaps what occurred on your drive is related to that.

Is there a reason you need to Clone? Really, Backup is safer and more flexible. Many users encounter problems Cloning which they would not have if they has instead used Backup.

Don't use Clone. Do a full disk Backup, selecting the entire disk, and a Restore. The end result will be the same as Clone, but with many advantages.

A full disk backup, selecting the disk checkbox rather than individual partitions, includes everything. It includes everything that a clone would include.

The difference is that while a clone immediately writes that information a single time to another drive, a backup is saved as a compressed .tib archive. As such, multiple .tib archives may be saved to a single backup drive, allowing for greater redundancy, security and flexibility.

Once a full disk image .tib archive is restored to a drive, the result is the same as if that drive had been the target of a clone done on the date and time that the backup archive was created.

Clone is riskier because we've seen situations where users mistakenly choose the wrong drive to clone from and to, thus wiping out their system drive.

I cloned because one disk in my Raid Array showed degradation so before installing new disk and rebuilding array, I was imaging the remaining disk to a scratch disk as a precaution (yeah really) in case something went awry in the array re-build process. I had done this before on an earlier version of Acronis and had an image of my main drive without issue years ago when in the same situation. I walked away during the cloning process as all appeared allright and heard the system re-booting not 5 mins later. System automatically tried to reboot and there was the error message that my registry had been corrupted with config\sys missing. my question is what is the fastest way to fix the problem. The drive is otherwise intact as i can see it thru BartPE.

Cealy,
Its unfortunate that you didn't have a back up of the array prior to attempting clone or repair. One of the drives in your mirror might be good from a mechanical standpoint, but has software corruption. The (other) disk that was reported as degraded should be fully tested and evaluated before putting it back into service.

System integrity is only an assumption if the array was degraded, mirror broken or "out of sync". No one knows for sure if your install is intact. Seeing a disk or array in the boot environment does not mean you will be able to recover succesfully. You don't know if what you have now is complete or repairable? I'm sure you understand this.

You have a few possible solutions, but no guraruntee. Success depends on the extent or type of failure. Is this XP?

This error is likely caused by a corrupted registry hive. There are several possible methods to repair. Again, no guaruntees since it's unclear what the state of the array was prior to it's failure. Mirror broken, out of sync, or physical issues with one or more of it's members.

Method 1: Restore a back up using the Recovery Console. This can be accessed using a windows XP install CD.

Method 2: Boot from a Ultimate Boot CD Windows and tell it to perform a registry repair. This process is automated (replaces the corrupted hive with a previous version) if you are not comfortable working with a command prompt.

*** Most importantly, I cannot guarantee your success. Other unknown factors may be present.

When you don't have a back up or image of your data, and you are unsure about the mechanical integrity of a disk, I always recommend that the failed drive be slaved in a working system and that all important data be copied off the drive before any type of repairs are attempted. If successful, you can attempt repair, perform testing and evaluate the disk's health safely.

I'd work with whichever disk wasn't reported as problematic or failing first.