Lightroom CC 2015.12 Integrity Check - used to take seconds now takes minutes

  • 1
  • Problem
  • Updated 1 year ago
I have used the same catalogue for years. Only 3500 photos. I delete the history. The catalogue is only 70MB in size. It has always passed the integrity check in seconds. Now, just suddenly, it takes minutes.

As has been suggested by others facing this issue, I made a new catalogue and imported the old catalogue. This fixed the issue on the day that I did it, now, returning to the catalogue a few days later, the issue has returned.

Again, as others have found, there is low CPU usage and disk activity. It's almost like nothing is happening.

I worry that there really could be an issue with integrity with this catalogue.
Please help !

Lightroom CC 2015.12
MacOS 10.12.6
2016 MacBookPro, 16GB RAM, 1TB SSD, 4GB VRAM
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
  • frustrated

Posted 1 year ago

  • 1
Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
Why are you deleting the Develop history? This may in fact be why the integrity check is taking longer. Do you do this before each catalog backup?
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
No, just like once a year. I don't need the history and it made the catalogue come down from 300MB to 70MB. It's an option within the program. I'm not doing anything outside Lightroom.

I haven't cleared the history in some months so I would doubt it's related. This issue just came on. The integrity check has been instant for years and now it seems to hang. Which is concerning.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
If it only take a "few minutes" (2-5 minutes) I wouldn't be concerned. Try closing all applications and reboot your system. Open just LR and and see how long integrity checking takes this time. I assume you have ample free space on your 1TB system drive and your LR catalog is located on that drive, correct?

You might also check for missing image files, which may cause integrity checking to take longer. In the Library module Catalog pane select 'All Photographs.' Next go to menu Library> 'Find All Missing Photos.' Relocate any missing photos or simply 'Remove' them.
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
Thank you for your suggestions.
Yes, only Lightroom is open. Loads of free space. No missing image files. I really do try and keep things lean and trim :)

The catalogue is located on a Thunderbolt 3 external drive so that I can work on another machine if I need to. Though, its always been on an external drive. The last drive I used was Thunderbolt 1 (for about three years) and never had an issue.

What is interesting is that making a new catalogue and re-importing everything fixed the issue. I opened and closed the catalogue quite a few times that day, backing up each time so I could check, and everything was instant. I really thought it had been fixed. Then today, back to waiting ...

My concern is not specifically the time, but that the process suddenly jumps in time from seconds to minutes. And I would hate to lose my catalogue for some reason related to integrity. It could have happened with the last release (a month or so ago) of Lightroom, though I'm not sure.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
You don't mention restarting/rebooting your system. If you haven't tried that please do. This clears out system memory and often resolves unexplained issues.

I just checked my LR catalog  with 35,000 image files and it only took 15 seconds for the integrity check and ~ 3 minutes total for the backup. However my catalog is on an SSD. Copy the LR catalog folder over to your 1TB SSD, open LR and go to File 'Open Catalog,' and select the LR catalog .lrdata file on the 1TB system drive. See how long it takes for the integrity check and backup on the SSD.
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
Thanks very much for your reply.
The Mac gets rebooted everyday and I'm afraid that doesn't make any difference.

I did just try the catalogue from the SSD and it is quicker. I guess it should be as its 10x faster than my HDD. 2000MB/s vs 200MB/s

I'm not so much worried that I have to wait a few minutes, I'm concerned for the sudden increase in time that either points to a genuinely failing catalogue or just that Lightroom has started doing this process a little differently/less efficiently recently.

If it is some sort of integrity issue, I wouldn't know what to do about it. Which is worrying.

The fact, though, that you can fix the issue for a day or so (by creating a new catalogue), and Lightroom blazes through the integrity check, suggests that Lightroom is having some kind of issue with something other than integrity problems? I'm not sure. 

If it had always taken minutes with an HDD, for the last several years, then it would be no concern.

Sorry to bother, thanks again :)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
No bother glad to help. There have been similar reports of integrity checking all of sudden taking much longer. Some think it's due to a change in an update, but then there would be a lot more complaints. Do you have 'Store presets with this catalog' checked in LR Preferences? If so that might be the cause....don't know!

One other thing you can try is to select 'All Photographs' and then File> Export as a catalog.' Make sure to NOT check 'Export negative files,' which will create copies of the original files.
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
Yeah. It is odd. Over the years I can see the odd post on the forum that could to be the same issue. But its really hard to track down what the issue is.

I don't store presets with the catalogue.

Okay. I just followed your suggestion. I went into my catalogue, selected all the images and chose ‘Export as Catalogue’. I then went to exit Lightroom, which brought up the backup prompt. So I ran it. The catalogue that took minutes the other day, completed in seconds. So the issue really does just come and go. I have no doubt that the the slow integrity check will return, but I’d love to know the cause of this.

The catalogue that I just created via ‘Export as Catalogue’ looks the same as the original. However, it took minutes to integrity check rather than seconds. Its so random.

