I recently also stumbled over the image corruption problem of Macrium v7 after using it for years without problems. I wanted to share my experience (excluding names) on the topic with you and others:
I wrote the following message to the Macrium support:
"Dear Sir or Madam,
recently I wanted to restore two SSD drives using Macrium Reflect v7 Home images. This images were verified by Macrium Reflect directly after the creation in July 2021.
I booted using a Macrium Reflect rescue media (USB key) and started the recovery including an initial verification of the image on the external 4 TB HDD. The program reported "Data verification failed - Block 918433, File offset 19314185248". I am using Macrium Reflect for several years now and restored images quite regularly, but never came across such error. Here are my attempt to analyze the problem:
a) verified the images in Windows (Macrium Reflect v7 Home) - same error
b) verified the images on my Laptop (Macrium Reflect v8 free) - same error
c) exchanged the USB-cable of the external 4 TB HDD - same error
d) 12 hour 55 min chkdsk-analysis of external 4 TB HDD - no HDD error
e) a copy of the images stored on an 8 TB HDD 200 kilometer away showed the exact same error
--> despite my best efforts I don't have a trustworthy backup and I am lucky that the recovery was intended to solve only a minor problem
f) I created new verified images of the SSDs on a different 4 TB HDD and successfully verified the images again on my Laptop with Macrium Reflect v8. Now I copied the files to the 8 TB HDD. The verification of the 50 GB image worked, the verification of the 160 GB image returned the following error "Data verification failed - Block 14501, File offset 2805463152". I verified the images on the 4 TB HDD again with no error. Thus, the copy process might have affected the 160 GB image. So I used TeraCopy (compares hashes of source and target files) to successfully create a verified copy of the image from the 4 TB HDD on the 8 TB HDD. However, the image verification returned an data verification failed error for the 160 GB image on the 8TB HDD again.
I will now run a chkdsk analysis of the 8 TB external HDD and retry the copy and verify attempt. I have not much hope, as the drive is new, the chkdsk analysis was done right after buying the drive and the verification error occurred on an error free 4 TB HDD already. I suspect that Macrium Reflect v7 and v8 have a problem with the verification.
I hope you can help me, as in the moment I am aware that I can't trust my beloved backup solution.
I received the following reply from the Macrium support:
Thank you for contacting us.
If the image was corrupted on the 4TB drive, moving it to a new location will not change the outcome of the verification.
Verification failure means that your image file is corrupt and either cannot be read back reliably or was corrupted as it was written(the latter is unlikely as the image was originally verified successfully).
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:https://knowledgebase.macrium.com/display/KNOW80/Understanding+Image+Verification+Failures
We recommend performing stress tests on the hardware to try and identify the issue, tools such as memtest86 will help with this process.
Another additional 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/
I am afraid that the license on your account is out of support.
Macrium Reflect v7 Home Edition includes 12 months of free Technical Support and I'm afraid your support time has run out.
Support Forum access and Minor updates (i.e. v7.0 to v7.3) will be perpetual for the life of version 7.
If you have any further queries you can direct them to our forum at https://forum.macrium.com
Macrium Support Team"
This is my answer to the message from the Macrium support:
thanks for replying to my request for help despite the support for my license ran out.
You mentioned that I wanted to move a corrupt image to a new location expecting a different outcome of the verification. Could you please point out the paragraph you are referring to?
I found it interesting that you excluded software related issues several times and pointed to the backup disk, USB, or RAM. At no point you discussed my thorough analysis (hard disk analysis, cable exchange, different PCs to verify the images).
You mentioned I should analyze my hardware. This is exactly what I did before I ran into the Macrium Reflect verification problem. To reduce the complexity, I did not mention that I wanted to restore my backup because I wanted to get rid of the tool clutter from a recent RAM upgrade (no manual overclocking, CPU Intel Spec, RAM XMP).
The (verified on creation) backup I wanted to use was made months before the RAM exchange. After the RAM upgrade I spent a week testing my PC with Karhu, HCI Memtest, Memtest86, Windows Memory Diagnostics, Prime95, Aida64 and other tools. After I was convinced of having a stable, reliable PC, I wanted to use my backup, which was corrupt being the cause of this help request. I also wrote that I created a new backup (on the torture tested PC) onto a different external hard drive with successful verification. After copying it to a third external disk (without and with TeraCopy), the image verification came up with errors. The image on the source drive was successfully verified for four times (before and after copying).
Here you mentioned ExactFile to check for failing hardware. This was already done, as mentioned in my first e-mail. TeraCopy creates a hash of the source file and compares it with the written file. TeraCopy confirmed that an exact copy was written. Now, how can Macrium Reflect 7 successfully verify the file on one disk and after creating an identical copy on another drive find the image is corrupt?
All that leaves not much space for a general "hardware is the fault" diagnosis. I think the software should be at least considered, which is supported by the fact that this verification error doesn't occur with EaseUS Todo Backup Home Lifetime License I now bought.
This ticket has been Closed 19 days ago by the Macrium support. Please find below a picture showing the successful EaseUS Todo Backup verification of Images on an external HDD also after copying the images to another external drive. Everybody who read to this point: I appreciate your time!