Skip to main content

failed to write data to disk

Thread needs solution

I was doing a clone from 120gb SSD to 500gb SSD and time was going back and forth from 8 hours to 8 minutes, stuck for a long time, then get this error? 2016-6571 WinPE boot disk.

 

 

 

 

Attachment Size
acronis_error.jpg 214.9 KB
0 Users found this helpful

Tim, your error message:

Failed to write to sector '40,201,088' of hard disk '1'.
Failed to write the snapshot manager volume. (0x1000D3)

This suggests that you have a problem on your source 120GB SSD drive - Acronis counts drives from 1 upwards which is different to Windows which counts drives from 0.  The message suggests that you have encountered a bad sector on drive 1 (120GB SSD).

Please try running CHKDSK /F /R against your source drive plus use any other drive specific utilities that may be provided by the manufacturer.

I will try this tomorrow, is the /R swtich necessary on SSD? It's an Intel SSD.

Thanks,

Tim

Tim, the error is referring to a sector problem so using the /R switch with CHKDSK is still valid to use as this will check for bad sectors from a Windows perspective in the NTFS file system.

chkdsk /F should be suffcient on an SSD drive.  Solid State Drives do not have sectors as do mechanical drives.  SSD uses blocks and those blocks are fixed or marked not for use by the drive controller.

ran chkdsk /F and went right though. no errors

running chkdsk /F /R now and stuck at 14% quite a while now.

Win 10

Tim, If chkdsk gets stuck, if might be an indication of a problem with the NTFS file system information, or (unlikely) a hardware issue with the SSD.

Try to perform a backup of your SSD. Make sure to select the source as disk and partitions, and select the entire SSD. If the backup fails, try to eliminate one partition from the backup until you have identified the faulty partition. Report back.

 

chkdsk /f /r finally finshed.

I was able to make an image of C: easily. when i try to clone to 500g SSD stuck at 8 hours again. i'll let it run. thanks.

Tim
 

Clone can be more finicky and has more limitations than a full backup image and restore.  If you have another drive or network share you can use, I'd take a full disk image, USING THE OFFLINE RECOVERY MEDIA (don't start the process in Windows, it's not worth accidentally corrupting the Windows bootloader when you can avoid this possible scenario simply by using your recovery media to start the process instead) and save the image to that other location.  Ssee how long it takes to create the backup; with a 120GB SSD, it should go pretty fast - even if storing the image on a USB 3.0 external spinner - not more than an hour I'd guess.  Restoring that image to the new 500GB SSD should go much faster, especially if it's attached to the internal SATA connector already.  

To each their own, but I generally recommend backup/restore over clone anyway.  1) it's less picky - no issues with different sector sizes among drives, not as susceptible to bad sector issus, etc.  2) you get a backup out of it which is your saving grace if something goes wrong  3) the end result is the same

Just make sure when you do a backup/restore, that you boot your recovery media to match how the OS was installed (boot in Legacy mode if your OS is a legacy/MBR install or boot in UEFI mode if if your OS as instaleld as UEFI/GPT).  How you boot the recovery media will determine the partition layout of the restored image - same as how you boot Windows insallation media.   

I was thinking the same thing. just restore from backup image.

C: is GPT, and I was using the WinPE boot CD, now wondering about UEFI boot from CD. never thought of that.

shouldn't matter if Boot CD was made on Windows 7 or 10? (OS is 10)

thanks again.

If using the default recovery media (linux based), it shouldn't matter which system you create it on.  Only if creating a WinPE instance, might make a difference, but that's really more related to the version of Windows ADK installed/used to build the WinPE.  Acronis 2016 is capable of creating the WinPE with the current Windows 10 ADK and just about anything lower - I'd recommend using the Windows 10 ADK as it gives the best driver support "out of the box".

Glad to be of assistance. 

 

well, it took overnight, clone ended up working. next time I will create and image and restore to the new drive.

thanks for the tip booting UEFI when restoring from an image.

thanks again