Backer wrote:When making a full image of a primary partition using the CD boot, and then restarting the PC, chkdsk jumps in right after boot up in an attempt to fix 'dirty volume'. It is possible that files are being corrupted in the hard drive all along but when I get that chkdsk thing at boot up, it happens after taking an image of the primary NTFS partition in a RAID 1 array. The loose correlation invites the question whether R-Drive image is causing the corruption. Not only is the NTFS partition corrupted, but the restored image has exactly the same corruption. This is in a WinXP pro SP3 environment. The chipset and SATA drivers are nVidia.
The question is: Os it possible that R-Drive Image is causing the partition that it images to become corrupted?
Is it really corrupted (chkdsk returns "serious" errors) or it's just an unjustified chkdsk that was triggered ?
Do you use some kind of instant recovery software such as Rollback RX, RestoreIT, Easeus ToDo Workstation, etc. ?
Alt wrote:Well, it's hard to say without looking at the disk and image.
"Instant recovery" means correcting a file system directly on the disk, doesn't it? If yes, no, and never. We value data of our customers too much to offer them such risky solutions.
Users browsing this forum: No registered users and 0 guests