Constant Errors, Data error (cyclic redundancy check)

WOW, 2 days, 10 reads, no response.
I was hoping for better than that from an Acronis sponsored forum about an Acronis product.

My guess from reading the log is that the drive is having a problem since the error is listed as a CRC which is normally presented by the HD itself. However, I'm not sure how the error would be listed it occurred in the USB interface.

If you haven't, run chkdsk X: /r where X is the drive letter of the partition being checked. Chkdsk is good but like any diagnostic, it won't find everything and you may need to use a manufacturer's diagnostic on the drive.

An easy thing to try first is to just change the USB cable and to put it on a different port. The rear ports on the machine are usually the better choice due to the much short cable length to the motherboard USB controller.

If you are able, you could remove the HD from the enclosure and mount it as an internal and see if the situation improves or worsens.

HTH.

Thanks for the reply. When this trouble started I actually reformatted the drive I also ran chkdsk G: /f several times with no errors. By habit I refer to the drive as a USB drive but I had it hooked up via firewire. I swapped it out to USB and ran chkdsk g:/r and had to many errors to fix in the files that were on the drive. I deleted all the files and ran it again and got the following report:

Free space verification is complete.
Adding 13 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

I should have a good drive and switched ports and wires.

I'll run some backups and see what happens.

I ran 3 backups and they all went fine with no errors.
Hopefully that did it.
Thanks

The image was that was captured became corrupt. I just ran into the same issue and had to do some investigative work in DOS (omg).

Attempted an xcopy and was unsuccessfully which means Acronis gave out a false positive when it said the image was sucessfully captured.

In my case it turned out to be the drive.
After a reformat it's been fine.

If it was some software bogie that caused the initial corruption, then reformatting the drive should put you back in good stead. However, if it was any kind fo hardware prob with the dirve, the great likelihood is that the errors will reappear with ever-increasing frequency. This might not be the drive you want to use to hold your important backups. It could be on the fast path inexorably to where all electromechanical devices eventually go -- the waste can for burial or materials recycling.

Also note that bad backups can happen from poor USB conections and from intermittently bad spots in the farthest reaches of memory.

"Free space verification is complete.
Adding 13 bad clusters to the Bad Clusters File."

How many bad clusters does the disk have??? I know this chkdsk process is designed to let hard disk drives fail slowly and gracefully so that as bits of the drive become unusable then they are ignored, but in my experience you would be unwise to put any faith in a drive with bad clusters.

Edit: By which I mean bad clusters that show up in chkdsk.

Almost all hdisks come from the factory with a few bad clusters; some of the platters come out of manufacturer with weak spots. It's like digital TVs, the manufacturers don't throw out a unit because of a few bad pixels -- that level of tolerance would cost too much. However, when a used drive starts throwing up new bad clusters, it's usually a sign that it is failing, that the read/write heads have been landing on the surface and scratching it, that dirt or moisture has enetered the drive, that it will continual to throw up more bad clusters until it becomes too unreliable to be usable. In the meantime, any file read or written might become corrupted. So, as a rule of thumb, if an hdisk is acting, throwing up bad clusters, then replace at the first opportunity.