since upgrading from Endpoint Backup 1.5 to Agent for Windows 2.0, backups on a Windows10 client finish with a warning about skipped bad blocks:
'One or more bad blocks were detected and skipped.'
I'm aware that 'SkipBadBlocks' is now enabled by default. When disabling skipping of bad blocks in the registry (REG_DWORD SkipBadBlocks=0) the job finshes with status 'success'
This behavior is also mentioned here:veeam-agent-for-windows-f33/crc-error-t36588-30.html
History also seems to be similar to the post above: the system having the issue was recovered from a defective SSD (indeed having bad blocks) to a brand new one using another backup/restore tool. Manual scans on the new disk (chkdsk, hddscan, ...) do not indicate any error condition on the replacement SSD. Also no mention of bad blocks in windows event log.
Is there some state beeing preserved by Veeam Agent for 'historic' occurences of bad blocks?