Jump to content
Sign in to follow this  
NCSUCPE

Regular error -641 on disk backups

Recommended Posts

Hello all,

 

I have a machine with Retrospect 14.1.0 (138) that I am using disk backup sets connected via USB to a 2007 iMac with 10.11.6 El Capitan which is the latest it can run. I get regular error -641 chunk checksum errors. When I get them, it appears the backup is toast. Two questions, 1 why are they happening, and 2 how can I recover. I have been fight these for over a year on previous version and I am just about feed up. If it helps, retrospect is spontaneously restarting from time to time too.

 

John

Share this post


Link to post
Share on other sites

Here is a portion of the log file:

+  Normal backup using Proactive Desktop Backup at 7/6/17, 1:45:10 PM

    7/6/17 1:45:12 PM: Finished scanning backup set data files
    To Backup Set Media Set A...
    -  7/6/17 1:45:10 PM: Copying Macintosh HD
    7/6/17 2:05:05 PM: Found: 731508 files, 173897 folders, 74.2 GB
    !Trouble matching Macintosh HD to Media Set A, error -641 (chunk checksum didn't match)
    +  Executing Rebuild at 7/6/17, 2:07:38 PM
    To Backup Set Media Set A...
    Scanned /Volumes/Backup Set A/Retrospect/Media Set A/1-Media Set A/ up to backup set data file index 974
    Using fast rebuild
    7/6/17 2:09:24 PM: Finished scanning backup set data files
    !Can't load source session tree for 6/29/17 10:57:14 PM, error -641 (chunk checksum didn't match)
    7/6/17 2:15:42 PM: Execution incomplete
    Completed: 344,219 files, 87.2 GB
    Performance: 14,409.1 MB/minute
    Duration: 00:07:42 (00:01:29 idle/loading/preparing)
  +  Retrospect version 14.1.0.138
  Launched at 7/6/17 2:32:08 PM 
 
  +  Retrospect version 14.1.0.138
  Launched at 7/6/17 2:50:27 PM 
 
    +  Normal backup using Proactive Desktop Documents at 7/6/17, 2:51:24 PM
    7/6/17 2:51:24 PM: Finished scanning backup set data files
    !Can't load source session tree for 6/29/17 10:57:14 PM, error -641 (chunk checksum didn't match)
    To Backup Set Media Set A...
    -  7/6/17 2:51:24 PM: Copying Macintosh HD
    7/6/17 3:07:49 PM: Found: 731508 files, 173897 folders, 69.3 GB

Share this post


Link to post
Share on other sites

This thread discusses the -641 error, and how henry-in-florida got around it.

 

I found the thread using the Advanced Search facility by clicking the gear icon on the extreme right of the top line in the Forums page that says "IPS Community" on the left.  I then typed "-641"—including the quotes—into the Find Words box; I could have selected "Retrospect 9 or higher for Macintosh" from the Find in Forums dropdown, but I didn't because I wanted to see posts from any Forum that discussed error -641.

Share this post


Link to post
Share on other sites

If you think this is a bug that should be fixed by Retrospect Inc., you will have to submit it as a Support Case.  For English speakers, that is done by going here and filling out the form (sorry, I don't know what the equivalent addresses are for non-English speakers, but they can figure it out from their appropriate Retrospect website address).  IMHO this is quite reasonable; obliging you to fill out the form provides Retrospect Inc. with useful details about your Retrospect installation that they would otherwise have to query you for.

 

As a result, Retrospect Inc. will pay no attention to your post in this forum.  On 12 December 2016, in response to a letter I snail-mailed to Mayoff,  I received an e-mail through a Mayoff account that was signed by JG Heithcock, CEO Retrospect Inc..  In it he says "From reading your letter, I think the main issue is that you view the forums as a good place to talk to us, Retrospect, Inc. But we view the audience of the forums as restricted to our customers [my emphasis]. The one caveat we have made on that is for feature requests, largely as we would like to see if other customers also agree on the desirability and feature set for these requests."

 

That means that the only audience for "Retrospect bug reports" in this forum will be other administrators of Retrospect.  Nevertheless, by posting in this forum you are providing a useful service to us fellow administrator peasants.  Thank you.

 

Please be aware that the "description of your issue" in the Support Case form is IME limited to about 2000 characters by the Support Case software.  If you go over that limit your "description" will be broken up into a "description" plus one or more "additional notes".  The same is true for any additional notes you may later post yourself.  I suggest that, to avoid the appearance of choppiness in your Support Case, you create your case in a post in this forum and then copy it paragraph-by-paragraph to your Support Case. 

 

Note that, despite the new dialogs in the Retrospect Inc. Support Case system urging you to sign up for Annual Support and Maintenance, Mayoff has verbally assured me that you don't need to be signed up for ASM to report a bug—only to get personal assistance with coping with it.

 

If this post sounds formulaic, that's because I intend it to be.  I intend to post it in every new thread that appears in this forum, unless the OP indicates that he/she has or will open a Support Case for the bug that the thread reports.  Of course, Mayoff could take 5 minutes of his time to post a slightly-more-polite version of this post as a  "sticky thread" that will always appear at the top of the forum.  I don't intend to hold my breath until that happens (insert appropriate smiley here).

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×