I don’t really think that the integrity check hangs, as such, because disk activity continues throughout. But something slows it up considerably. I’m kind of hoping that this is just software related rather than genuine integrity problems. Surely such problems would not get exported into newly created catalogues? And surely a corruption issue would not come and go like this?

Just FYI, there is no antivirus running in the background, Time Machine is not running etc. I don’t think that this issue ever occurred when I used a LaCie 3TB d2 Thunderbolt 1 / USB3 disk. It may not be related but the current disk is a G-Tech 10TB connected via Thunderbolt 3.

Thanks as ever.

Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
As a benchmark how long does the integrity check take on the G-Tech 10TB? When you place the catalog file on the system SSD how long does the integrity check take and is it consistent when you try it multiple times?
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
The external drive was always pretty much instant. Its a pretty small catalogue. Now it often takes a minute or two. But then, it will just surprise you and be done in a second or two, like I found in my last post. It doesn’t seem to be that the first integrity check will be the quick one. Or the fifth one (when testing). Just random.

The internal SSD is difficult to gauge because of its speed. Every integrity check is under a second. Maybe it would vary if I tested enough times. But it didn't vary whilst testing just now.

Either the speed of the SSD is hiding the issue, or the issue is only with an external HDD.

I will try and do more testing if I get time. Just trying to be sure my catalogue is okay ^^

Thanks again ~

Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
I just tested my LR catalog with 35,000 image files using a WD MyBook USB3 external drive. It has about 1/2 the R/W data transfer rate of my SSD. I got the exact same times as the SSD: 15 seconds for the integrity check and ~ 3 minutes total for the backup. I ran the external drive backup three times with the same results for all three backups. You might want to try another external drive and see if the results are similar to the SSD. Is so you may have an issue with the G-Tech 10TB drive. Perhaps try a different Thunderbolt cable and/or port.
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
Hi Todd,

Well, surprise Adobe CC 2018 release eh ^^ Anyway, I have not upgraded Lightroom yet. I thought I would try and pin this issue down before that.

Just incidentally. It seemed curious to me that your SSD was not at all faster than your internal HDD. I just wondered. Occasionally when doing this kind of test, I have found that when you copy a catalogue to a new location and do a backup with the original backup location still attached, the new backup often goes there instead. When you get the ‘perform backup’ prompt come up, make sure that it really is going to the new location. Anyway, that ‘may’ be why your SSD showed no difference.

Anyway, I have done some more testing. My original LaCie 3TB USB3 still has the Lightroom catalogue and all the DNG files on it, though about two months since it was last updated. I did a backup on this and got the usual instant integrity check. Yay!

I then copied this known good catalogue to my G-Tech 10TB Thunderbolt 3 drive, opened the catalogue, ran a backup, and got the stalled 2 minute backup. I then tested this drive over its USB3 interface and got the same stalled integrity check. I then copied this to another identical G-Tech 10TB Thunderbolt 3 drive and got exactly the same issue. In fact I have four of these drives and they all hang the integrity check! So the problem is not the catalogue or one particular G-Tech drive. It seems that this model of drive is at fault.

It seems incredible but I have tested it over and over with multiple drives. The old LaCie is instant and the GTech drives take about two minutes. Time to call G-Tech :/ I'll report back.

Thanks again for your help.

Photo of Todd Shaner

Todd Shaner, Champion

  • 1135 Posts
  • 366 Reply Likes
Please let us know what you find out from G-Tech. As an FYI I installed LR Classic along-side LR CC2015 (Advanced Option during install) and it converted my catalog with ~35,000 image files. The catalog backup with LR Classic took 1:25 versus 3:00 with LR CC 2015.12. It's much faster! This is with my LR Catalog on an SSD and LR Backup folder on a WD Black Caviar HDD.
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
Well, I did a variety of tests for G-Tech and found that the issue was 100% repeatable using multiple units of that model of G-Drive. It didn't matter what Mac, version of MacOS, or interface I used, when I ran the catalogue from the G-Drive, I got a stalled integrity check. If I run the same check from any other medium, it is instant. Internal HDD, external HDD, internal SSD, USB flash drive - all instant.

Even though the only piece of hardware that seems to cause the issue is the particular model of drive, G-Technology said that they couldn't help and that the issue must be due to my system
Photo of yowayowa

yowayowa

  • 13 Posts
  • 1 Reply Like
That's odd. Only half of my reply here... I'll continue.

Im summary, I guess the issue could be with Lightroom or something else. Though, as the only consistent element seems to be the model of drive, it is hard to blame anything else at this stage. I do feel that G-Tech have been less than professional here. It's a premium drive aimed at Mac users. I'm using a pretty new Mac, which, incidentally, must be one of relatively few computers to actually include this drive's main interface, Thunderbolt 3. Hardly an odd or unique system.

Anyway, I guess I will have to leave it there for now. Many thanks for helping to troubleshoot the issue ~