Skip to main content

Corrupted Images created on SSD

Thread needs solution

Hello All,

It is a bit of surprise to encounter this. But I think from my observations and testing, it seems when I use the rescue media to create an .tib image file, with the same USB-to-SATA adapters, the image file is stored on a SSD, invariably, I get a corrupted image.

Now here are the details:

I tried multiple USB-to-SATA adapters: USB-C USB3.1 to SATA, USB-A USB 3.0 to sata, USB 2.0 from a drive enclosure, and some more I can't recall. I validate the images on PC with Acronis installed. I've tested multiple SSDs, as I have some old 64GB and 128 GB SSD being retired from regular duty as systems move to NVME, and those inclued a PNY CS1311, Samsung evo 840, and  OCZ Vertex 3. BTW I format all these with NTFS so they will be easy work with with Windows. Sometime even in the middle of creating and writing out the file, Acronis will issue and error message about some write error, and it give me the option to retry. I select the retry and Acronis seems to be happy. But that doesn't mean I got a good image.

After I create the image, I will attempt to validate with a PC with Acronis installed. With a good image I can easily browse thru the .tib image file, and see all the content elements inside browse the user directories, windows system32 etc. However with image files created on a SSD, the error will immediately show up when you plug in the USB-to-SATA adapter with the SSD attached. Windows will complain about the drive being corrupted and needs chkdsk. I can do either chkdsk without the /f and see that windows complains, or I can do it with the /f and attempt to fix it. With the /f option, sometimes the .tib gets completely deleted as a result. Either way, if the .tib is still around, I try to browse with Acronis thru the file explorer, and invariably I will get an error message from Acronis about the image being corrupted or still in use by some other device.

I didn't clue in on the SSD being the issue, until after several attempts and having tried multiple SSDs. Often in the interest of time, I would switch to a HDD, or point it to network share. The same USB-to-SATA adapter connected to a spinning HD, and it is all good. And this is further obscured by the fact that it seems I can clone from SSD to SSD just fine, having done this multiple times and the systems all run flawlessly without issues. But somehow creating that images file on a SSD, has been very frustrating.

Please Assist. Thanks.

 

0 Users found this helpful

Tim...welcome to these user forums.

At this point, I don't have any solutions or possible causes, however, I do have 2 spare SSDs that I can connect via usb.  So I will try to duplicate your problem.  I have performed many backups to a spinning HD via usb using rescue media, with no problems.  I have not performed any using SSDs.

I will report back in a day or two.

 

I have conducted my first test using a Samsung MZNLF128HCHP-00L1 128GB m.2 hard drive in a StarTech usb enclosure connected via usb C.   I booted using WinPE rescue media and created the backup.  I also validated the backup using rescue media.  No problems were noted.  After booting to Windows 10, I navigated around the backup with no problems.

Tim, my first question is...are you using WinPE rescue media or Linux rescue media?

I will conduct another test on my other SSD tomorrow.

Regards,

FtrPilot

I have found that adapters are most reliable when they use their own power supply.  Those that draw power over the USB cable itself can fail because of an insufficient power level to run the drive. 

In reply to by truwrikodrorow…

Hello FtrPilot,

Thanks for taking time to experiment.

I am using the Linux Rescue media. I do have the Windows PE media, I suppose I can experiment with that also.

 

Tim

Tim,

EZ dock 3 provides power supply:

https://www.amazon.com/Kingwin-2-5-Inch-3-5-Inch-Clone-EZD-2537U3/dp/B0…

I have one and use it with 3.5 HDDs and 2.5 HDDs/SSDs.

I also recommend trying with WinPE rescue media.

Regards,

FtrPilot

 

Here is what I use:

https://www.amazon.com/gp/product/B005B3VO24/ref=oh_aui_detailpage_o00_…

I have used this adapter for the past 3 years and have not had a failure yet.

 

Hello All,

I did more experiments. I tried an adapter with an external power supply/AC adapter. This did not seem to make any difference to creating corrupted images on the SSD.

Then I tried using my previous adapter without external power, and with the windows PE rescue media. This time around the image was actually good and valid image on the SSD.

It seems somewhat troubling that the Linux Rescue media is unable to create a valid non-corrupted image on a SSD. While I've never seen the linux rescue media fail to clone an SSD to another, it is quite troubling that it has problem creating an image.

Does anyone know what is Acronis's official statement about this? Are they even aware there may be an issue here? How do we inform Acronis of the issue?

Thanks.

Tim

Tim,

You should open a support case with Acronis to make them aware of the issue.  You can get to the support site from the Windows installed application by clicking the question mark at the bottom left corner of the GUI.  Select the  About icon and you will find a link to support where you can contact them.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Tim,

I haven't found any similar issues logged in our internal sources, so it's definitely worth raising a support ticket for investigation. Please share the ticket ID here, so that I can monitor the resolution process. Should you have any questions, please let me know.