W00T!
Let's hope you come back.
Well that was fun ---- NOT!
All the patches went through without a hitch, as did all the clean-up work afterwards. It was the Macrium backups where I hit an issue.
Eight out of the nine were trouble free. But for one of my machines the Reflect backup failed on a CRC error reading from the C: drive, an Intel 256GB SSD
Fortunately it was one of my '
second league' machines, so nothing too vital.
Now I know I could have told Macrium to ignore bad sectors, but then I wouldn't be able to trust the image. HD Sentinel reported one bad sector found in its surface scan. I ran Chkdsk /f /r and that just made things worse. Now Reflect wouldn't even start the backup, it failed on verifying the C: drive saying that the MFT was corrupt. I had to run Chkdsk again to fix that.
By now I had identified which file was affected, it was a .vhdx for one of the Hyper-V VM's on this machine. Chkdsk's 'repair' of this file had truncated it and the VM now could no longer start up. Well, this VM hadn't been run in the last month, surely I could just replace its vhdx with the one from last month's image? No, now the VM wouldn't start due to permissions issues.
Restoring just this one VM from last month's Reflect image got
really convoluted. In the end I had to run last month's image as a VM using viBoot, then in this VM run Hyper-V Manager and export the VM I wanted to save. Then on the Host machine I deleted the bad VM and its virtual disks, then imported its good copy that I had just exported from within its own Macrium image while running as a VM. (I told you it was convoluted
)
Finally! I had a fully functional machine with an SSD that has one newly reallocated sector, and that HD Sentinel's surface scan now passed as being clean.
And most importantly of all, one that Macrium was finally happy to back up.
