Salta al contenuto principale

TI 2009 Build 9796 NTFS errors in W7

Thread needs solution

I used TI 2009 build 9796 to clone a 500GB disk containing W7 to a 640GB disk and now I get NTFS errors when W7 boots. Everything seems to work ok, in fact it took me over a week before I looked in the Event Log and saw the errors. Does anybody know if the latest build of TI 2009 fixes the cloning problem or do I have to pay another $30 to go to TI 2010? In the build 9809 release notes it mentions a W7 fix but does not say anything about the NTFS cloning problem. Before I go back to the 500GB drive and throw in the towel and go back to the 500GB disk, does anyone have a solution to the NTFS errors short of recloning with a hopefully fixed TI?

0 Users found this helpful

I do not recall seeing anyone else report this as a problem with TI. I've restored my Win 7 partitions several times with TI and have not had this NTFS error event occur.

I would suggest booting from the Win 7 install DVD and go to a manual command prompt. Run the command chkdsk x: /R on each of the partitions on the disk, substituting the correct drive letter (C:, D:, etc) for x: to do a thorough scan of each partition for bad sectors. This will take some time to complete on a 640 GB disk, so be patient. Check the event log later to see if the problem still exists.

Much to my surprise the repair option on the W7 disk said it fixed a startup problem and the Event errors went away!! Thanks DwnNDrty for the suggestion. However, I did not have the problem on the 500GB drive and it appeared on the 640GB drive after using TI Clone. Therefore, I tend to think TI has a problem that may or may not have been fixed in the latest build. Hopefully the Acronis technical people are watching and can respond.

Have you seen this regarding a new build for True Image 2009?
http://forum.acronis.com/forum/6134

Yes I saw that thread. Until a few days ago I would have agreed since I have been using W7 and TI since W7 first became available and did not have any issues (that I was aware of at least) until I did the cloning trick from a 500GB drive to a 640GB drive. Maybe my problem was just a random event but I doubt it.