LR3 catalog nightmare

Oy.
Power went out last week.  I was in the middle of a "write" action during an edit at the time.  The LR catalog was trashed because the Drobo S drive master index file became corrupted.  The drive could be seen by the Drobo Dashboard, but not by OSX.  At the suggestion of the incredibly nice and excellent Drobo support staff, and was able to copy the totality of my image files off of the drive to two backup drives (some to one drive, some to the other).  Because of the amount of folders and files (over 72000 images) I was unable to maintain the file tree exactly as it existed on the Drobo.
I successfully reformatted the Drobo and copied all of the images in their respective folders back to the reformatted Drobo, HOWEVER, because of the volume of folders and my extreme pain and suffering experienced at the prospect of losing 70000+ images, I neglected to write down the exact tree structure.  I am now using a backup of the LR catalog that is from 24 hours prior to the drive SNAFU.  Since the directory tree is now different from the one in the .LRCAT file, is there an easy way to have LR find all of my files while preserving my edits?
(I did NOT ever turn on the option to write changes to the XML file.)
Any and all suggestions will be appreciated.
Thanks,
David
P.S. If any of this is unclear, I can try to restate the problem.

A couple of suggestions:
- Use the Library > Find Missing Photos command to find all the missing photos.  Locate one of the missing photos and select the option Find Nearby Missing Photos, which will reconnect all the photos in the same folder.  This is described in detail here:
http://help.adobe.com/en_US/Lightroom/3.0/Using/WS3BC0B0A1-D48C-4271-891D-DA04EF388E29.htm l
You'll have to do this once for each folder.  Tedious, but at about 30 secs per folder, you'll get it done in a couple of hours.
- If you're a techie: Use the LR/Transporter plugin to dump a text file containing the file paths of each photo in the catalog. Use your favorite scripting language to recreate the folder tree and move the photos into the appropriate folder, disambiguating any photos that happen to have the same filename by using file size or any other clues. This approach will probably end up taking you longer than the first one (but no programmer can resist taking twice as long to automate something that could be done faster manually).

Similar Messages

  • Error message while importing upgraded LR3 catalog to new LR4 catalog

    I'm using a Win7 x64 system, 3Ghz Xeon dual core, 8 GB ram system.  After upgrading a LR3 catalog to LR4, it would not display all images in GRID VIEW in the upper level folders.  i.e. D:/Photos/2011.  It will display the images in the 2011 folder but not in the Photos folder.  And yes I do have the "Show Photos in SubFolders" selected. 
    By importing this updated LR4 catalog to a new LR4 catalog the display problem disappears.  However, I get an error message at the end of the import saying that "Lightroom could not import this catalog because of an unknown error."  This occurs after it says it is importing updated keywords.  But, as compared to the LR3 catalog, the new LR4 catalog shows the correct number of images in the catalog, shows the correct number of collections and seems to have all the keywords in the keyword list panel. 
    Because there seems to be some sort of catalog database upgrade error, I am hesitant to use LR4 for production at this time.  Does anyone have any suggestions as to what this error might be, or a work around for the error so I can be confident in my LR4 catalog?
    Thanks,
    Tony...

    I've pgraded to LR4.1 RC1 and then created a new catalog, imported from my original LR3 cat. It updated that temporary cat and then imported to the new LR4 cat without issues or error messages. I then just did an upgrade to my original LR3 cat and saved it in another location. Upgrade went without hitch or error messages and I am now using that catalog.  So far, so good with the new candidate.
    Tony...

  • I deleted my LR3 catalog from my MAC IHD; how do I relaunch fromEHD? relaunchfrEHD?

    I inadvertently deleteted my LR3 catalog from my Mac internal hard drive. The catalog is situated on an external hard drive. I tried to relauch the catalog into LR but have not been successful. I would relish any advice you can give me. Thank you, Peter

    Well to tell you the truth, I'm not sure I understand your situation.
    First you say you deleteted (yes, that's your word) the catalog accidentally. Then in the next sentence you say "The catalog is situated on an external hard drive", present tense, as if you are speaking of a different catalog file that you actually have available. So, I think this is a COPY of the catalog file.
    Apparently I misunderstood.
    Your catalog file is accidentally deleted. Then, I would say you are in dire straits, and I now give you different instructions.
    First, look in the trash can/recycle bin. If it's not there, then:
    Second, in Lightroom, try File->Open Recent and see if your catalog can be found that way. If that doesn't work:
    You need to downloand and install and run something called an "undelete utility". There are freeware versions available on the internet. This utility may be able to recover deleted files. However, this is crucially important — do not use your computer for anything else except this task. The more you use your computer, the less likely it will be that the file can be recovered. So, this is so important I'm going to say this again, in bold: do not use your computer for anything else except this task.
    Lastly, whenever you get this fixed, you need to adopt a comprehensive and regular backup plan that includes your photos and your catalog file.

  • Lr4 Install+AVOID lr3 catalog possible?

    Just downloaded the Lr4 final
    Had to search around to see if the beta was to be uninstalled. Never did find that info.
    At this time I do not want to merge or connect to the Lr3 catalog. Is there a distinct choice to accomplish that while installing Lr4?
    The beta version took over the file association of .Ircat so attempting to open an old Lr3 catalog was stopped with the message that it did not fit with Lr4
    Is this the expected behaviour post install Lr4?
    Rose

    eswrite wrote:
    A colleague of mine can't access his 3.x catalog after LR4 installed and converted his catalog. In my case, I can access either the old 3.x catalog using LR3.6 or the converted 4.0 catalog with LR4. Is there a reason for his 3.x catalog somehow being gone or inaccessible?
    No reason as far as Lightroom is concerned. Perhaps he uninstalled LR3.x?? What exactly are the symptoms of "can't access"?
    His main concern is that point curve edits he had made in 3.x are gone from the 4.0 catalog. I've read LR4.1 should recover those. Is that his best way forward?
    These two paragraphs are not the same thing at all. Unrelated to one another. Mark me down as confused.
    Anyway, yes the LR4.1 Release Candidate fixes the point curve issue.

  • Does LR3 catalog roll automatically into LR4 on installation?

    I installed LR4 and now have LR3 and LR4 catalog in the path: Mac HD>Users>me>pictures>Lightroom.  Do I need to keep the LR3 catalog. I'm not sure how to tell if it is redundant or not?
    My question: Can I delete the LR3 Catalog? Is the LR3 catalog  automatically brought into LR4 upon installation? 
    Thanks,
    Rima

    I would keep the Lr3 catalog for a while until you are sure that everything is OK in Lr4.
    As long as Lr3 is not un-installed, you can use it to check things out as they were in the Lr3 catalog.
    Lr3 cannot read the Lr4 catalog, so as long as you have the Lr3 catalog you can check things out in Lr3.
    But refrain from doing any work in Lr3 because it would be saved in the Lr3 catalog while Lr4 works with the Lr4 catalog. So your Lr3 catalog should be "read only" - only for checking things.
    Once you are sure that everything is fine and accounted for in Lr4 you can delete the Lr3 catalog and un-install Lr3.

  • External Lacie drive crashed, now I can't find a recent backup for LR3 catalog.

    I have LR3 on a Mac running OS 10.6.8.  My catalog, cache and images were stored on an external Lacie 1TB drive (partitioned so it can be used by a pc and mac).  My catalog backup files were saved on another external drive MXTR as well as copies of all my images.  The Lacie had started self ejecting while running LR3 and I thought it was maybe a problem with the cable, as it would work fine after rebooting.  Yesterday it crashed LR3 and never remounted.  I used Disk Utility to try and repair the disk and it instructed me to erase the disk and start over.  I was not worried, since my catalog was backed up to another drive.  10 hours to erase the drive (the drive never quit during this time).  Another 2 hours to copy my images from the MXTR to the Lacie (again the drive never self ejected during this time either).  So now I go to find my most recent backup catalog.  The most recent one I could find was dated 2/09/2012.  I am baffled.  What happened all those times I was backing up?  I upgraded to LR3 in 2011, and I don't remember ever telling it to backup to another folder or drive. 
    Any ideas as to what the problem may be?

    What happened all those times I was backing up?
    We can't possibly know what happend or where your backups are. But you can indeed search all of your available hard disks and see if there are any files named *.LRCAT with recent dates.
    By the way, I would be extremely wary of using that Lacie drive any more. If it was me, I'd replace it.

  • Upgraded LR1 - LR3 Catalog: blank Grid, non functioning app

    I've been dealing with support on this, but they're utterly useless, taking days to get back to me and spinning me over troubleshooting 101 stuff.
    Problem:
    Upgraded a perfectly working LR1 catalog to LR3.  No issues during upgrade.
    Upon trying to use the LR3, the first thousand or so of my photos show up in Grid, but everything after that is blank. By that I mean, a grid cell is drawn, but LR3 doesn't display a thumbnail, or any cell extras or metadata.
    Clicking on one of these empty cells gives me a thumbnail frame and some metadata (slowwwwly).
    Going to Loupe View on a non-empty cell gives me a "Loading..." spinner and an unrendered thumbnail preview (CPU is not ramping up at all)
    Going to Loupe View on an empty cell just gives me a blank screen (CPU is not ramping up at all)
    Develop module does load the picture, but slowly.
    When I quit, the app freezes up completely, with beachball.  Must force-quit (after giving it 20 minutes in case it was actually trying to do something)
    Initially, when I load LR3, my CPU runs high, 75%, like it's working on something.  Then it just cuts out as if it's given up.
    Console output when this happens is the following:
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERRORSERVER<AsyncDataServer( Lightroom 3 Catalog.lrcat )>: A command threw an exception.
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERROR Error: ?:0: attempt to perform arithmetic on field '?' (a nil value)
    6/17/10 7:27:38 PM Adobe Lightroom 3[518] Error initializing alternate universe. bad argument #1 to 'pairs' (table expected, got nil)
    System:
    MacBook Pro Core2Duo 2.1Ghz 3GB RAM, 500GB Drive.
    Initially Mac OS 10.5.8, but I tried upgrading to 10.6.3 and 10.6.4 (no luck).
    Library: 21,000 photos
    Other things I've tried:
    Trashing all LR3 prefs, caches (running YASU), LR preview caches, plists, extensions, reinstalling, restarting -- no luck
    Noticed it was copying the LR1 prefs plist, so I archived that.  LR3 generated a new pref, but no help
    Downloaded LR2 Demo, upgraded LR1 Catalog to LR2 Catalog (which works perfectly, no issues), and then LR2 Cat -> LR3 -- no luck
    Checking integrity of Catalog in LR1 and LR2 (no problems) and LR3 when upgrading (no problems)
    LR3 runs fine on an empty catalog and if I point it at my photo folder and import everything, it's ok (with none of my 3 years of modifications of course).
    Is my only option to write out LR1 data to sidecar files and then setup a new Catalog in LR3?

    Well, on top of having full access to the photo files, LR obviously has proper permissions to affect the files it generates in the AppSupport>Adobe>Lightroom folder, the Caches>Lightroom folder, the Pictures>Lightroom folder and the Preferences> folder, otherwise it wouldn't be able to build a new catalog, new prefs, new caches and so forth when I generate a new empty catalog.
    I really doubt this is a permissions voodoo issue or a monitor profile issue.
    LR3 works fine with a brand new catalog (and all the same Photo files).
    LR1 and LR2 have absolutely no problem with my catalog and photo files. 
    LR2 upgrades my LR1 Catalog without issue.
    LR3 fails with my upgraded catalog (and all the same photo files)
    Unless I'm missing something in my logic tree here, it seems to me this is obviously a problem with LR3 upgrading my Catalog. 
    Other people's catalogs upgrade fine, and that's dandy, but my catalog doesn't upgrade AND it fails with exactly the same error message every time in the Console (See original post), which seem to be related to some internal db issue, dividing by zero, nil values. 
    Something ain't being handled right by LR3 that previous versions of LR had no problem with. 

  • CS5 not updating LR3 Catalog properly on return

    Hi, 
    I'm going crazy with what looks like a bug in the SW - but may be operator error. 
    Starting in LR3 Grid view that is filtered on a keyword, I select a JPG.   I want to create a PSD copy that has a text layer and have the PSD staked on top of the JPG in LR when I return from CS5.  I had been doing this in LR2 and CS3 but it does not seem to wrok the same with LR3 and CS5.  I can't recall exactly how I got this to work in LR2 & CS3 but I belive my steps were similar to the following.  The main difference is that in LR2/CS3 it worked and in LR3/CS5 I have the problem indicated below. 
    Here are my steps...
    1)  I right click on a JPG image (in the LR3 grid showing images filtered on a keyword) and select edit in Photoshop CS5.  I then select "Edit a copy" from the popup (I've also tried "Edit a cooy with LR adjustments")
    2)  This creates a 2nd jpg file with "edit" in the file name on my hard drive and opens the image in CS5
    3)  I add a Text layer to the photo. 
    3)  I then close the image in CS5 and it asks if I want to update it and I say Yes
    4)  I then get the "Save As" dialog and save the image as a PSD which saves a 3rd image on my HD as a PSD (does not have "edit" in file name)
    5)  I then go back to LR and I see in the filtered grid that I now have my original jpg, and an "edit" jpg, marked as 2 of 3 and 3 of 3 - but no PSD
    6)  However, if I unfilter the grid, I see all 3 images,  the original jpg (3 of 3),  the "edit" jpg (2 of 3), and an a psd (1 of 3) 
    7)  Now, here's what's driving me crazy....  All 3 images have the exact Metadata, including the exact same keywords which means that all 3 should have been visible in the filtered view.
    8)  OK,  so I now refilter the grid on the keyword that all 3 images in that stack have but only the 2 jpg's show up.  This is crazy.  All 3 should be visible.
    9)  So, I go back and unfilter the grid again, revealing the PSD along with the two jpg's.
    10)  Now, I remove the keyword from the PSD (uncheck it in the keyword list),  then add the same keyword back (check it in the keyword list), and again filter by that keyword
    11)  Now I have all three images visible with the PSD on the top of the stack. 
    Q1 - Why did I have to remove and re-add the keyword to get the PSD to show up in the filtered view?  Is this a bug?
    Q2 - Is there a better way to go to CS5 and create a PSD hopefully without having a 2nd JPG created as well?
    Q3 -  Is there a way to add a text overlay in LR3 directly to the jpg without having to go to CS5 at all?
    Appreciate any help anyone has.
                       Thanks -- Dan

    Thanks, but I guess PSE works differently.
    I don't get a place to specify TIFF or PSD format when the image is passed to PS
    Here is also some new info.
    I applied all the latest "updates" to the LR3 and CS5  SW and now the symptoms are different.
    1)  When I "edit in CS5"  I no longer get a jpg created on my HD
    2)  When I "close" the image in CS5,  it asks me if I want to save it.  I say "yes" and it gives me the "Save As" dialog with PSD preloaded in the file type, the original folder preloaded in the location, and the file name is preloaded with the original name pluse "edit".
    3)  After saving, I flip back to LR and my filtered grid and here is what I find.
    a)  There is no image selected in the grid.  In other words the original jpg file is no longer selected (highlighted) and no other image in the grid is either
    b)  All the info in the right panel seems to be for the psd.  For example, the File Type says "Photoshop Document" and the Metadata Date is seconds ago.
    c)  All the keywords,rating stars, labels, title, caption, etc are present as well and the same as the jpg which is what I would expect.  This indicates that the LR catalog has been updated.
    4)  Unfiltering the grid makes the PSD visible and it is 1 of 2 with the jpg being 2 of 2 which is correct.
    5)  Both images have exactly the same keywords as evidenced by no "*"s in the Keywording section, and all the other keywords having a check mark (when both images selected) rather than a dash.
    6)  Even after synchronizing the psd metadata from the jpg metadata, re-applying the grid filter which happened to be in effect when I went I sent the jpg to CS5, still does not show the PSD file in the grid.
    7)  Howevr, filtering the grid by a different keyword that both images have in common does show the psd in the grid.
    8)  The only way (so far) that I have been able to get the psd to show up in the grid when the grid if filtered by the orignal keyword is to unfilter the grid, then uncheck that keywork in the keyword list, then re-check it.  After doing that it now appears in the grid when filtered by that keyword.
    It seems that the logic that decides which images to show in the grid based on the filters is ignoring the keyword that the grid was filteredby when the image was sent to and returned from CS5 - but is only ignored for the returned psd image. 
    I'm pretty sure this is a bug.  Does anyone know how to report a bug to Adobe?
    Thanks -- Dan

  • Importing LR3 catalogs into LR4

    What's the quickest way of creating new catalogs for LR4.  I have over 30 active cats for each client.

    Probably via File> Open Catalog in LR4 Brian. You'll be prompted to upgrade the catalog. This moves the LR3 Previews to LR4 too.

  • LR3 error when import PSE8 catalog

    Hello,
    can anybody help me? I used PSE5 for years and like to upgrade now to LR3 (catalog >13,000 pictures). As LR3 cannot import PSE catalogs, I installed PSE8 and converted my PSE5 to PSE8. The catalog works fine in PSE8, I optimized the catalog and already checked for errors (repair) - no issues found. I installed LR3 trial and used the function upgrade catalog. LR3 recognizes my PSE8 catalog and asks to upgrade it. But this doesn't work ! After 5 min at approx. 50%, the upgrade stops with the error "cannot upgrade catalog" and the message that an error occurred but no further info. I can only choose "show in explorer" or "select other catalog" or "Cancel". What can I do to identify the problem? I have no idea. Anybody knows is there is anywhere an import log file?
    Thank you very very much for your help!
    Matt
    PS: Windows 7 Home Premium 32bit, Intel i7-860 2,8GHz, 4GB Ram, 500GB HDD, catalog on local ntfs drive

    Summary (June 26th)
    I started the original post and still have no solution. What is the current status:
    1) The issue happens whether you use PSE7 or PSE8. It seems no solution to convert the PSE7 catalog to PSE8 and then trying to import into Lightroom 3. Users report that this wont help.
    2) Adobe is aware of the issue.
    3) I sent my catalog to Adobe but did not get any solution. They contacted me several times, which was a friendly nice contact with Becky. But the engineers did not contacted me as announced, not even a single time.
    4) The Lightroom 3 Beta tester discount was only valid till June 18th. This option is over now because I did not liked to buy a software that potentially wont work.
    5) I cannot recommend to contact the Adobe support directly via your support plan. Its just awful ! They do not have a clue at all, they do not know about the actual problems. They ask you funny and time wasting questions like to reinstall Windows or reinstall Lightroom and so on. Really annoying in my case was, that the said: "This is a trial, we do not offer support." They never answered my question "How should I try the software, if its not working?" and never offered a solution. Not even offered to contact the engineers or report a bug. The only help I got was trough this forum. Really bad job Adobe. Really really bad. (The software costs ~300 Euro !!)
    6) Thanks to everyone in this blog! We do the job that Adobe should do, testing their software. I loved Adobe and I fully agree that mistakes happen, but the way Adobe handles this is close to unaccaptable (I had really much trouble to migrate from PSE5 to PSE8. Also in this case forget about the support.)
    Best regards,
    Matt

  • Remedy to photos in both LR2 and LR3 Beta Catalogs?

    I don't mean to repeat the prior discussions, but I have a problem that appears common, and I want to ask whether the experts think my proposed solution is going to work.
    I have lots of pictures in my LR2 catalog.  I upgraded to LR3, and they came in fine to become the new LR3 catalog.
    I joined the LR3 Beta2 just a couple of weeks ago. I imported a single shoot into LR3 Beta that was already in LR2. I was anxious to try the noise reduction and sharpening, which are both a huge improvement over LR2.
    As predicted in these Forum threads, the duplicated shoot does not come into LR3 from LR3 Beta2.  I would like to make this shoot part of my LR3 catalog.  My question is: can I acheive that result by removing that shoot from the LR3 catalog, (but not from my drive) so that the duplication is gone. Would that cause the catalog to come into the LR3 catalog from the LR3 Beta 2 catalog?  Is there any other step I must also take?  Please let me know.
    Thank you.
    Larold7

    My question is: can I acheive that result by removing that shoot from the LR3 catalog, (but not from my drive) so that the duplication is gone.
    Yes.
    Would that cause the catalog to come into the LR3 catalog from the LR3 Beta 2 catalog? 
    Yes.

  • How to merge or upgrade the PSE8 catalog into the LR3 master catalog?

    I did some searching but wasn't able to find a good match for the issue I'm trying to resolve.
    I have recently installed LR3 after using LR3-beta, and had also been using PSE8 as my main photo library. After installing LR3 I used the "Upgrade Photoshop Elements Catalog...." to create a LR3 catalog of all photos that were in PSE8 catalog. In doing so LR8 created a separate catalog (Lightroom Catalog-2.lrcat) for these photos. However, I would like all photos in one catalog in LR8 (preferably in the LR8 master catalog: Lightroom Catalog.lrcat). Is there a way to either merge those 2 catalogs, or is there a better way to add the PSE8 photos into the LR3 master catalog? Thanks.

    Thanks for the reply.
    Tried that - while in LR using the master catalog, I selected the other catalog (Lightroom 3 Catalog-2.lrcat) and received the following pop-up box:

  • Unable to import Beta2 catalogs in LR3

    Hi,
    I did not see any topic about my problem.
    I had both LR2.6 and LR3Beta2 installed; I saved both complete catalogs and then installed LR3 complete final version.
    Due to file sizes, I initiated LR3 catalog with LR2.6 data with no issue.
    But when I want to import LR3B2 catalog, it fails with this error message (translated from French) : "Lightroom cannot import this catalog due to unknown error" (while searching for files in double).
    Unfortunately, I cannot open this catalog at all, the B2 has been removed from the computer during final release install !!
    Thanks in advance for your support
    Kind regards

    If you have a folder of images, say My Pictrures/2010/Vacation_in_France, present in both the catalog you import (A) and catalog being imported (B), Lightroom will fail to import from catalog.
    You have to remove that folder from any of the two catalogs (A) or (B), before importing (B) into (A).
    EDIT: Here's a related thread: http://forums.adobe.com/message/2886682#2886682.

  • Can I keep my Lightroom 3 catalog on a PowerMac hard drive with Apple Partition Map

    I want to keep my LR3 catalog on a HD in my Power Mac (Intel chip) that I had formatted and used to store my pre-LR3 photo folders on my G5 tower. The 1TB drive is half full, and was formatted as an Apple Partition Map. On swapping the drive into an empty bay in my Power Mac, I can open photos saved on the drive, although I can't seem to rename them. I created my brand new LR3 catalog on the drive as well, but haven't done anything other than import the LR3 catalog I had already created and exported from my MacBook. Other than the drive not being bootable on my Intel Power Mac, are there any risks to managing my LR3 catalog from this drive? Or should I only keep my LR3 catalog on a GUID partitioned drive?
    This HD is not of course my startup drive, but only to be used to store my photos.

    Oops, I should have used "Mac Pro" to describe my Intel machine, not "Power Mac"

  • LR3 Import dialog - Missing "Show in Library" option when importing existing photos

    Please add the option "Show in Library" into the right click menu when attempting to import a photo that already exists in the LR3 catalog. It was a convenient feature in LR2 to jump directly to the existing photo. In LR3 I must cancel the import dialog and search the photo manually.
    LR2
    LR3
    Maybe someone has a workaround?
    Thanks
    Andreas

    Thanks Sean.  Your reply worked.  I found them in the wrong drive.  Now I'll see if I can fix it.
    Charlie

Maybe you are looking for