Images lost after rebuilding aperture database

Hi,
After updating to Yosemite, Aperture started to show problems/ freeze etc. I could not acces my photo's and after updating Aperture 'it' announced that the libraries had to be rebuild.
These are images stored on a external harddrive and we're talking about over 3000 images. (over 4 years of family holidays to be exact so they are very valuable)
I left it running day and night, and after 4 days it was still rebuilding, which is understandable for that many pictures.
Sadly a family member did not realize that the plugged in harddrive was running and unplugged it after 5 days......Naturally Aperture showed an error. When I plugged the drive back in Aperture asked to finish rebuilding the libraries. Yet when I said yes it was finished in 3seconds and Aperture won't start up nor will it show me the libraries.
While the harddrive contained 2tb of info before, it's now only 500MB. It seems like 1/4th of my images are just gone. nowhere to be found and Aperture won't start back up.
Did anyone else encounter this problem or are there any measures that can be taken to possibly resolve the images?
Any suggestions are greatly appreciated.

Do you have any vaults or other backups of the images? I think that's what you'll need to look into. If the space is free on the drive, the images are gone.
I haven't known Aperture to delete images. Is the Aperture library also stored on the external storage, or was it on an internal drive? It's most likely that something corrupted the external drive and lost the images, and also corrupted the Aperture library. I actually have had this happen to me once - in my case I also had some music files go missing from my iTunes library, which is why I think some external factor was at play.
Thankfully I had a backup (I have Aperture vaults, and a separate Time Machine backup, as well as an online backup with Backblaze). Hopefully you have at least one method of backup as you're going to need it.

Similar Messages

Unsupported image format after merging aperture libraries

I've experienced a large number of files with 'unsupported image format' after merging aperture libraries from separate external hard drives. I did not have this problem in either library prior to merging them. Can anyone advise how to rectify this issue? Thanks

Try running library repair on the merged library and see if that helps.
To run the repair open Aperture while holding the option and command keys down. Select Repair from the menu.
Post back if you still have the problem.

After rebuild message database, mail folder come back into English

I rebuild message database for some reason. https://support.mozilla.org/en-US/kb/rebuilding-global-database
Then all default mail foler names become English. (They used to be Chinese) These are: Inbox, Drafts, Trash, Archive, Sent, Junk, Outbox.

Hello,
I am trying to rebuild system database after a DR Scenario by running the below.
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release>SETUP /QUIET /
ACTION=REBUILDDATABASE /INSTANCENAME=CORPPLN /SQLSYSADMINACCOUNTS=xxxxxx /SAPWD
=xxxxxx
It takes me to back to the command prompt as if it was successful.
However event log says:
Error 2(The system cannot find the file specified.) occurred while opening file 'C:\Program Files\Microsoft SQL Server\MSSQL11.CORPPLN\MSSQL\DATA\master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the
error. Verify your startup options, and correct or remove them if necessary.
Hi,
Error 2 means system cannot find the file specified. Can you make sure about location of master database file.
plus
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release>SETUP /QUIET /
ACTION=REBUILDDATABASE /INSTANCENAME=CORPPLN /SQLSYSADMINACCOUNTS=xxxxxx /SAPWD
=xxxxxx
In above query why are you going to release folder you must go to SQL Server 2008 r2 folder
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2
I guess script should be like
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2>SETUP /QUIET /
ACTION=REBUILDDATABASE /INSTANCENAME=CORPPLN /SQLSYSADMINACCOUNTS=xxxxxx /SAPWD
=xxxxxx
Setup.exe is in SQLServer 2008 r2 folder not in release folder
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
Hi Shanky_621,
I do not have a
SQL Server 2008 r2 folder with in the release folder.
Currently I am trying it from DVD which Alberto Morillo has suggested.
Best regards,
Mohan

Images deleted after export (Aperture 3.4)

