Aller au contenu principal

Failed to write to the Snapshot manager volume.

Thread needs solution

Failed to write data to the disk.

Failed to write to sector '4,094,128' of hard disk '2'.  Failed to write the snapshot manager volume. (0x10000D3) Unknown status. (0x9) Access is denied (0xFFF0)

 

I am using Clone Disk with True Image 2017.  Clone mode is set to Automatic.
Disk 1 is the source drive, Disk 2 is the target drive.
Both disks are SSD drives in an external USB Thermaltake BlackX dock.  

The source drive is a Samsung PM851 128GB SSD
The target is a Samsung 850 EVO 1TB SSD.  I also attempted to use a Samsung EVO 500GB, and a Crucial 256 GB, all with the exact same result.

The source drive is from a Lenovo laptop with one of their recovery partitions, which is why I am trying to clone the drive over as opposed to just do a clean OS install and call it a day.

 

All drives are in perfect working worder, checked with the Samsung utility.

0 Users found this helpful

Michael, thank you for bringing this topic to the ATIH 2017 forum rather than pursuing it in the Older Versions forum.

Just to be clear here, the Failed to write to sector '4,094,128' of hard disk '2' error message is normally indicative of a bad sector on the identified disk drive, i.e. disk 2.  However, to be sure as to which actual drive has the bad sector, you need to look in Disk Management on the system where this message is being given and check the drive numbers shown there then add 1 to the same, i.e. if Windows shows drive 0, ATIH would report this as drive 1.  In your message Acronis say disk 2 which would be drive 1 in Windows Disk Management.

You should run CHKDSK /R for the correct drive which may not be either of the two drives you are trying to clone, as the error is shown when writing snapshot data.

When you stated: All drives are in perfect working worder, checked with the Samsung utility - are you saying that all your drives in the system where you are performing this clone operation from within a running Windows system are all Samsung drives and you have checked them all, including the two Samsung drives in the external USB caddy?

Did you check Windows Disk Management and verify which specific drive was show as Disk 1 in Disk Management - was this one of the 2 USB mounted drives, or was it a different drive?  Acronis always numbers drives from 1 versus Windows that numbers from 0, hence the difference in numbers.

Snapshot data is not normally written to external drives, hence again why I suggested to check the other drives involved.

I assume Acronis is consistant with its numbering of drives?  When I listed which drives were which, I refered to what Acronis called them when I was picking source and target.

Indeed, all the drives involved were Samsung SSD drives (with the one exception of a Crucial I tried while troubleshooting), and all were checked.

Nope - Linux numbering may be different than Windows.  You will be best off if your drive names are unique in File explorer so you can identify them in the Acronis linux media.  Either way, if the error is occuring when trying to backup to other disks, the culprit is most likely the Source drive (your OS disk).  

Run 

SFC /scannow    from an elevated command prompt in Windows

Then, when that's done, run 

chkdsk /f /r     from an elevated command prompt in Windows

Reboot the sytem and let chkdsk do it's thing.  

When the system boots backup up, shutdown using a standard command prompt and 

shutdown /s /t 1         (/s is shutodwn /t 1 is a time of 1 second... if you don't put the time, the default is 60 seconds)

This will force a full shutdown.  It's possible that your OS is using fastboot (Win 8.1/10 have it enabeld by default).  This is essentially hibernation and it will store a hiberfile.sys on the hard drive and lock the drive from being fully accessed by 3rd party bootloaders to protect the hibernation file.  I have disabled fasboot and disabled hibernation on all of my systems as this has caused more trouble than help.  Plus, if yoiu're using a fast SSD like a Samsung EVO, I double you'll notice too much difference with fastboot/hibernation disabled anyway.  If you want to leave it on though, I suggest using the command prompt shutdown or "restart" instead of shutdown before backing up as restart will force a full shutdown too. 

Michael, part of the issue here is that you are performing the clone from within Windows which is why the Microsoft Volume Shadow Copy Service (VSS) is involved and creating snapshot data.  I understand that both the source & target drives for the clone are in the external USB caddy, which makes this possible to do, but the normal method of cloning is to do so completely outside of Windows by using the Acronis Rescue Media to boot the system, where there is no need or opportunity for VSS to get in the middle.

Rob, I agree that Linux drive numbering can be different but as above, Michael isn't using the Rescue Media so isn't getting into the Linux environment that the standard media would use.

Michael, please see KB documents:  56634: Acronis True Image: Cloning Disks and 1540: Difference between Backup and Disk Clone which offer more information on the processes involved.  You can use Backup & Restore as an alternative to using cloning, with the added protection of having a full backup of the source drive should anything go untoward.