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

Error fog booting from san device 0x80 after deploy

Scheduled Pinned Locked Moved
FOG Problems
8
15
11.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.
  • P
    pmonstad
    last edited by Aug 14, 2014, 10:14 AM

    I have a couple of Thinkpad R60e which upload/download OK, but after a deploy they cannot boot from iPXE. I get an error telling “fog booting from san device 0x80”. Then the machine hangs. If I unplug the LAN cable it works and boot as expected.

    Running Windows 7 (one disk, resizeable). Server is running FOG 1.2 on CentOS.

    1 Reply Last reply Reply Quote 0
    • J
      Junkhacker Developer
      last edited by Aug 14, 2014, 1:42 PM

      boot menu exit type
      try something other then sanboot

      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
      • P
        pmonstad
        last edited by Aug 15, 2014, 6:49 AM

        [quote=“Junkhacker, post: 35269, member: 21583”]boot menu exit type
        try something other then sanboot[/quote]

        Hm, I need some more info here as I really dont know what you suggest 😉 I have never chosen SANboot, and where do I turn it off? I have never run into this problem on hundreds of computers. Only these two R60e from Lenovo.

        1 Reply Last reply Reply Quote 0
        • C
          cadyfish
          last edited by Aug 15, 2014, 12:03 PM

          [quote=“pmonstad, post: 35300, member: 17422”]Hm, I need some more info here as I really dont know what you suggest 😉 I have never chosen SANboot, and where do I turn it off? I have never run into this problem on hundreds of computers. Only these two R60e from Lenovo.[/quote]
          With the current version of fog by default it uses SANboot as an exit type to get out of the fog menu. To change it do the following:
          [LIST=1]
          []Navigate to the FOG configuration page (gear symbol)
          [
          ]Click on PXE Menu settings
          []Change the exit type to “grub”
          [
          ]Save settings
          [/LIST]

          1 Reply Last reply Reply Quote 0
          • J
            Junkhacker Developer
            last edited by Aug 15, 2014, 2:05 PM

            the problem is in the way the bios of the computer handles the boot process. due to the number of inconsistent and buggy systems, we have included 3 different methods to tell the system to boot to the next boot device. you may also find that updating the bios on a system may fix the issue.

            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
            • P
              pmonstad
              last edited by Aug 15, 2014, 5:28 PM

              [quote=“cadyfish, post: 35303, member: 24458”]With the current version of fog by default it uses SANboot as an exit type to get out of the fog menu. To change it do the following:
              [LIST=1]
              []Navigate to the FOG configuration page (gear symbol)
              [
              ]Click on PXE Menu settings
              []Change the exit type to “grub”
              [
              ]Save settings
              [/LIST]
              [/quote]

              Thanks a lot for this info!

              1 Reply Last reply Reply Quote 1
              • P
                pmonstad
                last edited by Aug 15, 2014, 5:29 PM

                Was Grub the default setting in previous releases? Just wonder as I had no problems in older versions of FOG.

                1 Reply Last reply Reply Quote 0
                • J
                  Junkhacker Developer
                  last edited by Aug 15, 2014, 5:32 PM

                  previous version of fog used the pxelinux.0 network boot file, we now use a ipxe network boot file
                  these two systems use entirely different methods for their boot exit methods

                  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
                  • G
                    Gordon Taylor
                    last edited by Aug 27, 2014, 11:16 AM

                    is this possible to do on a per workstation basis? I only have a handful of workstations that don’t work with sanboot?

                    1 Reply Last reply Reply Quote 0
                    • R
                      rhythmtone
                      last edited by Aug 27, 2014, 4:28 PM

                      I would also like to know about this on a per-workstation basis. I have a few HP dc7900’s that show this behavior, stuck on SANBOOT 0x80 after imaging. I’ve tried updating the BIOS to the latest, etc, and cannot get past this…

                      The strange part is how most dc7900’s are fine, but I have at least 4 where this happens - perhaps it has to do with the make/model/firmware of the HDD or NIC?

                      If my memory serves me correctly, in our environment EXIT boot type caused problems on a greater number of systems, and that is a risk that I’d rather not take right now, as it would affect all machines PXE booting to FOG.

                      Thanks for any advice or help,
                      D.L.

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tom Elliott
                        last edited by Aug 27, 2014, 5:43 PM

                        You could try grub style exiting?

                        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
                        • G
                          Gordon Taylor
                          last edited by Aug 28, 2014, 12:54 PM

                          I’ve swapped to grub and so far I’ve not seen anything fail 🙂 but it would be good if it could be per workstation configurable at some point 🙂

                          1 Reply Last reply Reply Quote 0
                          • R
                            rhythmtone
                            last edited by Aug 28, 2014, 6:05 PM

                            If I recall correctly, there were some machines that failed with GRUB, and there were others that failed with EXIT, and I definitely cannot risk that right now. I guess that’s is more of a feature request, but I agree with Gordon that per-workstation or maybe per-group adjustment of this setting would be great!

                            Thank you for all of your work,
                            D.L.

                            1 Reply Last reply Reply Quote 0
                            • C
                              cbirch
                              last edited by Dec 19, 2014, 6:44 PM

                              I know that i am jumping in a bit late…

                              I also had this problem on a hp dc7900 i found that the sata emulation in the bios was set to ahci when i put it back to ide it would boot properly.

                              1 Reply Last reply Reply Quote 1
                              • W
                                Wolfbane8653 Developer
                                last edited by Dec 19, 2014, 6:57 PM

                                Same thing happens on Lenovo R500’s and Lenovo R61’s. Changed AHCI to compatibility. Its a known issue and its related directly with the hardware and BIOS. This will affect any install of Windows, ghosting, Acronis True Image and FOG. Sorry but not a FOG issue.

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

                                140

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project