Zoltan wrote: > I reinstated my old Raspberry Pi running SqueezePlug and I find that I > am able to mount the nfs share there without any issues with > permissions. > > The mount command I used there is: > > mount -o nolock <synology ip>:/volume1/music /mnt/.../music > > I'm not sure why the "-o nolock" here; I found this in my bash history. > No doubt it was advised on some website I found at some point. In any > case, I tried this option on the U3 to no avail.
So you have checked that the nfs-common-package is installed and the permission for gainig access to the directory which should be mounted is set to the right ip on your synology? You may set nolock without any problems, but I think it won't be a solution for your problem. my mount looks like this: <Synology-IP>:/volume1/SqueezeplugMusik /mnt/Musik nfs defaults,tcp,intr,_netdev,noatime and all works fine. defaults The device will be mounted with following options: rw, suid, dev, exec, auto, nouser and async tcp Specifies for the NFS mount to use the TCP protocol.(nfsV4 just supports tcp) intr Allows NFS requests to be interrupted if the server goes down or cannot be reached. _netdev The _netdev option tells the system to wait until the network is up before trying to mount the share. noatime Contrary to atime . Who wants to know no access times , can reduce disk activity with this option , because every time the inode table to be updated when a file access . I hope I was able to help you. ------------------------------------------------------------------------ alverus's Profile: http://forums.slimdevices.com/member.php?userid=62764 View this thread: http://forums.slimdevices.com/showthread.php?t=105643 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
