On my Mac mini, I’m copying a directory tree to an SMB mounted shared drive on my truenas server (a terramaster F4-424 pro).
Many, but not all of the file names are in Japanese. Many of the Japanese-named files are failing to copy over. I get this error message:
8/11/24 14:26:36 Unable to create /Volumes/public/RiekosFather/YasuoJimboPhotos/Dell Image Expert イメージ/2003 07 25: No such file or directory
This also occurs when copying via rsync.
Can you send me a system debug via private message?
1 Like
This sounds like a clear case of SMB Share MacOS Client Limitations When Using Decomposed Unicode Characters, see also: NAS-108622 and NAS-100787
I’m new to this system.
- How to send a private message?
- How to generate a system debug file outside of the bug reporting dialog in the TrueNas GUI (which I saw after my original report on-line)?
System->Advanced->Save Debug
Again, I don’t know how to send a private message.
However, dak180’s reference to “SMB Share MacOS Client Limitations” seems to describe the problem to a T. Besides the problem with Japanese (and seemingly around some of the katakana and hiragana with tenten (eg diacritical marks) it also have a problem with some European characters like é.
So the solution here is to go the TrueNas SMB settings under “System Settings/Services”, and edit the SMB settings.
Under the “Advanced Settings” click the button for:
Enable Apple SMB2/3 Protocol Extensions.
Works like a charm.
Note that someone should update “SMB Share MacOS Client Limitations When Using Decomposed Characters” to reflect this change as well.
1 Like
No, AAPL extensions should not be required for this at all. Changing that setting forces an SMB server restart, which may cause macos client to rescan the directory or other behavior.
Yeah, no. I had this exact same issue on my terramaster nas, and it was solved the same way. I figured something different was going on because tm proved afp connectivity.