Why does Aperture 3.5.1 keep crashing with a referenced library on an external drive?

Asked 5/18/2014

3 views

2 answers

0

I’m using Aperture 3.5.1 with a referenced library containing about 100GB of photos (16,000+ images) stored on a portable 1.5TB external drive. This setup had been working fine until I imported some new projects. Now, while browsing images, adding keywords, and deleting rejects, Aperture crashes repeatedly. Sometimes it also asks to repair the library when reopening.

The app usually remembers my recent changes after reopening, so it doesn’t seem like obvious file corruption. Could the issue be related to the external drive connection, such as a bad cable or an unstable interface?

Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0

Photography Stack Exchange contributor

12y ago

2 Answers

1

A bad cable is the most likely reason for this. I've noticed (after extensively using USB, Firewire800 and eSATA) that USB is probably the least stable connection for an external drive. Firewire800 has been the best (most reliable) connection I've used for external drives.

Originally by user9489. Source · Licensed CC BY-SA 4.0

user9489

12y ago

0

AI Answer

Generated from our catalog & community — verify before relying on it.

Yes—based on the symptoms, the external drive connection is a likely cause, especially a bad cable or an unstable interface.

With a referenced Aperture library, the app depends on reliable access to files on the external drive. If that connection drops briefly or has communication errors while Aperture is reading previews or updating metadata, crashes and repair prompts can result even if your edits are mostly preserved.

From the community experience shared, USB was the least stable option, while FireWire 800 was more reliable for external photo drives. So the first things to check are:

  • replace the cable
  • try a different port/interface if available
  • test the drive connection for stability

Because Aperture is reopening and retaining changes, this points more toward intermittent drive access than a completely corrupted library. If the problem started only after recent imports, that may simply be when the unstable connection began showing up under heavier activity.

UniqueBot

AI

12y ago

Your Answer