jeffpflueger Posted April 29, 2008 Report Share Posted April 29, 2008 OK. It has been almost two months now that I have been trying to resolve this issue. It started with an error that would crash retospect everytime a Catalog file for a particular backup set was read. I reinstalled Retrospect several times, I deleted the configuration files to have them rebuilt, I rebuilt the catalog file several times (days to do this btw) Finally, I was forced to delete my entire backup set and rebuilt the actual backup set. Now, retrospect no longer crashes when it tries to acess the catalog file for the backup set. Now, I get this error for each volume in the backup set as it tries to back them up: error -641 (chunk checksum didn't match) and then the backup quits. What to do now? Rebuild the catalog file from this backup set? Again? Thanks for any help, Jeff Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2008 Report Share Posted April 29, 2008 What else does the log say, it should have added detail you did not include. What version of Retrospect? What operating system version? Quote Link to comment Share on other sites More sharing options...
jeffpflueger Posted April 29, 2008 Author Report Share Posted April 29, 2008 (edited) retrospect version 7.5.508 Windows XP Here are some entries from the log: ######## Repair Catalog -> Update Existing Catalog File: ##### log: + Executing Recatalog at 4/29/2008 4:14 PM To Backup Set ReadyNAS_NV... 4/29/2008 4:14:26 PM: Execution completed successfully ######## Tools -> Verify Media ######## + Executing Verify at 4/29/2008 4:16 PM To Backup Set ReadyNAS_NV... Can't load source session tree for 4/25/2008 5:15 PM, error -641 (chunk checksum didn't match) 4/29/2008 4:16:36 PM: Execution incomplete Remaining: 421424 files, 875.4 GB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 00:00:01 (00:00:01 idle/loading/preparing) ##### Running the script I have to backup my computers: ##### + Normal backup using Backup_Photo_Media_to_NAS at 4/28/2008 5:50 PM To Backup Set ReadyNAS_NV... * Resolved container My Computer container to 2 volumes: 1TB Drive (C:) WindowsXP (E:) - 4/28/2008 5:50:03 PM: Copying 1TB Drive (C:) Trouble matching 1TB Drive (C:) to ReadyNAS_NV, error -641 (chunk checksum didn't match) - 4/28/2008 5:57:37 PM: Copying WindowsXP (E:) Trouble matching WindowsXP (E:) to ReadyNAS_NV, error -641 (chunk checksum didn't match) 4/28/2008 6:00:25 PM: Connected to Ebullient * Resolved container Ebullient to 1 volumes: Local Disk (C:) on Ebullient - 4/28/2008 6:00:25 PM: Copying Local Disk (C:) on Ebullient Trouble matching Local Disk (C:) on Ebullient to ReadyNAS_NV, error -641 (chunk checksum didn't match) 4/28/2008 6:08:24 PM: Connected to grey-pc * Resolved container grey-pc to 1 volumes: Backup HDD 250 (C:) on grey-pc - 4/28/2008 6:08:24 PM: Copying Backup HDD 250 (C:) on grey-pc Trouble matching Backup HDD 250 (C:) on grey-pc to ReadyNAS_NV, error -641 (chunk checksum didn't match) Can't access backup client NettiesLaptop, error -530 (backup client not found) 4/28/2008 6:12:07 PM: Execution incomplete Total duration: 00:21:43 (00:21:40 idle/loading/preparing) ###### everywhere, it is the "error -641 (chunk checksum didn't match)" error.... Any ideas? Edited April 29, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
jeffpflueger Posted May 2, 2008 Author Report Share Posted May 2, 2008 OK. I did the recatalog of the newly created backup set. During the 80 hour recatalog process, I got 86 errors of this sort: Generated MD5 digest for file "C:\Jeff's Work\Images\from_laptop\2006_04_11\_MG_9126.CR2" does not match stored MD5 digest. But the recatalog completed. Now trying to backup. We'll see what errors it throws. Any ideas about what is going on? Quote Link to comment Share on other sites More sharing options...
jeffpflueger Posted May 2, 2008 Author Report Share Posted May 2, 2008 Ok - so I have now done a backup after the recatalog with 86 errors and I get this message again: Can't compress Catalog file error -641 (chunk checksum didn't match) when I look into the log here is what it looks like: - 5/2/2008 9:28:06 AM: Copying Backup HDD 250 (C:) on grey-pc Trouble matching Backup HDD 250 (C:) on grey-pc to ReadyNAS_NV, error -641 (chunk checksum didn't match) Can't access backup client NettiesLaptop, error -530 (backup client not found) Can't compress Catalog File for Backup Set ReadyNAS_NV, error -641 (chunk checksum didn't match) 5/2/2008 9:32:30 AM: Execution incomplete Total performance: 385.3 MB/minute with 20% compression Total duration: 00:52:08 (00:39:21 idle/loading/preparing) So thinking that there was just a problem with "grey pc" I forgot it as a backup client and tried to backup again. Again, the same error. and this time the checksum error just moved up the list: - 5/2/2008 9:53:54 AM: Copying Local Disk (C:) on Ebullient Trouble matching Local Disk (C:) on Ebullient to ReadyNAS_NV, error -641 (chunk checksum didn't match) Can't access backup client NettiesLaptop, error -530 (backup client not found) Can't compress Catalog File for Backup Set ReadyNAS_NV, error -641 (chunk checksum didn't match) 5/2/2008 10:04:55 AM: Execution incomplete Total duration: 00:23:46 (00:23:45 idle/loading/preparing) It used to say the problem matching error for every backup client. Now, just the one at the end of the list. What is going on? Thanks for any help Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 2, 2008 Report Share Posted May 2, 2008 What is the location of the catalog file? Try rebuilding with the catalog on a different disk. When you get errors during a catalog rebuild, then the catalog rebuild was not successful. Quote Link to comment Share on other sites More sharing options...
jeffpflueger Posted May 2, 2008 Author Report Share Posted May 2, 2008 doesn't this error during the catalog rebuild indicate a problem with the backup files themselves and not the catalog file? Generated MD5 digest for file "C:\Jeff's Work\Images\from_laptop\2006_04_11\_MG_9126.CR2" does not match stored MD5 digest. The catalog file exists on a local hdd C:\My Documents\Retrospect Catalog Files why would I put the catalog elsewhere? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 2, 2008 Report Share Posted May 2, 2008 The catalog keeps getting corrupted. You should put the catalog file on a different disk during your next rebuild attempt (or try another computer) to see if the same problem happens. If the C disk has a problem, then the catalog file could get corrupted during every rebuild attempt. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.