That's a lot of stuff to read 😉

Going through you message, my first question would be: why check “Do not create sub-directory for mounting”?
Ideally you make one directory (~/mnt) where all mounts will appear for which you set a custom path.
ConnectMeNow will then use the share directory/name to create a sub directory in ~/mnt and on unmount (theoretically anyway) remove it.

With this option checked, I'm surprised to see this:

16:38:39 │ - Active share: home-christian (dxp4800-plus)(Path: /Users/christian/mnt/home-christian (dxp4800-plus))
16:38:39 │ - Active share: Media-Common (dxp4800-plus)(Path: /Users/christian/mnt/Media-Common (dxp4800-plus))
16:38:39 │ - Active share: Media-Own (dxp4800-plus)(Path: /Users/christian/mnt/Media-Own (dxp4800-plus))
16:38:39 │ - Active share: paperless (dxp4800-plus)(Path: /Users/christian/mnt/paperless (dxp4800-plus))
16:38:39 │ - Active share: Storage (dxp4800-plus)(Path: /Users/christian/mnt/Storage (dxp4800-plus))
16:38:39 │ - Active share: Storage-NB (dxp4800-plus)(Path: /Users/christian/mnt/Storage-NB (dxp4800-plus))
16:38:39 │ - Active share: TEMP (dxp4800-plus)(Path: /Users/christian/mnt/TEMP (dxp4800-plus))

The error would be (best guess, I may need more coffee to wake up some more haha): if ~/mnt is the custom path, and “Do not create sub-directory for mounting” is checked, then the first mount will be mounted against ~/mnt, which works, but then the second mount will try that as well, but cannot do this since ~/mnt is already in use as a mount point.

Best would be to UNcheck “Do not create sub-directory for mounting”, set the custom path (of all the shares) to "~/mnt".
No for each mount a new directory will be created in ~/mnt.

Bear with me though, and correct me if I misunderstoord, because I'm still not sure where these mounts come from:

16:44:57 │ - Active share: home-christian (dxp4800-plus)(Path: /Users/christian/mnt/home-christian (dxp4800-plus))
16:44:57 │ - Active share: Media-Common (dxp4800-plus)(Path: /Users/christian/mnt/Media-Common (dxp4800-plus))
16:44:57 │ - Active share: Media-Own (dxp4800-plus)(Path: /Users/christian/mnt/Media-Own (dxp4800-plus))
16:44:57 │ - Active share: paperless (dxp4800-plus)(Path: /Users/christian/mnt/paperless (dxp4800-plus))
16:44:57 │ - Active share: Storage (dxp4800-plus)(Path: /Users/christian/mnt/Storage (dxp4800-plus))
16:44:57 │ - Active share: Storage-NB (dxp4800-plus)(Path: /Users/christian/mnt/Storage-NB (dxp4800-plus))
16:44:57 │ - Active share: TEMP (dxp4800-plus)(Path: /Users/christian/mnt/TEMP (dxp4800-plus))
16:44:57 │ - Active share: backup (dxp4800-plus)(Path: /Users/christian/mnt/mnt (dxp4800-plus))

Hi Hans,

the is exactly what I did with my SMB-Shares (I unchecked the Option "Do not create sub-directory for mounting"). There it works.

But for NFS Shares with the same setting do not work:

You can see this in this line:

16:44:57 │ - Active share: backup (dxp4800-plus)(Path: /Users/christian/mnt/mnt (dxp4800-plus))

Read exactly the mount directory:

/Users/christian/mnt/mnt

Best regards

Christian

Hi Christian,

thanks for clarifying that 😊 
That does look like a bug indeed. I've added it to my to-do list, but I'll have to setup one or two NFS shares to do some testing to see where this goes sideways.

For a temporary (inconvenient) fix:

Assign a specific directory for each mount (eg. ~/mnt/backup, ~/mnt/paperless etc) and check the "Do not create sub-directory for mounting" option for each of them.
By the looks of it, you may have already done that.

