Build 4726 & corrupt volume

Forum rules
Discussion on the R-Drive Image software

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Build 4726 & corrupt volume

Re: Build 4726 & corrupt volume

by MerleOne » Fri Dec 02, 2011 4:56 am

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.
Well, actually, (most) Instant recovery software use some kind of virtual MFT, and recovery means resetting the pointers, but these kind of software are usually dangerous for filesystems, in case some process is interrupted by a power outage or simply a crash, so I agree with you, it's best to say clear from them, even if some of them are more robust than others. In any cases, this is not a backup solution.

Re: Build 4726 & corrupt volume

by Alt » Thu Dec 01, 2011 10:44 am

MerleOne wrote:
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. ?
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.

Re: Build 4726 & corrupt volume

by MerleOne » Thu Dec 01, 2011 9:51 am

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. ?

Re: Build 4726 & corrupt volume

by Alt » Wed Nov 30, 2011 8:57 am

No, R-Drive Image never attempts to write something on a disk being imaged. Moreover, it locks the disk to prevent any other program to write something on the disk.

Build 4726 & corrupt volume

by Backer » Tue Nov 29, 2011 11:16 pm

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?

Top