HELP!!!!! please!!!!!!

I went to update and migrate my photos from the old Light room classic to the new Lightroom CC

 

upon import it errored saying it couldn't find about 5300 photos from all my jobs in 2016...

 

I at first realized they are on my Unraid server i need to mount the drive and now using MacOS High Sierra i need to use Samba and not AFP

 

I mounted the drive and tried again...same error as before.

 

i went to my directory structure and found all the folders (one per job names by date and client) are now all scrambled names like in the attachment. the data seems to there taking space but i each folder appears empty as per my finder view.  I relied on Unraid's parity to protect me from stuff like this.

Is there any way to get my files back? I need them for an upcoming calendar project for the Calgary SPCA. HELP please.

 

 

Edited October 30, 20178 yr by Can0nfan

Do you have a backup or just one copy of your data?

these used to be backed up on about 3 separate drives, moving to Unraid (from Drobo) I thought with Parity this should be safe (cant recall last time I accessed these files but its been at least a month, maybe two), I have two 8TB parity drives.  As for current backups: I have some final copies for my clients (not all of them) stored on my Amazon Drive thankfully but all the original Raw files appear to be gone. I read about xfs repair thats my next step after the permissions check and repair is done.

 

 

any help is greatly appreciated.

Are the photos on a user share or a disk share?  Could there possibly be something wrong with one of the disks on the array?  And you say you have accessed these photos within the last two months using the same stated method above?

they are stored via user share. only difference on how they have been accessed is due to MacOS High Sierra dropping support for AFP and using Samba so updated my network mapping to Samba  I am still waiting on Permissions repair to complete, once completed I can double check the location of the share and what disk they are stored on. I dont know if this helps but I have dabbled with unraid 6.4 rc7 and rc9 both time going back to 6.3.5 but I never used the Hard Drive encryption they added to 6.4

If it's a user share that could very well rule out a disk issue assuming the photos are spread across the entire array.

 

Do you have other means to pull files off the array?  There's always a possibility that the server side is fine, and your client end is having issues for whatever reason.

I have two macs running High Sierra and one VM (windows 10) stored on unRAID both Mac's are showing the same corruption and as the permissions is running the Windows VM is running a bit sluggish but ill check it too and report back.  I find that other folders are ok so I might be just limited to a single disk issue, hopefully a filesystem issue that can be corrected...I have 34TB of data on this Server and it starting to worry me about data protection if I cant trust it for 155GB of photos.

I am going to check what disk the files are on once permissions are done (on disk 10 of 12 so close) hopefully it comes 

ok so some potentially good news.....my Windows 10 VM does have the corrupted folder names denoted the date and client name but it appears all the data inside is readable....phew so far. I can probably get the folder names from the error log migrating the Lightroom database. I just have to wait for permissions to finish so things stop lagging...good call on the format i was accessing them from....I will probably still run a xfs repair once done to make sure the disk these are on isn't failing file system wise thanks Living Legend that was a great idea.

I have a sneaking sensation a lot of the issues might be my PERMS as my itunes folder on the array was locking me out too my wifes is now accessible after perms updated her folder...my library is substantially larger and spread across about 6 drives. so expect that to fix too when the check is done

 

It looks like you have used characters that the Mac doesn't like or too long names. Therefore the name is just showing letters and numbers. 

If you SSH into unraid and go directly to the shares they should look normal. 

 

Regarding parity and backup. They are not the same. Parity is not a backup as it's just failsafe if one of your drives ( or two) dies. It does not protect against corrupt filed. 

So if you value your work, get a backup solution running as fast as you can. 

4 minutes ago, Can0nfan said:

ok so some potentially good news.....my Windows 10 VM does have the corrupted folder names denoted the date and client name but it appears all the data inside is readable....phew so far. I can probably get the folder names from the error log migrating the Lightroom database. I just have to wait for permissions to finish so things stop lagging...good call on the format i was accessing them from....I will probably still run a xfs repair once done to make sure the disk these are on isn't failing file system wise thanks Living Legend that was a great idea.

 

Good to hear, glad I could help.

 

I don't know much about XFS repair.  Something I may need to look into myself since I just ran into a big problem replacing an XFS disk.  It was going bad so I stopped the array and replaced with a new one.  When the rebuild was done, the new disk was under 200GB utilized rather than over 2 TB utilized.  No idea what went wrong.

 

With that said, and to reiterate, I know nothing about XFS repair.  Before running the XFS repair, make a copy of all of those files and place them somewhere that won't be affected (like off the array) if you were to screw something up with your disk.

Just now, Living Legend said:

 

Good to hear, glad I could help.

 

