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

    Synology NAS as FOG Storage node

    Scheduled Pinned Locked Moved
    Tutorials
    10
    31
    18.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.
    • george1421G
      george1421 Moderator @KKTwenty101
      last edited by george1421

      @KKTwenty101 said in Synology NAS as FOG Storage node:

      @george1421 I “cheesed” the dashboard in our FOG by mounting the image folder on the FOG server as NFS from my synology NAS (rather than add another storage node). Using an 815+ here and have been for a while.

      ^^Please explain this^^

      If I understand correctly you have an nfs share on your nas, and you mounted that nfs share over the /images directory on your fog server. And the fog server is sharing out the /images directory on your fog server??

      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!

      K 1 Reply Last reply Reply Quote 0
      • K
        KKTwenty101 @george1421
        last edited by

        @george1421 yes. That way the fog server considers /images local so the “defaultmember” pie chart works just fine.

        1 Reply Last reply Reply Quote 0
        • A
          Alex78
          last edited by Alex78

          @george1421 Hello, i did all the things you say, but i stay with this error, and i don’t know what this means:
          0_1530264310568_ok.PNG

          Did someone known this problem ?

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @Alex78
            last edited by

            @alex78 Just be aware that changes in the FOG program make using a NAS as a storage node a bit more difficult.

            Did you complete all parts of the tutorial? With synology nas, typically the path would be /volume1/images/igmWindows it appears you have missed a setting someplace.

            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!

            A 2 Replies Last reply Reply Quote 0
            • A
              Alex78 @george1421
              last edited by

              @george1421
              Ok, I am still checking all the steps of your tutorial and I will come back to you, if it not solved the problem or on the contrary if it solved it, thank you for your answer.

              1 Reply Last reply Reply Quote 0
              • A
                Alex78 @george1421
                last edited by Alex78

                I think it’s working thanks you 🙂

                Tom ElliottT 1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott @Alex78
                  last edited by

                  @alex78 Can you tell us what you had missed originally and what you did to fix it? This could help another user down the road, so always good to share if you can.

                  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

                  A 1 Reply Last reply Reply Quote 1
                  • A
                    Alex78 @Tom Elliott
                    last edited by

                    @tom-elliott I just unchecked “Enable advanced sharing permissions in affected folders”:
                    0_1530513445336_Capture111.PNG

                    1 Reply Last reply Reply Quote 0
                    • A
                      abrar1108
                      last edited by

                      I would like to appreciate this nice little post, I wish I had stumbled upon this earlier. Last week I tried creating my Synology NAS as a storage node and it worked. Little did I know that was the beginning of my misery. Whole week I struggled in fixing the replication issues.
                      Had I found this Thread earlier, I wouldn’t have attempted it.

                      1 Reply Last reply Reply Quote 0
                      • V
                        Vincent Caraby
                        last edited by

                        Hi,

                        First of all, thanks to george1421 and other users who deliver this solution.

                        Before i say what is my problem, the existant :

                        FOG serveur 1.5.4 on a Debian 9.4 with no graphical environment (terminal only) with 100Go disk. This debian is virtual on ESX6.5.0
                        NAS : Synologie DS116 with plenty of space

                        I’m a bit confuse.

                        All opération discribe here works whell, but when i capture, the image is copied on FOG server. Then, after capture, image is automaticaly copied on NAS. But after copy on NAS was finish, she stay on my FOG server, so after two Win10 capture the server is full.

                        What i miss out on ?
                        Is the capture normally do directly on NAS without any write on Server ?

                        Thanks in advance.

                        george1421G 1 Reply Last reply Reply Quote 0
                        • george1421G
                          george1421 Moderator @Vincent Caraby
                          last edited by

                          @Vincent-Caraby First let me say that changes in the fog server makes using a non-fog NAS a problem if you have it configured as you have it now. The FOG replicator will continue to copy the image over and over again to your NAS.

                          But let me tell you that you can do what I think you want. You must know that you can only capture images to a Master Node in a storage group. So in your settings change it so the NAS is the master node in your storage group, instead of the FOG server. This should make the images to go directly to the NAS and not FOG server.

                          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!

                          V 1 Reply Last reply Reply Quote 0
                          • V
                            Vincent Caraby @george1421
                            last edited by

                            @george1421

                            Thanks, i see the red message at top of topic to late.
                            I test this solution, it seem to be wright but i’m stuck on a permission problem.

                            Setup my NAS storage node to master node. But when i would capture there a message “permission denied” when mounting file system.

                            I don’t understand who on what give permission ? I suppose it’s my “adminfog” (fog server) to my NAS folders (images, snapins, tftpboot).

                            Is there a file where i can configure this rigtly ? A bit lost and not linux expert, but i prefer use config files if possible.

                            Some capture of my configuration :

                            2_1534946534225_fog_capture_error_wo_ip.png

                            1_1534946534225_config_storage_node.png

                            0_1534946534223_config_node_list.png

                            george1421G 1 Reply Last reply Reply Quote 0
                            • george1421G
                              george1421 Moderator @Vincent Caraby
                              last edited by

                              @Vincent-Caraby Well lets see if I can explain this, but the answer is simple and complicated at the same time.

                              The FOS engine connects to the master node as root so the synology nas needs to allow root to connect to the /volume1/images and /volume1/images/dev as root.

                              Also the FOS engine will use ftp to connect to the NAS using the adminfog user and password you defined in the Storage Node configuration to move the files from /images/dev to /images directory.

                              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!

                              M 1 Reply Last reply Reply Quote 1
                              • george1421G george1421 referenced this topic on
                              • george1421G george1421 referenced this topic on
                              • george1421G george1421 referenced this topic on
                              • george1421G george1421 referenced this topic on
                              • george1421G george1421 referenced this topic on
                              • M
                                mtrento @george1421
                                last edited by

                                @george1421
                                for those struggling with permissions with dev folder.
                                nfs creates a root:root with 775 permissions and fog ftpuser isn’t part of that group

                                Just use setgid feature on filesystem . it will enable inheritance
                                first change the owner of the folders and make “users” the group , lets say fog is your ftp user

                                chown -R fog:users /volume1/images/

                                #set inheritance to the dev folder

                                chmod g+s /volume1/images/dev/

                                now every new file under dev will have the directory group owner

                                Regards

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

                                195

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project