Lightroom Classic 8.2: Moved from external drive to SSD, now I can't see edit history in Develop module

  • 1
  • Question
  • Updated 1 year ago
  • (Edited)
Wanting to improve Lightroom Classic CC8.2  performance, I moved my Lightroom folder containing my catalog, backups, previews and smart previews to my desktop SSD from an external drive.  All my photos remain on the external drive.  I copied the folders with Windows Explorer.  Lightroom Classic CC found my photos on the external drive.  Everything looks good except that I no longer see any develop history in the Develop Module.  The grid display in the Library module show icons indicating the photo has been cropped, edited, keywords, etc but the Develop module shows no history.  I cannot figure out how to resolve this as I would like to see the history.  It also appears that the SmartPreviews folder has not been touched since I moved the folders using Windows Explorer.  I do not use the cloud or Lightroom CC.  My pc runs Windows 10.   I have backup files and I renamed the previous used files on my external drive in case I had a problem.  One other thing to note:  the Develop Module Histogram is showing "original Photo" and at least one of my photos is indicating Process Version 4 and has an option to update to current Process Version.  Any ideas on how to proceed? Thank you!
Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Dan Hartford Photo

Dan Hartford Photo

  • 456 Posts
  • 215 Reply Likes
Please tell me you didn't re-import the images after moving the catalog from the EHD to the SSD.

If you did not re-import the images,  after copying or moving the catalog folders to the SSD,  are you sure that when you start LR that it was actually picking up the moved catalog?  Please verify (catalog preferences).

When you say there is no history, are you saying that there is only one line in the history panel that is the original import?    Is this true on all the images (check a dozen or so in different folders)


Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes
Hi and thank you for your response.  I did not re-import the images after moving the catalog.  LR is using the moved catalog - verified.  In terms of the history panel, for any photos before Feb. 16, 2019, there is no develop history.  For example, this photo is missing the initial import and crop actions in the history.

Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes
Hi Dan, I'm sharing two additional screenshots.  And just to make sure I was clear in responding to your questions, I have checked several folders for Develop Module History Panel information and I found that the history information was missing for all photos I checked except for photos taken on or after February 16, 2019.  The two screenshots I am sharing are 1.  of the histogram in the Develop Module.  Not that the information is reading for the original photo.  2.  A picture of the same photo from the Library Module Grid view.  You can see the indicator for keywords, GPS coordinates and crop.  The keywords and GPS coordinate information is in Lightroom, but not the Develop History showing that I cropped the photo.

Photo of Dan Hartford Photo

Dan Hartford Photo

  • 456 Posts
  • 215 Reply Likes
Very odd indeed.  It's kinda smelling like a corrupted catalog.  Did anthing unusual happen on Feb 16?  Perhaps a power failure while LR was running?  Maybe a system crash or unplugging the EHD without ejecting it first?   

Do you, perchance, still have the catalog on the EHD?   If, so can you launch that catalog and see if you see the same problem there?   If so, go back to a catalog backup taken prior to Feb 16 and see if the problem is there as well.  If you don't have a copy of the catalog on the EHD, then use a backup taken just before and just after 2/16 and also just before and just after you migrated the catalog to the SSD.  At least that should narrow the problem to something on 2/16 vs the EHD to SSD migration.

If that brings no joy,  take one of the problematic images and export as catalog (including original RAW files) into a "temp" catalog.  Then import it back into LR using the  "import from another catalog" (if it complains about a duplicate image you may need to actually open the temp catalog and rename the image in the folders panel".  See if the re-imported image has the history.


Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes
Hi Dan, thank you very much for your reply.  I really appreciate your suggestions and assistance as I was reluctant to move forward without a second opinion.  I had looked at a backup on 2/28, that catalog had the same issue.  Your question about something happening around 2/16 is a good one.  I just looked at my files and found a corrupt catalog file folder.  Sure enough, there is a file in the corrupt catalog folder dated 2/18.  The images on 2/18 and after have the appropriate Develop history information.  I will try your suggestions in the morning and report back on my success.  Thank you for your assistance.

(Edited)
Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes
Hi Dan.  I think my initial problem was a corrupt catalog issue.  Now I have one more follow up question.  I was able to restore a catalog from a backup on the EHD (catalog date of 2/10/19).  All the edit information is available in the Develop module.  I copied this same restored catalog to the SSD and the edit information is also available in the Develop module.  So, I don't think the SSD migration was the issue.  

My follow up question is (and it's a dumb question)... I had imported images into the corrupt catalog after 2/10/19.  Do I need to import these images into the restored catalog?  Some of these images have .xmp files with them.  Do I need to do anything with those?  Should I try exporting the most recent images from the corrupt catalog as a catalog and try to import them?  I really appreciate your assistance.  Thank you!
Photo of Dan Hartford Photo

Dan Hartford Photo

  • 456 Posts
  • 215 Reply Likes
Yes,  the best is what you said last.  Export the newer images "as a catalog" from the corrupt catalog to a temp catalog (without the original image files).  Then open the recovered older catalog and import those images using "import from another catalog" and select the temp catalog.  This should make you whole except for images added between 2/10 (date of recovered catalog) and 2/16 date of corruption as they are probably corrupted but missing from the recovered catalog.  You may just have to re-import those.
Photo of Erin Wilson

Erin Wilson

  • 6 Posts
  • 0 Reply Likes
Thanks Dan.  I exported the newer images as a catalog and then imported the temporary catalog to the catalog restored from backup.  I decided that I can live without the edit history for the images between 2/10 and 2/16, even though 2/15 was the day I photographed the bobcat behind my house.  :)  I really appreciate your assistance to get me back on the path of productivity.