Jump to content

Partitions in APFS fail with volume error (Retro 14.5.x)

Recommended Posts

Certain partitions fail on clients with two different, strange errors:

  1. On an APFS formatted volume (internal SSD) on MacBook Pro 2017 backing up the entire drive. 
  2. On MacOS Journaled drive, network timeouts occur in accessing the source. The ONLY [systems Preferences>Energy Saver>Power Adapter [Energy Settings] settings that work for me are shown. Unchecking "Prevent computer from sleeping," will result in these timeouts. I don't see where that's clear in your manual or other instructions. Seems that this condition used to be known as "deep sleep". I haven't had that issue in MacOS before 13.x not in Retro before 14.5 (do not know or have any ideas as to which version of OS or your software causes this, do you?). 


See the attached picture/screen shot.

As to item # 1, here is log pertaining to this event. 

  Using Instant Scan data for RAID 4 SSD on MyNewGenie_MBP

    10/3/17 03:00:35: Found: 363376 files, 201365 folders, 1.1 TB

    10/3/17 03:00:41: Finished matching

    10/3/17 03:00:59: Copying: 743 files (2.5 GB) and 0 hard links

    [*] soccRecv: recv failed, error 60

    !Trouble reading files, error -559 (network connection timeout)

    10/3/17 03:02:55: Execution incomplete

    Remaining: 695 files, 1.7 GB

    Completed: 48 files, 818.3 MB

    Performance: 416 MB/minute

    Duration: 00:02:54 (00:00:56 idle/loading/preparing)



As to item # 2, here is log pertaining to this event. 


  -  10/2/17 07:14:44: Copying VM on MyNewGenie_MBP

      Scanning incomplete, error -1,101 (file/directory not found)

    10/2/17 07:14:58: Execution incomplete

    Total performance: 705 MB/minute

    Total duration: 00:50:09 (00:15:00 idle/loading/preparing)


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 http://www.retrospect.com/en/support/contact, 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. http://www.retrospect.com/en/about#exec.  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