I am having a problem with mounting an NFS share from my Western Digital server to my Raspberry Pi. As a relatively inexperienced Raspberry user, I solicited help from several collaborators and ultimately I learned that NFS was the best way to interface with the server. In addition, we learned that
rpcbind needed to be running for the mount to proceed. With their help, after creating an
nas folder within my
pi folder, I was able to insert the following lines in my crontab file:
@reboot sudo /etc/init.d/rpcbind start @reboot sudo mount -t nfs 192.168.1.152:/nfs/Music /home/pi/nas @reboot /usr/bin/asset/bin/AssetUPnP
This script actually worked quite well for a while. Unfortunately, I now find that the mount no longer occurs automatically, despite my being sure the server is awake and can be accessed before starting the Raspberry Pi. Of interest, I do find that the AssetUPnP program does open.
More confusing, however, is that following the unsuccessful mount, if I then access the Raspberry Pi directly via terminal and manually enter the first two lines in sequence, they work perfectly, the share mounts and then the -- already running -- AssetUPnP program can access the mounted share. Thus, I believe the scripts seem to be properly composed. Might anyone have any suggestions about what might be going on here? Do I need to program in some kind of delay between the first and second line? Am I missing something else? Any help would be greatly appreciated.