Skip to main content

Drive Cloning - Cannot Read Sector

Thread needs solution

Hey,

I bought Acronis True Image a few days ago and have been incredibly impressed with it. I had 2 hard drives both of which were failing. One had my Windows XP x64 install on one partition and a bunch of games on the other [total 200GB], the second disk had my music on one partition and files on the other [total 500GB]. So a total of 2 disks and 4 partitions.

The music drive was really struggling badly, Windows was failing to read from it relatively often and it was running slowly. So I ran chkdsk from Windows opting to repair bad sectors. Chkdsk found at least 15 bad sectors and apparently 'fixed' them. The drive was still running incredibly slowly so I decided to clone it to a brand new drive. The clone worked successfully (after 20+ hours of running) apart from showing me errors for failing to read from sectors. It warned about 3 sectors (322770232, 322770234 and 322849203) before I got fed up of selecting "ignore" and instead opted for "ignore all". The clone finished, I swapped the drives out and restarted the PC. All seemed to work fine.

The only thing is I am now worried that if it failed to read from those sectors (and potentially more - given I opted to ignore all), will there have been data loss? It is hard to tell if anything is missing as these are sizeable drives with a lot of files and directories. Is there any way to tell what may have been lost if anything?

My other drive (windows system drive) was cloned perfectly first time and I am now running my PC off that drive.

This is a great product, saved me a lot of money and time but just has left me with a few niggling worries in the back of my mind about those failed sectors.

Any thoughts would be greatly appreciated.

OJB

0 Users found this helpful

Various tools can help verify the coherence of the file system information and the files, but chkdsk /r will do this pretty well. Bad sectors are not an issue if the number doesn't increase widely, and the OS can work around them as they get identified. The risk of data loss is hard to quantify as it is not clear what the history of the bad sector has been (when it was occupied, when it was identified as a bad sector).

If I had been you, I wouldn't have selected ignore all, to get a sense of how many bad sectors I got. I would have ran a disk fixing utility to complement chkdsk, then:
- for the content files, I would have copied the files with a file copying utility that checks the integrity of the copying (with a CRC check for example). The verified file copying might uncover file corruption.
- for the system files, I would have run a sfc ( http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html ), and would have been satistied with this check,
- for the application files, I would have taken the risk that some of the application files could be corrupted (you can always reinstall the system and the applications, but the content files might not be replaceable).
Then, I would have created a disk and partition image, restored on a new disk ignoring the bad sectors.