Apologies for the inconvenience, and thank you for reporting this. I'll try to get back to you as soon as I can 😊 

Been doing some testing and for some reason cannot reproduce this.

What I tested (feel free to correct me if I missed something):

1. Created 2 NFS shares on the same NAS (NAS: 192.168.22.200, shares: Downloads and Public)
2. Mounted it similar to what you did (even tried /Users/<username>/Mountpoints and ~/Mountpoints - both worked).

3. Both mount correctly in their own subdirectory (Terminal mount output):

192.168.22.200:/Downloads on /Users/hans/MountPoints/Downloads (192.168.22.200) (nfs, nodev, nosuid, mounted by hans)
192.168.22.200:/Public on /Users/hans/MountPoints/Public (192.168.22.200) (nfs, nodev, nosuid, mounted by hans)

CMN log confirms this:

12:14:50 │ - Mount Status Updated: Counted 3 active share(s)
12:14:50 │ - Active share: SMB AllShares (Marvin)(Path: /Volumes/AllShares)
12:14:50 │ - Active share: NFS Public (192.168.22.200)(Path: /Users/hans/MountPoints/Public (192.168.22.200))
12:14:50 │ - Active share: NFS Downloads (192.168.22.200)(Path: /Users/hans/MountPoints/Downloads (192.168.22.200))

What am I missing (I'm not an expert on using NFS)?

• What is the share directory called (screenshot 2 and 3 in my screenshots) in your setup? (pretty sure its not "mnt" of course since I see "backup")
• I noticed that I have a "/" after the custom mount path, in your screenshot I do not see this - could this be the issue? (something I should fix if this is the case)

Hello Hans,

here are my screenshots:

The other NFS Shares have exactly the same configuration. Only the path for the share on the server is different.

I am using the version 4.0.23 (Build 86)

I have no idea, why only one NFS-Share is working.

The second NFS-Share I want to mount is using the same directory /Users/christian/mnt/mnt

Best regards,

Christian

Hi Christian,

can you try both mounts with a "/" at the end of the mount path? (which would be a bug of course if that worked)

So make ~/mnt -> ~/mnt/

It is a little weird indeed, so it probably is a bug, just want to see if we can narrow it down.

Hi Hans,

the issue is the same. The first NFS mount works and the second raises this error message:

16:45:48 │ Mount status update:
         │ Mount/Open Networkshare feedback (Commandline): 
         │ Mount attempt through Commandline:
         │ 
         │ - Mount path: /Users/christian/mnt/mnt (dxp4800-plus)
         │ - CMD: mount_nfs -o nfc "dxp4800-plus:/mnt/hdd/Media-Recordings" "/Users/christian/mnt/mnt (dxp4800-plus)"- Error - Possible error occured. Shell may have returned a fail code
         │ - Result: Mount request did not return an error (not a guarantee that it worked though!)

Best regards,

Christian

I'm really puzzled how this even happens.

Could this be related to the actually share point on your NAS is /mnt, and hdd and nvme are subdirectories of that "main" share?

When you look at my screenshots you see that each is their own specific share (/Downloads and /Public).

When selecting the drop down below the server address on the "Share Details" page, does it list the exact paths you're using?
Or does it show "/mnt" and you typed the rest behind it?

Eg. the published NFS shares on my NAS are listed as such:

Note that I'm not a NFS user at all, so my experience on this topic is quite limited, so please bear with me 😉 

Hello Hans,

the mount points are right.

I am using TrueNAS (Version 25.10.4) as operating system and the structure is always /mnt/<dataset>/<folder>.

Here is the list of my NFS shares:

When I mount them under Unix, I also use this format:

Best regards,

Christian

What does the dropdown show as published NFS shares? (see my screenshot)

Hello Hans,

the dropdown is empty for NFS Shares.

I think that ConnectMeNow only uses the first directory of the path /mnt/hdd/backup. That leads to a duplicate directory for the second NFS Share and so only the first one can be mounted.

My NFS shares are:

/mnt/hdd/Media-Recordings

/mnt/nvme/backup

/mnt/nvme/Storage-NFS

Perhaps the created subdirectory should be:

mnt_hdd_Media-Recordings

mnt_nvme_backup

mnt_nvme_Storage-NFS

Best regards

Christian

Hi Christian,

Not seeing shares advertised on your setup kind-a surprised me, but for several reasons maybe not a bad thing (eg. security, not everybody needs to know what shares are available, especially with NFS). Again: I'm not an expert on NFS. For SMB one can hide shares as well, even though it is rather uncommon.

Back tot the issue at hand: I think I found the issue.

So for SMB shares sub directories in the "share" are not a good idea (most of the time causing unwanted side effects), so:

/mnt/hdd/Media-Recordings

is seen a

share:

/mnt

Subdirectories:

/hdd/Media-Recordings

The subdirectories are (currently) simply removed to prevent issues with SMB shares - SMB seems to always use the root-share which would cause undesired side effects when one mounts to subdirectories in the share.
So the mount path ends up with "mnt" - which is why you're seeing /mnt/mnt.

I did a fix based on your ide to use "_" as a separator. I've uploaded a test verson for you to try, since I cannot even create an NFS share like you are doing (my QNAP won't allow it). Please let me know if this works for your setup.

