Announcement

Collapse
No announcement yet.

Corruption has been reintroduced in latest version v11.2.2704515766

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

  • Corruption has been reintroduced in latest version v11.2.2704515766

    C:\WINDOWS\system32>chkdsk c:
    The type of the file system is NTFS.

    WARNING! /F parameter not specified.
    Running CHKDSK in read-only mode.

    Stage 1: Examining basic file system structure ...
    485632 file records processed.
    File verification completed.
    11474 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    2397 reparse records processed.
    Error detected in index $I30 for file 2A.
    Index entry gsdll64.dll in index $I30 of file A15A is incorrect.
    Index entry nitroui12.hlp in index $I30 of file C408 is incorrect.
    Index entry NITROU~1.HLP in index $I30 of file C408 is incorrect.
    607984 index entries processed.
    Index verification completed.

    Errors found. CHKDSK cannot continue in read-only mode.
    Press any key to continue . . .
    I installed this version about 2 weeks ago and did an immediate rollback (like the previous version test) to see if corruption occured and there was none there. I've only been on my computer a couple of times since then and took at least 25 snapshots along with some deletes but only now did another rollback with the above results.....another confidence crushing moment.

    Back to previous version I go.

    PS I saved the data files if HDS require them.

    Edit: Just remembered that i ran the validation tool about 4 days ago only on my last snapshot at the time. I had run chkdsk before doing this and no errors were reported. However the tool showed "Validated. Failed to repair.." or something to that effect and then created a new snapshot straight after it and showed "Validated". When i looked at my snapshot tree a new snapshot had been created after my Last snapshot which still showed the arrow indicating i was still in this snapshot. I ran chkdsk and it showed no errors. So i simply deleted the newly created snapshot and got on with my life until the above occurred. This may or may not have anything to do with the corruption i have now but thought it was worth mentioning.
    Last edited by carfal; 04-12-2019, 09:11 PM.

  • #2
    OK, i may have jumped the gun because a couple of days ago i did a BIOS update while RB was installed and given the sensitivity of RB and changes to partitions, I'm thinking that this may have impacted RB's drive mapping tables.

    So, I've restored a good image using Macrium and have reinstalled RB v766. Will report here again if corruption appears this time....

    Comment


    • #3
      Thanks Carfal. Also, I at least would appreciate a report after a while if corruption does not appear this time. I'm still using version 11.0, and your posts about the first build of version 11.1 saved me a lot of grief.

      Comment


      • #4
        Hi dbolotin. Just reporting back that so far no more corruptions. Must have been that BIOS update i did that affected RB....time will tell

        Also, i havent tested the new snapshot integrity utility given the weird result i described earlier on and also i havent tested deleting the baseline since on a previous version deleting the baseline resulted in a 3 fold increase in space usage for the next snapshot that became the new baseline. I havent seen any literature that HDS have addressed this so that's a "10 foot pole" scenario for me.

        As long as i can take snapshots, rollback and delete them without any corruption appearing, I'm golden.

        Comment


        • #5
          Hey Carfal,

          The snapshot integrity utility tool is still sort of in beta, but we decided to include it as part of the download package. We're monitoring it very closely to make sure the results are what we expect, and if all goes well we will include that in the main program rather than it being a separate program as it is right now.

          Comment


          • #6
            I've experienced some corruption again that only affected the last 3 snapshots that i had taken at the time. I didnt take a screen shot but chkdsk showed something like 80, "" on a couple of lines. I rolled back one snaphshot and the same error was listed. Rolled back another snapshot and 2 or 3 other corruptions were listed showing the same error. Rolling back one more time gave me a clean result so I've continued on from here, so far no more corruption. Unfortunately i didnt have time to screen shot or save data files and because the corruption only affected my last 3 snapshots i didnt worry about it.

            Below is my current snapshot tree Rollback history 2019-05-04_12-47.jpg




            The corruption stopped at "B4 DVDFab v11" snapshot and i deleted the next 3 corrupted snapshots and recreated them.

            Below is my event log entries for the above snapshots Rollback event log 2019-05-04_12-49.jpg




            Sorry but its a long list. But it gives a good picture of my activity. Unfortunately it doesnt show any defrags that have occurred eitther at boot time or manually. Rest assured that I immediately defrag everytime I create a new snapshot. I like my space reclaimed immediately.
            Last edited by carfal; 05-03-2019, 07:38 PM.

            Comment


            • #7
              Does anyone from Horizon DataSys have a response to this latest post from Carfal? It certainly makes me unwilling to install this latest build of Rollback Rx Pro.

              Comment


              • #8
                C:\WINDOWS\system32>chkdsk c:
                The type of the file system is NTFS.

                WARNING! /F parameter not specified.
                Running CHKDSK in read-only mode.

                Stage 1: Examining basic file system structure ...
                Attribute record (80, "") from file record segment A59E
                is corrupt.
                485632 file records processed.
                File verification completed.
                12441 large file records processed.

                Errors found. CHKDSK cannot continue in read-only mode.
                Press any key to continue . . .
                Well....there's no escape. There is still an intermittent corruption issue with this latest build of RB. This is the error i got before only this time it was only my 2nd (maybe 3rd) snapshot.
                Rollback history 2019-05-16_12-47.jpg
                Rollback event log 2019-05-16_12-49.jpg

                So Win updates came through and i restarted. I took the last snapshot and did a manual defrag. I ran chkdsk and corruption discovered. I rolled back to "First snapshot" and corruption gone. I have the data files from the corrupted last snapshot if HDS are interested.

                I'm going to try rolling back to the last snapshot ("After Win Upd") as a curiosity experiment to see if the corruption is there. Also keep in mind RB is NOT in space saving mode yet because i've rolled back to a snapshot and i havent taken a new snapshot yet or 7 hr havent expired as per my settings.

                Here goes nothing....
                Last edited by carfal; 05-15-2019, 07:58 PM.

                Comment


                • #9
                  Nope. no go. That snapshot is corrupted and is now gone. Win Upd reinstalled the updates and this time no corruption occurred. Go figure.

                  Below are the updates in question (or not)

                  Windows updates2019-05-16_12-24-55.jpg

                  Comment

                  Working...
                  X