Skip to main content
tylers73957003
Participating Frequently
May 21, 2025
Question

Lightroom causing SSD error?

  • May 21, 2025
  • 3 replies
  • 917 views

To start, my Lightroom catalog is pretty big (23k+ photos) -- I know, I should probably start a new one. Everything (catalog files + photos) is stored on my 2TB SSD (sandisk), which is almost entirely full (~100gb remaining).

 

Last night, while editing a photo in LrC, Lightroom closed unexpectedly. At first I thought it was an issue with Lightroom, but then I realized my SSD was no longer recognized by my computer (which is a Mac mini w/ latest update). After taking it out and plugging it back in, assuming I had maybe nudged the connection, it no longer showed up on my computer, nor my other MacBook. Only after plugging it into a windows would it appear needing "repairs." After running the repair, everything seemed fine -- I could see it on my Mac after plugging in, all photos were seemingly there, and LRc opened. I assumed it was a one-off. But then, when I went to continue developing a new photo, the same thing happened -- LrC started spinning, it unexpectedly closed, and my drive was no longer showing as connected to the computer, nor could I reconnect. I repeated the same process to fix it, but now I'm not sure if it's my drive, which is only a few months old, or Lr. 


Has this happened to anyone else? Is it because my SSD is so full and my catalog is so large it just crashes? Again, not sure why that would cause the SSD to eject, but I'm not a tech guy in that regard. I have the catalog backup copied to another drive, and plan on migrating everything to a larger drive later today. Any thoughts on why this happened?

  

Latest version of LrC, latest OS for Mac, 3-4m old 2TB sandisk ssd 

3 replies

KR Seals
Community Expert
Community Expert
May 21, 2025

This definitely sounds like a hardware problem. Some of the possiblities are: 1. Defective cable to the external drive. 2 Defective USB-C/Thunderbolt connector on the Mac. Some of the  San Disk Pro SSDs were defective, but yours does not seem to be one of those.

Don't discount the possiblilty of the connector/port on the Mac being bad. Out of my three last MacBook Pros, two had bad USB-C connectors. Those were relativly new machines.

You don't mention having a backup drive. Do you? It's probably time to upgrade your photo external drive to 4TB and get another (preferably different brand) for your photo backup. You should also backup the LrC catalog everytime the app closes to a totally different drive than where the catalog is located.

 

 

Ken Seals - Nikon Z 9, Z 8, 14mm-800mm. Computer Win 11 Pro, I7-14700K, 64GB, RTX3070TI. Travel machine: 2021 MacBook Pro M1 MAX 64GB. All Adobe apps.
tylers73957003
Participating Frequently
May 21, 2025

Yep, have a 4TB Samsung SSD on the way right now that I plan to migrate everything to. I thought as well that it could be the cable to the ex drive, but would that explain why this is only happening when I access LR? As of now (after having made "repairs" on a windows computer), I can see and interact with the drive perfectly fine through finder. However, it's once I open LrC and attempt to edit that the whole thing happens again (LrC closes, drive missing from finder, can't see it again until I repair on a Windows). 

 

And you're absolutely right, I don't currently have a backup for my photos (stupidly) but I plan on doing that as well now. It was always something I meant to get to, but kept pushing off. Any tips on how to do that? Is it just as simple as routinely copying my image folders over to a new drive, or is there a specific program that would help be more efficient? I know keeping the folder paths/hierarchy the same is what LR wants if I should ever resort to using those photos -- or am I mistaken?

 

I will also now be saving my catalog backups to a separate drive, because again, I was not doing that...

Conrad_C
Community Expert
Community Expert
May 21, 2025

Just for context, for many years I’ve been working with Lightroom Classic on my MacBook Pro, with the photos on an external volume. First with hard drives, now with SSDs. My catalog is now over 150,000 photos, and it’s rock solid (crashes and SSD disconnections are rare). So the problems you are having should be solvable, and should not be directly related to using SSDs, number of photos in catalog, etc.

 

One thing to try: After using Windows to repair it so it can be mounted, next open Apple Disk Utility. Select the SSD and click First Aid, to see if there are any Mac-specific file system issues that Disk Utility can fix that might have been missed by Windows.

 

In case it’s a defective cable, definitely experiment with different cables, as long as you use one that supports the speed of the SSD.

 

quote

