This is always outside of the control of Macrium Reflect as the OS will report a write without any error. If data is read back with a different MD5 hash to that that was generated when the data was written, it is guaranteed to be corrupt. This guarantees that the same block of data cannot generate a different message digest (hash) value. Macrium Reflect uses the unmodified code from the reference implementation of the RSA Data Security MD5 message-digest algorithm. How does Macrium Reflect check the data integrity? The most likely suspect is your backup media - but memory and motherboard faults can also cause this issue. Quite simply, it means that data that was written to the backup or image file is not the same as is read back from the same file.Įrrors of this type are symptomatic of a computer system with a marginal hardware problem. This article explains what happens during the image verification process and how to troubleshoot problems with your system.
The vast majority of Macrium Reflect users will never encounter a single verification issue. We estimate that less than 1 in 1,000 systems have problems that lead to image file corruption. Though they do happen, verification errors are extremely rare.
0 kommentar(er)
