Synology NAS

[Relocated2007]

I have Synology Nas named DiskStation and in windows, I have a path to my music on it \\DiskStation\music, so I tried to find it on moode but it sis not appear after the scan. So I tried manual but DiskStation/music is not working my NAS IP/music not working, errors are:

Code:

20220625 215537 sourceMount(): Mount error: (mount error: could not resolve address for DiskStation: Unknown error)
20220625 215856 worker: Job sourcecfg
20220625 215857 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))
20220625 215945 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))
20220625 225956 worker: Job sourcecfg
20220625 225957 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))

I am always struggle on moode to find my nas I do not know why, on volumio it just worked. What is wrong with me ?

[GStevens]

I have Synology Nas named DiskStation and in windows, I have a path to my music on it \\DiskStation\music, so I tried to find it on moode but it sis not appear after the scan. So I tried manual but DiskStation/music is not working my NAS IP/music not working, errors are:

Code:

20220625 215537 sourceMount(): Mount error: (mount error: could not resolve address for DiskStation: Unknown error)
20220625 215856 worker: Job sourcecfg
20220625 215857 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))
20220625 215945 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))
20220625 225956 worker: Job sourcecfg
20220625 225957 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg))

I am always struggle on moode to find my nas I do not know why, on volumio it just worked. What is wrong with me ?

I have exacty the same setup.  I'm not sure whether I scanned for the NAS, or entered the details manually, but the Music Source Server Path in Moode is DISKSTATION2/music.  It's DISKSTATION2 from when I had had two NAS, but just the second one now.  I'm using Samba rather than NFS.

This all works fine (Moode 8.0.2 - not upgraded yet).

Regards,
Geoff

[TheOldPresbyope]

@Relocated2007



The error message is very suggestive. Try manually editing your source path to be "DiskStation.local/Music" (without the quotation marks, obviously).

Regards,
Kent

[TheOldPresbyope]

@Relocated2007

Sorry, for my brief answer but I had to break off to deal with real life(!).

You didn't say whether you are running the 32-bit or 64-bit release of moOde 8.1.1 (or even if it's 8.1.x).

There seems to be a difference between the two releases regarding the discovery of hosts on the LAN (cf https://moodeaudio.org/forum/showthread....0#pid41390 and my follow-up post there). 

Specifically, with the virtual DSM server I run for test purposes on my LAN, my 32-bit moOde 8.1.1 is happy with source path "DS3615XS/Music" while my 64-bit moOde 8.1.1 player requires "DS3615XS.local/Music". This despite the fact that both 32-bit and 64-bit releases return "DS3615XS/Music" as one of the SMB shares detected on my LAN when I invoke the SCAN function.

I understand in broad outline what's happening but I haven't found a smoking gun yet. Hostname resolution was so simple a caveman could do it back when I learned Unix. It's become a real mares' nest as Linux has evolved to accommodate DNS, mDNS, WINS, and god knows what else 

Regards,
Kent

[Sander]

I got mine working by using the IP address instead of the hostname.

[Relocated2007]

I had some errands to run but I tried IP/music did not work. Tried "DiskStation.local/music", but there is progress as the error is now permission denied, even though I have our mu id and pass when creating music source. I kind of shocked that Synology is so difficult to moode to discover, I might configure it wrong or so. But all other machines can discover Sunology without a blink so what is really going on.

I tried SCAN button but it does not discover Synology at all. Only the local NAS folder on sd card where moode is too.

[the_bertrum]

I had some errands to run but I tried IP/music did not work. Tried "DiskStation.local/music", but there is progress as the error is now permission denied, even though I have our mu id and pass when creating music source. I kind of shocked that Synology is so difficult to moode to discover, I might configure it wrong or so. But all other machines can discover Sunology without a blink so what is really going on.

I tried SCAN button but it does not discover Synology at all. Only the local NAS folder on sd card where moode is too.

I have a Synology too, and I've never managed to get it to show up in the scan.  <hos>.local/<share> always works for me however.  I have a special user for my moOde players defined on the Synology which has explicit read/write permissions on the music share.

[TheOldPresbyope]

I had some errands to run but I tried IP/music did not work. Tried "DiskStation.local/music", but there is progress as the error is now permission denied, even though I have our mu id and pass when creating music source.

"Permission denied" means moOde using "DiskStation.local/music" reached the NAS but gave it incorrect credentials for the "music" share. Best have another look at what you set up in the Source config panel. 

What do you mean exactly by "IP/music did not work"? It suggests the IP address you entered is incorrect. A quicky test from moOde's command line: if you ping "DiskStation.local" you should receive back the same IP address.

I kind of shocked that Synology is so difficult to moode to discover, I might configure it wrong or so. But all other machines can discover Sunology without a blink so what is really going on.

I tried SCAN button but it does not discover Synology at all. Only the local NAS folder on sd card where moode is too.

Since the last time Tim modified the relevant moOde code, I've had no trouble discovering the shares on my virtual Synology NAS along with the shares on my OpenMediaVault NAS, my other moOde players, and my Linux file server. I've already mentioned the need to append ".local" to the discovered server hostnames to force the use of mDNS but this is true for all my sources and not just the Synology.

Incidentally, I don't use Volumio but I just spun up Volumio 3.301 for a test on a spare RPi. It discovers the same shares on my LAN that my moOde players do. As well, moOde discovers the shares exposed by the Volumio player. I do notice that Volumio uses the IP address rather than the symbolic name for the NAS when it mounts the source.

Sorry, I can't repro your problem. I think I'm done here.

Regards,
Kent

[suzywong]

Curiously with the 64 bit 8.1.1, MoOde would not find my Synology NAS using <IP address>/music, something that previous versions have been doing for many years.

However it was happy using <host>.local/music.

[EarsOfAnEagle]

One thing to check, is that the SMB version mount flags (specifically the VERS= ) is compatible with the minimum SMB protocol version specified on your Synology NAS. 

In the Synology NAS DSM, the SMB versions are specified here:
Control Panel -> File Services -> SMB Tab -> Advanced Settings
Maximum SMB Protocol  -> SMB3 (or whatever is appropriate for your network)
Minimum SMB Protocol -> SMB2 (or whatever is appropriate for your network)

So in the above case, the Moode SMB Mount flag should specify:
VERS=2.0  or  3.0   as the values are within the maximum and minimum values specified on the NAS.

The default value of 1.0 would/should not work in the above case, so you need to check your specified values on your NAS to discern the proper flag value.
(FYI, use of SMB1 has been discouraged for a number of years)