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

    Blinking cursor after booting from hard drive in FOG menu, on Optiplex 5040s

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    8
    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.
    • ?
      A Former User
      last edited by

      Server
      • FOG Version: 1.3.4
      • OS: CentOS
      Client
      • Service Version:
      • OS:

      On our computers that are set to boot to network, the computer boots to FOG, is on the “boot from hard drive option” by default, and boots to the hard drive after the 15-second timeout.

      We put the same Windows 10 1511 image on both Optiplex 7010s and Optiplex 5040s. When the 7010s boot from hard drive in FOG, no issue. When the 5040s boot from hard drive in FOG, a black screen with a blinking white cursor appears. The screen never goes away until powering off the machine.

      These are all legacy/MBR.

      Both the 7010s and 5040s boot from the hard drive (not in FOG) just fine. We successfully image the 5040s with FOG just fine, too. As far as we can see, everything in FOG works fine with the 5040s except booting from the hard drive within the FOG menu.

      Any ideas?

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @A Former User
        last edited by

        @loosus456 Trying to understand the problem.

        5040’s are not getting through to iPXE at all (and booting to the OS which I’m guessing doesn’t exist?)

        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

          Sorry processed faster than I read.

          Can you provide the 5040’s MBR file (in email if you need to) and the contents of d1.partitions and d1.minimum.partitions

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

            While this “shouldn’t” matter. Do the 5040s have NVMe (M.2) drives or traditional SATA drives?

            If you deploy a Win7 image to to 5040s does it boot through fog correctly. Right now, in my mind its not clear if its the OS, FOG, or the hardware that is causing this boot failure.

            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
            • JunkhackerJ
              Junkhacker Developer
              last edited by

              so, the 5040’s that you have imaged with fog boot fine if you set the bios to not boot to the network first, correct?
              this is most likely caused by the “exit type” being used not working correctly for that model.

              to change this setting globally, change the setting “Exit to Hard Drive Type” in “FOG Configuration > iPXE Boot Menu Configuration”

              to change this on a host by host basis, change “Host Bios Exit Type” on the host’s profile page in “Host Management”

              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
              • Tom ElliottT
                Tom Elliott
                last edited by

                Feel I might like to add on.

                A lot of work has gone into the resizing and uuid settings of the imaging process and I believe this is what was causing your “blinking cursor”. Would you mind updating to the latest RC (13 as of this writing) to see if your devices are now able to successfully boot?

                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 1
                • S
                  Spicoli
                  last edited by

                  For those who run into this, I am receiving new computers from Dell with SATA mode set to RAID. Changing this setting to AHCI solves this problem for me. I am using Fog version 1.4.0-RC-14.

                  H 1 Reply Last reply Reply Quote 0
                  • H
                    hillie @Spicoli
                    last edited by

                    @Spicoli Thanks! RAID to AHCI worked for me.

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

                    285

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project