More > JRiver Media Center 27 for Linux
Quick Start Guide for Installing JRiver Mediacenter 27 on an rPi4 2-4-8GB
HaWi:
Thank you Wheaten,
I'll try this
mwillems:
I recommend including both noauto and the x-systemd.automount options rather than the auto option. The former options don't try to mount the share during boot, but instead automount the drive on demand at first user access. By contrast the "auto" option tries to automatically mount the share during the boot process which can delay the boot process or fail outright if the network isn't up in time for the mount. Mounting on demand is more robust IME. To be clear I haven't tested those options personally with nfs, but they should work, and with cifs they work a treat.
In re: samba/cifs if you want to use cifs but your share "goes away" periodically and gets "stuck" in a mounted or unmounted position, I feel your pain! I've also struggled with the issue. Linux sometimes doesn't recover gracefully when a network mount goes away while mounted. Here are my current cifs network share fstab options that I've refined over a few years to address the issue as a reference (you'll need to modify the share name, mount point, usernames, etc if you want to use them):
--- Code: ---//192.168.xxx.xxx/sharename /local/mount/point cifs noauto,x-systemd.automount,x-systemd.idle-timeout=5min,_netdev,uid=user,gid=users,credentials=/home/user/samba-credentials,vers=3.0 0 0
--- End code ---
This does three things: (1) doesn't mount during boot to avoid network readiness issues; (2) waits to mount until someone tries to access the mount (it takes less than half a second to mount so its pretty seamless) and (3) automatically unmounts the share after five minutes of idleness. This has the advantage that the share is only mounted when in use, which greatly reduces the likelihood that the share will "go away" while mounted and get stuck. From the user perspective, it's transparent: when you access the share it's just there, and I haven't had issues with the share getting stuck or being unavailable since I adopted these options.
HaWi:
Thank you mwillems, I appreciate your help. I am very new to this
HaWi:
Unfortunately, I am getting the "Parse Error" again with
--- Code: ---//192.168.7.224/volume1/music /mnt/music nfs noauto,x-systemd.automount,x-systemd.idle-timeout=5min,_netdev,uid=1000, gid=1000 0 0
--- End code ---
mwillems:
--- Quote from: HaWi on February 14, 2021, 01:48:33 pm ---Unfortunately, I am getting the "Parse Error" again with
--- Code: ---//192.168.7.224/volume1/music /mnt/music nfs noauto,x-systemd.automount,x-systemd.idle-timeout=5min,_netdev,uid=1000, gid=1000 0 0
--- End code ---
--- End quote ---
There should be no spaces in any of the comma separated options. You've introduced a space between the uid and gid options which is giving you the error, I suspect. The fstab format has six elements separated by spaces and there should only be spaces between those different elements, i.e.
--- Code: ---device mountpoint filesystemtype options,separated,by,commas,only dump pass
--- End code ---
If you're curious, there's more detailed info here:
https://www.man7.org/linux/man-pages/man5/fstab.5.html
https://en.wikipedia.org/wiki/Fstab
or by typing
--- Code: ---man fstab
--- End code ---
on the command line
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version