• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

FOG server - Fatal Error: Failed to mount NFS Volume

Scheduled Pinned Locked Moved
FOG Problems
15
30
46.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    joshua
    last edited by Mar 12, 2012, 6:44 PM

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

    1 Reply Last reply Reply Quote 0
    • M
      Matthew.Hart
      last edited by Apr 22, 2012, 10:21 PM

      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.

      1 Reply Last reply Reply Quote 0
      • K
        KK20 Banned
        last edited by May 23, 2012, 10:23 AM

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • K
          KK20 Banned
          last edited by May 23, 2012, 3:31 PM

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • K
            kenneth
            last edited by Aug 9, 2012, 6:41 PM

            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!

            1 Reply Last reply Reply Quote 0
            • M
              madeinoz67
              last edited by Aug 14, 2012, 12:59 AM

              [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…

              1 Reply Last reply Reply Quote 0
              • M
                madeinoz67
                last edited by Aug 14, 2012, 3:24 AM

                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 🙂

                1 Reply Last reply Reply Quote 0
                • L
                  lanshan75 Banned
                  last edited by Aug 15, 2012, 6:40 AM

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • M
                    mootsfox
                    last edited by Dec 12, 2012, 8:33 PM

                    Bumping this thread because I have the same problem. mntcheck files are there, ubuntu system can see the mount and can write to/read from it.

                    I’ve using a FreeNAS system with a NFS share, authorized network set to 192.168.16.0/24 (my local subnet). All directories box checked, mapall user set to root.

                    When I try to pull an image, it does exactly what the OP says. Stuff about permissions. I’ve chmoded /images on the ubuntu box (mounted from my FreeNAS). Is it possible that I need to change the permissions on the FreeNAS system somewhere? I’m out of ideas and google hasn’t been of much help anymore for this roadblock.

                    1 Reply Last reply Reply Quote 0
                    • N
                      Nikolai Domaev
                      last edited by Dec 13, 2012, 9:31 AM

                      Hi there,
                      this:
                      [url]http://www.fogproject.org/wiki/index.php/Moving_your_images_directory/Adding_Storage_to_the_Images_directory[/url]
                      and this:
                      [url]http://www.fogproject.org/wiki/index.php/Adding_Storage_to_a_FOG_Server[/url]
                      might be usefull 🙂
                      good luck 🙂

                      1 Reply Last reply Reply Quote 0
                      • M
                        mootsfox
                        last edited by Dec 13, 2012, 1:50 PM

                        I will look into those again. I looked through them while doing this though. The permissions used from the first link are more inclusive than the permissions from the second link. I didn’t notice that before, but I tried adding those as well just now, and no change.

                        Here is a text dump of what shows on the unit that I am trying to upload an image from.

                        [CODE]* Send method…NFS

                        • Preparing to send image file to server.
                        • Mounting File System …mount: 192.168.15.72:/images/dev/
                          failed, reason given by server: Permission denied
                          mount: mounting 192.168.15.72:/images/dev on /images failed: Bad file descriptor
                          Done
                        • Checking Mounted File System…
                          ##############################################################

                        An error has been detected!

                        ##############################################################

                        Fatal Error: Failed to mount NFS Volume.

                        ##############################################################

                        Computer will reboot in 1 minute.

                        ##############################################################[/CODE]

                        Should be noted that 192.168.15.72 is my FOG server. 192.168.15.15 is my FreeNAS box with the storage and /image file. I know the store mounts correctly because I can see it in Ubuntu and I have full permissions to read/write/execute on it.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mootsfox
                          last edited by Apr 11, 2013, 3:52 PM

                          Bumping this because I finally got that problem fixed. I added a storage node with the ip and mnt point of the NAS, and set that as the active and master storage node. Images create just fine.

                          However, now I get “* unable to move /dev/macadress to /imagename” I can rename the image in dev and move it when in the dev file (sudo mv macaddress …/imagename) Which works, but I’m planning on running hundreds if not thousands of different images, I do not want to do this manually for each image.

                          This error is the exact one listed here: [url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Separate_NFS_Server[/url] under KNOWN ISSUE.

                          I have turned on the FTP service on my FreeNAS system, but there is no place for a username or password to be entered. I have both “Allow Root Login” and “Allow Anonymous Login” checked in the settings, the path set to the same place as the mount. I believe everything is set up correctly in there and I’m hoping someone with more knowledge of FOG and using FreeNAS with NFS can chime in on what I am overlooking or not understanding.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kktwenty
                            last edited by Mar 5, 2014, 9:31 AM

                            It seems my old kk20 account was deleted for being a “spammer”. Great as I had quite a few fixes posted under that username (from when I installed fog) and had never spammed in my life… oh well.

                            anyway I am revisiting this as I have moved my FOG to a new server and came up with the same error, luckily someone had “quoted” my original fix so I could look in the post_stage2.php file for changes I made (and I had commented them! yey!). Here is the change I made to post_stage2.php

                            this line:

                            [B]$dest = $noderoot . $_GET[“to”];[/B]

                            I changed to

                            [B] $dest = “/raid6/data/FOG/” . $_GET[“to”];[/B]

                            It seemed that the $noderoot was somehow incorrect for me. No idea why as it was only the final FTP that failed for me. Anyway, after hard coding my FTP location (not ideal but I needed a quick fix rather than a debug) this works fine for me and has done for years.

                            for information, /raid6/data/FOG is my listed NFS share in FOG (which also has FTP share enabled in openfiler). I have no idea why the $noderoot does not work yet everything else does. Anyway, that single change in post_stage2.php fixed my final FTP issue (so no more manual image moving necessary!)

                            1 Reply Last reply Reply Quote 0
                            • 1
                            • 2
                            • 2 / 2
                            • First post
                              Last post

                            212

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project