Aller au contenu principal

Cloning data - error 0xa0001: Failed to prepare operations. Error code 3: 'internal error: script is inconsistent'.

Thread needs solution

Hello,
I'm trying to clone 1TB HDD to 500GB SSD with Acronis True Image 2020.

What I was trying to:
On the previous system, there is a 1TB Seagate HDD, which is separated with ~500GB as C: partition(~120GB was in used) and ~500GB as D:(~80GB was in used)
I wanted to mount a 500GB WD SSD and clone from HDD to SSD except for D: partition.
After the migration, I was planning to delete C: and boot partition in HDD.

I am trying to copy these two disk drives with another PC that Windows is installed in M.2 SSD. That's why the log looks I am copying G: and H: instead of C: and D: (Because the operating ATI on Windows, which is installed in HDD, was too slow).

Thus, I mounted both drives on this PC and operated ATI, as previously mentioned steps.

The cloning process seemed followed well, but when it starts to clone, it fails with the error. The log file is attached below.

I want some information on the reason for this error code (error 0xa0001: Failed to prepare operations. Error code 3: 'internal error: script is inconsistent'.), and the solutions to solve this problem.

I am waiting for your advice, so please share your wisdom. Thank you!

______________________________________________________________________

After I read a forum thread 'Why is GPT default when cloning an MBR disk?',

I realized both disk drives (Seagate HDD and WD SSD) were MBR format, and the M.2 SSD that I am trying to operate ATI  was GPT format. I will retry manually to copy with MBR format on WD SSD, but I am not sure this is the critical source of this error. If you have any experience copying the MBR format disk drive with GPT format, please advise me.

Fichier attaché Taille
log_1.png 423.2 Ko
0 Users found this helpful

______________________________________________________________________

After I read a forum thread 'Why is GPT default when cloning an MBR disk?',

I realized both disk drives (Seagate HDD and WD SSD) were MBR format, and the M.2 SSD that I am trying to operate ATI  was GPT format. I will retry manually to copy with MBR format on WD SSD, but I am not sure this is the critical source of this error. If you have any experience copying the MBR format disk drive with GPT format, please advise me.

______________________________________________________________________

 

Probably it is the source of the problem. Although I copy disks manually, it was impossible to copy disks to MBR partition format with my UEFI bootable PC. It may possible with BIOS bootable PCs, as the tutorial says.

 

Anyway, It was impossible to solve with ATI software as I can do, I solved it with another disk migration tool. Thanks!

Jin, the only method of preserving MBR format when cloning disks on an UEFI system would be to use the Acronis Rescue Media and boot that PC using that media in Legacy / CSM boot mode, which may not be possible if the PC doesn't allow this!

Please submit Feedback directly to Acronis (use the tool provided in the GUI Help section) and ask for your vote to be added to the Acronis internal feature request TI-179333 Allow selecting the boot mode (BIOS or UEFI) after recovery/cloning.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Everyone,

registered this topics as a vote for  TI-179333 Allow selecting the boot mode (BIOS or UEFI) after recovery/cloning, thank you!