You can download it via this link.

Hi Hans,

thank you for your quick response.

This week I am on a business trip and have only access to the NAS with VPN.

When I try to mount the shares, I see that the directories are created as you mentioned - but the mount does not work.

Here is the output of the Log:

16:49:12 │ Mount requested for: "backup"
16:49:12 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
16:49:12 │ - Doing default short mount delay (1 second)
16:49:13 │ - Starting mount background task
16:49:13 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
16:49:13 │ - Enabled timer for potential extra mount attempts
16:49:13 │ - Thread started
16:49:43 │ - RETRY MOUNT TIMER: Stopping timer
16:49:43 │ - RETRY MOUNT TIMER: Quiting, nothing left to retry, and no Fallback servers left either
16:49:43 │ - Updating "Mount onAppear" list

16:49:49 │ Mount status update:
         │ Mount/Open Networkshare feedback (Commandline): 
         │ Mount attempt through Commandline:
         │ 
         │ - Custom is mount point: No
         │ - Custom path: /Users/christian/mnt
         │ - Unique path: /Users/christian/mnt/mnt_nvme_backup (dxp4800-plus.fritz.box)
         │ - Mount path: /Users/christian/mnt/mnt_nvme_backup (dxp4800-plus.fritz.box)
         │ - CMD: mount_nfs -o nfc "dxp4800-plus.fritz.box:/mnt/nvme/backup" "/Users/christian/mnt/mnt_nvme_backup (dxp4800-plus.fritz.box)"- Error - Possible error occured. Shell may have returned a fail code
         │ - Result: Mount request did not return an error (not a guarantee that it worked though!)

16:49:49 │ Thread - Calling for forced status update (only shows results if something changed)

16:49:49 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------
         │ 
16:49:49 │ Update type
         │  - Initial read     : -
         │  - Timed Interval   : -
         │  - Get Network info : -
         │  - Forced Update    : YES
         │ 
         │ Status Interval     : 10000 milliseconds
         │ Interval Interrupts : 500 milliseconds
         │ Failed mount after  : 30000 milliseconds
         │ 
         │ Default gateway     : 192.168.156.1 (MAC: 00:09:0F:09:00:1A)
         │ 
16:49:49 │ - Mount Status Updated: Counted 0 active share(s)
16:49:49 │ - Matched 0 Network shares. (matched all)
16:49:49 │ 
         │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
16:49:49 │ - Updating "Mount onAppear" list

16:49:49 │ Updating Tray Menu

Perhaps it is also VPN issue. But the connect to the SMB Shares are working through VPN.

Without VPN I can test it on Friday.

Best regards

Christian

Hi Christian,

thanks for testing - I'll look at your log later today, feel free to respond when you can test at home as well (although I think you're right; it may not make a difference). 😉