From the GUI you are not able to mount NFS shares…
It seems the fix would be simple as it can be done from the command line…
It looks like there are two options to make this successful:
1) Start statd
2) Add the '-o nolock' to the mount command
Here is the output below when mounting from the CLI
[email protected]:~$ sudo mount 192.168.1.104:/export/Media/Music /mnt/NAS//
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
[email protected]:~$ sudo mount -o nolock 192.168.1.104:/export/Media/Music /mnt/NAS/<MOUNT_POINT/
as you can see I used the -o nolock which worked and my database is building….. this will take a while
Just FYI
when you login you can also simply run
rpcbind
then do a sudo mount 192.168.1.3:/export/Music /mnt/NFS/
And it mounts just fine.
the only issue is that sometimes it unmounts it… (not sure what is going on there yet)
I strongly support your request about NFS support.
I have to run a script manually after boot. Have not got it to start at boot yet.
My script:
/etc/init.d/rpcbind start
/etc/init.d/nfs-common start
mount -t nfs 192.168.1.107:/mnt/raid/music /var/lib/mpd/music/Server
/etc/init.d/mpd restart
This works fine on my system once up and running.
I would say, make some code for it so they only need to add a few buttons and a webpage
So if the correct command is:
sudo mount -o nolock 192.168.1.104:/export/Media/Music /mnt/NAS/<MOUNT_POINT/
The IP:location should be editable as well as the mount_point so youll get to see the correct name in the database, so you would get a command a little something like this:
sudo mount -o nolock %ip:%location /mnt/NAS/%mount_point
Put it in a python (or what style/language is prefered) make %ip %location %mount_point variable
Then the scipt can be incerted in the other startup scipts that already run.
And the variable filling, shoudnt be to hard for the webpage creators and submit it to them so they can test and implement it.
For the people who dont know how to start a script when there system starts, you can do it with bash.bashrc or as a cronjob.
For a Cronjob do:
crontab -e
Goto the end of the file add:
@reboot /[complete path of the script]
[edit] mabey you want to give the R-pi a few seconds to get the network online then youll need to put a delay in the scipt.
Most Users Ever Online: 200
Currently Online:
7 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Gyp: 82
yoghurtlidlicker: 37
PaulM: 36
icai: 35
Derek: 29
Karsten: 27
tc-fi: 22
Ronaldo: 21
ENSen: 21
chriz: 20
Member Stats:
Guest Posters: 3619
Members: 569
Moderators: 0
Admins: 1
Forum Stats:
Groups: 4
Forums: 10
Topics: 469
Posts: 13163
Newest Members: polo2016, dongdong8, wlpwlp, Sager, ninestab123, lmx66, lmx, jlgg, chenyan, guoyanying
Administrators: admin (401)