Rollback Rx will not take snapshot

[perstare]

I read through all the posts involving snapshots. I didn't find any mention of my problem. I've also submitted a ticket on this problem just a few minutes ago.
XP 32 bit, SP3

Rollback Rx does not take snapshots any more.
It doesn’t take scheduled snapshots.
It doesn’t take snapshots when I request that it do so.
It doesn’t take snapshots when I add a scheduled snapshot to take place in five minutes, and then I wait ten minutes to check the list of snapshots. No snapshot was taken. HOWEVER, the small popup does appear in the lower left of my screen telling me that a snapshot is being taken. Nevertheless, the snapshot doesn’t appear in the snapshot history.

This situation began when I had a crash yesterday. My computer would not boot up. I got a message that the “\windows\system32\config\system” file was corrupt but unreadable. I repeatedly used Rollback Rx to restart, using earlier and earlier restore points. I am now using the computer normally. I want to take another snapshot but I can’t. The latest snapshot is almost 24 hours old.

I have Acronis True Image on my computer, not running now. I have AVG on my computer, not running now.

I am very reluctant to reboot because I might get back to the difficulty that I had before.

Who knows what to do here? I want to take a snapshot BEFORE I try to reboot. If I have an up-to-date snapshot, I can use it to restart if I have more problems.

[pvsurfer]

Does your C-drive still has ample free-space? If so, I suggest the following:

1. Use Acronis True Image to fully backup C: (be sure to verify the backup).

2. Reboot and when you see Rollback Rx loading its subconsole press the Home key.

3. Uninstall Rollback Rx to your current/preferred snapshot.

4. Run chkdsk c: /r (you can do this using Run in the Start menu by entering cmd > ok and then entering chkdsk c: /r at the command prompt; or you can just go to My Computer | C-Drive | Properties | Tools | Error-Checking | then click both boxes and Apply).

5. Now is a good time to run a disk cleanup and disk-defrag.

6. Reinstall Rollback Rx.

Good luck,
pv

[perstare]

I am now running Acronis True Image to fully backup C:

Please tell me the function of "/r" in the CHKDSK command which you suggested. I've looked it up and I can't find it.

Many thanks.

Mike B

[pvsurfer]

Mike,

The /f switch finds and fixes errors on the designated disk.

The /r switch locates bad sectors and attempts to recover data from those sectors (moving the data to good sectors), as well as performing the functions implied by the /f switch. In essence, it's a more complete disk repair, but it does take longer to run than /f.

If you are running chkdsk by using Run > cmd, at the command prompt enter chkdsk /? and you will see all of the switch options defined.

pv

[perstare]

I will use chkdsk as you suggested.

Mike B

[perstare]

For the last 24 hours, I've been trying to correct a major crash in my computer. You helped me more than you could guess. Your last advice regarding the use of the CHKDSK command helped me to at least to go in the right direction to solve the problem.

CHKDSK took about four hours to run! BAD SIGN!

There were lists and lists of files which had indexing problems, cluster problems and on and on.
It was clear that a possibility existed that the disk itself was at fault. It is an expensive Seagate Constellation ES (st3500514ns) made for 24/7 continuous service, as in an office environment. It is 15 months old with a 5 year warranty.

I have a brand new C Drive in my computer, cloned from the old C after it had been CHKDSK-ed at least twice. Each time revealed more errors. I used Acronis Utiliites to make the clone.


At the moment, I'm trying to rebuild Favorites for Firefox, install Rollback RX (the program rejects my genuine product ID) and several other problems. When this new C drive is working right, I will run some of the Seagate diagnostics and see if I have a legitimate claim for replacement.
DON'T UNDERESTIMATE the importance of your effort to help me out and the benefit that I got from your advice. ...and thank you for replying so quickly to my question regarding the /r command.

Thank you very much!

Mike B

[pvsurfer]

Mike,

You're welcome, glad I could help. Chkdsk errors in themselves are not necessarily an indication of a bad disk, but getting increasingly more bad sectors is definitely a bad omen! I might suggest you download this free disk monitoring tool.

If you're having problems activating RBRx, contact tech support and I'm sure they will remedy that.

pv

[carfal]

Perstare (and pvsurfer), I'm not entirely convinced that the mentioned HD is bad.

Let me explain.

This sounds alot like the dreaded chkdsk problems that were plaguing Rollback v8 and early v9. In those days you would get very long "lists and lists of files which had indexing problems, cluster problems and on and on." The end result being a trashed system which require a complete format and reinstall. Search these forums and you'll find the proof.

I think that the only thing that saved perstare was the fact that Rollback was uninstalled when he ran chkdsk on his HD. Chkdsk was making repairs without the added interference of Rollback.

You might say that because Rollback was uninstalled then the errors are now "Real Errors". This is true but also false. Meaning that the errors are there only because they existed in the final snapshot that perstare chose. So they are really inherited errors from a corrupted snapshot.

Evidence of this is what you say here

Originally Posted by perstare

I repeatedly used Rollback Rx to restart, using earlier and earlier restore points.

This is a classic symptom of what happens when the snapshot table becomes corrupted from a sudden power failure or reboot. You find that each snapshot you rollback to (one step back) will either not boot or chkdsk will attempt to run and fix hundreds of errors (very bad idea). If your lucky (as in your case perstare) you find a snapshot that "works". But things are not always as they seem (as evidence of your reported chkdsk errors). Unfortunately, it looks to me that you have chosen a snapshot that is corrupted as a final system state.

You stated that you have now cloned this "damaged" HD. I personally would not trust the current system installed on the "damaged" HD. I would recover all of my important data immediately and start again from scratch on the new HD.

It may well be that i am completely wrong and probably off my rocker! The HD mentioned may actually be faulty. It is also worth mentioning that so far v9.1 seems to be very stable in respects to so called chkdsk corruptions. But one must always leave room for the possibility that Horizon havent completely stamped out this catastrophic issue and you have been unfortunate enough to reveal its still lerking in the background.

I hope you can report with absolute certainty that your HD is actually faulty so that Rollback can still hold it head up high.