Jump to content

jeffpflueger

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jeffpflueger

  • Rank
    Newbie
  1. jeffpflueger

    error -641 (chunk checksum didn't match)

    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?
  2. jeffpflueger

    error -641 (chunk checksum didn't match)

    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
  3. jeffpflueger

    error -641 (chunk checksum didn't match)

    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?
  4. retrospect version 7.5.508 Windows XP 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, updated as many times as well. 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 (a readyNAS NV+). I checked the filesystem and integrity of NAS - with no problems Now, retrospect no longer crashes when it tries to access 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? Here are some entries from the log to provide full details: ######## 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?
  5. jeffpflueger

    error -641 (chunk checksum didn't match)

    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?
  6. 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
  7. jeffpflueger

    Assertion failure at “elem.cpp-1000″ in Retrospect

    Still I have no resolution on this issue. I get the error above no matter what I do. I have rebuilt the Catalog file (again) a two day process - and.... When I rebuild the catalog file from the backup set, I get this error: "Can't compress Catalog file for Backup Set Backup Set A, error -641 (chunk checksum didn't match)
  8. This error is killing me. It comes up everytime I try to execute a script, even when I try to repair a catalog file. Then Retrospect closes. As a consequence I have been unable to backup for nearly a month. I am using Retrospect 7.5.508 with hotfix 7.5.13.100. I am running it on windows XP. Here is what I have done: Uninstalled and reinstalled retropect several times, updating all the way to the most current. No luck Rebuilt the entire catalog file from the backup set. 3 days later, no luck Deleted Config75.dat and Config75.bak to start from scratch. No luck. I get the error the instant I try to read the catalog file. Copied Config75.bak to Config.dat. No luck here either. Whatever I do, once I read the Catalog file for my backup set I get this error: Assertion failure at “elem.cpp-1000″ in Retrospect Even after I've rebuilt the entire catalog file from my backup set....Is the backup set corrupted? If so, How do I fix? Thanks for any help or wisdom out there....if I can't find a solution fast, it might be time for a Macintosh and TimeMachine.
  9. jeffpflueger

    Assertion failure at "elem.cpp-1000"

    humm. Thanks for that. I just renamed Config75.dat to config75_old.dat and launched retrospect. Indeed, it rebuilt config75.dat, but I am still getting this error whenever I run a backup script - and when I quit the program: "Assertion failure at "elem.cpp-1000" " the current version is now ( 7.5.387 ) and the windows installer continues to crash when I try to use the updater to update to later versions.
  10. jeffpflueger

    Assertion failure at "elem.cpp-1000"

    I have Retrospect Professional 7.5.285 running on XP Recently, there was an auto-update, after that I started getting this error: Assertion failure at "elem.cpp-1000" every time I try to back-up and also every time I quit the program. I uninstalled the updated version, restarted and reinstalled the original, I rebuilt the catalog (3 days to do), but whatever I try, I still get this error. I've been reading about the preferences file getting corrupted...I cannot find it. Whatr should I do?
×