I already have that in mind, the problem is chkdsk is designed to be run interactively, and I wouldnt consider it good enough, I have had instances where chkdsk /r passed but then macrium still couldnt read the backup (either by restore or verification). Macrium itself seems able to pick up unreadable data more.
To make chkdsk workable I would need to write a script that either spits out the output somewhere, maybe a text file or something, or to have it generate an alert if a read error occurs. I would prefer a built in feature.
But is sad to hear that Macrium gets feature locked so early
I will work on a chkdsk (or maybe other 3rd party solution), as after my recent problems of unreadable backups I feel I need some kind of reliable bitrot detection. I may actually now setup a LAN based ZFS storage system and have all my backups go to that given that ZFS handles the problem natively.
The problem with the ZFS idea, is it adds hassle if I need to access the backups from winPE Macrium.
Also the command line options looks a good bet, thats certainly better than the chkdsk idea. Thanks
I will also repost this on the v8 wishlist after release as well.