Paul Webster wrote: > In general, it is easier (for newcomers) to get CIFS working than NFS - > assuming your NAS allows connections from Windows systems using Windows > File Manager (or whatever it is called nowadays). > > In that case first show that you can access the NAS share from a Windows > machine and make a note of the exact path ... something like > \\nasbox\shares\mymusic > or > \\192.168.1.50shares\mymusic > and see if you can get in without a username/password ... or a user name > of guest with no password etc etc. > > Then show all of the fields that you have set in the pCP configured > section for that NAS mount.
I can access the NAS share from Windows Explorer with no problem, and I think I can arrange for the NAS to let in a guest with no password. The command that pCP is using to mount the share is: > mount -v -t nfs -o addr=192.168.2.158,nolock,uid=1001,gid=50 > 192.168.2.158:"/volume1/Audio" /mnt/Pythagoras > But I would be more interested in trying to get it working through ordinary NFS. This seems doable. If I boot the Pi with the full raspbian software, I can mount the NAS share with a simple command (same as the above but without a lot of the details), play music, and it's beautiful. So, it's not a matter of permissions or something else wrong on the NAS side. The command that works in raspbian doesn't work in pCP (which, ironically, is the very command—simplified—that pCP itself tries to use). It seems like something is missing (or not loaded) from the pCP distribution that is blocking the mount. My present state is that I can't figure out what that is. I don't know how to verify that nfs is running under pCP. The apt command seems to be missing. I also tried installing the nfs extensions found under "Extensions" on the Main Page: nfs-utils.tcz. This changed the error message for the mount command to: > [INFO] mount -v -t nfs -o addr=192.168.2.158,nolock,uid=1001,gid=50 > 192.168.2.158:"/volume1/Audio" /mnt/Pythagoras > > mount.nfs: timeout set for Tue Oct 12 17:09:25 2021 mount.nfs: trying > text-based options > 'nolock,uid=1001,gid=50,vers=4.2,addr=192.168.2.158,clientaddr=192.168.2.29' > [ERROR] Disk Mount Error, Try to Reboot. When I reboot and the network drive tries to mount, the previous error message is repeated along with: > mount.nfs: mount(2): Invalid argument > mount.nfs: an incorrect mount option was specified > This seems like progress. Your help is very much appreciated!! -David ------------------------------------------------------------------------ dpotts's Profile: http://forums.slimdevices.com/member.php?userid=29782 View this thread: http://forums.slimdevices.com/showthread.php?t=114828
_______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
