Fatal Error: Failed to mount NFS volume
-
@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…
-
@Wayne-Workman Nope, still getting the same message because it doesn’t see the path /FOG/Images
-
@Wayne-Workman
“I tried setting the Fog server on several Ubuntu boxes and was unable to do so. After reviewing this case with our team, its come to my attention we can only currently support NFS shares directly to Ubuntu System. I have put in request to our development team for testing and support for FOG server.”Synology technical support
I randomly came across this, has anyone ever used Synology boxes and would this even make sense? Could this be the reason why it is not working?
-
Just so everyone knows, I called Synology and we got it working. The problem was that on the Synology the NFS Permissions had to be changed. Squash had to be no mapping and the host IP address was changed to *. Once this was done, upload started right away.
I want to thank everyone for your help. Really appreciate it!
-
After the image finished uploading, it gave an error message of
I am going to reboot the machine to see if the image upload took but wanted to see if anyone knows why I got this error message?
-
Check this out:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTPlet us know if you need help.
If you solve it, please report what was done to fix it.
-
Good afternoon, sorry I work in a school district and was off yesterday. I am mstill troubleshooting through that ftp issue from last week but so far FTP seems to be working fine and could be the user log in info that is incorrect. Will update further…
