Fatal Error: Failed to mount NFS volume
-
@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.
-
@Wayne-Workman Ok I apologize I want to make everything clear for you so you have all the info. As you know I created a mount point within the Ubuntu folder images/. On my NAS server I created a folder called FOG, in this folder is the Images folder and in that folder is the dev folder. Clearly I didn’t do that right but should I use that syntax but replace “/data” with “/fog”?
I am sure I just confused everyone so please tell me if I need to be more clear
-
@szecca1 said:
@Wayne-Workman Ok I apologize I want to make everything clear for you so you have all the info. As you know I created a mount point within the Ubuntu folder images/. On my NAS server I created a folder called FOG, in this folder is the Images folder and in that folder is the dev folder. Clearly I didn’t do that right but should I use that syntax but replace “/data” with “/fog”?
I am sure I just confused everyone so please tell me if I need to be more clear
lol yeah that’s confusing…
So… You have a mount called images
On the NAS, there’s a folder called FOG/images?
Yeah just replace the /data with /FOG
Remember, Linux is case-sensitive. -
when done, restart NFS again. see if the errors go away.
-
@Wayne-Workman HAHA my apologies but you did get the idea of it which I appreciate you making out my disaster. I will give that a try but I have 1 question before I do that.
Do you know what the fsid is for?
-
@szecca1 said:
@Wayne-Workman HAHA my apologies but you did get the idea of it which I appreciate you making out my disaster. I will give that a try but I have 1 question before I do that.
Do you know what the fsid is for?
Absolutely not. But I know that it MUST be unique for each entry…
