Reloading LR After Reformatting- Help Again?

  • Thread starter Thread starter Boris G
  • Start date Start date
Status
Not open for further replies.
B

Boris G

Guest
LR fails to load on this clean install of OSX1'.6. The error message that "the program has failed to be installed, call the manufacturer" came up. It worked beautifully before. Is this something that I need to clear up with cust. serv.? Or is there a fix? Please tell me I don't have to call cs. Thanks
 
Sort by date Sort by votes
Re: Reloading LR After Reformatting

Welcome to Lightroom Forums Boris!

Do not load from the original Lightroom 2.' disk as a bug was reported for that one. Instead, download 2.5 and install it. There is no need for LR2.' to be installed first.
 
Upvote 0 Downvote
Re: Reloading LR After Reformatting

Thanks, it worked! But now I'm trying to add the catalogue and re-link it with the photo file in the proper order. Can you help with this? Again, thanks.
 
Upvote 0 Downvote
Hi Boris, welcome to the forum!

So how far have you got? The catalog you can just transfer back, and double click to open. And then it's just a case of relinking - are the folders in a nice tidy hierarchy, or have you got a long list of folders?
 
Upvote 0 Downvote
Thankfully, the single catalogue in question is only 5K big. However, I think that some how, it has been corrupted and I will need to simply import all the photos from the (actual) photo backup drive, use them without all the refinements of Lightroom, and begin a new catalogue altogether (with a view to being more careful next time): But, if I can save this catalogue, of course, I will want to do so.

With respect to the actual photos, though, is it necessary to import them after you click on the backup Lrcat as you have mentioned above (putting the corruption issue aside for the moment)?
 
Upvote 0 Downvote
Do not "use" the backup. You want to keep it safe from any modification. Rather make a copy of this backup elsewhere from the backup folder and rename this copy to a sound name. Then open this copy.

There will be no need to reimport as everything will be in the state it was at the moment the backup was made. This backup is simply an exact copy of the working catalogue with a dated name.
 
Upvote 0 Downvote
[quote author=Denis Pagé link=topic=8358.msg56697#msg56697 date=1258'49815]
Do not "use" the backup. You want to keep it safe from any modification. Rather make a copy of this backup elsewhere from the backup folder and rename this copy to a sound name.
[/quote]

“Elsewhere” ... as in : the backups should be on different physical media than the originals. Backups on the same hard disk are not backups — if this disk crashes, you have zero copies of your precious photos.
 
Upvote 0 Downvote
Well, I just meant to make the copy of the backup at another place than the backup directory itself. Boris is not talking about making backups at the moment but recovering from one. That said, it is a good recommendation for any future backups to be made on another drive.
 
Upvote 0 Downvote
[quote author=Boris G link=topic=8358.msg56693#msg56693 date=1258'45133]
With respect to the actual photos, though, is it necessary to import them after you click on the backup Lrcat as you have mentioned above (putting the corruption issue aside for the moment)?
[/quote]

5k as in 5kb? Yeah, that sounds empty. Perhaps you have another catalog on one of your drives somewhere? Might be worth a look.

If you are able to find and open an existing catalog, then no you won't import, you'll just relink the catalog references with the new locations, if the photo location has changed.
 
Upvote 0 Downvote
Thanks to everyone.

I have 4-5''GB internal disks on machine and 2-2 TB external disks in Raid config., so the actual photos are well protected and I do have multiple copies of said catalogue as well. I just need to determine which are actually corrupted and which are OK.

Using your advice, I will attempt to re-introduce a good copy of the catalogue back into Light room and, perhaps, rub my lucky rabbit's foot!

The 5K is the # of photos in the subject catalogue. and while this only a portion of the total, it's certainly worth rescue. I'll post once more to let you know how it turned out.
 
Upvote 0 Downvote
As it turned out I had several problems that had nothing to do with Lightroom [which really saved my bacon]. Even though the backup software corrupted the backed-up lrcat and since the original had been erased in the formatting process, I needed to create a new catalogue and import from the actual photo files . Despite the fact that I no longer have the ideal pre-format Lightroom setting for this catalogue, I have a very accessible Lightroom "folder" complete with all the sub and sub-sub folders in the lefthand Folders Panel. Now, for shots I will soon take in Tibet and Nepal, I'll start from a whole new catalogue and take extra care when toying around with backup software. The upshot of all this is that Lightroom is an amazing program and it can be entrusted with very valuable photos. Enough said!
 
Upvote 0 Downvote
How sad it is! :(

We always tell everyone to backup but always forget to also say that it is important to make recovery tests. :eek:
 
Upvote 0 Downvote
That's the best advice , certainly. I think that Time Machine lulled me into inattention. Up until now I'd always used PCs and this Mac Pro just made things too easy. 'Once bit, twice shy', as they say! :-[
 
Upvote 0 Downvote
Aaaaaah, Time Machine. Yes, there are incompatibilities if TM backs up while the catalog's open (Aperture excludes itself for the same reason). If you can find a backup that ran while LR was closed, it'll probably be ok.
 
Upvote 0 Downvote
THAT'S good to know! I have tried "Super-Duper" ( I know, the name ) and it seems to make accurately copied and bootable partitions for my photos. However, I hope Apple sees fit to improve it's "Time Machine" so that it stands down when Lightroom is open.
 
Upvote 0 Downvote
It's not Apples problem. Any open, transactional database will be corrupted if it is copied. Practically all backup software would have the same issue. This is why Adobe give you a utility to backup the catalogue before it is opened.
 
Upvote 0 Downvote
I would assume that the LR team will put a block into LR to automatically exclude it from TM while it's open at some point too.
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top