Sierra / Issue with Synology network drives

I don't know what those links were worth, one is so old, it's archived and probably refers back to version 1 of that auto document save bit.

Look, there is a post in another thread similar to this one where the problem might be with Keychain and not AFP.

Basically he used Keychain Access and deleted all the references to the NAS, rebooted, then added the shares back in.

This seemed to at least stop the problem of constantly being asked to log into the share and mounting with the name/password embedded and still being asked to enter the info again.

I haven't tried it but something to try. This problem might be totally different but there is some logic with that solution over a major defect in AFP.

Okay. I don't see a sheer coincidence between the problem described in this post by the author (preview) and the issue I was telling about (numbers). Its the same behaviour. By the way, even TextEdit crashed. I simply guess that there might be a connection.

Now, what has keychain to do with the issue described in this initial question and here ?? No one ever mentioned some problem about beoing constantly asked to log in.

عندي مشكله ماقدر أشحن رصيد في لعبة بوم بيش عن طريق الايتونيز

Didn't you have to give Finder a username/password when you first got that thing to mount the share?

Normally in Finder, when you want to mount a remote share, you go up to "Go" and then "Connect to Server".

Since most NAS are protected by a username/password for the share, that was entered and normally saved into the keychain. That way in future mounts, when the computer is rebooted, the share automounts without having to do that all over again.

The point is, if that was done, it looks like AFP is having a problem with the way the keychain was imported from the old macOS you were using. It keeps trying to re-authenticate in the background screwing up everything from automounting, Time Machine and access to the folders on the share.

If this was a clean install for you or you are running the NAS without password protection, I suppose it doesn't apply.

In case this helps:

The Synology Mac Sierra compatibility issue may be getting blown out of proportion. I had two Macs I upgraded at different times testing the Synology Cloud station synchronization.

The Laptop (MBPro) required I delete the Synology Cloudstation app and re-install it. The iMac worked fine without a need to delete and re-install the Synology App.

Near as I can tell, the upgrade on the MBP in Finder broke something Synology had set up for Synch'ing. A re-install reset that and they're all working fine. Interesting the iMac didn't require that - they both were at the same level MAC OS X before upgrading.

Also, have had no issues with my Security Cameras recording on AFP NAS mounted drives.

Hope this helps anyone else having difficulties!

There is a problem with Apple File Protocol - AFP. If you are connected that way you will encounter problems.

You can try SMB instead, but then you may have other problems with file and folder names.

Please anyone with this problem contact AppleCare ASAP.

See this thread on the Synology forums.

https://forum.synology.com/enu/viewtopic.php?f=64&t=122975&p=451468#p451468

Backup disks you can use with Time Machine - Apple Support

Yes of course I do have to enter my user name and pass. And yes, these were saved in Keychain.

But it has nothing to do with the issue the author descibed (JPG saving via AFP) nor the one I described (saving a Numbers file). I did not get problem with the login and also my Time Machine Backups are running normal. Only issue is the saving of files from the Apple Apps such as Preview, Numbers, Pages, Keynote & TextEdit. All these Apps are using file versioning. That might belong together. Another hint, that it might belog together is the following: I found files like these "2016-08-14 13-27-17.txt.sb-9b82e34b-ga2Nla" on the share which are file versions of the orignial txt file which caused TextEdit and the Finder to crash and therefore to kill the AFP connection.

Hi!

I have the same issue with my Synology NAS and my iMac. I´m connected over ethernet and every time I try to save any file from Word to NAS, Finder doesn´t response. I force quit Finder but it doesn´t reboot anytime, I have to reboot my iMac.

I think it´s a Synology issue, an update will come soon, but, does Apple Support anything to say about this?

Thanks!

It seems to be an AFP problem. You can connect using SMB to get around it. Many people reporting that problem connecting by AFP to Synology. Its affecting everything I have on the NAS (itunes, iphoto etc).

Bit of an update on previous reply. I have upgraded 1 x MacBook Pro and 1 x iMac. Both usually use Time machine for backup to my 12TB Raided Synology NAS, as does the other, still on El Capitan, MacBook Pro. I did the MBP ( it has a 128GB internal Disk) first after making a separate TM backup to a USB3 capable drive. So all went well, apart from the first attempt which aborted 'cos there wasn't enough room on the "Mackintosh HD". It wasn't obvious how to get back to the original EL C system. It kept retrying and moaning about not enough space. It dawned on me that I should quit the installer and that allowed me to get back in and to remove 10GB of files to my Synology NAS. Once the upgrade had gone OK - not too long, being about 1 hour - I set off Time Machine and that worked fine although it spent more than normal amount of time "preparing backup" - a nervous time. Anyway patience payed off and it got on with the backup. I had decided to do this via Ethernet ( I have a USB to Ethernet adapter). After that finished I went back to wireless and ran another TM backup. So far so good.

Next over to the iMac. This wasn't quite so stress free. I did a TM backup and then off to the App Store and got on with the upgrade. Took a while but went and had dinner, leaving it to get on with it.

iMac has 1TB disk, in case you're interested. When it had finished I did a TM Backup which seemed to be "Preparing backup" for 2 hours or so. I was beginning to fret. "Be Calm!" I said to myself. I did reboot a couple of times after stopping the backup. So started the backup again and set Caffeine ( see : http://osxdaily.com/2012/08/03/disable-sleep-mac-caffeinate-command) up so the iMac wouldn't sleep and went to bed. In the morning the backup had finished. I ran another backup, just to see if it really was working. (BTW iMac is connected via Ethernet. I only need to turn on the WiFi to use Airdrop.) All now running TM OK on both upgraded machines. Then there were a couple of problems:

1. I have recently bought a Steinberg UR22MkII Audio interface. This has been working brilliantly on El Capitan. After the upgrade to Sierra it went awry. USB lamp flashed constantly when it should be always on when powered through it's USB port. A bit (well actually a lot) of googling hinted that it m

might not be getting enough power from the USB port. I connected it to the MBP after loading the driver. It worked fine until I rebooted the MBP, after which it did the same as on the iMac. Hair-tearing time now. Some

body suggested updating the Firmware. I had to connect the UR22 to the still not upgraded MBP as neither the iMac or the upgraded MBP would recognise it. After the firmware update it worked fine on MBP but still not on iMac. I tried a different USB cable. No luck. Problem was fixed by connecting to a different USB port on the iMac. All seems OK at present (36 hours later). So now I'm happy with that.

Interestingly I bought the Steinberg because I previously had a E-MU 204 from Creative, which stopped working with the upgrade to EL Capitan. There was plenty of discussion on the Internet about this an also that other USB devices didn't work with EL C. Neither Apple or Creative could care less or offer any response to any of the complaints. Creative support seem to completely ignore any email and are still selling the E-MU saying it works on OS X. Disgraceful, I say but there you go, I appreciate that they need to make us spend our money on new toys but it would be good if they actually told us they were not going to support old ones.

2. Photos is a nightmare. I have several photo libraries and use a program "Power Photos" to swap between each. The main library worked OK but I found that the CPU was almost completely used at over 90% by a process called "photoanalysisd". This turns out to be a process which sets up the new facility in Sierra for the "People" setting in Photos. That took about a day to sort the main library. It is still doing one of the other libraries which has about 50,000 photos. It also says that at least one other library is corrupted, although Power Photos sees it OK. I'm sure I can sort something. Not much is beyond the wit of mankind!

Altogether a pretty stressful 2 days. I still have my wife's MBP to do but as that one doesn't get used for anything complicated I'm sure that will go fine. I'll still do a separate TM backup to my USB Disk first.

All devices are working with TM to my Synology NAS and also file access is working OK - I have both iTunes and Photos libraries on that device.

For those interested this is a terminal Screenshot showing disks mounted. You will see that it looks to me that it is using afp to access the NAS:

Last login: Mon Sep 26 11:45:21 on console

MacBook-Pro:~ dougtred$ mount

/dev/disk1 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

//dougtred@SYNOLOGY1._afpovertcp._tcp.local/TimeMachineBackups on /Volumes/TimeMachineBackups (afpfs, nobrowse)

/dev/disk3s2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, journaled, nobrowse)

MacBook-Pro:~ dougtred$

I watched the Keynote live which intro'd Sierra. I thought it odd that the item which the audience seemed to get most enthused about was the fact that SuperMario now runs on IOS. Such a great leap forward for Science.

Anyway, Have fun everybody and lets hope that Apple, in future, tells us what might go wrong or not work with further upgrades.

Happy computing.

Doug Tredwell

Berkshire

UK

I have the same issue; My Photos library was on my Synology NAS and is now unaccessable/toast.

I have an 'case' open with Apple (Case ID 100030957832) and the last troubleshooting was to try a safe boot and try it again (failed same way). They were supposed to call me back with the next troubleshooting step 'in 15-30 minutes'; that was two day's ago. No word from Apple....

I also opened an issue with Synology; and they are aware that something has changed in the AFP process/protocol and that their Mac users are having trouble.

I am also now prompted for external share user credentials (yes stored in the key chain) and the share's won't auto mount.

I would recommend not upgrading to Sierra if you rely on AFP and external network storage devices.

I would revert to El Capitan if it weren't such a pain.

Allan Eckert wrote:

Apple recommends against the use of networked drives.

What does this mean? Are you claiming that Apple discourages the use of NAS devices?

From our 4 computers and two tablets, only the Macbook has issues connecting to our shared documents on the network drive. It is a bloody shame that an update makes your mac useless in a normal network setup with shared documents, any access to the NAS required a reboot.

It has been a long time that I wished to have a windows machine!

For the time being I have reconfigured all shares to SMB, and Word, Excel and numbers etc seem to work again.

Still very very sloppy upgrade!

If someone from Apple recommends not to use network drives, where do they want you to put shared documents? on a USB stick?

My understanding is that AFP is EOL, and that SMB3 is the default for El Capitan, Sierra, and the future.