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

    Accidentaly Deleted /Images/Dev

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    7
    2.2k
    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.
    • D
      dwagner
      last edited by

      Server
      • FOG Version: 1.4.0-RC-1
      • OS: Linux
      Client
      • Service Version:
      • OS:
      Description

      Was trying to remove old Images and accidentally deleted /images/Dev. Recreated the folder but now when capturing an image I receive a * Running post init scripts…

      JunkhackerJ 1 Reply Last reply Reply Quote 0
      • D
        dwagner
        last edited by

        This is resolved just restored a backup…done

        1 Reply Last reply Reply Quote 0
        • JunkhackerJ
          Junkhacker Developer @dwagner
          last edited by

          @dwagner sounds like you need to recreate the /images/dev/postinitscripts directory, and it’s contents, a single file named “fog.postinit” with the contents

          #!/bin/bash
          ## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
          ## <SCRIPTNAME> should be changed to the script you're planning to use.
          ## Syntax of post init scripts are
          #. ${postinitpath}<SCRIPTNAME>
          

          permissions 777
          also, you’ll need to create an empty file named “.mntcheck” in /images/dev too, if you haven’t

          signature:
          Junkhacker
          We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

          1 Reply Last reply Reply Quote 3
          • D
            dwagner
            last edited by

            This is resolved just restored a backup…done

            1 Reply Last reply Reply Quote 0
            • Wayne WorkmanW
              Wayne Workman
              last edited by

              For future readers, the way to recreate this if you accidentally delete /images/dev is:

              mkdir -p /images/dev
              touch /images/dev/.mntcheck
              mkdir -p /images/dev/postinitscripts
              echo "#!/bin/bash" > /images/dev/postinitscripts/fog.postinit
              echo "## This file serves as a starting point to call your custom pre-imaging/post init loading scripts." >> /images/dev/postinitscripts/fog.postinit
              echo "## <SCRIPTNAME> should be changed to the script you're planning to use." >> /images/dev/postinitscripts/fog.postinit
              echo "## Syntax of post init scripts are" >> /images/dev/postinitscripts/fog.postinit
              echo "#. ${postinitpath}<SCRIPTNAME>" >> /images/dev/postinitscripts/fog.postinit
              chown -R fog:root /images
              chmod -R 777 /images
              

              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 2
              • T
                Thomas787
                last edited by

                I have done all of the aforementioned and still have not fixed the problem. Still stuck on:

                *Running post init scripts…

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

                  @Thomas787 Could you start your own thread, and include a screen shot of the error taken with a mobile phone? I can’t say your situation is the same as the OPs of this thread. A picture gives us the context of where the error occurs.

                  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!

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    Thomas787 @george1421
                    last edited by

                    @george1421 I have left work for the day, but will do so tomorrow morning. Thank you.

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

                    180

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project