Failed to write data to the disk error
Used this software in the past to clone Windows Systems and had no problems but recently I've had this error with every single disk I try.
When cloning a Windows 7 system to another disk I get
Failed to write data to the disk
Failed to write to sector ######## of hard disk '4'. Failed to write the snapshot manager volume (0x1000D3) Unknown status. (0x9) Access is denied (0xFFF0)
The destination disk then shows up to have all the Windows file data copied over but not the System Reserved partition that makes the disk bootable.
This has happened three times in a row and has made using this software basically pointless.
Any idea on why this happens?
I saw a previous post that was posted back in 2012 about somebody with the same issue but all they got as a response was to run a disk check through command prompt, which I did, but fixed nothing.
Attachment | Size |
---|---|
error.png | 70.16 KB |


- Log in to post comments

Ok so initially I was doing via the App in Windows 10 and was getting that error. I then switched and tried using the WINPE-Based Media with Acronis Plug-In, got the same error. Then I used the regular Acronis Bootable Rescue Media to clone the disks and didn't get any error, it just said "Clone succesful" at the end, however, when I looked in Windows Disk manager I could see that the System Reserved partition still was not copied over to the destination disk from the source.
I really don't understand why this keeps happening. I've cloned a bunch of disks before with the Win10 App and never had this error and now all of a sudden I'm getting this error with every single disk I try to clone. I followed the instructions to clone a disk exactly, and with their bootable media I didn't even get an error like I did with the Win10 app, yet it still didn't work. I've also done disk checks on all the disks I've been recently trying to clone and they've all turned up with no problems whatsoever.
- Log in to post comments

You need to run the chkdsk command on each partition on the disk and in this case you seem to have a problem with the system reserve partition in particular.
Having said that what you should try firt is to simply restart your Windows 10 PC and then see if you still get the same error. If you do then use Disk Manager to temporarily assign a drive letter to the Reserve Partition, run chkdsk from an admin command prompt on that partition to correct errors then after chkdsk finishes, remove the temporary drive letter from the Reserve Partition and attempt the clone again.
MVP Steve Smith is correct that the Clone function should only be run from the bootable Recovery Media so use it to run the clone again.
- Log in to post comments

Still having trouble cloning. chkdsk doesn't turn up any errors, the cloning process also doesn't turn up any errors when running. Tells me cloning was successful but doesn't copy the system reserved, making the disk not bootable. Cloning in the recovery software and not the Win10 app
- Log in to post comments

Are you running chkdsk /r on the partitions? chkdsk by itself may not return errors even though they are present.
You should run chkdsk /r on the target disk as well because if the disk that is being cloned to has bad sectors the clone would fail as well.
My instruction to restart the PC means just a restart, not shutdown and restart, just restart from the power menu.
When running the clone from the bootable media make sure you select to "shutdown PC" when job completes. Once machine shutsdown, detach the original disk from the PC and connect the new cloned disk to the data connector that was on the original disk. If both disks are left attached when the PC is rebooted this will cause failure. If data cables are not switched as above, this can cause failure as well.
Are both disks being used Basic disks? Basic disks are only supported in cloning operation. If you have dynamic disks, cloning will fail as the cloning of dynamic disks is not supported.
- Log in to post comments

Related to the above mentioned problem.
I have copied a lot of disks without any problem, now suddenly I get the error in attachment.
I 've source and destination disk connected via USB using Windows 7
some more tips ?
Attachment | Size |
---|---|
401120-135802.jpg | 36.28 KB |
- Log in to post comments

Wim, welcome to these user forums.
The error you are seeing are related to the Microsoft Volume Shadow Copy Service (VSS) which is used to create snapshots of data being backed up, this again only is used when running in Windows, though the error may also indicate that you have one or more bad sectors on your hard disk 3.
Note: Acronis numbers drives from 1, whereas Windows numbers from 0, so this should be drive 2 in Windows Disk Management.
The first step should be to identify which particular disk is your drive 2 as shown in Disk Management, then run CHKDSK /R against that drive. If you still have a problem then you may need to check whether you have any hidden partitions on that drive, if so, allocate a drive letter temporarily to the hidden partition and re-run CHKDSK /R against it.
The alternative here is to perform the actions here using the Acronis bootable Rescue Media where VSS will not be used at all, so will eliminate any issues that may be related to using it.
- Log in to post comments

Wim,
Can you open an Admin Command Prompt and run: "vssadmin list writers" without the quotes?
Look through the results from that command and make note of the State and Last error entries for all writers appearing.
What you should see there for State is Stable and Last error is No error.
For any writer where you see something else please write down the Writer name(s) ie. (ASR Writer) and post them back here.
- Log in to post comments