autofs not working properly now!

Synology released an update to their NAS software that appears so far to have resolved the AFP issues. I'm testing it on the latest Sierra beta release.

I developed my way around this issue. Please try my app, which I think will solve your problem: https://itunes.apple.com/us/app/automounter/id1160435653?ls=1&mt=12

I also had the same problem after upgrading to Sierra.

I think I may have found the solution from https://forums.plex.tv/discussion/239074/how-to-fix-auto-mounting-shares-broken- in-sierra-macos#latest

I've tried mount to my home directory...so far so good. But if you try this big word of caution: mount to a sub-folder within your home directory. If you mount directly to your home directory it stops MacOS from being able to load your home directory - quite scary when I did it as it looks like everything is gone!

So, do NOT do this in your autofs file:

/Users/<username>/ auto_cifs

Doing the above mounts your 'share' as /Users/<username>/share but you lose the rest of the home directory!

Instead, do this:

/Users/<username>/tmp auto_cifs

This mounts it as /Users/<username>/tmp/share/

I've still got to do some testing but am hopeful yhis

My update after some changes:

- I changed from afp to smb ... mounting is a bit quicker now

- I applied the Synology hotfix

On the surface now everything looks find, but automount is still broken.

I'm able to automount filesystems. They stay mounted and get unmounted after a while. So far, everything normal. BUT ... once the filesystem get's under load sooner or later (ranges from minutes to hours) this happens:

plex:~ plex$ mount

/dev/disk0s2 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)

map auto_misc on /misc (autofs, automounted, nobrowse)

//plex@diskstation/Music on /misc/Music (smbfs, nodev, nosuid, read-only, automounted, nobrowse, mounted by plex)

plex:~ plex$ mount

/dev/disk0s2 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)

map auto_misc on /misc (autofs, automounted, nobrowse)

//plex@diskstation/Music on /misc/Music (smbfs, nodev, nosuid, read-only, automounted, nobrowse)

The filesystem that was before mounted by plex changes it's owner: from one second to the other now root owns the filesystem and all permissions are changed accordingly:

plex:~ plex$ ls -lad /misc/Music

ls: /misc/Music: Permission denied

plex:~ plex$ sudo ls -lad /misc/Music

drwx------ 1 root wheel 16384 11 Sep 01:13 /misc/Music

plex:~ plex$

Same problem. I've got two Disks in my NAS (D-link, so not a Synology). I've got them mounted as ~/Shares/Nas/Volume_1 and ~/Shares/Nas/Volume_2. Sometimes they disappear at the same time, but other times only one will disappear.

Did anyone manage to find a solution?

Anyone found a solution to this?

I purchase the Automounter app. It sort of works but the path is incredibly long for adding to Sabnzb, Sonarr, Couchpotato, plex etc. Also, for some reason the coachpotato renamer fails when using the paths.

Even though both to and from folders are entered correctly in couchpotato using the ridiculously long Automounter paths, Couchpotato returns the error below.

Apart from this, the mounts appear to be a lot more stable. I have only had one of my mounts disconnect randomly, but that has so far happened only once whilst using automounter.

Both the "To" and "From" folder have to exist

After my earlier post, I found that mounting it to the home directory still did not work (lost connection after a while).

However, I have now edited my autofs.conf to add browse to the mount options. i.e.

AUTOMOUNTD_MNTOPTS=nosuid,nodev,browse

After 24hrs or so, I get a connection every time which is better than before. I'll post back if it fails. The only word of caution is as follows from this link. That said, so far no issues for me but I have only one mount.

[no]browse

This is an autofs specific option that is a pseudo

mount option and so is given without a leading dash.

Use of the browse option pre-creates mount point

directories for indirect mount maps so the map keys can

be seen in a directory listing without being mounted.

Use of this option can cause performance problem if the

indirect map is large so it should be used with

caution. The internal program default is to enable

browse mode for indirect mounts but the default

installed configuration overrides this by setting

BROWSE_MODE to "no" because of the potential

performance problem.

Forget it...didn't work! Again, same problem.

As an earlier poster said, the mount is reverting to be owned by root! Doing sudo automount -vuc will remount it as owned by user but that isn't a nice solution! In fact it is no solution. 😟

I have no idea why it is changing ownership. Some more experimenting to do!

Too bad! This problem is really annoying, I have to restart my computer every day because the mounts have been unmounted again.

Any luck with further experimenting?

Unfortunately not...I've various things without any success.

I found this link where people are discussing the same issue 5yrs ago!! I am now trying 'noowners' option in my auto_master file.

OK, after more experimenting, the only thing I found to work is to increase the mount timeout in /etc/autofs.conf. I think the problem of ownership changing to root occurred during the timeout (but can't be sure).

So, now I have AUTOMOUNT_TIMEOUT=36000.

Kind of lose some of the functionality of autofs but it worked for me.

Is this still working for you? And what functionality do you lose?

I had to increase the timeout to stop it ever timing out and unmounting (commenting it out might have the same end result). But essentially it continues to work for me.

When I say loss of functionality, I mean that the timeout is supposed to unmount the share after a period of inactivity - that is essentially lost. What I haven't done is see what happens when I am not on my network with this infinite timeout (e.g. will it cause a hang in Finder). I had problems in Linux of hanging (a long time back) but I do not believe MacOS has the same issue.