Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
I have my share configured as Command Line and Auto Mount configured as Network Change -> Only if Default Gateway MAC is.
It seems that when the Mac goes to sleep for a long time, it cancels (or times out) all connections, including my share's. Sometimes my share is mounted and available when waking up, but sometimes it is not. In the logs, I've noticed these messages:
09:06:40 │ POWER STATE CHANGE - Your Mac is waking up out of Sleep Mode after a 8 hours and 20 minutes nap. 09:06:40 │ - Checking if shares need to be remounted (were mounted before sleep, but not anymore) 09:06:40 │ - 0 shares were no longer mounted 09:06:40 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------ │ 09:06:40 │ Update type │ - Initial read : - │ - Timed Interval : - │ - Get Network info : YES │ - Forced Update : - │ │ Status Interval : 10000 milliseconds │ Interval Interrupts : 500 milliseconds │ Failed mount after : 30000 milliseconds │ │ Default gateway : 10.0.0.1 (MAC: [redacted]) │ 09:06:40 │ - Mount Status Updated: Counted 1 active share(s) 09:06:40 │ - Matched 0 Network shares. (1 unknown) 09:06:40 │ │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
In the second line, it says there were shares mounted before sleep, but they were not mounted anymore. Then on the third line it says "0 shares were no longer mounted", does that mean the app detected that all shares have been mounted?
Then it also says it counted 1 active share, what does "active" mean here? Is it the "on/off" switch on the app's UI? It says this even though my share is not mounted anymore. (The log I pasted above was after a long sleep and my share was not mounted after waking up in that instance)
I've noticed that even with command line mounts, Finder messes around. I've seen Finder trying to unmount the share, remount the share and complain that the share was not accessible. Finder being Finder..., this is probably Apple messing with the mount, not CMN's fault. Do you have any ideas of what is going on and how to keep the shares mounted?
Thank you so much for this incredible app!
Hi AndreG 😊
In the second line, it says there were shares mounted before sleep, but they were not mounted anymore. Then on the third line it says "0 shares were no longer mounted", does that mean the app detected that all shares have been mounted?
Then it also says it counted 1 active share, what does "active" mean here? Is it the "on/off" switch on the app's UI? It says this even though my share is not mounted anymore. (The log I pasted above was after a long sleep and my share was not mounted after waking up in that instance)
CMN tries to determine what shares are mounted before going to sleep, and verifies that list when waking up again to see if mounts are still there.
The line suggests that whatever was mounted is still reported by macOS as mounted.
My person work aorund for when this happens is:
Preferences:
1) check "Quick Unmount shares on network loss"
2) check "Remount mounted drives On WakeUp from sleep" (probably already checked)
Per Share:
1) Check "Auto Mount when ConnectMeNow starts" (may not be needed)
2) (under Advanced Option) Check "On network change"
Under Advanced options I'v also check and set "Only if Default gateway MAC is" with the MAC address of your router.
I've noticed that even with command line mounts, Finder messes around
Finder does make a mess of things on occasion indeed. Still blows my mnd why Apple hasn't fixed this yet as it has been behaving like that for decades now.
The only thing I see on rare occasions:
Sometime it tries to remount after waking up from sleep - you'll get a login message which I always simply close (do not login). Forgot what the button was that I use for that as it happens very rarely on my setup.
I've never seen Finder unmount anything though, so that makes me wonder why this is happening on your setup. Do you have any other tools running that may interfere with mounted shares?
Maybe the settings I just mentioned address this issue as well?
