Annoying error when trying to move recently imported files to a folder

[Zack attack]

Hi folks,

First time posting here.  Really hoping someone can help me with this.  I am trying to add photos already on my external hard drive to my LR catalog and then into specific folders by year.  After attempting to move the recently imported photos to a folder, I get this message: "There was an error copying files to the destination you selected."  I have a late 2015 macbook pro running Catalina 10.15.7.  LR version is 11.5.  I did the thing where you go to security and privacy to give your computer full access to LR, but that didn't work.  It's super frustrating, and I don't understand why this is happening.  I'm trying to add both Raw and jpeg--no weird file extensions.  Everytime I think I've gotten the hang of LR, something else trips me up.  Thanks for your time.      

[Sameer K]

Welcome to the Lightroom Community. I'll help you figure this out. I understand you cannot update to a newer version of Lightroom Classic.

Try this step on the external drive, where the images are stored.

• Search for Disk Utility from Finder's spotlight search or magnifying glass.
• Run 'First Aid' diagnostic on the external drive. Check this to learn more: https://support.apple.com/en-us/HT210898
• Restart the computer

Let me know how it goes,

Thanks!
Sameer K

[Zack attack]

Thanks for the response.  Unofrtunately this did not work.  I was on the phone with Adobe monday and today, and I was told the issue is with my external hard drive needing to grant permissions to read and write files.  I guess I have to call the manufacturer of my drive now.  Such red tape.  Makes me want to just give up.  

[Sean McCormack]

When you import are you using Add, Copy or Move? 

[Zack attack]

I'm choosing add. Called Glyph today and they had me try some super technical code stuff, but they think it's a software issue. Idk at this point.

[Sean McCormack]

I'm not sure why granting 'Full Disk Access' didn't just fix it as it sounds like a permissions issue. Given that you're using Add and the files aren't even moving, I can understand why it's confusing. 

Do you have space to move the files and reformat the drive? 

[Zack attack]

They're moving into the catalog but not when I try to move them into a sub-folder(ex. 2019). The glyph drive came pre-formatted for Mac, and I've never had this issue before. Tons of space available on the drive. Glyph suggested moving the files and reformatted the drive as well. Seems like such a simple task I'm trying to do. 

[Sean McCormack]

You could try using Copy, and using a dated folder option, but this really does sound like a permissions issue that may be fixed with a reformat. 

[DdeGannes]

@Zack attack ,

You stated, "They're moving into the catalog but not when I try to move them into a sub-folder(ex. 2019)."

When you use the Add option to import image files to the Lightroom Classic Catalog the image file remain in the Folder of your computer system. The Lightroom Catalog file does not contain image files or copies of the original images. The Catalog file is a data based file and only contains information about the image files, location, metadata, and edits done with the images.

[Sean McCormack]

@DdeGannes I believe @Zack attack is discussing moving the files around inside Lightroom after Import via Add. They're aware the files are on the external drive. 

[DdeGannes]

@Sean McCormack, 

I am only dealing with what Zack stated and do not wish to assume!

There are no image files in the Lr Catalog.

[DdeGannes]

I am attaching a link to a source of Lightroom Classic video tutorials by Julieanne Kost a Lightroom evangelist who has multiple free videos tutorials where I am sure you will get the info you need to solve your problem.

https://jkost.com/blog/lightroom-training-videos

[DdeGannes]

@Zack attack, If you have not sorted out your problem could you take a screen capture of the Library module Folder structure which shows the connected external drive and those on your main drive. Also the 2019 folder you wish to move the images into. See the screen shot below. Make sure you use the insert photo icon so the picture displays in the body of your post.

[Zack attack]

Thanks for linking Julieanne Kost's videos.  I remember watching some a while back.  I'm posting some screenshots of my file structure on my drive(my entire catalog and photos are on the drive) and the popup I keep receiving.  I honestly don't know what to do anymore.  Very discouraging especially when I'm paying for the software.    

[DdeGannes]

@Zack attack , Ok the selected image is showing in the Previous Import collection.

What happens if you click and hold on the central part of the image then drag and drop on the folder you wish to send it to?

I am not seeing any indication that the external drive is connected to your Computer. Did you remove the external drive after you added the images to the Catalog?

[JohanElzenga]

Select the image and then choose 'Photo - Show in Finder'. That will select the image in the Macintosh Finder. Press Cmd-i. That will show you the info dialog for this image. Check that the image is not locked, and check its permissions at the bottom of the dialog.

[Zack attack]

Thanks for chiming in.  I have read and write permissons on all these images.  When I click "show in finder," the photos show up under the bulk folder of my drive.  

[DdeGannes]

@Zack attack , Just another thought, I know you stated in your original post " I did the thing where you go to security and privacy to give your computer full access to LR, but that didn't work. ".  This may be a play on words, however with recent macOS versions Apple Security and Privacy preferences require that you allow Lightroom Classic to have "Full Disk Access " to your macOS system. It is no longer sufficient to have read and write privileges to specific folders. See the screen capture.

When you make changes to your Apple Operating System Preferences you need to Power of your Computer and then reboot.  Doing Restart will not work.

[JohanElzenga]

No, there is no need to power off the computer. There is even no need to restart it. Restarting Lightroom should be enough to apply the 'full disk access' permissions you've just set. Please note that the screenshot is a pre-MacOS Ventura screenshot. In MacOS Ventura this looks different (there is no padlock, for example), but the functionality is still the same and the need to give full disk access still exists. https://www.solve.uk.com/post/how-to-grant-full-disk-access-in-macos-ventura

[DdeGannes]

@JohanElzenga , The author stated in the initial post "I have a late 2015 macbook pro running Catalina 10.15.7.  LR version is 11.5.". 
There is no info in the thread to suggest this has changed. Maybe this is creating problems.

My checks indicate that the MacBook Pro late 2015 can run macOS 11 BigSur, so if it is upgraded it will also be able to upgrade to the latest version of LrC. See the screenshot.

[JohanElzenga]

OK, I did not check the first post again. But other people read this thread too. That is why it is useful to point out that in MacOS Ventura this has changed a bit. And that a reboot is not required.

[Zack attack]

I recently upgraded to Catalina.  Waited a while becuase I wanted to make sure all my apps would still fucntion properly.  I also do audio production.  I can't recall ever encountering this issue when using High Sierra, and I also don't have this problem when importing from an SD card.  At this point, I'm not sure what to do.  Re-formatting the drive is an option others have brought up, but I don't want to do that if I can avoid it.  That said, shutting down my mac didn't solve the issue.  A lot of others also have this issue.  Hopefully we can all find a fix.

[DdeGannes]

Could you show a screen capture, like the one I posted to show if your Apple Preferences > security and privacy has been sellected to allow "Full Disk access to Lightroom Classic"?

[Zack attack]

Okay folks,

I think I figured it out finally! I don't know if something happened when I called Glyph and they had my do some technical stuff in terminal, but I noticed that my name was not under the sharing and permissions section of my drive.  Therefore, I added my name and updated the permissions to read and write and now it's working!  Hooray!  Feel like I just won a contest!  Cheers everyone.  Thanks for your help and suggestions!  

[Sean McCormack]

I did think it was a permissions issue. Glad to hear it's sorted and I can more than imagine your joy and relief.