I am desperetly trying to add my shared directories into volumio (volumio-2.001-2016-10-15-pi) but without success.
I run Volumio 2.001 on Raspberry Pi. It was working immediately with an earlier version (Volumio1.55PI)
I have been reading and testing almost all day, and nothing works. I am about to give up.
With journalctl -f I saw some access denied (at boot time?), and errors when defining the share in the GUI (Missing error handler, Cannot read property ‘replace’ of undefined)
Did anyone succeed adding a share from Synology? Any problem/solution? (can you give snapshots in both volumio and Synology of working examples).
Should I:
mention the IP address or the alias
with or without / or //
the Path should contain volume1 or not (e.g. volume1/music)
same Problem here with my synology.
Sometimes volumio finds it by scanning, but when I click on the find, the list is empty (never saw how it should look right, but I guess there should appear the shared Folders). But most of the time, a scan does not find anything. I could reproduce the finds and at the same time the nas is always available from other apps/Software like the Explorer.
I also tried Manual configuring like mentioned above, all that stuff. Checked also this thread experience-getting-volumio-going-t746.html
Have sharing with NFS activated and tried there also nearly every Option.
I am at the end of my limited possibilities.
Yes, shares definitely work with my Synology NAS using NFS. Volumio’s NAS discovery doesn’t work for my setup, but manual configuration has always been straightforward.
On the Synology NAS, you need to:
(1) know the path of your share on the NAS … my shared folder ‘Music’ path is actually ‘/volume1/Music’;
(2) enable the NFS service from ‘File Services’ in the ‘Control Panel’;
(3) enable NFS permissions for the device (Volumio IP address) accessing it by editing the ‘Shared Folder’ permissions for ‘Music’.
[spoiler][/spoiler]
This settings of permissions for NFS may be a problem if your Volumio device does not have a static IP address, although I believe, but haven’t tried personally, that you can use a “network segment” here to cover a range of addresses.
In the Volumio UI, you need to:
(1) choose an alias (anything you want to call your NAS);
(2) add the NAS IP address in the form 192.168.1.x.y;
(3) add the NAS path to the shared folder eg. /volume1/Music;
(4) choose NFS as file share type.
[spoiler][/spoiler]
You do not need to add filename, password or further options
did everything like that and did not succeed. Checked “nearly” everything, but now it works. Call me dumb, but I did rebooted my NAS. After a reboot, volumio could Mount the Folder immediately. DId not know, that NFS Shares Need a reboot to activate. Is that so?
Hmmm… I have gone forward and the problem is back.
I added some other drives, and :
previoulsy defined one was unmounted
new one never got mounted
after reboot I got the following messages for each drive:
Nov 02 14:27:45 volumio volumio[854]: exec error Error: Command failed: /usr/bin/sudo /bin/mount -t nfs -o ro,soft,noauto DEVIDISK:/volume1/music-eac /mnt/NAS/eac
Nov 02 14:27:45 volumio volumio[854]: mount.nfs: access denied by server while mounting DEVIDISK:/volume1/music-eac
Nov 02 14:27:45 volumio volumio[854]: info: Cannot mount NAS at system boot, trial number 4 ,stopping
@chsims1: thanks for your questions. I tried what you said (with volumio 2.01) unfortunately with no sucess…
In the share drive:
two are like the picture below
one has the volumio username and password
one has options _netdev,x-systemd.automount
… none works.
I get this with journalctl… everything looks all right - at least there is no return code.
What surpries me are the “PWD=/ ; USER=root” settings. If have allowed volumio. ‘root’ is reserved in Synology, and not selectable in the “Permissions” list of users. So I cannot allow root.
I allowed administrators to give it a try. Not better.
Nov 03 19:39:23 volumio volumio[923]: info: Loading plugin "networkfs"...
Nov 03 19:39:24 volumio sudo[960]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mount -t nfs -o ro,soft,noauto,_netdev,x-systemd.automount 192.168.1.2:/volume1/music-eac /mnt/NAS/eac
Nov 03 19:39:24 volumio sudo[960]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 03 19:39:24 volumio volumio[923]: info: Loading plugin "alarm-clock"...
Nov 03 19:39:24 volumio sudo[962]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mount -t nfs -o ro,soft,noauto 192.168.1.2:/volume1/music-sacd /mnt/NAS/sacd
Nov 03 19:39:24 volumio sudo[962]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 03 19:39:24 volumio sudo[964]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mount -t nfs -o ro,soft,noauto 192.168.1.2:/volume1/music-mp3 /mnt/NAS/mp3
Nov 03 19:39:24 volumio sudo[964]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 03 19:39:24 volumio sudo[970]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mount -t nfs -o ro,soft,noauto 192.168.1.2:/volume1/music /mnt/NAS/misc
Nov 03 19:39:25 volumio sudo[970]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 03 19:39:25 volumio sudo[960]: pam_unix(sudo:session): session closed for user root
I have tested with volumio 1.55, it worked immediately with basic settings. Well now the definition of the drives have dissapeared automatically after an update ???
but it was working. (my library is really huge - over 4TB of music - could it be the reason for the scab failure, that’s another problem).
The test returns indeed “access denied” (I used the same as configured):
Test 1:
volumio@volumio:~$ sudo /bin/mount -t nfs -o ro,soft,noauto,_netdev,x-systemd.automount 192.168.1.2:/volume1/music-eac /mnt/NAS/eac
mount.nfs: access denied by server while mounting 192.168.1.2:/volume1/music-eac
volumio@volumio:~$
Test 2:
volumio@volumio:~$ sudo /bin/mount -t nfs -o ro,soft,noauto 192.168.1.2:/volume1/music-sacd /mnt/NAS/sacd
mount.nfs: access denied by server while mounting 192.168.1.2:/volume1/music-sacd
volumio@volumio:~$
Well as Michelangelo said previously, it looks as though the problem may well lie with the Synology NAS denying volumio access to the share. I don’t understand though how it worked previously & then did not. Can you revert to the original share working?
Also, @Michelangelo, why should it work with volumio 1.55?
Nov 3 22:00:43 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-sacd (/): not exported
Nov 3 22:00:43 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-mp3 (/): not exported
Nov 3 22:00:43 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music (/): not exported
Nov 3 22:01:14 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music (/): not exported
Nov 3 22:01:14 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-mp3 (/): not exported
Nov 3 22:01:15 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-sacd (/): not exported
Nov 3 22:01:15 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-eac (/): not exported
Nov 3 22:01:22 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music (/): not exported
Nov 3 22:01:22 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-eac (/): not exported
Nov 3 22:01:23 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-sacd (/): not exported
Nov 3 22:01:23 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-mp3 (/): not exported
Nov 3 22:01:27 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music (/): not exported
Nov 3 22:01:28 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-eac (/): not exported
Nov 3 22:01:28 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-sacd (/): not exported
Nov 3 22:01:28 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-mp3 (/): not exported
Nov 3 22:01:32 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music (/): not exported
Nov 3 22:01:33 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-eac (/): not exported
Nov 3 22:01:34 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-sacd (/): not exported
Nov 3 22:01:34 DeviDisk mountd[7308]: refused mount request from volumio for /volume1/music-mp3 (/): not exported
I’m a bit confused really. Failure of manual mounting would suggest a problem with NAS permissions/services. Volumio 1.55 working ok would suggest it is a volumio problem. It’s rather a difficult problem solving someone else’s set up
Problem is solved, please find my conclusions (I did not spent hours on double checking but these are let’s say more likely the source of my problems.
What were the issues (I think):
in NFS Permissions : wildcard seems to not work completely:
working: * or full ip address (did not try hostname)
NOT working: network range: 192.168.1.*
NFS permissions must be defined as needed BEFORE the mount
So, if you try to make changes to these permissions for testing (which I did all day long… ) these seems to not be effective before reboot
So if you change the NFS permissions, a reboot is required after the permissions changes of first the NAS, than the volumio.
Here are my working settings:
On the NAS:
On volumio:
Thanks for your help.
PS: the fact that it was working with volumio 1.55 might be because I used icfs instead of nfs… but I am not sure.
[/spoiler]
[/spoiler]
)
:mrgreen:
