Fatal Error: Failed to mount NFS volume
-
I ran that command and still getting that same permissions error.
That is my file structure just so you can see. I am not sure as to why I am not getting access -
@szecca1 Where is mount your NAS on your server ?
-
I apologize, I am a newbie but as far as I remember I created the mount point under images. I mounted the NAS drive under images/ to minize the editing of fog since I saw FOG saves its images to that folder. If I did something wrong please suggest away. I am open to anything at this point.
-
As far as I can tell, FOG is seeing the storage fine and NFS is turned on properly. I just cant figure out why the mount is being denied.
Thank you
-
Verify that NFS is actually running?
Give the NFS service a restart?
Verify that Ubuntu Firewall is OFF.
-
@WayneWorkman I turned off the firewall running “sudo ufw disable.”
How can I verify that the NFS service is running? In the post below I have NFS checked on the Storage device. If I do find that it is running, how do I also restart that service?
Thank you
-
@szecca1 said:
@WayneWorkman I turned off the firewall running “sudo ufw disable.”
How can I verify that the NFS service is running? In the post below I have NFS checked on the Storage device. If I do find that it is running, how do I also restart that service?
Thank you
Try these:
[CODE]sudo service nfs-kernel-server status
sudo service nfs-kernel-server restart[/CODE] -
I ran those commands and this is what I got. The concerning part is where it says /images/dev does not support NFS export and /images does not support NFS export.
Is there something I missed that could be causing this?
-
@szecca1 said:
I ran those commands and this is what I got. The concerning part is where it says /images/dev does not support NFS export and /images does not support NFS export.
Is there something I missed that could be causing this?
Here’s your problem.
You’re telling FOG to mount the nfs server from the NAS, not the FOG Server, which you’re showing in the picture above.
-
@Tom-Elliott Ok I think I get what you mean. How do I change that? Sorry I am a beginner at this
-
@szecca1 You need to login (in much the same way) to the NAS box itself.
You can use ssh, or putty, or maybe from the web gui?
I don’t know the exact setup to figure things out.
-
@Tom-Elliott Ok so if I understand you correctly, the FOG client is trying to connect to NAS server and not to the fog server for its images? How do I tell the client to look in the right direction?
And when you say login to the NAS box in pretty much the same way, do you mean that the login and password have to be the same? I am using a Synology box with a web gui.I can send you anything you need to know about my setup that you need to know.
-
@szecca1 You need to have a user fog in your nas with the same password of your fog server.
-
@ch3i Created the user that I log into the FOG management console and still getting the same error message
-
@szecca1 The same login as specify in fog configuration FTP_TFTP_PASSWORD I think.
-
@ch3i Ah no I was using the password to log in to the admin console. I just changed it to that password which was different. I deleted the task of upload and started a new one and got the same error message. I even tried to restart the NFS service again and even that gave the same “does not support NFS export” error message.
-
@ch3i Do I need TFTP enabled on my NAS server? Could that be the problem that TFTP is not enabled right now?
Again thank you all for the assistance
-
-
@Tom-Elliott I saw this on another site, does this make any sense?
If still receiving the same error message after perfroming the above commands, you may need to edit /etc/exports to include your new mount point, i.e. /data/images and /data/images/dev with corresponding permissions.
See following example of /etc/exports:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
/data/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/data/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
-
@szecca1 said:
@Tom-Elliott I saw this on another site, does this make any sense?
If still receiving the same error message after perfroming the above commands, you may need to edit /etc/exports to include your new mount point, i.e. /data/images and /data/images/dev with corresponding permissions.
See following example of /etc/exports:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
/data/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/data/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
Your exports should reflect where the images are actually stored.
So if it’s /images, then you don’t need the /data lines; etc.
