I’ve been running into issues with my SSD, mainly being unable to make a shadow copy of it (using Veeam Agent).

Just noticed that when Veeam fails, I get a bunch of errors in Windows event log saying : \Device\Harddisk4\DR4 has a bad block

But earlier, I figured bad blocks might be the issue and already ran a full chkdsk /f /r /x on the disk, but it didn’t find any bad block.

Is there another way to find these bad blocks?

  • hobbyhacker@alien.topBEnglish
    1·
    1 year ago

    you can run a full read scan with HD Sentinel, Victoria, or anything else you like. That will read each sector and also show which file is at that sector. Anyway, on SSD everything works magically different, so expect some surprises.

    • DiNoMC@alien.topOPBEnglish
      1·
      1 year ago

      That did it! (I found out about Victoria SSD/HDD earlier today)

      Doing a full scan with Victoria it found just 13 bad sectors, that was enough to make Veeam fail surprisingly. Dunno why chkdsk couldn’t find them.

      It was a bit finicky getting Victoria to remap the sectors on Windows 11 and on a SSD, but I eventually got it. Then I ran chkdsk again and it said it found an error and “fixed the filesystem.”

      Now I just ran Veeam again and it finally succeeded :)

      • hobbyhacker@alien.topBEnglish
        1·
        1 year ago

        cool. looks like it was a “real” error then. For me there are random disappearing errors from time to time, that’s why I wrote about surprises. Needs some learning, but Victoria is pretty good for fiddling with these errors after you finally understand what it does.