Exported my newly imported images using the Export Originals function in Aperture. After that, all exported images were gone from the file system (previews still showing in Aperture but the refernced files are gone, also not in the Trash, but "fully gone").

One more question - I forgot: What is your current Aperture version? Have you upgraded to Aperture 3.4? Then you may need to reinstall Aperture - see this support article:
Aperture 3.4: May quit unexpectedly on launch after updating
Not to mention that Aperture crashed in the meantime, then claimed the library is locked, I had to reboot and then to wait 30 mins for the library to be fixed as it was corrupted...
After a crash Aperture will repair the library, but it may be necessary to rebuild it is well, see: Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
Looked for the images with Spotlight
Did you search the entire mac from the Finder?
In the Finder, choose File > Find or press Command (⌘)-F.

Red badge error in the dock after rebuilding account database...

Hi all,
I recently "Rebuilt" my email databases. After successfully rebuilding both accounts, I now have a red badge with the number "205" on my mail icon in the dock.
I have manually checked every mailbox, there is no RSS feed, etc. No new and unaccounted for email. If I get new emails in, the number 205 increases appropriately, but 205 is the minimum number.
Any thoughts?

Also read the article about font management, as you check your fonts:
http://discussions.apple.com/thread.jspa?threadID=122011
Ernie

IPhoto not showing thumbnails or images even after rebuild.

Hi there,
I've never posted before but have always found the forums useful. Hope somebody can help.
Sorry if its a long post.
I recently transfered my iPhoto library from an eMac (after the screen died) onto my mac mini. I initially placed them on an external HD to save space (The photos are 11GB) and on opening iPhoto told it to choose the new library. It said it needed to upgrade the photos because they were from an older version of IPhoto, which it did successfully.
Unfortunately, like a goon I accidentally unplugged the hard drive so iPhoto couldn't see the library. After turning it all back on the thumbnails and pictures have dissappeared.
I've tried holding option/command on launch, to rebuild thumbnails - no joy.
And I've tried re-copying the original untouched library from the emac again, but it still did the same thing. Any ideas? There's a lot of photos to start copying manually!
Many thanks

Thanks Larry,
It worked! That's a relief. I can see my sons birth again!
Once I chose the pictures folder it updated the files & thumbnails like the first time. So iPhoto must have still been looking for the old 'damaged' library even though I'd moved it.
Thanks again,
OL.

Images losted after encryption

Hi, my pictures stored into terminal and sd card become unreadable after the encryption process ended.

Hi,
Sorry by terminal I mean the phone itself.
I can see files, I can see my pictures in small size but when I select it to be in full screen. I've got an error. Dark screen with a small symbol in the middle fo the screen like unreadable.
When I try to access my image from computer, I've a message : Format not recognize but it's a .jpg so ?
And everything was fine prior I did encrypt phone and sd card. I did an uncrypt but no change with my picture files.
One other strange thing is, I've got a downloaded image. And this image has not been affected by my issue. Only pictures I'd taken with my phone.
Any help would be very appreciated.
Tks

Images lost after ppr when configured through CDN - jdev 12c

Hi
I configured CDN in adf-config.xml , the images are loaded fine when the page loads initially but when we do the ppr on any region that has images, the images are lost and instead of getting it from the base resource uri configured , it looks with in the application. Any idea what is going wrong ?
Jdevleoper 12.1.3.0.0.
Thank you
Ranjith

<adf-uri-rewrite-config xmlns="http://xmlns.oracle.com/adf/rewrite/config">
    <resource-uris>
      <base-resource-uri uri="http://10.25.245.50:7101/StaticContent/"
                         secure-uri="https://10.25.245.50:7101/StaticContent/">
        <match-pattern>^/.*/resources/images/.*\.png$</match-pattern>
        <match-pattern>^/.*/resources/images/.*\.png\?ln=images$</match-pattern>
      </base-resource-uri>
    </resource-uris>
</adf-uri-rewrite-config>