I don't know much about XFS repair.  Something I may need to look into myself since I just ran into a big problem replacing an XFS disk.  It was going bad so I stopped the array and replaced with a new one.  When the rebuild was done, the new disk was under 200GB utilized rather than over 2 TB utilized.  No idea what went wrong.

 

With that said, and to reiterate, I know nothing about XFS repair.  Before running the XFS repair, make a copy of all of those files and place them somewhere that won't be affected (like off the array) if you were to screw something up with your disk.

 

Please don't start to repair anything based on the file names on Mac or Windows. Especially if you don't know anything about it. 

Go check the files in unraid first. 

9 minutes ago, saarg said:

It looks like you have used characters that the Mac doesn't like or too long names. Therefore the name is just showing letters and numbers. 

If you SSH into unraid and go directly to the shares they should look normal. 

 

Regarding parity and backup. They are not the same. Parity is not a backup as it's just failsafe if one of your drives ( or two) dies. It does not protect against corrupt filed. 

So if you value your work, get a backup solution running as fast as you can. 

seem like maybe Mac and Windows dont like the names ......Sierra never had an issue with them as thats how they were in Light room in my local Pictures folder before i migrated them.

 

but you are also right i ssh'd into the server and files names are fine, should i be renaming via CLI to correct them?

 

I do have more than enough external drives floating around the house I will be backing these up multiple times once again. I do under stand parity not being a backup solution for corruption but was still in the mindset that dual disk parity would save me from Hard Drive failures, which it will. I have 

Edited October 24, 20178 yr by Can0nfan

10 minutes ago, saarg said:

 

Please don't start to repair anything based on the file names on Mac or Windows. Especially if you don't know anything about it. 

Go check the files in unraid first. 

 

 

answered my own question.....I was naming completed projects with a folder name of "*** 2016-07-20 <client name> <pet name>"

appears windows and now MacOS doesnt like the *** now...i used mv to rename one and it shows now....

 

 

thanks Saarg you just saved me a lot of stress. now I can do these calendars sell them and donate the proceeds to the Calgary Humane Society.....

now my only problem is lightroom it will be expecting folders with those *** I may have to reimport them into Light room classic and save it all over but at least the files are there.

 

 

thanks.

one last note is on a recovered folder name i used Finder to change it back just to see......and it stays visible. so i found a less stressful solution....I guess that the file name might be been problematic with nano the CLI i used to move the files to the server in the first place.

 

20 minutes ago, saarg said:

 

Please don't start to repair anything based on the file names on Mac or Windows. Especially if you don't know anything about it. 

Go check the files in unraid first. 

 

This.  Last resort for sure.  But seems like you got things figured out.

Good thing you fixed it 

 

Not sure why * confuses Mac, as I thought the same applied as in linux regarding file names, but it might be samba that is the limitation. 

1 minute ago, saarg said:

Good thing you fixed it 

 

Not sure why * confuses Mac, as I thought the same applied as in linux regarding file names, but it might be samba that is the limitation. 

yes I think you're right. it must be Samba, 

when i tried to rename one 

mv ***\ 2016-09-04\ YYC\ Pride/ ***\ 2016-09-04\ YYC\ Pride1/ it didnt error but the folder name in a mount using samba changed...

 

I have to use no *** then i can use Finder (using samba mount to add them back)

 

now its brackets......hmmm got some i put the pets name in Brackets...unraid is confused by this

 

trying to rename this one

 

 

***\ 2016-10-29\ Deanna\ A\ (Dexter)/

 

i get this error

 

-bash: syntax error near unexpected token `('

and now i fixed that..... just needed to add " around the brackets

 

mv ***\ 2016-10-29\ Deanna\ A\ "(Dexter)"/ 2016-10-29\ Deanna\ A\ "(Dexter)"/

 

that worked

 

 

Issue fully resolved unraid side now....thanks for the help everyone!

5 minutes ago, Can0nfan said:

now its brackets......hmmm got some i put the pets name in Brackets...unraid is confused by this

 

I regularly use brackets in filenames (with Windows clients) so I think there must be something else going on.    I can understand that * caused a problem as that is a reserved character in filenames on Windows, but brackets are not).  

 

You need to be careful though if using the command line as then brackets might well have special meaning if not escaped depending on the tools you are using.

EDIT:   I see you have worked this out already!

Edited October 24, 20178 yr by itimpi

Just now, itimpi said:

I regularly use brackets in filenames (with Windows clients) so I think there must be something else going on.    I can understand that * caused a problem as that is a reserved character in filenames on Windows, but brackets are not).  

 

You need to be careful though if using the command line as then brackets might well have special meaning if not escaped depending on the tools you are using.

just needed to add " around the brackets

 

mv ***\ 2016-10-29\ Deanna\ A\ "(Dexter)"/ 2016-10-29\ Deanna\ A\ "(Dexter)"/

Jack thanks you all for recovering him....