Fatal Error: Failed to mount NFS volume

szecca1 · May 27, 2015, 7:37 PM

@Wayne-Workman The image is stuck in /images/dev.

I am guessing that would be the problem

Wayne Workman · May 27, 2015, 7:39 PM

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/images

So 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/Volume1

It’s just a shot in the dark maybe?

szecca1 · May 27, 2015, 7:44 PM

@Tom-Elliott Should I do this before I try to upload an image?

Tom Elliott · May 27, 2015, 7:46 PM

@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 · May 27, 2015, 7:46 PM

@szecca1 I just tried that command and it says failed to create symbolic link as directory /Volume1/Volume1 does not exist

Wayne Workman · May 27, 2015, 7:50 PM

@szecca1 said:

@szecca1 I just tried that command and it says failed to create symbolic link as directory /Volume1/Volume1 does not exist

Tom didn’t know what your volume was called. You have to put in the right name.

ch3i · May 28, 2015, 7:19 AM

@szecca1 said:

@szecca1 I just tried that command and it says failed to create symbolic link as directory /Volume1/Volume1 does not exist

Hi,

If you have mount your NAS in your server, please post the result of that command :

cat /etc/fstab

Regards,
Ch3i.

Tom Elliott · May 28, 2015, 9:44 AM

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.

szecca1 · Jun 4, 2015, 6:02 PM

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!!!

Chris Bosman · Jun 30, 2015, 9:29 PM

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.

Wayne Workman · Jun 30, 2015, 4:29 PM

@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.

Chris Bosman · Jul 1, 2015, 4:06 PM

@Wayne-Workman Hey, thanks for the reply. I’m back in to the office and working on this issue.

I was able to confirm that FTP is working in general on the NAS via Windows.

So my problem is twofold:

The first is I was/am having the same specific issue as @szecca1 where after uploading an image, the image does not properly get FTP’d to the folder for images that I have set up and instead stays in the dev folder under the MAC address. I am assuming this has to do with the FTP issue that @Tom-Elliott described and suggested the symbolic links. I was able to eventually properly put up the symbolic links. I haven’t been able to test yet, but I think that any new upload will be able to be used properly.

But that’s where my second issue comes in. I have an upload that I need quickly downloaded that ended up in a /dev/[MACADDRESS] folder. I manually moved the image to a folder named appropriately for said image but I’m still not able to create a download task. It’s like the image within FOG is not associated with the folder I created. I am not sure how to forge this association so I can start the download task. This is a large image file and I do not necessarily have time to upload it again. Any suggestions would be appreciated. Thank you.

Wayne Workman · Jul 1, 2015, 4:11 PM

@Chris-Bosman Image paths and names are case sensitive. the hidden .mntcheck files are required. Also check your permissions on the /images directory, maybe set them recursively. https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS#Permissions

Chris Bosman · Jul 1, 2015, 4:48 PM

@Wayne-Workman Case is confirmed correct and the .mntcheck files have been moved there. Uploading works fine. I set the permissions recursively but still cannot set up a download task. I get the error:

“Download task failed to create for [COMPUTER] with image [IMAGE NAME]
To setup download task, you must first upload an image”

Wayne Workman · Jul 1, 2015, 4:09 PM

@Chris-Bosman @Developers @Moderators

I was able to take a look at Chris’ issue via Team Viewer.

The FTP root directory is:

/volume1/

I created a soft symbolic link:

ln -s /volume1 /volume1

However no FTP user (admin and fog) could see the symlink. So I tried to change permissions and ownership of the file.

chown fog:root /volume1/volume1
chmod 777 /volume1/volume1

While the permissions did change, the ownership of the link did not, and no FTP user could see the link still.
The ownership is set as root root and it would seem that… for some reason… this can’t be changed…

I then created just a test file called /volume1/test.txt
I changed the ownership of this file to fog:root and permissions to 777 and still no FTP user could see this file either, and still the ownership did not change like it should have.

Only the directories inside of /volume1/ could be seen by any FTP user.

So the issue is… for some reason, the FTP user admin and fog can not see any individual files located in /volume1/ therefore the symlink is not working.

Additionally, this particular NAS has many network interfaces (all operational) that are boded together to a interface named bond0 so I set this interface name within the storage node settings.

Wayne Workman · Jul 4, 2015, 2:36 AM

@Chris-Bosman A new feature has been added to FOG Trunk that allows users to specify the FTP path to the image directory for any storage node.

This is exactly what you need in your situation. The relevant thread is here: https://forums.fogproject.org/topic/5333/ftp-path-for-storage-nodes

Here is how you would upgrade to FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Fatal Error: Failed to mount NFS volume

162

12.0k

17.3k

155.2k