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

    After image download windows boots to pxe then black screen

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    9
    4.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.
    • M
      Michael Green
      last edited by

      So I, finally, got a Windows 7 image uploaded and last night I set it up to download to 5 computers (identical specs to master). This morning I came in and all 5 were sitting on a black screen. No blinking cursor just black. This behaviour doesn’t change if I disable pxe, disconnect from network, or F12 to single boot from HDD. I found this ([url]http://fogproject.org/forum/threads/windows-7-image-boots-to-blank-screen-after-deployment.10893/[/url]) but his solution is for an older version and the fog.download script in 1.2 is different. I’ve also tried changing the pxe menu exit behaviour from sanboot to exit with no effect. The HDD is visible from the BIOS and the sytem passed the self test. The server is Debian 7 on ESXi, FOG 1.2.0, OS is Win 7 Pro 64 bit with OEM licensing (not volume), and the client boxes are Optiplex 760’s with Core 2 Duos.

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

        My guess is the image that you “uploaded” from came from a resizable image downloaded to the machine from a 0.32 image. The upload was to bring it into current specs.

        Can you check the file:
        [code]/images/<imagename>/d1.original.partitions[/code] and give us the output of the /dev/sda1 partition?

        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

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

          Also, if you’d be so daring, can you try the Latest SVN?

          It should have the workaround fixes to do the sector 63 issue as described in the previous posting in a more appropriate methodology.

          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

          1 Reply Last reply Reply Quote 0
          • M
            Michael Green
            last edited by

            The upload image was from a fresh install that I deployed some standard applications to (Avast, Some equipment drivers, Foxit). This is my first time attempting to use FOG (or pxe booting in general). The output you requested:

            partition table of /dev/sda

            unit: sectors

            /dev/sda1 : start= 63, size= 128457, Id= 7, bootable
            /dev/sda2 : start= 128520, size=156167865, Id= 7

            Additionally following your sig’s advice I checked the apache logs and they don’t contain anything applicable.

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

              [quote=“Michael Green, post: 38323, member: 26877”]
              /dev/sda1 : start= 63, size= 128457, Id= 7, bootable
              /dev/sda2 : start= 128520, size=156167865, Id= 7
              [/quote]

              yep, looks like tom guessed right. this has been fixed in the SVN

              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 0
              • M
                Michael Green
                last edited by

                Ok. So where can I get the latest SVN? And from there should I just reimage the master and attempt to redeploy? Or does the fix work retroactively?

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

                  works retroactively.

                  Follow these steps:
                  [url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk#SVN[/url]

                  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

                  1 Reply Last reply Reply Quote 0
                  • M
                    Michael Green
                    last edited by

                    Alright. I’ve done that and am redeploying to one of the test machines.

                    1 Reply Last reply Reply Quote 0
                    • M
                      Michael Green
                      last edited by

                      Redeploy finished and the box rebooted to the PXE menu. Booted to HDD and get the same black screen. Output of d1.original.partitions is the same.

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

                      213

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project