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

Moving storage to different location

Scheduled Pinned Locked Moved
FOG Problems
5
9
2.0k
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
    jetint
    last edited by Feb 4, 2016, 9:42 AM

    I have currently 4 images in a storage (default) at location /images. I have added a new SSD disk and mounted (ext4) it to /images-fog. I then copied everything: cp -rp /images/* /images-fog. Then I changed the storage (default) path in the FOG web fronted to /images-fog. However, even after restarting the system, I was not able to download any image anymore. Am I missing something? I have followed the guide https://wiki.fogproject.org/wiki/index.php/Moving_your_images_directory/Adding_Storage_to_the_Images_directory. The only difference is that all permissions of /images-fog are 777 and root:root, because this was already the case of /images.

    I would be greateful for any help.

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth Feb 4, 2016, 3:48 AM Feb 4, 2016, 9:47 AM

      @jetint As you don’t need the old /images directory anymore it would be a lot easier to just mount your new disk into that path without messing around in the settings. Move the images to your new disk (mounted somewhere), then unmount it, empty /images (hope you have a backup) and mount the new disk to /images, done.

      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

      J 1 Reply Last reply Feb 4, 2016, 9:56 AM Reply Quote 0
      • J
        jetint
        last edited by Feb 4, 2016, 9:51 AM

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • J
          jetint @Sebastian Roth
          last edited by jetint Feb 4, 2016, 3:58 AM Feb 4, 2016, 9:56 AM

          @Sebastian-Roth Yes, this is actually much easier. However, I have tried this before, but this did not work too.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Feb 4, 2016, 4:05 AM Feb 4, 2016, 9:59 AM

            What exactly did you do and which errors did you see??

            As a temporary solution to not kill your images you can just move /images for the moment.

            mv /images /images-old
            mkdir /images
            umount /images-fog
            mount /dev/sd<xy> /images
            touch /images/.mntcheck
            touch /images/dev/.mntcheck
            chmod -R 777 /images
            

            Depending on having copied the images to the new disk already you are now ready to go. But make sure you add the disk to your fstab to have it automounted on reboot!

            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

            1 Reply Last reply Reply Quote 0
            • P
              plegrand
              last edited by Feb 4, 2016, 1:33 PM

              it seems that when you modify images path on the web frontend, the export file (nfs) is not modified. You have to modify it and relaunch nfs

              G 1 Reply Last reply Feb 4, 2016, 1:41 PM Reply Quote 0
              • G
                george1421 Moderator @plegrand
                last edited by Feb 4, 2016, 1:41 PM

                @plegrand said:

                it seems that when you modify images path on the web frontend, the export file (nfs) is not modified. You have to modify it and relaunch nfs

                This I would expect. Since the process that runs the web service is not/should not have root level access (which is required to modify the nfs share). I think this should be the function of the install script to update the nfs share AND the database. Where you would just update the .fogsettings file and then rerun the installer and the rights bits should be put into place. We would need the @developers to look at this to update the install script.

                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!

                W 1 Reply Last reply Feb 4, 2016, 3:16 PM Reply Quote 0
                • W
                  Wayne Workman @george1421
                  last edited by Feb 4, 2016, 3:16 PM

                  @george1421 I can prob do that.

                  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/

                  G 1 Reply Last reply Feb 4, 2016, 3:21 PM Reply Quote 1
                  • G
                    george1421 Moderator @Wayne Workman
                    last edited by Feb 4, 2016, 3:21 PM

                    @Wayne-Workman The thing I noticed with the installer script is that it will skip over the database updates if there are already settings. That installer needs to replace the settings in the database as well as update the exports file.

                    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!

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

                    155

                    Online

                    12.1k

                    Users

                    17.3k

                    Topics

                    155.3k

                    Posts
                    Copyright © 2012-2024 FOG Project