Messages lost after rebuilding mailbox

Inbox had a message that said it was damaged --rebuilt as suggested and then each message in it said that it had not yet been downloaded from the server. Tried rebuilding it again and now all of the messages are gone. Then tried importing inbox.mbox which produced a selection of email that did not resemble the original inbox.
Are my original inbox messages retreivable?

No, it isn't clear. I still don't know what does "I attempted to import files from it (unsuccessfully)" mean, nor what does "I then tried to reconstruct the inbox from the mac back up" mean. These statements are too vague.
The only items within an *.mbox folder used by Mail 2.x are Info.plist and the Messages folder. Any other files you may see there are almost certainly Mail 1.x files that Mail 2.x leaves there after the conversion. This is poorly explained in Mac OS X 10.4 Mail: Some mailbox files used by Mac OS X 10.3 are not deleted after importing. The article only talks about mailboxes in ~/Library/Mail/Mailboxes/, but the same could also be said about mailboxes in any of the "POP-" account folders.
As long as you keep a backup copy of the old files for a while (at least, until you're sure everything was converted properly), they can safely be removed from the Mail folder. OnyX has a Cleaning > Misc Options > Temporary and obsolete items option for getting rid of all those files.
Note that if you see strangely-named Messages-T0x... folders, these aren't old files from previous versions of Mail, but rather an indication that there is something amiss. More specifically, these are temporary folders created by Mail 2.x during an import or a reindexing process (e.g. rebuilding a mailbox) that Mail should have deleted when done. Their presence is a clear indication that something didn't work as expected.
Importing a mailbox that still has the old files there would produce different results depending on how you try to import it. Importing it as Other, for example, would cause Mail to look at the old mbox file only, ignoring everything else, which almost certainly is not what you want.
In order to import the current mailbox contents, you must first move all the *.emlx files out of the Messages-T0x... folders and into Messages proper, then get rid of the (now empty) Messages-T0x... folders. In Mail, do File > Import Mailboxes, choose Mail for Mac OS X as the data format, and follow the instructions. Note that Mail wants you to select the folder that contains the mailbox to be imported, not the *.mbox folder itself.

Stuck in 'Processing' after rebuild

I have a 140k image library. I moved to Aperture because Apple advised me that iPhoto wasn't built to handle large libraries and I should move to Aperture.
I only have about 110k images, the rest are duplicates because the iPhoto to Aperture conversion didn't complete fully and I had to import directly form an export - where all the 'versions' became their own images. But the duplication I can handle - I am on the ready with 'Duplicate Annihilator'
The real problem is that Aperture keeps going into a 'Processing' state
I have done several rebuilds after realizing that 'repair' wasn't cutting it.
The rebuild takes 4 hours where it reports # versions restored
After this - it is stuck in 'Procesing; - and I have left it for 24 hrs - and I don't think it is doing anything. Even 'Show Status Cmd-Shift-0 doesn't respond
In Aperture, I moved all my events to 'referenced' - Not wanting to be in 'Managed' mode as was iPhoto
Any pointers - ? Is there any way I can see if anything is moving within 'Processing'. Activity Monitor is pretty uneventful during this state
I have to Force Quit it - This is after a 'Rebuild ' !! From all my research - A rebuild is supposed to fix everything !
iMac 3.2 GHz 12 Gb RAM
Aperture 3.4.5

The rebuild takes 4 hours where it reports # versions restored
After this - it is stuck in 'Procesing; - and I have left it for 24 hrs - and I don't think it is doing anything. Even 'Show Status Cmd-Shift-0 doesn't respond
In Aperture, I moved all my events to 'referenced' - Not wanting to be in 'Managed' mode as was iPhoto
More than two days, that is close to the longest processing time I have seen reported here.
If your library is truck on processing a corrupted image file after rebuilding, you could try to relauch Aperture with the shift-key held down. This will defer the generation of previews, and you should be able to open the Activity Window ⇧⌘0.
Now select the images from half of your projects and run the command "Photos > Update previews".
Watch the Activity viewer for the names of the files that are being processed and see, if any tasks are hanging.

After Fixing Update Images lost to unsupported format

Like everyone, I had Aperture go buggard after update. Don't even get me started on that mishap. Several library fixes later to no avail, deleted Aperture and downloaded from App Store. One more library fix and Apeture opens once again. However, I now have a listing of recovered projects that report that the photo is an "unsupported image format". Little over 200 photos effected. I tried to reprocess but no help. I downloaded backup from offsite but still shows same message. I moved backup to lightroom which opens files and displays image but cannot edit. I cannot think of a bigger screw up since I started using Apple. I have a call in to Apple scheduled for Sat, but was hoping to get some useful information before that in an attempt t save my photos.

Are all your Sony 850 and a nex 5n images unsupported, or only the 200 "lost & found images" and other sony raw files are ok? Are you able to open Sony images at all?
Can you tell by the filenames, if the unsupported images are duplicates of images that are o.k.?
After a rebuild Aperture shows all stray images, that are not connected to current versions in a kind of Lost&Found folder - usually these are redundant images that you can delete and forget (after making a backup of them just in case). Look at the dates and filenames and check, if you have good versions of them.

Rescuing and/or Accessing Images From Aperture Database Without Aperture

Early reviews of Aperture mentioned that Aperture created a closed, inaccessible database of all the images contained therein. This apparently means that these images cannot be accessed unless you have Aperture. Does anyone else feel nervous about this? What happens if the Aperture database is corrupted and won't open? As far as I can see, you would be toast because you couldn't reach your images. I would appreciate hearing from someone who can address these concerns. How stable is the Aperture database? Is there a chance it could be corrupted and refuse to open? And if so, how would you go about rebuilding it and/or rescuing your images? It also appears that the only way you can move images is by exporting them (which requires a working program).
Any thoughts?

No problem! Trying to answer these questions is a very helpful way to learn the app by looking at aspects of it I have not encountered yet.
Yes, you can rebuild the Aperture database in a similar way to Entourage (and iPhoto). Holding down command-option after launching Aperture will make a Rebuild Library dialog appear. HOWEVER, don't do this unless you really want to see it work, because there seems to be no way to cancel the process. You can choose Rebuild Now or Don't Rebuild. If you choose Don't Rebuild, your Projects will nonetheless need to be recovered before use. The dialog mentions a Rebuild Later button, but there is no such button available.
I have done this a few times both ways in the course of writing this, and there does not seem to be any negatives to rebuilding other than the time rebuilding takes, so if your projects aren't large it may be worth doing now to get comfortable with the process.
G5 Dual 2.7 Mac OS X (10.4.3)

Aperture library lost after deleting preferences/repair?

Hi:
I tried opening Aperture this morning and got an error message saying: "There was an error opening the database for the library <library_name>."
I found this article from Apple support (http://support.apple.com/kb/HT3805) on the problem. I wasn't able to use the "first aid" tools (even with Option/Cmd held down, Aperture refuses to open) so I deleted my user preferences.
I was able to reopen Aperture, but now EVERYTHING is gone. I use referenced files (apparently, a good thing in this case) so I know that the original RAW or TIFF files are there. I also verified this independently through Finder.
However, I'm not sure where all my projects are, or my keywords/tags on the photos. My fear is that this is all stored in the Aperture database, and that it's all gone at this point. Is that the case?
By the way - I tried a repair, and nothing happened. I'm guessing the library file is "zeroed out" at this point (everything gone) and so a repair job didn't have anything to repair.
Bottom line - how screwed am I at this point?
Jim

Hi Frank:
I really appreciate all your help, especially since I know you're doing this out of the kindness of your heart...
OK, answers:
All referenced files, nothing managed.
There's a backup (I think) of library from last month, I may end up reverting back to that.
RE: how the drive is formatted - I was pretty sure I'd formatted it OS X extended with journaling, but Disk Utilities show it's a Win NT filesystem.
Tried copying the library to my internal HDD, it won't even copy over (the copy function just says "Preparing to copy to desktop" but never completes).
I'll try the rebuild but since I (apparently) can't get Aperture to 'skip over' the new catalog it creates (as opposed to pointing it to the old catalog), then I don't know how the rebuild will turn out.
Been using it for a while, and there's enough work in it that it'll be a PITA to recreate - especially if I've lost my tags and my non-destructive edits. If those are all still there somehow, someway, in XML files or whatever, that's cool. Fortunately my file structure on the HDD is "/PHOTOS/<year>/<month/<shoot date and name>", and the structure for my projects is (was?) the same. So if all I have to do is recreate the projects, not a big deal.

Help! All referenced Aperture images offline after Time Machine restore!

Okay, I finally decided to upgrade the internal drive of my 15" MBP from the 250 stocker to a 640 WD drive. I did a Time Machine backup right before swapping the drives, then restored from backup. Everything seems to have transferred fine, except for Aperture. All the photo's metadata is still there, all my various projects and everything are fine, but the actual photos are nowhere to be found. They were all referenced from my iPhoto library. When I go File>locate referenced files, Macintosh HD is offline (which i'm guessing is my old HD). Thing is, under the Not Found column, it says 0..... Can someone please help me with this??

So I just had the same problem. I had restored my whole disk drive from a backup after Apple replaced the hard drive.
All images that were referenced on the internal drive were listed as offline even after a Aperture DB rebuild and a disk drive identically named to the original.
Procedure: first test this on a few files, then you can do the whole library.
Select any project with multiple pictures that are referenced and have a red tag indicating offline. Do a select all on the images in that project, even if some do not have offline indicated. After the selection use File -> Locate Referenced Files.
Uncheck the box that says "Show Only Referenced Files" Select one of the files that you know has a status of offline. Next, in the bottom window, navigate to that exact file and select it. Click the Reconnect All button, it may take a few minutes, but when it is done the number of offline files will have decreased and the new number of online files will be reflected.
The Reconnect All feature is smart enough to figure out the folder hierarchy for your whole library. I subsequently used the HUD to select all 14,300 "offline" images in the library, I then selected one and told it to Reconnect All as above. Took about 15 minutes but at least there was a progress bar.
Good Luck

Aperture using 3 week old file paths for referenced files after Rebuild

I recently had major problems with some Nikon D60 files (the referenced files switched original files). I had to re-import everything a start again. Having sorted everything out, I then relocated the files with new files names (thinking that the original file names may have caused the problems).
This was 3 weeks ago. However, when I Rebuilt the library today, these renamed images went offline because Aperture has kept the original file paths (with the original names).
Does anyone know how to update file paths to the current ones? (rather than some random previous one).

Thanks for the reply. I will check out the links.
I should have mentioned that all renaming/moving of files was done from within Aperture. Aperture is not updating its own file paths.
The process is this. Having moved/renamed the images (using Aperture's Relocate Masters) I am able to use the software, close it down, restart etc and the images will be found correctly with few/no 'lost' images. It is when I use 'Rebuild' that the file paths revert to an old, previously used version that is no longer valid. It is as though there are two preference files, each with a different file path information. There was a post sometime ago that mentioned using Terminal commands to force Aperture to update to the correct files paths/directories. I haven't been able to find the post yet though.
These particular files (Nikon D60) are not from my own camera so I am not sure why I have had such an issue. Normally I am using a Canon 5D MK2 or a Phaseone digital back. However, even with my own equipment I do regularly have to 'Reconnect' one or two image files that have become lost which is annoying. So I am keen to get to the bottom of this issue.

Images lost after rebuilding aperture database

Similar Messages

Maybe you are looking for