Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Restore (large) Library from Vault fails with no error message

I just got a new hard drive because my previous Aperture drive started glitching to the point where a straight copy of my old library to the new disk fails, so I'm being forced to rebuild it from my latest vault backup.


I created a new, blank library to import the vault contents into, but when I do File --> Vault --> Restore Library... and select the appropriate vault (and confirm), it starts a progress bar saying "calculating disk space" and then that goes away and... nothing replaces it.


There's no error message, there's no progress bar, there's no high CPU usage from Aperture and, even more frustratingly, nothing helpful in the system log.


I do get the following message in the system.log, but it doesn't make much sense to me:


Dec 26 21:41:09 Alice.local Aperture[3634]: view service marshal for <NSRemoteView: 0x7f97be4bf9e0> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldnâ&#128;&#153;t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x600001879100 {NSDebugDescription=The connection was invalidated from this process.}
    process/thread/queue: Aperture (3634) / 0x122d10000 / com.apple.NSXPCConnection.user.endpoint


This is a rather large library, about 800GB. No referenced masters, everything is inclusive.


And I would really, really like it back.


Help?

Aperture 3, OS X Mavericks (10.9.1)

Posted on Dec 26, 2013 6:45 PM

Reply
Question marked as Best reply

Posted on Dec 27, 2013 3:55 PM

Ah, I managed to figure it out!


It was a permissions thing. Somehow, when I added the new drive to the system, the drive somehow was given the owner root:wheel, making it really hard to do anything with that, haha.


If anyone else somehow ends up with this problem, the solution is to open Terminal (under Utilities) and type the following (with the appropriate <replacements>):


whoami     (enter)

the answer to this is your short username


sudo chmod -R <short username>:staff /Volumes/<your drive name>/   (enter)



<Edited by Host>

1 reply
Question marked as Best reply

Dec 27, 2013 3:55 PM in response to NightHawk663

Ah, I managed to figure it out!


It was a permissions thing. Somehow, when I added the new drive to the system, the drive somehow was given the owner root:wheel, making it really hard to do anything with that, haha.


If anyone else somehow ends up with this problem, the solution is to open Terminal (under Utilities) and type the following (with the appropriate <replacements>):


whoami     (enter)

the answer to this is your short username


sudo chmod -R <short username>:staff /Volumes/<your drive name>/   (enter)



<Edited by Host>

Restore (large) Library from Vault fails with no error message

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.