Clone Disk Error: Failed to write data to disk 0x1000D3
I am attempting to use the clone function to transfer an SSD which is my C boot drive to another, larger SSD using ATI2018s clone function.
I am using the bootable media as instructed, and not attempting the cloning process within Windows. I followed all the steps in the video and all the information I can find online, but I’m still receiving error in the attached picture.
I have ran chkdsk /f /r on both drives with no issues, but cannot get past this error. Any ideas?
Well, I found a solution...use a different program! Used Samsung’s transfer program and was up and running in less than 20 minutes. The problem lies with the ATI2018 software.
Glad to read that you have found a solution that did the job you needed to do. Ultimately that is the most important thing, though I am sorry that you found that ATI 2018 was not able to do this for you.
In your screen shot, the disk giving the error is shown as hard disk '4' but this uses a different numbering system than you would see in Windows Disk Management. Windows always starts from disk '0' whereas Acronis starts from disk '1', so in Windows terms, the disk giving the error was disk '3'.
Same problem with ATI 2015.
Source disk is not my bootable, destination disk is free and it's size is bigger.
After thinking about 20 min ATI says, that Failed to write data to disk 0x1000D3
Error to write on drive 3....
in Acronis Drive 3 is _SOURCE DRIVE_, not Destination
Сергей Иванышкин wrote:Same problem with ATI 2015.
Source disk is not my bootable, destination disk is free and it's size is bigger.
After thinking about 20 min ATI says, that Failed to write data to disk 0x1000D3
Error to write on drive 3....
in Acronis Drive 3 is _SOURCE DRIVE_, not Destination
Hello!
Please try to clone using the WinPE B.media: https://kb.acronis.com/content/48152
If the issue persists, I suggest you to run a CHKDSK: https://learn.microsoft.com/en-us/windows-server/administration/windows…
I also checked our records and I saw similar errors with the latest build of ATI2015 and they were just fixed with the ATI2016 version. Unfortunately this versions are outdated since a long time ago and without maintenance so it's complicated to have a complete feedback.
Thanks.