bansuri Posted March 20 Share Posted March 20 Hi! Just started transferring lots of old drives to my array via Krusader. All going well - but then when i delved in via my mac I can see that some folders the names aren't transfering peroply. So I checked via the Unraid UI and it's correct but when accessing on my mac they are incorrect. Why could this be? On the screenshot, the left is the Unraid UI which is correct, and on the right is mac which isn't. It seemed to have show as random letters and numbers on my mac. Any help? Quote Link to comment
itimpi Posted March 20 Share Posted March 20 Not quite sure why this is happening, but the names displayed in the screenshot on the Mac are the sort you get when the long filenames cannot be displayed and it reverts to the old DOS 8.3 version of the names. Quote Link to comment
Squid Posted March 20 Share Posted March 20 Can you post your diagnostics. Also, if you delete the .DS_Store file rm "/mnt/user/Personal and Backups/Backups/.DS_Store" and then disconnect and reconnect the server / folder in finder does it show correctly? Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 On 3/20/2024 at 11:26 PM, Squid said: Can you post your diagnostics. Also, if you delete the .DS_Store file rm "/mnt/user/Personal and Backups/Backups/.DS_Store" and then disconnect and reconnect the server / folder in finder does it show correctly? Hi All! I've tried deleting the DS Store file and it didn't work. Here is my diagnostic file.. I'd really appreciate a hand here. Thanks all x tower-diagnostics-20240322-0005.zip Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 I've just realised that on the Unraid UI it doesn't have a location for the folder names that are scrambled... yet I can still open it and the files within. Has this got something to do with it? Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 All the folders that the name are scrambled all seem to not have a "location" in that tab... but can still use and access them. That's the pattern. How can I add a location to them? Quote Link to comment
trurl Posted March 22 Share Posted March 22 1 hour ago, bansuri said: How can I add a location to them? You can't What do you get from command line with this? ls -lah /mnt/user/Personal\ and\ Backups/Backups Quote Link to comment
Squid Posted March 22 Share Posted March 22 Can you install Fix Common Problems via the Apps tab and run it. I *think* you may have inadvertently sent stuff to /mnt/disk3 or something that doesn't actually exist. FCP should show that. Quote Link to comment
Maxrad Posted March 22 Share Posted March 22 I encountered this problem and traced it to situations (copy files via SMB) where the file name or folder name ends with one or more blank spaces. It seemed odd that SMB should mangle the file name or folder name when it ends in a blank space. I wasn't inclined to investigate the problem further or raise it with SMB project. Of course, this might not be the trigger for mangled folder/file names in your situation. Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 9 hours ago, trurl said: ls -lah /mnt/user/Personal\ and\ Backups/Backups It doesn't come up with anything Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 7 hours ago, Squid said: Can you install Fix Common Problems via the Apps tab and run it. I *think* you may have inadvertently sent stuff to /mnt/disk3 or something that doesn't actually exist. FCP should show that. Sadly it came up with no errors Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 I transferred these all of these files using Krusader... shows up correctly in Krusader. Could this be part of the issue? Quote Link to comment
Solution JorgeB Posted March 22 Solution Share Posted March 22 Did you check if they have a blank space in the end? That can cause what you are seeing, you can also try disabling mangled files on Samba, but then, they might no show up over SMB. Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 Maybe it's because when I used Krusader... I went into my share via the MEDIA folder... and then transfered. Instead of directly to the drive and then the share? Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 4 hours ago, JorgeB said: Did you check if they have a blank space in the end? That can cause what you are seeing, you can also try disabling mangled files on Samba, but then, they might no show up over SMB. THIS FIXED IT. Why on earth would this be the problem??? 1 Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 Been deleting the space after the name in Krusader... then re-connecting to the drive in mac and it shows correctly. It also gives it a drive location in the Unraid IU now. Thank you so much. I'm so confused why this would happen Quote Link to comment
JorgeB Posted March 22 Share Posted March 22 20 minutes ago, bansuri said: Why on earth would this be the problem??? Because not every OS can display names correctly with spaces in the end over SMB, so Samba purposely "mangles" the names, to make sure they are displayed. Quote Link to comment
bansuri Posted March 22 Author Share Posted March 22 3 minutes ago, JorgeB said: Because not every OS can display names correctly with spaces in the end over SMB, so Samba purposely "mangles" the names, to make sure they are displayed. Well shows what I know! Thanks so much for this. No idea why I would have put spaces there in the first place but hey... old archive drives for you! Thanks for your help! Quote Link to comment
Maxrad Posted March 22 Share Posted March 22 (edited) Yep, I had a similar reaction. I was feeling incredulous that an "innocuous" space would result in such a loss! Then I just accepted it, renamed a few dozen directory/folder names and file names, and got on with life. "Life. Don't talk to me about life" Marvin The Paranoid Android On macOS I routinely use A Better Finder Rename 12 at several different points in my "managing media for Plex Media Server" workflow. A Better Finder Rename 12 can scan and correct this type of problem before large copies from macOS Finder to Unraid over SMB. Edited March 22 by Maxrad 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.