Announcement

Collapse
No announcement yet.

Fixing MBR messed up RBRX

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Fixing MBR messed up RBRX

    I had a problem with corrupt MBR. I tried to restore RBRX snapshot of previous two days, but Windows still did not boot up. Fixed the MBR using Windows installation disc. Now Rollback is not running cannot reinstall it, it gives error that RBRX is already installed. I read about Snapshot Scavenger tool, how can I get that?

    Thanks

  • #2
    You should stop running that System AS SOON AS POSSIBLE if you hope to have any chance of getting any of your snapshot DATA back. Even if HDS supplies you with the Snapshot Scavenger (which I doubt), your chance of getting anything useful back will most likely be minimal...

    You'll definitely need to work with HDS Support if you hope to get any of your snapshot DATA back.
    Last edited by Froggie; 05-14-2018, 05:38 AM.

    Comment


    • #3
      Your original "corrupt MBR" was most likely not corrupt at all. Whatever detected that condition was not aware of Rollback's special MBR configuration. Once you re-wrote your MBR, Rollback was history... and most likely your snapshot DATA saved ever since you created your baseline.

      Best of luck with this one...

      Comment


      • #4
        Thanks Froggie. Windows was not booting up and showing that no OS present on the disk. It gave an option to repair and that process was followed. But before i did that, I had restored the RBRX snapshots twice for the two previous days, when the system did boot up and was working. When the restoring of these snapshots did not work, I repaired the MBR using Windows installation disk.

        Was there any other option? other than repairing MBR given that the older RBRX snapshots were also not making Windows boot up?

        Just a thought - Most software like this does not put the data at risk of losing due to software scenarios like uninstalling, boot corruption etc. And if RBRX is supposed to be used with a disk cloner, just dont sell them seperately!!

        Thanks





        Comment


        • #5
          rkheria ... as far as the problem you have described, if you really wanted to get that System BOOTable once again, you took the only action that could have done it, replaced the MBR with the "standard" Windows MBR which the repair action you chose, did. I'm not sure what state your System is in... it'll either be the CURRENT STATE at the time of the problem or your original BASELINE STATE when you installed Rollback... hopefully it was the former.

          HDS sells a "companion" product called "Drive Cloner RX" which is capable of imaging a Rollback-embedded System, including its snapshots. That application is supposed to protect your System against what happened to you as well as any hardware failure which affects your System and its snapshots. I have no idea what state that application is in. I was part of the BETA team that tried to exhaustively test that version of Drive Cloner (v6), and as far as I was concerned, that BETA was a disaster and its unscheduled conclusion hoisted upon a user base was very questionable at best (its a long story and I choose not to get into it at this time). And of course HDS Marketing would sell them separately... it's called a revenue stream . Of course your original problem should never have happened to begin with, but with Rollback RX, strange things happen occasionally.

          If you think that Rollback RX absolutely needs to be on your System (there are slightly slower alternatives) due to its speed, I would consider TRIALing Drive Cloner to find out if it really meets your needs as far as System protection is concerned. And read through that product's Forum first to try and see what state it's currently in.

          Comment


          • #6
            Hello Froggie. I'm pleased to see a candid view about Cloner. Rollback has been essential for a number of years, working perfectly. However, now the major Windows Updates need to have Rollback uninstalled, currently 1803. I've paused updates for a month until I figure out what to do. Cloner seemed to be a perfect solution, since I could save my snapshots. But my first attempt with Cloner already has a "known issue" (as the support team said) -- "GetProtectedDiskPartInfo is false." No solution date is estimated. Do you have any advice? Should I just uninstall Rollback and trust?

            Comment


            • #7
              davidgeo -- I'm not proficient like Froggie is, but for what it's worth: Drive Cloner 6 didn't work for me, and so what I do is uninstall RollbackRx every month and then clone my disk with Acronis True Image (or I might have used Macrium Reflect). Then I reinstall RollbackRx. It's not that difficult, and it makes me feel a lot safer to know that I have relatively recent backups on an external hard drive. In fact, I once had to resort to this external backup (because of the one and only RollbackRx MBR problem I ever had over many years), and it worked.

              Comment


              • #8
                dbolotin -- thanks for adding your thoughts. I've always done Macrium Reflect with Rollback still active, so your method makes me re-think that. It's probably safer to restore a backup that isn't attempting to re-create the Rollback special installation. But I'm curious why you do it every month, without apparent regard to Windows Update. For major Windows Updates, I'm thinking a best practice would be, with Win Update paused -- #1. full Macrium Reflect (in case the next step has a problem) #2. uninstall Rollback #3. full Macrium Reflect (this would be the main one) #4. defrag the hard drive (since that can't be done while Rollback is active) #5. unpause and start Windows Update #6. test for system functioning #7. reinstall Rollback #8. run CCleaner. None of that needs Cloner (I should probably ask for my money back, since it doesn't work and doesn't have a fix). The eight steps seems excessive, but I lost a huge amount of time trying to get the Creators Update to work and I don't want a repeat of that frustration.

                Comment


                • #9
                  david geo -- I uninstall Rollback Rx every month because I don't want to attempt my monthly disk cloning with it installed. It CAN be done, but to restore a clone that was imaged with Rollback Rx installed requires a tricky "Fix MBR" procedure -- in order to boot up the restored image -- which makes me uncomfortable. And even assuming that you have done that successfully, Rollback Rx won't work, so you have to uninstall it and then reinstall it. (The procedure for fixing the MBR is given here: http://support.horizondatasys.com/Tr...er/Step/View/5. Note that you need a USB/CD/DVD with the appropriate windows installation media. And the reason you have to use this procedure is given in Froggie's post near the top of the following page: http://community.horizondatasys.com/...quick-question). Otherwise, I do pretty much the same things, and in the same order, as you. Good luck in getting your money back for Drive Cloner 6.0.

                  Comment


                  • #10
                    Greetings all! Sorry for the absence (just back from 10-days in the EU).

                    davidgeo, since you're willing to live with the loss of your snapshots during these "questionable" Windows updates, the best approach is to uInstall Rollback (or deActivate it if using the latest v10.7 version), reBOOT your System (this must be done to eliminate the Rollback TRIM problem driver as well as the non-Standard WIndows Master BOOT Record <MBR>), then image "used" or "active" sectors depending on what imager you use. Following this process, do your System maintenance (defrag, etc.) functions followed by your Windows update/upgrade outstanding options. When complete, reInstall (or reActivate) Rollback and you should be fairly protected. The new deActivate function will remove all Rollback database dependencies from your System and leave the basic code intact... which does nothing until it is reActivated once again. This just saves a reInstall function and keeps your original SETTINGs in tact. When the reActivation occurs, a reBOOT is required during which time the special, non-Standard Rollback MBR as well as the TRIM deprived special Rollback disk driver are reInstalled and a new Baseline snapshot is formed just like when Rollback is initially installed.

                    Since you're already using Macrium Reflect as your imaging System, if using Reflect v7 you may consider using that System to basically "snapshot" your System. This is easily done using their CBT (Changed Block Tracker) option when installing and taking required Incremental "snapshots" (images) when you need System states to fall back on. With CBT in place, the Incremental imaging and restoration processes is minimal and only slightly slower than Rollback when returning to recent snapshots. At the same time you have the System protection you need against software, malware and failing hardware events that you really need to protect your System. Unless you need the absolute speed of Rollback's ability to return to any snapshot, this process works very well.

                    If you wish to consider this approach, feel free to contact me via the Private Message system of this form and I'll be happy to assist you in understanding how the whole thing works.
                    Last edited by Froggie; 06-09-2018, 03:46 PM.

                    Comment


                    • #11
                      Thanks so much for your generous advice, Froggie. You've explained it clearly and I'll try the alternate method with Reflect -- but I would use only Full Backup rather than Incremental or Differential. Having the image managed by the program over a period of time seems to invite possible complications (this hesitation is reinforced by https://knowledgebase.macrium.com/di...al+Image+Files), but a full backup needs only more patience and increasingly cheaper external storage media.
                      Last edited by davidgeo; 06-10-2018, 06:09 AM.

                      Comment


                      • #12
                        davidgeo, your reference to problem Incrementals above was a one time issue associated with Macrium's regression testing for the two versions involved with that problem... it's not a general problem of any kind with a good imaging product. I have been using Macrium's product since February 2015 (when they released their RAPID DELTA RESTORE <RDR> feature) and the product has been flawless when using any sort of image type. I don't just use it for images between updates, etc... I use it to snapshot my System as well just like Rollback.

                        Comment

                        Working...
                        X