FOG server - Fatal Error: Failed to mount NFS Volume
-
Inbroker - did you only make these changes:
“[FONT=sans-serif][COLOR=#000000]Edit the storage node definition with the IP address of your NFS server and set the image location to the path on the nfs server. Make sure it has a file called .mntcheck in the root of the share, a directory called dev and a .mntcheck file in the dev folder.” or did you also have to edit the config.php file? I am getting the same error trying to save the images to a Lacie 5big NAS. [/COLOR][/FONT][quote=“Inbroker, post: 1020, member: 398”]Hi Nikolai,
thanks for your reply. Actually in my case the solution was even simpler since i didn’t have to mess up with iSCSI but just an external NFS server. So, another classic case of RTFW as described here [url]http://fogproject.org/wiki/index.php?title=FOGUserGuide#Separate_NFS_Server[/url].
Don’t know why but my mind has stuck in the idea that the /images folder was some kind of a magical folder required by Fog. I just pointed the image directory to the NFS share and it worked fine.Thanks for your help.[/quote]
-
Hi everybody,
I am having the same problem. Here is my setup.
FOG Server is installed on a Ubuntu Server 10.04 with the current version 0.32.
the NFS Server is currently a FreeNAS version FreeBSD 8.2-RELEASE-p1.I can mount the NFS Share and access it on the FOG Server using Webmin and create / modify /delete files and folders.
I have also successful followed the instructions
[B]Change NFS location[/B] ([url]http://www.fogproject.org/wiki/index.php?title=Change_NFS_location[/url])
with the exception of the step 2 exportfs -a, because when I SSH into the FreeNAS Server and run it, it says “unknown command”.But what my basic fundamental question is on what Maproot User, Maproot Group, Mapall User, Mapall Group on the FreeNAS NFS share I have to select, because this I think is the problem in not getting the NFS share mounted when booting the client for uploading or downloading an image from the NFS share on a separate NFS Server.
The configure of the new image location works so far that I can see at the dashboard the correct Freespace size of the NFS Share.
The exports file on the freenas has following entry.
/mnt/Library -alldirs -network 192.168.111.32/27
which does not look the same as in the instruction [B]Change NFS location[/B], but it is forbidden to change the exports file manually on the FreeNAS.
Any workaround?
I will keep looking and keep you posted.
-
Ditto:
I have seen this issue everywhere, some claim a solution… but no solution has worked for me yet.[B]What:[/B] 192.168.1.63:/images/dev/ failed, reason given by the server. No such file or directory
mount: mounting 192.168.1.63:/images/dev/ on /images failed: Bad file descriptor
Fatal Error: Failed to mount the NFS Volume
Background: I have a NFS server which I mounted within the fog-server… Its mapped to the “/images” directory.
I also added another mountpoint for “/images/dev” (after it failed).[B]Mntcheck?[/B] Yes, I added the file to both the /fogimages and /fogimages/dev (.mntcheck)
I checked the user and group settings as well… I compared them to the default /images and /images/dev.
They are all root root (owner and group) and permissions are 777 for both.
Now, Like I said, I mounted the NFS locations and that part works… In terminal I can goto /fogimages/ and see the files on the NFS Share.
I did follow this guide [URL=‘http://fogproject.org/wiki/index.php?title=Image_Upload:_Error_Checking_Mount’]Image Upload: error Checking Mount from the wiki. [/URL]
Obviosly it looks like it cannot access or write to the /images/[B]dev[/B] directory.
any suggestions? I think I have tried everything.
-
Hi there,
for a temporary solution I just installed a 2TB hdd into the FOG Server directly, so I can use it. My problem seems to be the lack in understanding on how to configure NFS. I am coming from the windows side :(.
But I have also the impression that a seperate NFS Server will work when you have that NFS Server installed as FOG Storage Node. I guess it does come down to the user name, password and permissions on the NFS share. Within windows i would have no problems to setup a share and make it work, so I assume t should be done in a similar fashion.does anyone have a good tutorial on NFS Shares?
cheers
-
This post is deleted! -
Hello,
I am also receiving this error when I attempt to upload an image from a machine. I have used webmin to mount my NAS NFS share on /images. As long as it is mounted I get this error, as soon as I unmount the NAS, I have no problem uploading an Image to my fog server’s hard drive. When it is mounted I have read/write access from the fog server, and can freely add files to the NAS with no issues. I believe the issue lies in the host trying to mount /images, which is really my NAS. Any help is greatly appreciated and I am extremely new to Linux. Oh and it’s on debian.Thanks Adam
-
Can anyone confirm the user that fog is mounting the NFS share with? is it fog? [B]Permission Denied.[/B]
the clue is pretty clear:
[B]Fatal Error: Failed to mount NFS Volume.[/B]Then when I setup my /etc/exports and run exportfs -a I get an error of
[B]/images does not support NFS Export.[/B]
So, far we have the facts:
A: Permission Denied
B: Failed to mount NFS Volume
Does not support NFS Exportstill searching for a solution… am also about to try a few other things, will share if anything comes from it.
-
Bump… Still stumped on this…
-
This is actually the same problem I am having.
NFS share on FreeNAS machine is exported, and i can mount it from the FOG Machine fine.
I created a fog user on the FreeNAS machine with same password as fog user on FOG install.Created a user on FreeNAS (fog, same password as fog user on FOG machine)
chown -R fog /mnt/mountPoint/NAS/images
chmod 777 //mnt/mountPoint/NAS/images (for testing of course)on fog server mount the images directory as /NAS
can created file, directory’s there no problem, as well as in /NAS/dev
have .mntchek file created in both places (/NAS, /NAS/dev)
when I log into the web interface, the storage node stats are correct.
Tried setting IP in storage node to IP of FOG and also of NFS server (FreeNAS machine)
Also tried changing the path to local path or NFS path (Fre.NAS.IP.ADDR:/mnt/mountPoint/NAS/imagesi still get permission denied when client boots up and tries to mount NFS share to upload image to.
I also get " Does not support NFS Export" when running “exportfs -a”.
Kyle
-
What user id does does the FOG client use when it attempts to mount the storage directory from the fog server?
-
on my machine (fresh install of ubuntu 10) fog is user 1001.
I made sure the user fog had the same ID and pass on my NAS. (no success) -
Hey there,
I am tinkering around with another problem. I am receiving also on one of the laptops the vbe_init () failed with -22 because it seems that the /sbin/v68d is missing.
so I am wondering if this NFS permissions problem is not with the FOG Server, as we can create the NFS Share on a different Storage Solution and mount it, but more like the kernel file or image or config used in the /tftpboot/fog on the fogserver is the problem?
cheers
-
[quote=“Inbroker, post: 1020, member: 398”]
Don’t know why but my mind has stuck in the idea that the /images folder was some kind of a magical folder required by Fog. I just pointed the image directory to the NFS share and it worked fine.
[/quote]So what EXACTLY did you put in there besides /images?
You said you put in the image directory on the share? how? 192.168.1.xx:/images ???This may be the answer everyone is seeking.
-
I was getting the OP’s error. When trying to mount the NFS it was failing. I noticed that it had the wrong IP address, it was that of the outside NAT card, no the internal LAN card (VM). After correcting the settings in the FOG server (Storage management, all stoage nodes, edit, IP Address) I was still seeing that incorrect IP address when booting a host. I tried rebooting the server thinking that something might not have applied correctly - no difference.
Then I decided to try registering the host again through the boot menu. After that and setting up the image task it was able to start the task! I don’t know if the settings are actually stored on the host machine or if it’s just coded into the host configuration file, but I would suggest that to everyone having problems in this thread. Make your changes, re-register your client, and then see if it works for you.
-
This post is deleted! -
This post is deleted! -
i had the same problem, turns out i just needed a .mntcheck file created in /images and /images/dev.
[url]http://fogproject.org/wiki/index.php?title=Image_Upload:_Error_Checking_Mount[/url]
ive mounted a 1TB drive to /images before installing fog, created the .mntcheck files, and it now works perfectly! -
[quote=“KK20, post: 3647, member: 1185”]As an addendum. Openfiler has a particular quirk. Openfiler lets you create a folder then assign a share to the folder. You get to mix and match from SMB,CIFS, NFS, FTS or RSYNC. I chose NFS and FTP for my FOG share. NFS maps this as /mnt/raid6/data/FOG/
however. within FTP it is mapped to /raid6/data/FOG - i.e. the /mnt is dropped. In order to get the very last FTP copy portion to work (to avoid “unable to move” errors)I needed to edit :
/var/www/fog/service/Post_Stage2.php
and alter the $src and $dest portions slightly. Im sure there is a config area for this somewhere but I didnt have time to find them. I couldnt see one in the settings part of the UI.[/quote]
Hi KK20, what changes did you do to the Post_Stage2.php? as I’m having the exact same problem with FOG and Openfiler?
Many thanks,
Stephen…
-
nevermind for future reference I inserted the following after line 78 of /var/www/fog/service/Post_Stage2.php
$noderoot = ltrim($noderoot, “/mnt”);
All working with openfiler now
-
This post is deleted!