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

Computer wont boot from hard drive after PXE from FOG

Scheduled Pinned Locked Moved
FOG Problems
9
30
19.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.
  • A
    alli @Tom Elliott
    last edited by Aug 11, 2015, 2:22 PM

    @Tom-Elliott
    yes but,

    I have a good connection and restart the computer and turn it off and still the same . I do not know what it is šŸ˜ž and not found.

    1 Reply Last reply Reply Quote 0
    • A
      alli @SupEric
      last edited by Aug 11, 2015, 2:27 PM

      @SupEric

      I have the same problem you had at the time of loading the image I get black screen and a blinking in the corner hairline.
      Do you have the solution to this problem?
      Could you help me fix it?

      1 Reply Last reply Reply Quote 0
      • M
        MJR
        last edited by Aug 18, 2015, 2:53 PM

        Microsoft AD environment with 200+ computers. Upgraded fog server to 1.2 from 0.32. No previous similar problems.
        On approximately 10% of campus computers, we are also seeing the ā€œperma-blinkingā€ top left cursor after
        the Fog Menu screen during PXY boot. Laptops and Desktops running Windows 7. Have to turn off PXY boot
        for work around. Today tried my first Fog ā€œQuick Imageā€ on a Dell Latitude with this issue and it also hangs about
        15 minutes into the reimage on the same blinking cursor screen. Hoping for some information, directions, questions.
        Thanks very much.

        M W 2 Replies Last reply Aug 18, 2015, 2:59 PM Reply Quote 0
        • M
          MJR @MJR
          last edited by Aug 18, 2015, 2:59 PM

          @MJR Correction; the Quick Image worked (after turning back on PXE) , it apparently just hung on the final reboot in the same place it always does.

          1 Reply Last reply Reply Quote 0
          • W
            Wayne Workman @MJR
            last edited by Aug 18, 2015, 3:00 PM

            @MJR Can you provide a list of models that are problematic?

            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/

            M 1 Reply Last reply Aug 18, 2015, 6:01 PM Reply Quote 0
            • M
              MJR @Wayne Workman
              last edited by Aug 18, 2015, 6:01 PM

              @Wayne-Workman Thanks for your response; I don’t know how specific you need me to be but we are 90% Dell.
              Generally speaking, there’s at least one Optiplex 780 (2012?), a few Optiplex 3010’s (2013), and 3 or 4 Dell Latitude E6520’s (2011). Our Network Engineer suggested maybe a certain brand/model of NIC’s…

              W 1 Reply Last reply Aug 18, 2015, 6:03 PM Reply Quote 0
              • W
                Wayne Workman @MJR
                last edited by Aug 18, 2015, 6:03 PM

                @MJR I was asking for exact models, lol. But that’s fine - you can do what I was going to do. Please look through these two lists, you’ll know what you’re looking at:

                https://wiki.fogproject.org/wiki/index.php/WorkingDevices

                https://wiki.fogproject.org/wiki/index.php/ProblematicDevices

                Now, if you find some that are noted as working but are not working for you - we need to explore those.

                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 0
                • C
                  ciry
                  last edited by Aug 20, 2015, 3:48 PM

                  Hello all, i’m googling/reading a lot of thread from at least a week on this problem, just today i reg to this forum, only to say I have same issue with Acer P253M notebook.
                  I tried recover image (from Acer dvd disks) with win7 and win10, same issue, Bios boot type was set to ā€œlegacyā€ (not uefi) but the O.S. was set by Acer with GPT partition.
                  I fear this is the problem, the GPT Partition.
                  I’m going to try with an ā€œMBR partitionā€ā€¦ (microsoft call the partition schema in this clear wrong way)…

                  But after all i would ask: what kind of boot pxe-fog-booting-img use?!
                  It’s Syslinux?
                  May be it’s there the problem, could a syslinux update (or downgrade) to solve the problem?

                  I found this workaround for an old version of Fog in wiki:
                  https://wiki.fogproject.org/wiki//index.php?title=Boot_looping_and_Chainloading
                  and other site
                  http://community.spiceworks.com/how_to/108551-fog-boot-looping-and-chainloading

                  But i can’t apply this method just because i can’t find /tftpboot/pxelinux.cfg/default
                  i’m going off road…?

                  Thank you.

                  J 1 Reply Last reply Aug 20, 2015, 5:32 PM Reply Quote 0
                  • J
                    Junkhacker Developer @ciry
                    last edited by Aug 20, 2015, 5:32 PM

                    @ciry fog 1.0+ versions do not use syslinux. fog uses ipxe.
                    trying to boot a gpt uefi system with the bios set to legacy would not work regardless of pxe.
                    fog gives you multiple methods to exit the pxe environment to try to load the OS, have you tried them all?

                    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
                    • O
                      Obi-Jon
                      last edited by Jul 10, 2017, 9:33 PM

                      I know I’m gravedigging an old topic, but since this is all the Google could find for me on this topic I thought I’d post a solution for future reference.

                      For my setup (FOG 1.3.5), the following allowed me to get my Dell Latitude M4800 and E7470 laptops to exit iPXE and continue booting the hard disk properly without the dreaded flashing cursor:

                      FOG Configuration -> iPXE Boot Menu -> Exit to Hard Drive Type = GRUB_FIRST_HDD (default is SANBOOT, which was giving me trouble)

                      Hope this helps someone.

                      Jon

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

                      149

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright Ā© 2012-2024 FOG Project