Ingest problem

[vAfotoriporter]

As I remember the issue with OSX system files disturbing ingest had been corrected but it seems the new beta has problems with it again:

Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexArrays to: /Photo/IngestFolder/live.1.indexArrays
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexCompactDirectory to: /Photo/IngestFolder/live.1.indexCompactDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexDirectory to: /Photo/IngestFolder/live.1.indexDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexGroups to: /Photo/IngestFolder/live.1.indexGroups
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexHead to: /Photo/IngestFolder/live.1.indexHead
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexIds to: /Photo/IngestFolder/live.1.indexIds
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexPositions to: /Photo/IngestFolder/live.1.indexPositions
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexPostings to: /Photo/IngestFolder/live.1.indexPostings
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.indexUpdates to: /Photo/IngestFolder/live.1.indexUpdates
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.shadowIndexGroups to: /Photo/IngestFolder/live.1.shadowIndexGroups
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.1.shadowIndexHead to: /Photo/IngestFolder/live.1.shadowIndexHead
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexArrays to: /Photo/IngestFolder/live.2.indexArrays
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexCompactDirectory to: /Photo/IngestFolder/live.2.indexCompactDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexDirectory to: /Photo/IngestFolder/live.2.indexDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexGroups to: /Photo/IngestFolder/live.2.indexGroups
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexHead to: /Photo/IngestFolder/live.2.indexHead
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexIds to: /Photo/IngestFolder/live.2.indexIds
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexPositions to: /Photo/IngestFolder/live.2.indexPositions
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexPositionTable to: /Photo/IngestFolder/live.2.indexPositionTable
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexPostings to: /Photo/IngestFolder/live.2.indexPostings
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexTermIds to: /Photo/IngestFolder/live.2.indexTermIds
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.indexUpdates to: /Photo/IngestFolder/live.2.indexUpdates
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexArrays to: /Photo/IngestFolder/live.2.shadowIndexArrays
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexCompactDirectory to: /Photo/IngestFolder/live.2.shadowIndexCompactDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexDirectory to: /Photo/IngestFolder/live.2.shadowIndexDirectory
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexGroups to: /Photo/IngestFolder/live.2.shadowIndexGroups
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexHead to: /Photo/IngestFolder/live.2.shadowIndexHead
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexPositionTable to: /Photo/IngestFolder/live.2.shadowIndexPositionTable
Error copying: /Volumes/EOS_DIGITAL 1/.Spotlight-V100/Store-V1/Stores/AAB2B942-8E49-4533-B039-681780001EB4/live.2.shadowIndexTermIds to: /Photo/IngestFolder/live.2.shadowIndexTermIds
Warning: Not erasing volume "/Volumes/EOS_DIGITAL 1/", because there were errors.
Warning: Finished copying from volume "/Volumes/EOS_DIGITAL 1/", but not unmounting because there were errors.

[memoriesbymichael]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

[vAfotoriporter]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

I surely use the last PM beta expiring early july. My OS is OSX 10.5.2 I didn't upgrade to the latest yet.

[Kirk Baker]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

Are you saying that you're getting errors reported by Ingest, or is Photo Mechanic crashing?

-Kirk

[Kirk Baker]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

I surely use the last PM beta expiring early july. My OS is OSX 10.5.2 I didn't upgrade to the latest yet.

We are adding code to skip these Spotlight files in the next beta.  But I strongly recommend that you find some way to keep Spotlight from indexing your camera cards.  That is a really bad thing to do.  You only have one copy of the photos on the card until they make it onto your hard drive and for Apple to add a lot of files amounting to possibly several megabytes onto a camera disk just isn't right.  Often when a camera card is pulled out of a camera it is because the card is already full and cannot have any more pictures on it.  Mac OS X 10.5 already added some junk into camera cards with their '.fseventsd' folder for tracking file change notifications, and now they're Spotlight indexing camera cards.  This is just 'asking for problems' in my opinion.

It would be nice if there were some way to keep the OS from modifying the card at all.

It may be that the OS is the cause of other errors being seen by some folks like Michael.

-Kirk

[vAfotoriporter]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

I surely use the last PM beta expiring early july. My OS is OSX 10.5.2 I didn't upgrade to the latest yet.

We are adding code to skip these Spotlight files in the next beta.  But I strongly recommend that you find some way to keep Spotlight from indexing your camera cards.  That is a really bad thing to do.  You only have one copy of the photos on the card until they make it onto your hard drive and for Apple to add a lot of files amounting to possibly several megabytes onto a camera disk just isn't right.  Often when a camera card is pulled out of a camera it is because the card is already full and cannot have any more pictures on it.  Mac OS X 10.5 already added some junk into camera cards with their '.fseventsd' folder for tracking file change notifications, and now they're Spotlight indexing camera cards.  This is just 'asking for problems' in my opinion.

It would be nice if there were some way to keep the OS from modifying the card at all.

It may be that the OS is the cause of other errors being seen by some folks like Michael.

-Kirk

I would also be happy if the OS wouldn't add files but how can one achieve that? I'm relatively new and not an expert in OSX.

