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?
Thank you for the reply, Hans!
I have all those options enabled. In the left side of the Preferences panel, the only options I don't have enabled are "Restore windows positions", "Audible Mount/Unmount Notifications", "Eject External Drives on sleep" and "Only mount when Mac is Unlocked". I don't think these would change this behavior.
I don't have any other apps for mounting shares. I honestly think it's Finder (or some internal Apple subsystem) that could be interfering with CMN's ability to detect the share. You said those lines mean the share was reported by Apple as mounted, but it was not. That would explain why CMN didn't attempt to mount it again and why it was not available after waking up (although, CMN's tray icon was showing the share as unmounted).
Even though I have the mount "On Network Change" option checked, my personal laptop very rarely (i.e, never) leaves my home. So in reality it is always connected to the same network. I've only enabled that option to guarantee the share was always available. I think, perhaps, when the laptop goes to deep sleep (lid closed, not connected to power) Apple doesn't clean the mounts' connections completely. So when it wakes up, it conflicts what it reports as mounted (what CMN sees) with the reality in the network stack/kernel state. The reason I say this is because I've seen it happen once when Finder reported the share as mounted, I tried to browse to it and it completely hanged Finder (not even `killall Finder` would work). Then I tried cd'ing into it on Terminal and it hanged Terminal the same say, force quitting wouldn't work. I resolved this by killing my WiFi and waiting. When it finally reported the mount was inaccessible, then my apps started working again. This was all Apple, not CMN's fault.
I have all those options enabled. In the left side of the Preferences panel, the only options I don't have enabled are "Restore windows positions", "Audible Mount/Unmount Notifications", "Eject External Drives on sleep" and "Only mount when Mac is Unlocked". I don't think these would change this behavior
You're right, those would be irrelevant for your situation.
Also good to know no other apps are interfering. 👍
CMN uses a few methods to determine if a share is mounted or not.
The closest to that would be the "mount" output in Terminal.
Sometimes macOS has not yet detected that a share disappeared and holds on to a share for a little bit. I suspect this is so shares wouldn't be unmounted to quickly/often when there are little network hickups.
So, the system still reports a share being mounted, yet in reality it isn't.
Mount output example:
~ $ mount /dev/disk3s3s1 on / (apfs, sealed, local, read-only, journaled) devfs on /dev (devfs, local, nobrowse) //admin@192.168.1.100/AllShares on /Volumes/AllShares (smbfs, nodev, nosuid, mounted by hans)
(I removed a bunch of local disks - the last line that starts with "//" is a mounted share no matter how it was mounted)
Even though I have the mount "On Network Change" option checked, my personal laptop very rarely (i.e, never) leaves my home. So in reality it is always connected to the same network. I've only enabled that option to guarantee the share was always available. I think, perhaps, when the laptop goes to deep sleep (lid closed, not connected to power) Apple doesn't clean the mounts' connections completely. So when it wakes up, it conflicts what it reports as mounted (what CMN sees) with the reality in the network stack/kernel state. The reason I say this is because I've seen it happen once when Finder reported the share as mounted, I tried to browse to it and it completely hanged Finder (not even `killall Finder` would work). Then I tried cd'ing into it on Terminal and it hanged Terminal the same say, force quitting wouldn't work. I resolved this by killing my WiFi and waiting. When it finally reported the mount was inaccessible, then my apps started working again. This was all Apple, not CMN's fault.
I guess I use my laptop the same way 😉
However - I always have it wired through ethernet, so no WiFi, since WiFi is much slower and much less reliable (even if the speed indication suggests it would be faster - in reality it rarely is).
Your observation matches my experience, especially with WiFi (as mentioned before).
Try and see if you can try using an ethernet connection for a while and see how well/bad things are.
I actually always disabled WiFi, because even though Apple states it would take the better connection, at times it still uses WiFi (I see a serious speed drop when that happens).
You're absolutely correct about WiFi. While on 6 Ghz and being very close to the AP, macOS reports the PHY being capable of 2.4 Gbps — not true. I can try WiFiman or iperf3 all day and they don't get anywhere near that speed.
Unfortunately I don't have enough physical ethernet ports on my switch to connect my laptop right now. It's in future plans. My PC (that doesn't have WiFi and connects via ethernet) gets much better speeds with my NAS.
Anyway, I've also found out another Apple quirk. I use the Handoff/Continuity features with my iPhone (such as using my iPhone as a webcam) very frequently. When that happens, Apple forces the WiFi to drop from 6 GHz to 5.4 GHz and that causes all sorts of issues with the NAS. Not just the NAS, anything that is connected gets briefly disconnected and sometimes issues happens. And macOS requires WiFi to use the Handoff/Continuity features, even if the iPhone and macOS ethernet are on the same network. Apple being Apple...
So, I think this is fine for now. Your app already helps me a lot keeping this share active on "regular" use and if it does disconnect because of Apple's quirks I can easily re-mount it. And I can now FINALLY respect UNIX's filesystem with my regular files not being considered "executables". Thank you!
I used to use WiFi a lot, due to where my laptop is located (just like you: no physical cable).
Since I often move around big files (app. 1-4Gb per file) I started noticing that my ethernet connection (2.5Gbps) is about twice as fast as a WiFi connection that promises 2.4Gbps. Not to mention, the ethernet connection is rock solid.
So I ended up getting a 2.5Gbps switch from AliExpress (this one performs very well, 2.5 Gbps to be future ready) and with a half baked solution by running a cable through the living room, tucked away where possible.
I also noticed that when WiFi is enabled and ethernet connected, macOS should (according to Apple) use the Ethernet connection, but sometimes it doesn't (notice the significant speed drop). Having said that, I think it may have to do with macOS selecting the connection wth the highest theoretical throughput. Maybe.
WiFi would be nice to have though since macOS and iOS do use WiFi for copying and handing off where you left on the other device.
Kind-a like what you are experiencing, maybe a little different, but equally annoying.
In your case it most likely is seen by equipment as a new network connection (maybe).
So software may see this as a disconnect and a different network reconnect.
Glad to hear you're content for now.
Let me know if you see anything happening that I may be able to address in ConnectMeNow 😊
