Skip to main content
B
bruce964
Known Participant
August 15, 2019
Answered

Does LR classic require a sata drive?

  • August 15, 2019
  • 2 replies
  • 723 views

I can open and create catalogs on my two sata drives C: and F: however LR will not open or let me create a catalog on my two nvme drives which are installed with a pcie adaptor. coincidence? 😧 and E: if I right click and run the lrcat with LR Classic I get an unknown error-retry box. I have over a dozen catalogs over these two drives and none will work

any Ideas please?

Thanks

Bruce B

I"ve done the obvious:

full control

run as admin

reinstall LR 8.4

Win 10 1903 fully updated

32 GB ram

8 core xenon

rtx 2080 gpu

    This topic has been closed for replies.
    Correct answer Jao vdL

    OK it does seem that the lrcat files are corrupt, I have to replace them with my backup to get into the catalog. replacing everything but the lrcat file doesn't help. If I replace lrcat and the two db files I'm fine. 'cept for the few new pics that haven't been backed up.

    1) Is there guide to what information is in each of these files / folders?

    1a) I'm an old school data nerd, Is there a sufficient description of the lrcat file that might enable me to find a fix? or at least help me figure out why or how I corrupted it?

    2) I assume (dangerous I know) that if I replace the lrcat file with an earlier version, I can import the missing photos?  lucky me, I think, I use  xmp so my edits should be safe and I haven't created any collections sice my last backup. So my exposure is minimal.

    I really don't think Adobe or Lightroom caused the problem, but, I need to what happened  so I can prevent it from happening in the future.

    Care to share one of your paint mine pics?

    thank you

    Bruce


    1) not really but the lrcat file is the heart of your Lightroom catalog.

    This is where all edits and file locations are stored. The previews catalog

    is generated from the originals and the catalog file and is not essential

    but is used to accelerate the display of images in the library module.

    There can also be a folder with smart previews present there.

    1a) the lrcat file is an SQLite database and can be viewed and edited with

    that. That is not for the faint of heart though and it is easy to mess up

    your catalog. If you google around you will find some people successfully

    editing the catalog using these tools but there is no official

    documentation.

    2) yes this should work

    Paint mines pictures:

    https://lagemaatphoto.smugmug.com/Landscapes/Southwest/Paint-mines

    Also check out

    https://www.google.com/maps/@39.01287,-104.2694233,0a,75y,353.32h,70.78t/data=!3m4!1e1!3m2!1sAF1QipNw5fxD7zgdGt5qVM07lskaoV-H4qISTLpoUNxT!2e10

    2 replies

    J
    Community Expert
    Jao vdLCommunity Expert
    Community Expert
    August 17, 2019

    Calhan Paint Mines! There is no incompatibility issue with NVME interfaces AFAIK. Many people run Lightroom catalogs from such drives so indeed something wrong with the catalog files itself it appears.

    B
    bruce964Author
    Known Participant
    August 17, 2019

    LOL, yep its the paint mines. My son and I spent the night there under a new moon. with permission from Colorado Springs of course.

    Yes, I have two problems, how to fix the catalog files and, how did I get it to that state, that one is indeed my problem.

    My plan is to take my known good backup and replace each folder one at a time until I find the culprit.

    The two db files, previews I think must be obvious. If I kill that I can rebuild previews. what is the root-pixels.db? is it recoverable? and what is in the folders 0-E?

    Bruce

    J
    Community Expert
    Jao vdLCommunity Expert
    Community Expert
    August 17, 2019

    Wonderful little known place. Photographed there a few times.

    You should only need the lrcat file (and the originals of course).

    Lightroom can rebuild all the previews and other files

    GoldingD
    GoldingD
    Legend
    August 16, 2019

    I do not have an NVME, so I have not been down this particular rabbit hole.

    I do not suspect this to be an Adobe issue. I suspect Hardware issue, perhaps firmware or drivers.

    ___________________________________________________________________________________________

    I assume that the PCIe card needs a driver, is that working, Is their an updated driver.

    Is another driver needed for the NVME drives?

    Is a BIOS mod required for this to work properly?

    Do you have a conflict with that PCIe card and the GPU card? A possible PCIe Lane Complication? (Check your motherboards manual). Might have to put in a particular slot

    As it is a PCIe card it may be addressing the SATA bus, do you have a conflict with one or the other (if another) SATA Bus? Another Lane conflict? (See Motherboard manual)  (As you are running the drives off a PCIE card, and not a newer M.2 bus slot, are they in fact using the SATA bus?)

    Is a mod in the BIOS required to allow that PCIe card to work properly?

    ____________________________________________________________________________________________

    What particular NVME?

    What particular PCIe card?

    Mfg web pages for them with support info???

    __________________________________________________________________________________________________

    Incidental, per this link:

    NVMe SSDs: Everything you need to know about this insanely fast storage | PCWorld

    Hmm, those NVME are compatible with installing in a PCIe card then a slot, Not the newer ones that need their own meant for bus? M.2 slots?

    And google "nvme drive problem", you will get things like:

    https://www.addictivetips.com/windows-tips/how-to-fix-pcie-nvme-ssd-boot-and-driver-problems/​

    and

    https://www.pugetsystems.com/labs/articles/Overview-of-M-2-SSDs-586/   (see discussion on PCIe Lane Complications)

    B
    bruce964Author
    Known Participant
    August 17, 2019

    Thank you for your suggested reading however; I have come to the conclusion that my hardware is fine and there must be an issue with LR being able to read my catalogs after I migrated them to the nvme drive.

    I can read and write to the nvme drives in Photoshop, office etc. no problems. I did discover I could create a new catalog on the two drives in question. When I tried to import a small catalog to the newly created empty catalog LR said that catalog must be upgraded. after selecting that option LR then offered:

    Well, I don't have 7 any more so I tried again to open in 8.4 with the following results:

    I Then downloaded this project from my backup (only a few images) to my nvme and LR not only upgraded the catalog but opened it as it should. It appears there is something corrupt that LR doesn't like in all the migrated catalogs. 

    So I'm wondering what is corrupt? Under this catalog is the lrcat file, a folder with the images, an lrdata folder with 2 db files, previews and root-pixels. and a series of folders 0-F. 

    Any thoughts please?

    Thank you

    Bruce Bell

    P.S. I just realized these catalogs had worked under the nvme because I had edited and saved this image after the install

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices