Can you switch off a Synology DS box from the Power Button? I asked myself this morning when I got a text from our building manager to remind me that the electricians would be in at my day job this morning and I couldn’t login via quickconnect.
This is not an easy thing to find out (if you’ve not actually switched off your box physically before) and no-one wants their box to be inadvertently powered down. But it is possible.
Fortunately I have a box at home too and can practice. The key is to hold down the blue power button until it makes a loud sharp beep and then it’ll power down gracefully.
And it worked. The fabulous Dawn was able to easily shut down the server. Crisis averted. Re-wiring of our lighting underway.
“AFP_VFS afpfs_DoReconnect: connect on failed”: I’ve been plagued by this error for some weeks, which relates to waking my Macbook Air from sleep after being connected to my synology NAS at work. The console is replete with hundreds of these messages as it tries to re-connect to the server that is no longer available and there does not seem to be a routine that allows it detect that the server is no longer available and stop attempting to reconnect. As a result the finder simply ceases to be responsive and if you force quit it, it does not spawn properly again.
How to fix it
After getting frustrated with having to log out and log back in again to regain a responsive finder, I googled and failed to find a solution so I turned to the Activity Monitor where I noticed substantial activity from the “soagent” and found that if I force quit that – don’t worry it’ll respawn unharmed – then I got my finder back. Not the most elegant of solutions but quicky, dirty and more importantly successful. I hope the bug will get corrected in a future release of OS X (at the time of writing I’m using 10.10.3) but in the meantime this works.
Okay that solution didn’t work frequently enough but this new one, thanks to Krysole at superuser.com does indeed work. I generally check which smb mounts are malfunctioning from the console and then go to terminal and use the following command:
sudo umount -f /Volumes/”volume name”
And bye, bye problem!
This problem has now been fixed by El Capitan… Woot!