More > JRiver Media Center 27 for Linux
Quick Start Guide for Installing JRiver Mediacenter 27 on an rPi4 2-4-8GB
HaWi:
--- Quote from: erviv on February 13, 2021, 02:50:27 pm ---For what it’s worth, I never was successful at mounting a network attached (actually router attached) storage device on my rpi. So as a solution I always opened the path manually from the Debian desktop on my Pi to the NAS, or from vnvserver. From there I could reach my music files. This worked fine unless there was a power failure in which case I had to re-establish the connection to the NAS.
What has worked much better was attaching my storage device directly to my Pi and mounting it via fstab. I also use systemd to auto open JRiver. So when I have a power failure everything restarts successfully.
--- End quote ---
Thank you erviv,
I am very new to the RPi and don't even know how to mount a drive on the Pi manually. I'll do some research on that. I am currently running MC27 in docker on my NAS and it's working fine. I'd like to keep my media files on the NAS and run MC on the Pi because I can get a HDMI output directly to my AVR which allows me to play multi channel tracks.
mwillems:
The path portion of the fstab should not contain a protocol (no smb: prefix), it should be in the form:
--- Code: ---//<IP address of NAS>/<sharename>/<directory inside share if wanted>
--- End code ---
The uid and gid should be the local uid and gid (on the pi), not the NAS's uid and gid. Those flags set the local user and group of the shares on the pi. That is to say if you want to mount the share so the "pi" user can access it, you'll want to use the uid of the pi user and the gid of a group the pi user is in. You can use names instead of numbers to make it easier, e.g. uid=pi,gid=audio etc.
EDIT addendum:
Some nice to have tips:
These days I would also suggest using a smb/cifs protocal version higher than 1.0 if your NAS supports it, as version 1.0 is deprecated and insecure and may not be supported by all samba server implementations anymore. I use 3.0 here, but your NAS software will determine which version is best.
HaWi:
--- Quote from: mwillems on February 13, 2021, 03:06:43 pm ---The path portion of the fstab should not contain a protocol (no smb: prefix), it should be in the form:
--- Code: ---//<IP address of NAS>/<sharename>/<directory inside share if wanted>
--- End code ---
The uid and gid should be the local uid and gid (on the pi), not the NAS's uid and gid. Those flags set the local user and group of the shares on the pi. That is to say if you want to mount the share so the "pi" user can access it, you'll want to use the uid of the pi user and the gid of a group the pi user is in. You can use names instead of numbers to make it easier, e.g. uid=pi,gid=audio etc.
--- End quote ---
Thank you mwillems,
I tried many versions but always forgot the trailing":" after the IP address ('cause I didn't know).
--- Code: ---<IP address>:/volume1/music /mnt/music nfs defaults 0 0
--- End code ---
Thank you for your effort, it is highly appreciated
Hans
Wheaten:
you don't need a trailing ":".
Are you able to mount the remote share via the shell?
you can replace "vers=1.0", by a higher version, depending on your NAS supported SMB version
--- Code: ---sudo mount -t cifs -o rw,vers=1.0,credentials=/home/pi/.credentials //192.168.xxx.xxx/share /home/pi/Music
--- End code ---
--- Code: ---sudo mount -t cifs -o rw,vers=3.0,credentials=/home/pi/.credentials //192.168.xxx.xxx/share /home/pi/Music
--- End code ---
HaWi:
Thank you Wheaten,
I have been able to mount the share but I will be changing the version as the Synology can do SMBv3, or, alternatively, I'll try to mount it as an NFS share, as I have good experience with that on my iMac. NFS seems to be more stable. On the iMac, SMB shares disappear for no reason occasionally and I need an automounter to keep them connected. With NFS shares that doesn't occur (as often, I should say).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version