After lots of research and study... no answer found - here or elsewhere, so:
Bulit a new computer. First: Win7 Pro, 64-bit OS. Old rig was Home Premium 64-bit, but I would be surprised if that was an issue. Moved to an Ivy Bridge i7 3770 processor, so new motherboard and OS. New bigger SSD for the C drive, and of course a fresh OS install. To move LR, I studied all the steps from posts here and elsewhere but the initial "migration and reawakening" of LR4 is not appearing to follow one part of the usual scenarios.
I don't see the little symbols on thumbnails -- that show metadata is associated with the picture -- as the re-connection proceeds. Perhaps that is normal, but that worried me so I stopped the process. Here are some details:
I use a large internal drive for photo storage, holding all Lightroom-managed images in a top-level folder called "Lightroom". There are a bunch of folders underneath that level which were managed by LR4 for a coupe of weeks on the previous rig and before that LR3.5, LR2, etc. I bought a newer drive (same make and model of 2TB drive) as part of my move to the new motherboard and copied all the old hierarchy to this newer drive. Last night, as the final step for the transition I reassigned letter "E:" to this new drive, the same letter that had been used by the old data drive and therefore the letter in the LR paths for each photo. To repeat: LR4.1 had been used on the older motherboard and had used this "E:" hierarchy successfully. I figured that Lightroom's ".lrcat" file was holding metadata for all images partly based on finding it in the same path. I figured it would be easier to "find" images if the drive letter was the same.
I clicked the ADD SOURCE "+" symbol and added the "Lightroom" folder on "E:" After some time chugging away it displays to me a suggested import of those pictures from this big folder and subfolders that it feels are not duplicates. Disturbingly, some of these I think should have already been in the database. But more importantly, among the many grey-out images there are *no* little metadata markers on any images greyed out to show that LR thinks they are duplicates. So maybe the metadata didn't make it. Not good if so.
I have canceled the Add operation. I actually didn't expect the Find Missing…" operation to look like an "Import" operation.
My ".lrcat" file is 649MB for about 60,000 images. When LR came up in the new OS it told me there were 56,000 images misplaced. The associated preview file is 22.4Gig and has 74,000 files and over 44,000 folders. I did look for the previously-established keywords and they seem to be there, but in an operation I am told I cannot associate any metadata during the "Add" so they aren't showing in the right pane during the "Add" which I think of as a "Find".
Perhaps this is just the interface not showing the associations with metadata. But the apparent use of the Add function worried me, too, despite the greyed out images that I guess are "found".
Thanks, in advance, for any help.
To move LR, I studied all the steps from posts here and elsewhere but the initial "migration and reawakening" of LR4 is not appearing to follow one part of the usual scenarios.
Perhaps you could tell us exactly what you did, what you saw in those posts, what steps you followed, as this is uninformative.
It sound from the rest of your post that you are using some form of the Import dialog box, where you have (or tried to) imported photos. That is the only way I can interpret this information. Please confirm.
The appropriate method of moving a catalog and photos from one computer does not involve using the Import dialog box. So before we can diagnose if you did the right thing, you have to tell us what you did.
There are several ways to move a catalog and photos, and it sounds as if you moved the photos themselves properly. If you did that, and the photos are in the exact same path as they were in on the old computer, then you would also move the catalog file (and associated presets and preferences) to the new computer and then double-click on the catalog file.
dj, thank you for such quick reply.
At the beginning I said I had tried to learn as much as I could to be ready, and that no material I read talked about this particular interface question. I used too many resources to try to reprise them here. I do know that what I was trying to accomplish was not an import, and that is why I gave the steps.
I had to reconnect the LR database with the files on what was a new drive with the same-as-old-computer letter assignment and folder hierarchy. I invoked a "Find Missing" command, NOT an Import, and that is why I was concerned and stopped the process. I wanted confidence that my data was intact to be connected to these images, as I did not see the little symbols that usually display at the corner of the images. But I knew that I was in the middle of the whole move process and perhaps they do not show in that step.
I see above that I left out a step I took. Here's an abbreviated list of what I did:
1. Copy entire Lightroom folder and subfolder hierarchy to new HD in new machine. Retain its reative position on the drive hierarchy. (a top-level folder under root)
2. Make sure the last-used version of ".lrcat" and ".lrdata" files is in the exact same location in folder hierarchy.
3. Start LR4 on new machine from this file.
4. LR4 tells me I have 56,000 missing photos.
5. I click the "Add" symbol at the upper right corner of the left pane to get the Lightroom folder on the "E:" drive to show among the drives in that pane, because it was not there.
6. Right click the "Lightroom" folder and pick "Find Missing Photos" from the context menu.
7. Process moves along and then I have what looks like and is labeled as an "Add" interface, with isome thumbnails displayed normally and many grey images. Looking at the left pane I see what appears to be the full hierarchy I previously had in LR4 on the older rig.
8. I notice no metadata symbols on greyed images I know where cataloged with names, etc. But I can't remember if there EVER were such symbols on a grey image. Grey image to me means "already in the database".
9. Last step: wonder if there is a problem with the metadata. Perhaps I am worried needlessly.
Sorry I didn't capture some screens.. would have helped. Pretty sure I have the steps correctly noted and in order...
Thanks, again for tackling the question.
At step 5, you wouldn't have wanted to click the Add button. What you really want to do is right-click on the top-level parent folder and select "Update Folder Location". In the dialog you would select the matching top-level parent folder on the E: drive.
Do you think I should have seen the metadata symbols in the grey-out images?
Your answer makes sense to me but I remember being surprised that I didn't see ANY sign of the drive assigned "E:" as that had been the drive that housed the Lightroom Folder. So I had no top-level folder or drive to click on for Find Missing.. or "Update Folder Location".
So if I don't see the E: drive or, better, the folder on E: named "Lightroom", what is the best way to force it into view in the left pane?
Thanks for helping. I'd love to get this functioning tonight. Pictures to edit!
The simple way to get your new pictures drive showing, is to tell LR that the existing pictures within your Catalog are now located inside that drive.
So you will need to first see all the old folders that are listed in the "wrong" place; and then to re-address them so as to correct "wrong" to "right". You do not need to use "find missing images" because you already know what is missing. You can directly address the top containing folder involved, and LR fixes all the contents of that on the same precedent.
The "update folder location" command shows you an operating system file-browser dialog giving access to all the drives that your computer can see, regardless of whether these currently show in LR, or not.
But this is not the Import (Move / Copy / Add) dialog and you will not see any images, greyed-out or otherwise, while you do this. You are just identifying a different location for the folder concerned, by name.
IOW, you are not re-inserting anything afresh; just correcting what is already present.
Completing this procedure will automatically show this other drive inside LR, of necessity - since images within the Catalog are now known by LR to occur on it. All the image folders will start showing in this new place, and correspondingly, will stop showing in the old place.
However if you have already removed these "apparently missing" folders from your Catalog, you will need to instead use a prior Catalog backup that still includes them - for example, by re-copying your prior Catalog across from the old PC.
The presence of the metadata "badges" should be unaffected through this, since the Catalog retains the underlying content unaffected; but note that firstly, the display of these badges is optional - and secondly, if the Filmstrip is reduced small enough, no badges are displayed there.
Hmmm.. Well, one thing that stands out above others: your drive mapping probably didn't work right.
You see, if your old images were stored under E:Lightroom, and you copied everything to a new hard drive, exactly as it was on the original, then renamed that new hard drive E:, lightroom would have never complained about missing images.
So something in your "copy" went wrong.
I would start over, and use some type of copy tool and recopy everything, including the catalog file onto your new blank drive. Then unassign your old drive (you did that first time, right?) and assign your new drive. To your file system it should now look like your new drive is in the exact place the old drive was.. i.e, you can't tell the differnce.
Then simply start up LR, and it should be happy. No "find missing files" or "reconnect" needed, as it's all in the same place.
If that doesn't work, then you have another problem somewhere, perhaps you aren't assigning the drive name properly, or you have not copied the drive contents into the same locations. Check this out before you start digging around in LR. And above all, do NOT add, move, import your images, or all edits/flags/keywords will be gone!
Up early out here in the middle of the Pacific and good food for thought for breakfast... thank you for these replies. I am glad for the reminder that the little metadata badges might not have been set to show, anyway, and I did know that I was on the wrong path when I saw these Add screens. Process canceled. The lack of badges made me wonder if the metadata was intact in the catalog file.
Jasonized, I was shooting for that instant recognition goal, which is why I copied the original "E:" drive under the control of the OS (no other tool) and then disconnected the cable for that old "E:" drive. Is this achieving unassignment? The relationship between hardware and OS software can be mysterious sometimes; there are a few differences between the copies, although the LR folder is at the same place in the drive hierarchy. I may have taken the opportunity to delete some drive content elsewhere that I thought didn't affect the hierarchy, as I had that goal in mind.
Before I tried to start LR on this machine I undertook to reassign drive letters using Computer Management. (I had been setting up and installing some programs for a few days and made the mistake of letting the "E:" assignment end up elsewhere.) Thus: several letter shifts throughout the drives to bring the drive full of images to the "E:" position. Would not have thought this would confuse Lightroom. The OS seems happy enough...
richard, Your suggestion seems like my next step, and Jasonized's idea as a Plan B.
Very helpful, all, Aloha and thank you.
Hmm... No, simply disconnecting a drive will not "unassign" it, as you found out having to move other letters around. :} But successfully assigning another drive to E: would take care of it.
Your problem might be permissions based, since you say the OS can see E:Lightroom just fine but inside LR you can't see it. Win7 pro uses ACL's, I think, to control access.
Are you sure you didn't accidentally assign it an alias, or a shortcut, and are looking at somewhere else physically?
Those are basic thoughts, things to check.
I just migrated to a new RAID array and was having the exact same problem as described by Jonathan above. Your answer in post #3 (what to do in step #5) worked like a charm! Thank you for your help.