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

iPhoto library LOST after automatic upgrade OS 10.8 + iPhoto 9.3.2

Hello,


Just after automatic upgrade of the last Lion system + iPhoto software, when using iPhoto, I suffered a brutal stop of the software and my MacBook automaticcally restart.


When re-openning the system, my library was around 10 MB size, instead of 14 GB size.



All photos have disapeared.


So a recurent message asking iphoto files is displayed file by file.... and its now impossible to quit normally iphoto (except by changing library).

Others libraries are running (for the moment... but I wil not use them with this OS+ software relase, that's sure !!!)



The structure of the library inside its directory is not usual. Missing nearly every usual folders.



I 'm very surprised of such a painfull bug.



I'm looking around into various system logs, and I will inform about these datas into this post.



If anyone knows the same, please post.



Thx.


Jean-Louis, mac user since 1986,

Paris.

iPhoto '11, OS X Mountain Lion (10.8)

Posted on Sep 23, 2012 6:45 AM

Reply
3 replies

Sep 23, 2012 2:01 PM in response to Jean Louis Bruneel

Hi,


I completemy post with additional infos I didn't provide previously.


At first, situation is solved.


How to ? By checking logs into , I have found that a second library whith my original content exist in a sub-folder of the folder that I have checked.


What happens : after the crash, the iphoto path has been lost by the system, and iphoto automatically swithed its path to a second path where in the past a clone of my phototheque has existed... I don't remember exactly why it was here.


So I thought it was the last phototeque, and as It was nearly empty, i panic !!!. But when looking the logs I have seen the right path and found my 67 Gb library !!!!


So I have tried to open it and I have been by the same trouble that occured probably and cased the crash : management of authorizations of files has a little bit changed. When some files are found with bad authorizations, in the past this was quite ignored, and now in 9.3.2 am essage is dispayed file by file proposing to search the file manually... let's Imagine the recurent work if tons of files suffer bad authorizations.


The reason of the trouble is that i manage a unique iphoto library with multiple (2) logins users on the same mac. I have put the iphoto library into a shared folder. But even when i rebuild authorization (with a new users group) I have trouble when each of the 2 logins create new photos. Some previews are not assigned to the group by default, so image cannot be displayed corectly sometimes. In fact since icloud exists, some new folders have appeared, and this multiuser trouble is also happening with photos coming from the photo flux of the cloud. Too much subfolders are now managed, my trick to share photos is no more the right solution.



I 've checked internet, and some post explains that, more than just putting the library into a shared folder, it was better to put it on a volume that is not managing authorizations. Yes,this would probably solve the little incidents I have already suffered with some photo displays. I use a macbook, so it is necessry to create a virtual disk, mount it automaticcaly, and avoid to manage on it some authorizations. But : I will have to fix the size of this volume, so I have to check before how to extent it, in order to avoid future troubles of size. Not sure it is easy to change size dynamically.



The crash I suffered remind me that back-ups are mandatory. I have one available, but it is not fully recent, my server is not always mounted and i have to relocalize the destination of the back-up. and plan and wait for a new and complete one.



One info, here under the log of the crash : I was moving some existing photos from the main photo list into a new album, and I have probably moved one photo created into the library by the second user and coming from icloud.


Note : into the log, the authorization problem is clear and furthermore : the apple developper has planned a clear message explaining the trap that the program found.... interesting!!! The truth : the bold text is not mine...



Sep 23 14:21:28 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Thumbnails/2012/09/23/20120923-142127/K6t7YJTdRv+uwQGKCbLV1g

Sep 23 14:21:29 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Thumbnails/2012/09/23/20120923-142127/PxGzv04qQLmCs++7iHC3%Q

Sep 23 14:21:29 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Thumbnails/2012/09/23/20120923-142127/yQiWyi4ISOuv3hUfMUxINg

Sep 23 14:21:29 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127

Sep 23 14:21:30 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127/8uqREwcNQCuHuHZNAAEOCQ

Sep 23 14:21:30 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127/h0LddfGaSRu8QoQTCYYMPQ

Sep 23 14:21:30 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127/RlNhGbecS6qBdkX+QJxxNw

Sep 23 14:21:30 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127/sU8IIhW6SF+3uh86pSzeLw

Sep 23 14:21:30 MacBook-XXXX.local mdworker32[7143]: File paths From PLUGIN side... /Users/Shared/XXXXX/iPhoto Library 10/Database/Versions/2012/09/23/20120923-142127/UjmvNHy0SZi3+fF1lNE4yw

Sep 23 14:22:05 MacBook-XXXX.local com.apple.backupd[7130]: Starting automatic backup

Sep 23 14:22:05 MacBook-XXXX.local com.apple.SecurityServer[18]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [14] for authorization created by '/usr/libexec/UserEventAgent' [14] (100012,0)

Sep 23 14:22:07 MacBook-XXXX.local mtmd[39]: Set snapshot time: 2012-09-23 14:22:09 +0200 (current time: 2012-09-23 14:22:07 +0200)

Sep 23 14:22:07 MacBook-XXXX kernel[0]: nspace-handler-set-snapshot-time: 1348402929

Sep 23 14:22:07 MacBook-XXXX.local com.apple.SecurityServer[18]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [14] for authorization created by '/usr/libexec/UserEventAgent' [14] (100012,0)

Sep 23 14:22:07 MacBook-XXXX.local com.apple.backupd[7130]: Backup failed with error: 19

Sep 23 14:26:16 MacBook-XXXX.local iPhoto[7136]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.

Sep 23 14:39:02 MacBook-XXXX.local SystemUIServer[275]: _CSBackupServerProxySendMessage() failed to send message to backup server, error: -4

<<<this is the crash>>>

Sep 23 14:51:19 localhost bootlog[0]: BOOT_TIME 1348404679 0

Sep 23 14:51:35 localhost kernel[0]: Darwin Kernel Version 12.0.0: Fri Jun 22 20:01:10 PDT 2012; root:xnu-2050.7.7~1/RELEASE_X86_64

iPhoto library LOST after automatic upgrade OS 10.8 + iPhoto 9.3.2

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