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

mounting /home/images on /images failed: permission denied

Scheduled Pinned Locked Moved Solved
FOG Problems
4
10
3.1k
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.
  • F
    finvader
    last edited by Nov 15, 2016, 1:35 PM

    Server
    • FOG Version: 1.2.0
    • OS: Centos 6.8
    Client
    • Service Version:
    • OS: Centos 7.2
    Description

    The default of /images works just fine when I image a machine. However the / partition only has 15 GB of space. The /home partition has over 500GB of space for images. I created a /home/images folder and made it the master node, the only node for holding images. I am getting a permission denied error.

    NFS is mounting 172.16.61.17:/home/images/dev on /images failed: permissioned denied.

    I checked the perms and they appear to be ok at 777 on the /home/images folder recursively.

    Any ideas?

    Just trying to change the default path from /images to /home/images

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Nov 15, 2016, 1:40 PM

      What does your /etc/exports file look like?

      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

      F 1 Reply Last reply Nov 15, 2016, 5:52 PM Reply Quote 1
      • F
        finvader
        last edited by Nov 15, 2016, 1:49 PM

        /images *(ro,sync,nowdelay…fsid1)
        /images/dev *(ro,sync,nowdelay…fsid2)

        not seeing /home/images… does it need to be here, if so I believe it would be something like

        /home/images/dev *(ro, sync…fsid3)

        ?

        1 Reply Last reply Reply Quote 0
        • F
          finvader
          last edited by Nov 15, 2016, 2:03 PM

          Got it, was missing the .mntcheck and dev folder. Not sure why the dev did not get created but just copied over and maintained perms.

          I am IMAGING!!!

          A great learning process for me for sure. Thank you for all the help. Now the lab is up. Back to 1.3.0 on CENTOS 7.2. I think I got it this time around no prob.

          V/R

          1 Reply Last reply Reply Quote 0
          • F
            finvader @Tom Elliott
            last edited by Nov 15, 2016, 5:52 PM

            @Tom-Elliott

            Quick question:

            The FOG server was able to upload (capture) the image successfully, however when I look in /home/images (my new image path), I see the mac address as the image name instead of centos72IT1103, the image name associated with my hosts? The old fog server created the same name folder in /home/images as the image name in “Image Management”.

            V/R

            T 1 Reply Last reply Nov 15, 2016, 6:03 PM Reply Quote 0
            • T
              Tom Elliott @finvader
              last edited by Nov 15, 2016, 6:03 PM

              @finvader
              The mac address labeled folder is typically ONLY when you’re imaging. ro should actually read rw for the dev line.

              You should not need to have /home/images and /home/images/dev if your /images is a symbolic link to the /home/images point.

              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

              F 1 Reply Last reply Nov 15, 2016, 6:08 PM Reply Quote 1
              • F
                finvader @Tom Elliott
                last edited by Nov 15, 2016, 6:08 PM

                @Tom-Elliott
                Not sure I understand what you are saying.

                Do I only need the /home/images in my /etc/exports?
                I think I understand that the /home/images should be rw instead of ro?

                Q 1 Reply Last reply Nov 16, 2016, 12:54 PM Reply Quote 0
                • W
                  Wayne Workman
                  last edited by Nov 15, 2016, 6:12 PM

                  I think you setup /etc/exports properly if you were able to capture. I think you forgot to change the FTP path inside of Storage Management -> node -> FTP Path or Image Path.

                  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!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

                  1 Reply Last reply Reply Quote 0
                  • Q
                    Quazz Moderator @finvader
                    last edited by Quazz Nov 16, 2016, 6:55 AM Nov 16, 2016, 12:54 PM

                    @finvader You can leave your /etc/exports to default if you create a symbolic link to your /home/images

                    I think I understand that the /home/images should be rw instead of ro?

                    No, /home/images/dev should be rw

                    I don’t even know how it wrote anything in your /home/images/dev folder if it’s defined as ro in your exports…unless you never exported it and already have a symbolic link that is.

                    Assuming all of that is true, then you need to remove the /home/images line from /etc/exports and do what Wayne says.

                    1 Reply Last reply Reply Quote 0
                    • F
                      finvader
                      last edited by Nov 16, 2016, 9:02 PM

                      This post is solved

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      1 / 1
                      • First post
                        7/10
                        Last post

                      221

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project