And you're absolutely right, I don't currently have a backup for my photos…Any tips on how to do that? Is it just as simple as routinely copying my image folders over to a new drive, or is there a specific program that would help be more efficient? I know keeping the folder paths/hierarchy the same is what LR wants if I should ever resort to using those photos -- or am I mistaken?

By @tylers73957003

 

You are correct, you want the backup to exactly mirror the folder organization that you use for Lightroom Classic. That way, if something happens to your working SSD, you simply get the backup and copy the same folder organization back to the replacement working SSD. 

 

And no, it is not as simple as copying the folders yourself. It can be that simple for the initial backup. But a backup is only useful if it’s kept current, so how do you do that? You don’t want to manually figure out which images are new/changed, and then manually drag them over, because that’s tedious and prone to error especially since you could change hundreds of different images in a session.

 

Apple has its built-in Time Machine backup feature, and that is one way. It updates the backup every hour. If you enable Time Machine, I think by default it does not include external volumes so you would have to add them. You will also have to understand how to restore an external volume from a Time Machine backup, because it’s different than restoring the Mac’s internal volume. 

 

However, I do it in a different but also common way that’s existed since before Apple created Time Machine. I use reliable, proven Mac backup software (Carbon Copy Cloner) that can maintain an exact copy of any volume or folder. You can also use other Mac backup apps like SuperDuper! or Chronosync, they will work just as well for this. 

 

For the first backup, whatever software you use will simply copy the whole volume to the backup volume you designated.

 

For subsequent backups — this is where you save time and effort — the software analyzes the working and backup volumes, and lists every difference (new and changed files). It then copies just the files that changed. This is called an incremental backup. (Time Machine does incremental backups too.) By automating incremental backups, it takes only a minute or two to update your backup so that it is once again an exact copy, and you don’t have to think about it at all. You just push the button and it does it.

 

You might not even have to push the button to update. Many backup apps let you schedule backups so that it updates the backup at the time interval you specify. Of course this works only when the backup volume is connected. I like to keep my backups disconnected and in a locked fire safe so that if something happens to the computer like a fire, burglary, or computer crash, it doesn’t take the backups with it.

 

Software like Time Machine can save multiple versions of a file over time, so that if the current version is screwed up you can roll back to an earlier one. But this means the multiple versions on the backup will use more space than the original files. So if you use a backup app that maintains versions, get a backup drive with more capacity than the original.

GoldingD
Legend
May 21, 2025
stored on my 2TB SSD (sandisk)

'What model?

tylers73957003
Participating Frequently
May 21, 2025

Sorry, it's a 2TB Saidisk SDSSDE61-2T00-G25M

dj_paige
Legend
May 21, 2025

To start, my Lightroom catalog is pretty big (23k+ photos) -- I know, I should probably start a new one. 

 

Not big, don't use that as an excuse to start a new catalog.

 

Last night, while editing a photo in LrC, Lightroom closed unexpectedly. At first I thought it was an issue with Lightroom, but then I realized my SSD was no longer recognized by my computer (which is a Mac mini w/ latest update). After taking it out and plugging it back in, assuming I had maybe nudged the connection, it no longer showed up on my computer, nor my other MacBook. 

 

Obviously, this is a Mac/Hard disk problem and not a probelm caused by LrC

 

Is it because my SSD is so full and my catalog is so large it just crashes? 

 

Unlikely, but we don't know how full your SSD is. Can you tell us? Size of the catalog would not cause this, and in fact, people have catalogs 20 times larger than yours and they run without problems.

tylers73957003
Participating Frequently
May 21, 2025

Not big, don't use that as an excuse to start a new catalog.

 

Alright, well that's good to hear. I enjoy having everything in once place since I'm always referencing older work so starting a new catalog definteily wasn't something I was looking forward to. In January, I did have an issue where my orginal catalog that I started in 2020 was corrupted. Luckily, for the most part, I was able to start a new one on my own with all the same files and develop history after a long and tedious export process. This new catalog has been running smoothly ever since, until now. 

 

Unlikely, but we don't know how full your SSD is. Can you tell us? Size of the catalog would not cause this, and in fact, people have catalogs 20 times larger than yours and they run without problems.

 

Currently using 1.81tb / 2tb. It's showing there are 189.55gb remaining. It is a Sandisk SDSSDE61-2T00-G25M.