[Kirk Baker]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

I surely use the last PM beta expiring early july. My OS is OSX 10.5.2 I didn't upgrade to the latest yet.

We are adding code to skip these Spotlight files in the next beta.  But I strongly recommend that you find some way to keep Spotlight from indexing your camera cards.  That is a really bad thing to do.  You only have one copy of the photos on the card until they make it onto your hard drive and for Apple to add a lot of files amounting to possibly several megabytes onto a camera disk just isn't right.  Often when a camera card is pulled out of a camera it is because the card is already full and cannot have any more pictures on it.  Mac OS X 10.5 already added some junk into camera cards with their '.fseventsd' folder for tracking file change notifications, and now they're Spotlight indexing camera cards.  This is just 'asking for problems' in my opinion.

It would be nice if there were some way to keep the OS from modifying the card at all.

It may be that the OS is the cause of other errors being seen by some folks like Michael.

I would also be happy if the OS wouldn't add files but how can one achieve that? I'm relatively new and not an expert in OSX.

I don't use 10.5 very often, but there might be a way to change the Spotlight behavior in the Spotlight panel in the System Preferences.  10.4 allows you to mark specific folders or entire volumes as off-limits.

HTH,

-Kirk

[vAfotoriporter]

I just started having the same errors last weekend.  I noticed it's on multiple cards off 3 different camera bodies.  The files it crashed on was ALWAYS the last file on the card. 

Running OSX 10.5.3.

Are you saying the OS or PM is a beta ??
 I'm trying to remember what got updated recently.

I surely use the last PM beta expiring early july. My OS is OSX 10.5.2 I didn't upgrade to the latest yet.

We are adding code to skip these Spotlight files in the next beta.  But I strongly recommend that you find some way to keep Spotlight from indexing your camera cards.  That is a really bad thing to do.  You only have one copy of the photos on the card until they make it onto your hard drive and for Apple to add a lot of files amounting to possibly several megabytes onto a camera disk just isn't right.  Often when a camera card is pulled out of a camera it is because the card is already full and cannot have any more pictures on it.  Mac OS X 10.5 already added some junk into camera cards with their '.fseventsd' folder for tracking file change notifications, and now they're Spotlight indexing camera cards.  This is just 'asking for problems' in my opinion.

It would be nice if there were some way to keep the OS from modifying the card at all.

It may be that the OS is the cause of other errors being seen by some folks like Michael.

I would also be happy if the OS wouldn't add files but how can one achieve that? I'm relatively new and not an expert in OSX.

I don't use 10.5 very often, but there might be a way to change the Spotlight behavior in the Spotlight panel in the System Preferences.  10.4 allows you to mark specific folders or entire volumes as off-limits.

HTH,

-Kirk

Thanks Kirk, I will try to find out how to do it.

[memoriesbymichael]

Sorry Kirk - Not crashes ... Errors./

I'll research it some more.  Now this really has me freaked out.  Had no idea Spotlight might be the problem.

[Rick Baumhauer]

Open up the Spotlight Preference Pane in System Preferences, then click the Privacy button and add your card reader or camera to the list there.  If you're using a reader, you will probably need a card in it for it to show up in the Finder and allow you to select it in the Spotlight Privacy pane.  Since all of my cards have the same name (created by the camera), I think you'll only need to do this with one card (not positive, though).

[memoriesbymichael]

Thanks Rick .. I'll try that.  I have three stacked readers ... same brand and using 3 different camera bodies.  Mark II, Mark III and Mark II 1DS.

The cards are also 1, 2 and 4 gig .. all sandisks.  It sounds like the card readers will all look the same to spotlight right ??

Michael .

[jax]

i added all of my cards to the privacy section of spotlight, restarted computer and had everything load to the external hard drive first (per email suggestion-What happens if you ingest one of your cards if you swapped your secondary destination drive and your primary destination drive?)
im still getting the error.
i will try the logging version of pm if you would like.

[attachment deleted by admin]

[memoriesbymichael]

No such luck - I just took everyone's suggestion tonight and still had the same problem.  I than noticed Spotlight did not retain the added reader from a few weeks ago.  Are we supposed to add the cards under the Privacy button in Spotlight each time we download or restart.  This used to be my favorite piece of software ... losing faith quickly.

[Kirk Baker]

No such luck - I just took everyone's suggestion tonight and still had the same problem.  I than noticed Spotlight did not retain the added reader from a few weeks ago.  Are we supposed to add the cards under the Privacy button in Spotlight each time we download or restart.  This used to be my favorite piece of software ... losing faith quickly.

I'd prefer to get you a logging version of PM so we can see what is causing the errors.  If you're willing to test a logging version it will help me get to the bottom of your issue.

-Kirk

P.S. The Ingest feature has been used to download millions of images without these sorts of errors happening.  It is the recent release of Mac OS X 10.5.3 that has brought about these problems.  Photo Mechanic 4.5.3.1 did not change spontaneously and it worked fine before the 10.5.3 Mac OS X update.  We're looking into creating a workaround for this issue, but it is likely that the only solution to this issue will come from Apple.