There are 1 replies, with the last one on November 22 2013 at 08:37:32 by C.Bamford
Quote:
Hi,
Thanks for posting and welcome to the forums.
Verification failure means that your image file is corrupt and either cannot be read back reliably or was corrupted as it was written. Reflect uses the unmodified code from the reference implementation of the RSA Data Security MD5 message-digest algorithm. This guarantees that the same block of data cannot generate a different hash value. 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 is always due to unreliable hardware. It could be a problem with your backup disk, your USB subsystem or even your RAM.
Image verification issues can nearly always be put down to failing hardware. Please see the following KB article for more information:
http://kb.macrium.com/KnowledgebaseArticle50048.aspx
An example hardware test is to isolate a multi gigabyte file (similar in size to a resulting image file) run the ExactFile utility to generate an MD5 hash, copy the file to the same target disk where images or backups will be created and run ExactFile on that resulting, copied file to get another MD5 hash which can be compared with the original. If these MD5 hash values do not match then this is an indication of failing hardware.
You can download ExactFile from here: http://www.exactfile.com/downloads/
Step by step instructions can be found here: http://updates.macrium.com/reflect/utilities/exactfile.pdf
I hope this helps.
Kind regards.
Chris - Macrium Support
Quote:
Hi,
Thanks for posting and welcome to the forums.
Verification failure means that your image file is corrupt and either cannot be read back reliably or was corrupted as it was written. Reflect uses the unmodified code from the reference implementation of the RSA Data Security MD5 message-digest algorithm. This guarantees that the same block of data cannot generate a different hash value. 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 is always due to unreliable hardware. It could be a problem with your backup disk, your USB subsystem or even your RAM.
Image verification issues can nearly always be put down to failing hardware. Please see the following KB article for more information:
http://kb.macrium.com/KnowledgebaseArticle50048.aspx
An example hardware test is to isolate a multi gigabyte file (similar in size to a resulting image file) run the ExactFile utility to generate an MD5 hash, copy the file to the same target disk where images or backups will be created and run ExactFile on that resulting, copied file to get another MD5 hash which can be compared with the original. If these MD5 hash values do not match then this is an indication of failing hardware.
You can download ExactFile from here: http://www.exactfile.com/downloads/
Step by step instructions can be found here: http://updates.macrium.com/reflect/utilities/exactfile.pdf
I hope this helps.
Kind regards.
Chris - Macrium Support