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

    boot into windows failure after deployed image

    Scheduled Pinned Locked Moved
    Windows Problems
    3
    18
    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.
    • george1421G
      george1421 Moderator @bc601
      last edited by george1421

      @bc601 It doesn’t have to be another 7020. Any computer that has windows on it will work. But its true I didn’t consider only having one drive power cable. I do have a Y power cable in our build up room, so whenever I run into a single drive power plug we just insert the power Y cable.

      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
      • B
        bc601 @george1421
        last edited by

        @george1421

        What are the instructions for getting to the logs in debug mode from FOG ?

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

          @bc601 The instructions are not easy, but they are not hard either.

          1. On the computer that has failed. Reschedule a FOG capture task but enable debug mode.
          2. PXE boot the target computer
          3. After a few enter key presses you will be dropped to a linux command prompt on the target computer.
          4. key in fog to start the capture process (no worries we are going to jump out before anything is captured)
          5. Press enter until you are after the step of Mounting file system (press enter)
          6. When you see the step Checking mounted file system press Ctrl-C. This will drop you out to a linux command prompt again.
          7. Key in df -h you should see a line that says /images on the FOS client is connected to /images/dev on the fog server. (you need this step to have a place to move the log files to.
          8. Now you need to connect to the target computer’s hard drive. I find this command works most of the time ntfs-3g -o force,rw /dev/sda2 /ntfs This command will connect the 😄 drive of the target computer to the /ntfs on FOS.
          9. Now navigate to the Panther directory using this command cd /ntfs/Windows/Panther
          10. You can either look at those files there with vi or copy them to the FOG server so you can download them with WinSCP to review them in windows. The log files all end with .log extension.
          11. If you want to copy them to the fog server this command may get you close. cp /ntfs/Windows/Panther/*.log /image Then on the fog server you can pick up those log files in the /images/dev directory.

          I’ll tell you its much easier to just get a Y power cable for sata like this one and review the log files on a second computer. But the above way will work. I’ve done it several times with the steps outlined above.

          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!

          B 1 Reply Last reply Reply Quote 0
          • B
            bc601 @george1421
            last edited by

            @george1421

            I Received the following error on step 8 : ntfs-3g mount: failed to access mount point /ntfs: no such file or directory

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

              @bc601 Ok then run this command just before the mount.

              mkdir /ntfs

              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!

              B 1 Reply Last reply Reply Quote 0
              • B
                bc601 @george1421
                last edited by

                @george1421

                0_1510670741359_ad1d0198-7b49-4e2a-b88c-8d4e8aa9be03-image.png

                On the last step. Step 10. I received an error message stating the following
                CANNOT CREATE REGULAR FILE '/IMAGES/DDACLSSYS.LOG:READ ONLY FILE SYSTEM.
                This error repeated for each .log file. I also included the screenshot of the rights to the /images folder.

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

                  @bc601 Did you create a capture or deploy task. Only a capture task will allow you to write to images (/images/dev on 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!

                  B 1 Reply Last reply Reply Quote 1
                  • B
                    bc601 @george1421
                    last edited by

                    @george1421

                    Ok it was a success. I now have the log files. I noticed something weird the setup.log file is empty and spelled incorrectly

                    0_1510755062377_15ac54e6-1839-4a55-9d6f-afb9aa28d93b-image.png

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

                      @bc601 in there you have setupact == setup activity log. and setup error logn. Where did you get those files from>

                      I haven’t figured this out quite yet. But I’ve found these files in c:\windows\panther and c:\windows\setup\sysprep sometimes. You probably should see both places. Also I suspect the setup error [setuperr.log] to contain the reason why your OOBE failed. Sorry I can’t be more specific its been about 6 months since I last debugged a deployment.

                      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!

                      B 2 Replies Last reply Reply Quote 0
                      • B
                        bc601 @george1421
                        last edited by

                        @george1421

                        I have no idea were they came from.

                        So how do I correct the setup error ?

                        1 Reply Last reply Reply Quote 0
                        • B
                          bc601 @george1421
                          last edited by

                          @george1421

                          Okay found out what the issue was. I did not sysprep the image correctly went back and syspreped the PC used for the image and tried it again. This time it worked after redeploying the image

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

                            @bc601 said in boot into windows failure after deployed image:

                            I did not sysprep the image correctly went back and syspreped the PC used for the image and tried it again. This time it worked after redeploying the image

                            Do you know what you did wrong? What did you do differently?

                            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/

                            B 1 Reply Last reply Reply Quote 0
                            • B
                              bc601 @Wayne Workman
                              last edited by

                              @wayne-workman

                              Yes I did not activate the sysprep application. Once I activated it and recaptured the image. The problem was resolved.

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

                              157

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project