November 14, 2025Nov 14 Hi everyone,i have a problem transfering a folder to my unraid share. I allwys get an Error -8062.Here are some Details:Unraid 7.2 (Tiger)Share Name: productionMacOS Compatibilioty: yesSecured: PrivatMacOS Tahoe 26.1I connect to my share with Apple+K smb://192.168.1.xxx/productionI can see all my files and i can download it from that share. I tried to upload smaler fiels up to 300mb. That worked, tooEverythinmg looks normal.But if i grab that 49 GB Folder with a lot of files in different sizes, and drag it over it creats that folder but then i get the Error MessegeDer Vorgang konnte nicht abgeschlossen werden, da ein unbekannter Fehler aufgetreten ist (Fehler -8062)._______What i already tried:- reboot of course- tried it on a publich share. Same error- checked: Enhanced macOS interoperability: Yes - Tools -> New Permissions -> That Share: Still get the Error- checked if my user has Read/Write. Yes is has.- erased any data in Apple Keychain with anything like „._smb._tcp.local“ and did a clean connection.- Checked the log: log stream --predicate 'subsystem == "com.apple.smb.client"' --info[2025/11/13 19:57:19.136678, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict) parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.[2025/11/13 19:57:19.176952, 0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict) parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.local[2025/11/13 19:57:36.041858, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict) parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.[2025/11/13 19:57:36.083482, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict) parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.[2025/11/13 19:57:36.118773, 0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict) parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.localTha lead to the idea DFS isn´t working well with MacOS so i put[global]host msdfs = nomsdfs root = noto the SMB ExtrasStill i get this error. Any Ideas
November 14, 2025Nov 14 Community Expert 48 minutes ago, charley said:[2025/11/13 19:57:36.118773, 0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict) parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.localThese should be informational only, and unrelated to the issue, or does the time code coincide with a transfer error?
November 15, 2025Nov 15 Author On 11/14/2025 at 12:03 PM, JorgeB said:These should be informational only, and unrelated to the issue, or does the time code coincide with a transfer error?no i don´t think so. it only informational then
November 16, 2025Nov 16 Community Expert If there's anything else logged when the transfers fail, it may be an external issue. See if you can repeat the transfer from another PC, using a different cable/switch port.
November 19, 2025Nov 19 Author ok i could shrink it down.i zipped the folder and it worked. The zip file was about 18GB. So the Problem must have something to do with los of smaller files, subfolders and so on. I still get the error if i thy to copy the unzipped foilder.
January 25Jan 25 I am now having the same issue as you. Also MacOS (Tahoe 26.2) and Unraid. I can also perform the transfer if I first zip the folder, but get the error -8062 error if I don't.Did you find a solution to this?Thanks.
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.