(04-30-2018, 01:34 PM)Martin Wrote:

(04-29-2018, 08:34 PM)Tim Curtis Wrote: sudo not needed. The log might have been automatically cleared by the maintenance task.

Open Sources screen, click RESCAN then wait a bit, then view the log.

I have clicked RESCAN and had a look at the log. It appears to have scanned the SD card but not the 
NAS.

Apr 30 14:28 : update: updating SDCARD/Stereo Tes

t/LRMonoPhase4.flac

Martin

(02-04-2019, 07:04 PM)Paulbj Wrote: I have a very similar problem RPi 3B + Kali + Piano2.1 with Synology DS216se NAS

I have SSHed to the NAS and created a suitable etc/exports file. I have two identical streamers the second one is currently running Volumio and I can connect to the NAS with that one, OK. However all attempts to connect the player running Moode have failed. Attempting to connect using NFS with "192.168.178.59/volume1/music" as connection string and all other params as default, results in the following error msg "20190204 195413 wrk_sourcemount(): Mount error: (mount.nfs: mount point /mnt/NAS/Music1 does not exist)".

Trying with Samba gives the following error "20190204 200111 wrk_sourcemount(): Mount error: (Couldn't chdir to /mnt/NAS/Music1: No such file or directory)"

(02-05-2019, 01:11 PM)Paulbj Wrote: I assumed that the error log was referring to the directory " /mnt/NAS" not existing on the Moode device rather than on the NAS. That would be the rational conclusion, I think. It's the Moode device that is mounting the NAS rather than the other way round.

(02-05-2019, 03:26 PM)TheOldPresbyope Wrote:

(02-05-2019, 01:11 PM)Paulbj Wrote: I assumed that the error log was referring to the directory " /mnt/NAS" not existing on the Moode device rather than on the NAS. That would be the rational conclusion, I think. It's the Moode device that is mounting the NAS rather than the other way round.

@Paulbj

The directory /mnt/NAS is predefined in moOdeOS as the root of all the NAS mountpoints. The mountpoints themselves are derived from the info you enter into the NAS Source panel (the "friendly" Name) 

Example:

My OpenMediaVault (OMV) NAS with the hostname OMV-HC1 has a directory '/export/Music'. In its '/etc/exports' file I* tell NFS to export this directory read-only to my entire subnet.

Code:

/export/Music 192.168.1.0/24(fsid=1,ro,subtree_check,insecure)

At this point, the directory is visible to NFS clients on my LAN as 'OMV-HC1:/Music'.

In moOde's NAS Source panel, I enter this into the Host/Share box as 'OMV-HC1/Music' (note we lose the ':'). I give it a friendly Name 'OMV-NFS' (to differentiate it from, you guessed it, 'OMV-SMB' for my Samba share //OMV-HC1/Music from the same host).

When I'm all done and look at moOde's mount list, I see among the many entries

Code:

pi@moode:~ $mount
...
//OMV-HC1/Music on /mnt/NAS/OMV-SMB type cifs (ro,relatime,vers=1.0,cache=strict,username=moode,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,soft,unix,posixpaths,mapposix,acl,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
OMV-HC1:/Music on /mnt/NAS/OMV-NFS type nfs4 (ro,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.182,local_lock=none,addr=192.168.1.12)

The first entry is the Samba share and the second is the NFS share from my OpenMediaVault NAS. Here you see explicitly the moOde-named mountpoints such as /mnt/NAS/OMV-NFS.

As an aside, choosing directory names such as 'export' and 'Music' is arbitrary; what's important is that the names be consistently used between the NAS and moOde and not confused with the friendly name you assign in the NAS Source panel.

Regards,
Kent

*more precisely, that's what the OMV Admin UI entered based on what I told it.