currupted my hard drive

I think Rollback RX currupted my harddrive. I have had it installed and running fine for a month. All I was doing was updating my baseline. It had me reboot and was moving data and was at 95% when it had some kind of sector error and stopped. I had to reset the computer. It started back up and got to 98% moving the data when it said "not enough space for sytem". It then restarted and now I get the error message "Error loading operating system". I do not get the Rollback start up screen. It goes right from the Bios screen to the "Error loading operating system". Anyone know of way to fix this or get to the data. Would fixmbr or fixboot work? What about an NTFS hard drive recovery utility? I have used it on another hard drive and it was able to repair the directory structure. This is critical and any help would be greatly apprecitated.

Ken

[Baldrick]

Hi Ken

Apologies for not responding sooner and the fact that I am not technical enough to help personally but, in case you have not done so already, did you try logging a Support Ticket at the main HDS website. They may not be the fastest to respond but they may have some knowledge of this and be able to adise on a recovery procedure...if still in the pickle it may be worth a try.

[Nick10]

Originally Posted by Ken Hines

I think Rollback RX currupted my harddrive. I have had it installed and running fine for a month. All I was doing was updating my baseline. It had me reboot and was moving data and was at 95% when it had some kind of sector error and stopped. I had to reset the computer. It started back up and got to 98% moving the data when it said "not enough space for sytem".
Ken

Ken,

We would like to see what the issues is... Did you already log a support ticket at http://support.horizondatasys.com ? If you have your support ticket number, let me know so that I can try to escalate the issue, if it still remains.

Hello,

I have resolved this issue on my own. .

After 2 weeks of my hard drive being corrupted, I was able to purchase some software that first let me take an image of the hard drive and recovered my data from this image. After I was sure I had my data, I let it scan my hard drive to see if it could fix it. It found that your software currupted the MBR. The software was able to restore the MBR and I was able to reboot to the drive with everything intact.

I have been using the restored drive minus your software for 2 weeks now without any issue.

The bottom line is that your software cannot be trusted and I will no longer rely on it to protect me and I will not recommend it for others to use.

I am a computer programmer for an insurance company and rely on this computer for my work. This has been very stessful and I think un-necessary. When you purchase software to protect your valuable data on your hard drive, it should never leave you in a state like this. It should have let me at least restore to the last snapshot. If I have to purchase an imaging backup software to protect me from your product, then I might as well just use the other product.

Ken.

[HDS-Stormy]

Originally Posted by Ken Hines

Hello,

I have resolved this issue on my own. .

After 2 weeks of my hard drive being corrupted, I was able to purchase some software that first let me take an image of the hard drive and recovered my data from this image. After I was sure I had my data, I let it scan my hard drive to see if it could fix it. It found that your software currupted the MBR. The software was able to restore the MBR and I was able to reboot to the drive with everything intact.

I have been using the restored drive minus your software for 2 weeks now without any issue.

The bottom line is that your software cannot be trusted and I will no longer rely on it to protect me and I will not recommend it for others to use.

I am a computer programmer for an insurance company and rely on this computer for my work. This has been very stessful and I think un-necessary. When you purchase software to protect your valuable data on your hard drive, it should never leave you in a state like this. It should have let me at least restore to the last snapshot. If I have to purchase an imaging backup software to protect me from your product, then I might as well just use the other product.

Ken.

Ken,

I'm going to pass this on and hopefully have a response for you today.

Maxxy

[HDSjames]

Originally Posted by Ken Hines

Hello,
It found that your software currupted the MBR.
Ken.

Part of the install is a replacement bootloader. This allows for restoration if you wipe out the files in the root of the drive or your Windows directory (making it non-bootable) from a Snapshot. There should be a Rollback Rx screen when booting that says "Press the HOME key to restore from a snapshot" before it starts loading Windows.

Hello,

This is from my orginal post:

It then restarted and now I get the error message "Error loading operating system". I do not get the Rollback start up screen. It goes right from the Bios screen to the "Error loading operating system".

As you can see, the Rollback start up screen never came back after the error. The bootable piece you are talking about is in the MBR that it corrupted.

Hello,

Please see my prior post to this one. I think after I had too reset it the first time when it had an error at the 95% mark and rebooted, that screen did come up. The problem was though that I was in the middle of a baseline update and didn't know what to do at that point. I thought everything was still ok and after it showed the boot screen it went right back into moving the data for the baseline update. The percentage went from 95% to 98% when it had the error "not enough space for sytem". At that point, it restarted my system for me and the boot screen did not come back nor would the system boot at that time.

[Nick10]

Originally Posted by Ken Hines

... I think after I had too reset it the first time when it had an error at the 95% mark and rebooted, that screen did come up. The problem was though that I was in the middle of a baseline update and didn't know what to do at that point...

I have asked the technician that was working on your case.. He believes that your issues is caused by bad sectors on your hard drive. As you reported in the initial problem report “It had me reboot and was moving data and was at 95% when it had some kind of sector error and stopped. I had to reset the computer.”…

the Techs believe that, unfortunately, the bad sectors were being used by the snapshot tables that’s being updated during the update baseline process... The chance of this happening is very rare but theoretically it could happen. In this instance the new snapshot table (created by update baseline) would be incomplete and cause the problem that you've experienced.