Aperture 3 Vault - Updating Vault issue

I am experiencing the exact same problems and I have one other data point to consider:

I have two vaults that I created and I updated both of them simultaneously. The progress bar got to 50% and then stopped. I checked the vault sizes and #1 was close to what I expected but vault #2 was not touched at all. So, it seems like the vault process almost completes but gets stuck right before completion.

Is iDefrag the only solution you all have found that works?

Hi,

I can not say if IDefrag is better then " New " but I bought a brand new 1.5 TB Lacie Firewire 800 and still no go.

I would assume that a new drive should even be better then one that was defraged or no ?

So back to the chalk board for me....

Cheers

Hi,

I am seeing the same thing. Running Aperture v3.0.2 and when I do a vault update it gets stuck around 50%. I deleted my old vault and made a new one, but the same thing happened. I am using mirrored internal Seagate drives formatted to Apple Extended.

Even though the progress bar is on 50% I can quit Aperture properly even though it takes some time.

Best wishes

Michael

I have the exact same problem. I tried on a brand new WD 2 TB external hard drive, and the newly created vault only manages to update to around 90% of the actual library size. I repeated the process on a Lacie 750 GB hard drive and an upgraded vault from ver 2, with identical results.

Something that I have noticed with my Vault issue (where it goes a little over 50% and stops) is that it doesn't seem to copy the Previews over completely. I checked the Aperture Library and Vault Library and there is a slight size discrepancy. Right-clicked them and looked at package contents and what I saw what that there was a 500 MB difference in the Preview folder size and that there was no Thumbnails folder in my fault though there was in my active library.
I ran all three launch options for Aperture, Fix permissions, rebuilt, and repair, but the issue remains. What I am doing now is having Aperture rebuild all Thumbnails and Previews for my images. this is currently under way with my 10k+ images. If having Aperture reprocess the Thumbs and Previews doesn't fix the issue than it has to be a hard program code that will be fixed soon.
Just in case you are wondering my Masters folder is the exact same size.

To answer another question I have seen in reply to this issue; "Is it safe to recover from the 'incomplete' vault if worse comes to worse?" My answer would be a hesitant "Yes." What would you should do is check the vault to see if the Masters folder is the same size as your active library folder. The issue seems to be more with other folders than the Master so worse case those would be rebuilt after recovering you library. It is a good idea though to make 'hard-copies' of the library though.

Other things I have done to try and remedy this have been trying different drives (3 of them formatted and reformated HFS, HFS+ and HFSX). This isn't my first rodeo and patience is a virtue but don't blame Apple if you haven't done your due diligence.

I think I might have just stumbled across a fix for the issue. For data's sake I backed my library up to Time Machine (on my Time Capsule) before trying this.
My Aperture 3.0.2 vault is on a Drobo (2nd gen) and my library has 10k+ files. I upgraded from A2 to A3 but I started a new Aperture vault after that. Matter of fact I deleted the old one after creating the A3 vault. So as I mentioned in my above post I looked into the folder contents of both my local Aperture Library pkg ("Aperture Library.aplibrary") and looked onto my Drobo's locked vault pkg ("Vault.apvault"). According to Finder there was a 6GB+ size variance (where local was larger than the fault). Upon looking at the subdirectories I saw that every folder, except for "Masters," was smaller in the vault as compared to the active library. So what I did was run "cp" commands one by one like this:
"cp -rfv /Volumes/Macintosh\ HD/Users/user/Pictures/Aperture\ Library.aplibrary/Thumbnails/ /Volumes/Drobo/Pictures/Vault.apvault/Thumbnails "
I did this for all the directories except the Masters. For me the "iPod Photo Cache" folder was missing in the fault and the "ApertureData.xml" file were not in the vault so once I had everything else matching in file size, I unlocked the fault in the 'Get Info' window and dragged those two items into the vault (copied over in a couple seconds). With that done I rechecked the file size and Finder had both of the pkgs as the same size. Here came the real danger...
I launched Aperture and had it update the vault. It blazed past the first 75%. AWESOME! It was great to see it past the 51% area.
Now for me my 10k image (80GB+) library synced to the vault after about 15 minutes. It worked! My hunch was right, there are some App permission issues when it comes to copying to the vault. Sorry if this doesn't make much sense but it is 02:20 AM where I am. If you have any questions just reply or go to my site. Best of luck.

The 3.03 update didn't fix this problem.

Question to xgenius:

After your fix with cp command: Does your vault run smoothly now or do you have problems again. Thank you in advance for your answer.

Best regards from Stuttgart

Wolfram

I'm having the exact same problem.

http://discussions.apple.com/thread.jspa?threadID=2534053&stqc=true

did a fresh install of OS 10.6 and Aperture 3.

Still no luck. This is ridiculous.

I updated the vault but when I look at my vault on my external drive it says last modified was nearly 2 weeks ago...

crazzy88ss

as a first aid, now I use TimeMachine for the Aperture database backup. This seems to work. And it is better because you have stored ongoing changes in history. But the problem with the stopping and not responding vault updates still resists.

Wolfram

I'm having the same problem with the vault hanging around 51% ... I've tried it a couple times... this is getting really frustrating.

if you think you found a bug or glitch let apple know
http://bugreport.apple.com

you might need a developer account (which is free) but you will get feedback from Apple


or you could let them know via feedback (you don't get a reply but you don't have to sign up for a free developer account)

signed up for a developer account and verified it and everything ... tried your link ... entered my login info, and got the following:

You do not have access to the Apple Bug Reporter (aka RadarWeb).

<Edited by Host>

interesting . . .
I am getting a failed to open page
hmm

well I found http://developer.apple.com/bugreporter/noconnect.html so it seems they do wanna know if people aren't connecting at times