[SOLVED]Problem Adding Synology NAS as Source

[poecameraon]

I'm not able to add my synology nas as a source for my RuneAudio Pi running a newer version of rAudio. Here's my setup:

version: rAudio 1 • 20210302
OS: 5.10.17-2-ARCH armv7l
Hardware: Raspberry Pi 3 Model B Plus Rev 1.3
SoC: BCM2837B0 • 962MiB
CPU: 4 Cortex-A53 @ 1.4GHz

Synology is a DS218+ on a VLAN setup for IOT/music.

I'm able to access the nas normally from a windows pc by mounting it \\192.168.XX.YY\music\

When I try to add the nas folder via the UI I have tried adding it as a CIFS with the following settings:
name: MediaNas
IP: 192.168.XX.YY
sharename: music
user: xx
password: xx
options: blank

When I click ok "network mount mount... " shows up in the bottom left corner blinking and a blinking icon shows up at the top for a short while and then stops and no new device is added.

I've tried changing the share name to several variations: music\ music/ etc. I've also tried enabling NFS on the synology and tried adding the folder as that and get the same result. Am I missing anything obvious? Any suggestions to try to debug? Any help would be greatly appreciated.

[eea123]

I would double check the directory, I have a QNAP NAS and had to use the default music directory of:

Multimedia/Music

On my network it appears as //10.0.0.XX/Multimedia/Music/ I also had to login as admin.

[rlsten]

[giovilux]

Hi,
I'm using a Synology DS218J with NAS.
You should find out what is the shared folder path in your NAS:
Control panel --> shared folders --> change your folder (in my case "Music") --> NFS tab --> you should see "mount path: /volume1/music"

in RAudio sources providing that the IP of your nas is correct --> /volume1/music

It should work

Giovanni

[rlsten]

[tsawyer]

great response risten. I had the same problem trying to get rune attach to a nas (pi running samba sharing a portable drive) and never got a chance to go back to it. in my case, part of the issue was getting samba to talk to the win10 box the way I wanted but even after solving that rune would only blink. I need to redo the nas (other reasons and need to finalize documentation for a lab exercise) but I definitely think editing fstab that way is going to bypass the nas button that hasn't been working. I only got a chance to do a quick look at the syntax of connecting to a 'windows' share from rune but think that nails it.

[poecameraon]

Oh man, I was about to call it quits after another evening of banging my head against the screen. I took a look at this post
post21144.html
and took another look at my NFS permissions in synology and realized the IP I gave permissions to (supposed to be rune pi) was incorrect, updated it and boom, source shows up. For others working with Synology NAS take a look at NFS permissions:

The Answer: A bad configuration of NFS on my NAS Synology.
For those who have the same problem:

in Control Panel/shared folder/music
In "Permissions", verify if on the line "admin", read/write is checked.
After in "Autorisations NFS"
I have the configuration like this:

Hostname or IP: 192.168.x.xx (it's the ip of my runeaudio)
Privilege: Read/Write
Squash: Mapping all users on admin
Security: sys

And check all after (mode asynchrone...)


While trying to debug I have not been able to ssh into my pi (using root/rune) but that's a battle/post for another day.

Thank you for all the helpful suggestions, it is much appreciated.

[neanderthaler]