+x

 

JK - 5 January 2022 9:53 PM

Is your Samsung_T1 drive connected by USB?  Are you using a USB hub?  

You should review the KnowledgeBase article I had linked above (and follow the troubleshooting advice given there), but frequently, the cause of these types of problem is a bad USB connection.

Alternatively, if the "Index Load Error" message as shown in the log created by your German-language installation is in fact the same thing as the "Index Load Failed" message that is described in this article, then the problem may be caused by antivirus or similar security software.

Yes. I chance nothing. T1 connected by USB Hub. Security Software is Kaspersky. It worked fine. Since to weeks its the problem i posted.

Even if your configuration has not changed, hardware failures can occur over time.  If the culprit is third-party software, a bad software update can cause problems suddenly.

Does the error now happen consistently every time you attempt to backup, or is it intermittent?  If the error is reasonably consistent, then you can do some troubleshooting to find the source of the error.

Do you have access to another computer?  If so, you could try attaching the Samsung_T1 to the other computer, and performing a manual verification of the 1F2855D69B6CAD6F-00-00.mrimg file; if the other computer does not have Reflect, then you can install the free version of Reflect, or try booting from USB Rescue Media.  Having another computer will also allow you to do some additional testing, as recommended in the KnowledgeBase article on verification failures.

                                

One more thing... If you're creating new images for testing/troubleshooting purposes, I recommend creating a new destination folder, or (temporarily) modifying your retention rules.  According to your log, your current destination folder (F:\MacriumReflect\) already contains 3 full backups, and your retention policy specifies deletion rules that will delete the oldest of the 3 backup sets each time that you create a new full.  Since the Full Backups you that you have been creating recently are not verified (and thus presumably corrupt), you will be deleting any older non-corrupted backups if you keep backing up to the same destination folder.  It may already be too late (i.e., because this problem has been occurring for 2 weeks, you may have already deleted all of your useable backup images from that folder).  If you do not have any good backup images (i.e., images that can be successfully verified) stored in other locations, you should make it a high priority to create at least one good backup before continuing to troubleshoot the issue.  For best chance of success, use a different destination drive (not the Samsung_T1), connected directly to the computer (not via a USB hub), and create the image from the Reflect Rescue Environment.

                                

Well, i check the backups and Macrium says everything is ok.
Then i started the planned xml file manual. Everything works fine. The Backup is complete and the verification is ok.
Today the problem again with the planned backup. Verification failed.
I have also checked the T1 SSD with chkdsk. No error.
I use Kaspersky Internet Security on all mine laptops. And i use there planned schedule with Macrium. No errors.
Do you have other solutions ? Thx.

If you have a specific backup file that passed verification successfully when it was first created, then try manually verifying it later on, which you can do from the Existing Backups tab in Reflect.  See if the exact same file delivers different verification results on different test runs.  If you see inconsistent verification results, then you'll need to start isolating variables.  For example, try another USB cable.  Try connecting that disk to another PC that has Reflect (even Reflect Free is fine) and verify that same backup file on another PC to see if you get consistent results.  If you find that the same file reliably verifies the same way on a different PC but goes back and forth on your PC even after changing the USB cable, then the most likely culprit is probably a RAM module in your system.  One user here found that their CPU was the problem.  He had a system and two CPUs, and he consistently found that verification failed with one CPU and passed with another CPU, even though nothing else about the test was changing.

The solution is to go through a systematic process of elimination to narrow down the source of the problem.  In an earlier response, I pointed you to a KnowledgeBase article about verification errors, which contains recommended troubleshooting steps that eliminate or confirm possible sources of the error.  JP's post above also proposes a process that you could follow to identify the source of the issue.  It doesn't seem that you have attempted to follow the recommended troubleshooting steps yet, so that might be the best thing to do next.