Sierra / Issue with Synology network drives

It looks like a widespread (but not universal) issue for many people with Sierra and Synology NAS units. Please post updates/solutions as you receive them. Last I heard from Sinology was 3 days ago when they asked me to run a packet sniffer programme. Awaiting word back...

First:

Apple contacted me regarding my question. The iWork team asked me to share system diagnostics and how to reproduce the issue. Hopefully this might help.

Second:

I found a workaround which helped me out of this situation.

Long story short:

Switch to SMB. It is the new standard of macOS.

Long story long:

I had trouble with just launching SMB because a lot of directories and files were named with special characters like a slash. And I had a lot of folders with a space at the end or a period at the end of the name. This caused SMB to show these files and directories with so called mangled names. (There are workarounds to disable name mangling, but this caused my affected folders to be empty.) The files were named via AFP, which didn't cause any issues at all so far.

Of course it is impossible to seek and change the Terrabytes of files and directories manually.

I reseachred like 3 entire days, tested a lot and finally learned a lot:

I created a bash script which lists all the files and directories with bad names. I ran it via SSH. The list is formatted and saved to a .csv file which allowed me as a human to catch the paths and names easily to get an overview of the situation.

After that I changed the script, that it actually created another bash script which sequentially replaced the characters in the file and directory names with underscores and added a random number at the end to prevent overwriting data.

I created a .csv file again to check whether my plan worked – with an empty result.

I now have AFP and SMB running.

AFP is used for Time Machine backups, there is one single share on the server for time machine backups only. Besides the admin accounts, only one time machine user has access to that share. The login data for that time machine user is saved on all Macs keychains. This is working perfectly.

All other network shares are accessed via SMB, the macOS default. I can just click the server in the Finder's sidebar. Login data are stored in keychain as well, but obviously only for smb://server.local.

Make sure to delete every login details related to the server from keychain to ensure that Finder is only connecting via SMB.

That's it. Numbers, Word, TextEdit, Preview and the others are working perfectly again via SMB without the problem of crashing Finder while the process of saving a file.

The irony:

Connected via SMB, files and folders named with the same special characters which drove me crazy days ago, are not shown mangled. No Problems at all now. (I guess its because smb uses another character coding ..., what ever)

I hope this helped anyone. If you are facing the same problems just ask me. I can describe the procedure more detailed.

I also had the issue of the connection to my Synology NAS constantly being dropped after the update to Sierra. Finally, I managed to connect via SMB; however, I was unable to access my Photos library (on the NAS), receiving the error "you do not have the permissions to access this file," or something to that effect. Switching to CIFS finally fixed that problem, but now when attempting to access the Photos library via iTunea to sync to my iPhone, I get "Photos library is not yet available."

This is driving me crazy. I hope there's a fix, either from Apple and/or from Synology, ASAP!

Cheers,

Chris

Thanks for the detailed writeup, mindphunk! I was just casually reading through this, and this issue doesn't affect me, but this is the kind of detailed writeup that is truly helpful for others. Kudos!

Cheers mate - this fixed the issue for me.

My problem was that I couldn't save stuff to my Synology NAS anymore (the corresponding app would crash and then the finder as well).

I removed all the NAS entries from the finder, from the user profile settings, and from the keychain, then re-connected everything using SMB - and voila, it worked like a charm. 🙂

I will try this. But.. where do you change the user profile settings.. and remove the entries ?

Very helpful. Much of this beyond my skill. Could u spell it out? I will likely await some solution from either apple or synology but welcome hearing your input in detail. Thx!!

Yeah of course. I already wrote a more detailed walkthrough in the German Synology forum. Since this is a Synology specific, or at least NAS or file server specific issue, I posted the walkthrough in the official Synology board. Hopefully it might help!

There we go, happy trying!

thx very much. am filing this meantime until there is hopefully some Synology or Apple solution. but to have the detail is incredibly helpful of you. many thanks

this just in from Synology support (who have been v helpful):

Please be noted that we've launched Critical Update 2 and you shall be able to see it by Monday.

By update it you will have the fix for your DS213+.

so everyone check Monday!

Seems it is a synology issue. Same issues. DS414

trying to get a USB drive online to receive backups while synology figures out the issue.

I had a similar problem.

In another forum I read that Sophos Antivirus was responsible. By disabling (in my case uninstalling) Sophos I was able to solve my problem. I no longer have any issues with macOS Sierra in connection with Synology network drives.

Synology just released the fix with v6.0.2-8451-3. AFP is now working as expected with Sierra.