Fatal Error: Failed to mount NFS volume
-
Do you have more than one storage node?
Are you using the location plugin?
-
@Wayne-Workman I do have two storage nodes, one that is the default and one I added called test. The default one had the admin login, so I changed that. Now it seems that is where it is pulling the login as now it is saying this error
“To setup download task, you must first upload an image”
Which may seem pretty basic but I already uploaded an image?
And unless I am using this location plugin by accident, no I don’t think I am using it -
@Wayne-Workman Should I only have one storage node?
What is the location plugin?
-
@szecca1 said:
@Wayne-Workman Should I only have one storage node?
What is the location plugin?
You can have as many storage nodes as you like…
The location plugin allows for image replication and for one primary FOG server to dictate orders and such to other FOG servers across WANs.
-
@Wayne-Workman I’m only going to have 1 FOG server on my network so would the location plugin be needed?
Why is the image that I uploaded not being detected by FOG? I probably set something up wrong, didn’t I?
-
@szecca1 said:
@Wayne-Workman I’m only going to have 1 FOG server on my network so would the location plugin be needed?
Why is the image that I uploaded not being detected by FOG? I probably set something up wrong, didn’t I?
If you’ve only got one fog server, you do not need the location plugin.
I thought uploads were working?
-
@Wayne-Workman I just started a new upload to test again but it is working. It’s when I go to download the image on to a client that says “to setup download task, you must first upload an image.”
My first impression is that the fog server doesn’t know where to pull the image file from but I dont know if I am right. I am uploading another image just to be sure right now.
-
Can you make sure these images are not stuck in /images/dev on your NAS ?
-
This is actually a very well known issue with Synology, and potentially other NAS’.
Basically, the NFS side works perfectly, but FTP fails miserably.
This is a configuration issue of FTP on the NAS. What’s happening is the “fog” user defaults to a jailed root position.
In your case, /Volume1/NAS/data/images (or whatever the path is)
NFS side works as expected, but FTP fails because it’s Jailed to start at:
/NAS/data/imagesSo basically, the mount point you have is set to /Volume1/NAS/data/images.
When FTP attempts to happen, It’s looking for /Volume1/NAS/data/images, but it’s really going to / which is the root of /Volume1
Basically ftp is looking for:
/Volume1/Volume1/NAS/data/images at that point, which obviously doesn’t exist.One way you could try to fix it is create a symbolic link to /Volume1 in side of /Volume1/
This could be done with:
ln -s /Volume1 /Volume1/Volume1It’s just a shot in the dark maybe?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Wayne-Workman The image is stuck in /images/dev.
I am guessing that would be the problem
-
@Tom-Elliott said:
This is actually a very well known issue with Synology, and potentially other NAS’.
Basically, the NFS side works perfectly, but FTP fails miserably.
This is a configuration issue of FTP on the NAS. What’s happening is the “fog” user defaults to a jailed root position.
In your case, /Volume1/NAS/data/images (or whatever the path is)
NFS side works as expected, but FTP fails because it’s Jailed to start at:
/NAS/data/imagesSo basically, the mount point you have is set to /Volume1/NAS/data/images.
When FTP attempts to happen, It’s looking for /Volume1/NAS/data/images, but it’s really going to / which is the root of /Volume1
Basically ftp is looking for:
/Volume1/Volume1/NAS/data/images at that point, which obviously doesn’t exist.One way you could try to fix it is create a symbolic link to /Volume1 in side of /Volume1/
This could be done with:
ln -s /Volume1 /Volume1/Volume1It’s just a shot in the dark maybe?
-
@Tom-Elliott Should I do this before I try to upload an image?
-
@szecca1 Well, for now, lets just get an image that’s there downloading. If that works, it will automatically work for uploads when they’re performed.
-
@szecca1 I just tried that command and it says failed to create symbolic link as directory /Volume1/Volume1 does not exist
-
-
-
This should be fixed. The ln command I gave is meant to be entered on the nas, not on the server. We did this last night and szecca1 was able to successfully create an image task. I don’t know for sure if it works but I have a strong feeling all is well now.
-
Hey guys sorry its been so long, I just wanted to test a few things before I came back here. Everything is working perfectly. Thank you so much!!!
-
I have gone through this thread because I too was trying to add a Synology NAS share as additional storage for my FOG server. Everything in this post was very helpful…
Until I got to the end. How did the FTP issue get resolved, step-by-step? I attempted to perform a symbolic link on the NAS as instructed in the final developer post, however this did not seem to resolve my issue.
Any further help would be greatly appreciated.
-
@Chris-Bosman There are FTP example commands here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
You would FTP into your Synology box and just see where that lands you… what is the default directory? Do a directory listing… maybe create a small file there (then later search for where it went) and just do what you can to figure out where you land when you FTP in.
You’d basically symbolically link that default directory that you land in to the actual root of the Synology box. (to my understanding).
There are also other ways… you can symbolically link from the default directory straight to the images directory… and define your storage node path as such.
