5 Replies Latest reply: Apr 6, 2013 1:32 AM by MarkPek
gjsmith Level 1 Level 1 (20 points)

My RAID with my Aperture masters has become a bit dodgy, so I have cloned the drive onto a new RAID box and am trying to reconnect to the files there.   The last time I had to reconnect was about three years ago when my primary raid had a hardware failure and I had to switch over to the backup.

 

This time, things aren't going well. 

 

First, I tried to reconnect the entire library (about 600K images).  The process appeared to be going fine (according to the dialog box), but about 8 hours later, when the process was completed, not a single image had been reconnected to the new drive.  And when I reopened the Library, I got an "Aperture has detected inconsistencies" message, so I repaired the Library.

 

So after repairing, I again try to reconnect.  Except this time I pick a small project--about 500 images-- and start with that.   Reconnection goes smoothly.  Then I try a larger project, 20,000 images, and I immediately get the SBBOD.  And it doesn't go away, ever.   Even so, the progress box does show progress, but it's excruciatingly slow--I did a rough calculation and it will take 45 hours to finish this job.  In Activity monitor, Aperture is showing as Not Responding, and it's running at around 100% cpu (I have an 8 core Mac Pro) with 19-20 threads open.

 

Does anyone have any ideas about what's going on, or how to get around the problem?  Is 3.4.3 just buggy with respect to reconnecting?

 

 

Thanks in advance

 

Gordon


Aperture 3
  • 1. Re: Reconnecting masters an ordeal under OS X 10.8/Aperture 3.4.3
    Kirby Krieger Level 6 Level 6 (11,915 points)

    Hi Gordon,

     

    Let it run.  I tested this with a 500 GB Library.  Reconnecting all Originals took 80 hours of processing time on my 2012 rMBP.

     

    I found no reliable way to determine if anything was actually happening at any point.  The progress bar was useful for rough estimates (at 24 hour I calculated that it would finish at about 80, which is the only reason I let it run;  it did).  iStat (a front end for Activity Monitor, afaict) reported either single-digit percentage of CPU to Aperture (on a quad-core machine), or else just over 100%.

     

    The "Not Responding" message misleads (Apple needs to change this, imho).  Force quitting causes additional problems.

     

    The reason for my test was to do determine if it was faster to move Originals using Finder, and then reconnect them using Aperture, than it was to simply use Aperture to relocate them.  I concluded that I was better off using Aperture to relocate Originals.

     

    (Added:)

    I was copying/moving between external USB3 drives.  I did not try this on a RAID.

     

    Message was edited by: Kirby Krieger

  • 2. Re: Reconnecting masters an ordeal under OS X 10.8/Aperture 3.4.3
    gjsmith Level 1 Level 1 (20 points)

    Thanks, Kirby.  I had planned to let it finish up.

     

    Aperture has definitely regressed with this function; I was able to reconnect to my entire library (about 4 TB) last time in under 12 hours.

     

    Did I understand your email to say that you can use relocate masters (or "originals" now) to move referenced masters from one hard drive to another?  If so, I will give that a try to see quickly that goes.  I didn't want to use consolidate then relocate.

  • 3. Re: Reconnecting masters an ordeal under OS X 10.8/Aperture 3.4.3
    MarkPek Level 2 Level 2 (155 points)

    Please let us know who this turns out!  I'm about to try something similar. 

  • 4. Re: Reconnecting masters an ordeal under OS X 10.8/Aperture 3.4.3
    gjsmith Level 1 Level 1 (20 points)

    OK--I am back from vacation and want to report how this turned out for all who may be interested.

     

    I had copied all of my referenced masters from on old RAID box to a new, higher-capacity RAID (the new RAID will be my working RAID: the old one will become my backup).  I had assumed it would be an easy task to reconnect the masters for my entire Library at one time.

     

    As explaned above, that didn't work out, so I picked a single project -- 20,233 Nikon nef raw images -- and tried to reconnect the masters for it alone.  This task completed in just over 47 hours.

     

    Then I did a test-- I relocated the masters for the project back to a holding folder on the original drive.  This took about an hour and a half.

     

    Now I'm busy relocating all my masters to the new RAID from the original drive.

     

    I don't know whether the unacceptable sluggishness of the reconnect command is a function of my particular set up, but I will be praying that I never have to reconnect to your backup drive.  Hopefully this issue will be addressed in Aperture 4 or Aperture X (whenever we see it).

     

    Gordon

  • 5. Re: Reconnecting masters an ordeal under OS X 10.8/Aperture 3.4.3
    MarkPek Level 2 Level 2 (155 points)

    All right!  Good luck!