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

    Could not mount images folder Error

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    35
    3.9k
    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.
    • L
      lschnider
      last edited by

      I actually am trying to capture an image not deploy one. I havent been able to successfully capture one yet. I did follow the article but i definitely could have missed a step or something. I will try it with the firewall off and see if that works.

      george1421G 1 Reply Last reply Reply Quote 0
      • L
        lschnider
        last edited by lschnider

        Okay so it looks like its capturing the image now, i went back through the wiki article you sent me and followed all the steps again. and everything said “Warning already enabled” the only one that I wasnt sure about was the 0_1543932914055_f8a07d49-d8a9-40b6-9542-40463960a5af-image.png what command do i actually run in this.

        Also when it finished capturing the image it went to this 0_1543933655174_0d660f83-11f6-4af7-91b9-34798548cb7a-image.png

        It did not successfully capture the image after that.

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

          @lschnider

          systemctl disable firewalld
          systemctl stop firewalld
          

          Then check the status of selinux

          sestatus
          

          SELinux status: should be set to permissive.

          Edit: For your new post, we need to see the error at the top (just off the top edge if the screen)

          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!

          L 1 Reply Last reply Reply Quote 0
          • L
            lschnider
            last edited by

            
            [root@localhost cmc_it]# sestatus
            SELinux status:                 enabled
            SELinuxfs mount:                /sys/fs/selinux
            SELinux root directory:         /etc/selinux
            Loaded policy name:             targeted
            Current mode:                   permissive
            Mode from config file:          permissive
            Policy MLS status:              enabled
            Policy deny_unknown status:     allowed
            Max kernel policy version:      31
            
            
            george1421G 2 Replies Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @lschnider
              last edited by

              @lschnider You will still have an issue. You did not follow the prerequisites for installing FOG.

              Now you need to edit /etc/selinux/config
              In that file edit
              SELINUX=enforcing
              to read
              SELINUX=permissive

              reboot the 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!

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

                @lschnider scratch that, it is set to permissive. I did not read well enough.

                OK we need to see the error that is just off the top of the screen in your previous picture.

                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 0
                • george1421G
                  george1421 Moderator @lschnider
                  last edited by

                  @lschnider Also I’ve seen that date.timezone warning message before. I don’t know if that is something new with 1.5.5 or not. Can you confirm that this FOG setting is correct for your timezone: FOG Configuration->FOG Settings->General Settings->TZ INFO

                  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!

                  L 1 Reply Last reply Reply Quote 1
                  • L
                    lschnider
                    last edited by

                    Well maybe this is a dumb question but how do you scroll up on that screen. I have been trying to but it wont let me.

                    george1421G 1 Reply Last reply Reply Quote 0
                    • L
                      lschnider @george1421
                      last edited by

                      @george1421 The date/time was wrong. I fixed that, i will try to run the capture again.

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

                        @lschnider You can’t it a character mode terminal. If its scrolled off the top of the screen then its lost. Lets see if we can fix the TZ issue so those warning messages will go away.

                        Let me ask you have you messed with / changed the password for the FOG linux service account called fog? This is not the default webui admin called fog this is the linux user called fog? If you changed this account I might expect this error message at this point in the capture process.

                        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!

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

                          @lschnider said in Could not mount images folder Error:

                          @george1421 The date/time was wrong. I fixed that, i will try to run the capture again.

                          You may need to reboot the fog server for that setting to get installed.

                          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 0
                          • L
                            lschnider @george1421
                            last edited by

                            @george1421 no i dont believe i have. Is there a way to tell if the password is like it should be?

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

                              @lschnider There is a hidden file /opt/fog/.fogsettings The linux user account for fog is listed in there.

                              Test from a windows computer, ftp to the fog server. Login as fog and the long password from the .fogsettings file. If that works then we need to look at the configuration.

                              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!

                              L 1 Reply Last reply Reply Quote 0
                              • L
                                lschnider @george1421
                                last edited by

                                @george1421 okay i tried to ftp and it says 0_1543935762843_97cef566-ff9f-4f69-910e-f727cf7a0e0a-image.png

                                I will try to get a picture of that error you asked about earlier.

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

                                  @lschnider OK just to confirm you used the value from the password field from the .fogsettings file? If so I have a tutorial on how to resync the fog service account here:
                                  https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

                                  Run through that tutorial to ensure everything is reset correctly.

                                  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!

                                  L 1 Reply Last reply Reply Quote 0
                                  • L
                                    lschnider @george1421
                                    last edited by lschnider

                                    @george1421 Okay i followed your tutorial and made sure everything was done correctly. Now i am able to capture an image with no problem but im getting a different error when trying to deploy an image. 0_1543938417518_8459597580356331004.jpg

                                    I have tried two different hard drives, and the second one was a blank 500gb ssd. Both hard drives said the exact same free space.

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

                                      @lschnider Well that’s an error I haven’t seen before.

                                      can you confirm that this file exists on the fog server. /images/Windows_Basic_Test/d1p2.img

                                      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!

                                      L 3 Replies Last reply Reply Quote 0
                                      • L
                                        lschnider @george1421
                                        last edited by

                                        @george1421 How would i go about browsing to that folder. /images isnt showing anywhere.

                                        1 Reply Last reply Reply Quote 0
                                        • L
                                          lschnider @george1421
                                          last edited by lschnider

                                          @george1421 just kidding, i was being dumb. 0_1543944353217_40be290d-a911-4820-a678-c80e6b7986cc-image.png
                                          Yes that file is there.

                                          1 Reply Last reply Reply Quote 0
                                          • L
                                            lschnider @george1421
                                            last edited by

                                            @george1421 it seems like its not creating a partition big enough when wiping the drive and then creating the partition to write the image to.

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

                                            283

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project