Operational Defect Database
BugZero found this defect 2554 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2295
One or more bad blocks were detected and skipped
Last update date:
12/6/2021
Affected products:
Veeam Agent for Microsoft Windows
Affected releases:
2.2
Fixed releases:
No fixed releases provided.
Description:
Challenge
Veeam Agent for Microsoft Windows displays the following warning during the backup:
Cause
During a backup using Veeam Agent for Microsoft Windows, each block is read. If a block is not readable (i.e., corrupted), Veeam Agent will skip that block and throw a warning message. Unreadable blocks on the disk may indicate that the disk is unhealthy, and replacement may be required. The NTFS file system stores information about bad blocks in a $BadClus metadata file. More information about NTFS file system metadata can be found here.Note: The $BadClus metadata file is backed up by Veeam Agent for Microsoft Windows. If a bare-metal restore is performed to a new drive, the $BadClus metadata is restored. To update the $BadClus metadata file, run the command shown in the solution section of this article.
Solution
The following command will clear the list of bad clusters on the volume specified and rescans all allocated and free clusters for errors. Execute this command on the machine that was being backed up. Specifying the volume for which the warning occurred (e.g., C: )
