I wonder if to let the chkdsk goes after imaging..

[Scorpion]

Hi all,

After imaging bad drive with Atola Imager to a good drive I connect the drive to OS station and before the syetem up (win 7) the system automatically run chkdsk on the good drive for few minutes.
Usually I stop this process before it even begin and then scan the drive with R-studio for recover the files from the damaged file system.
I stop the automatically process of chkdsk because I have the unexplained feeling that the checking delete or damage few of the files before I manage to recover them.
Is this correct that checking and fixing the file syestem table can damage the files? or to let the checking to repair the file system table (that gives me after that a convenient way to get access to the data and so save the long scaning with R-studio)?

Best Regards,

[thatdellguy]

Use a write blocker. Any changes to your image is probably not a good thing. Wouldn't you agree?

[Scorpion]

Use a write blocker. Any changes to your image is probably not a good thing. Wouldn't you agree?

Sure that I agree this is why I don't let the checking fixing my drive.
Sorry for the might be a silly question, but I don't use a write blocker.
Can you please expand about this?

Best Regards,

[HDD Spaz]

If you really want to use check disk, image the image first. write blocker = write protection, you should know what this is if you are offering professional data recovery services.

[Scorpion]

If you really want to use check disk, image the image first. write blocker = write protection, you should know what this is if you are offering professional data recovery services.

Of course that I know what is write protection, I use it all the time.
I know what is the importance of such feature.
I thought that write blocker is a kind of software name or somthing.