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

    System Hangs - Boot from SAN device

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    24
    5.3k
    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.
    • D
      dholtz-docbox
      last edited by dholtz-docbox

      Yeah, that was what the output below was from, actually.

      #!ipxe
      set fog-ip 10.1.10.42
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      exit
      

      edit: I hit ‘s’ to enter PXE before booting, otherwise it stated that chainloading failed…

      http://imgur.com/a/IiYP0

      -Dustin

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @dholtz-docbox
        last edited by

        @dholtz-docbox Can you check the apache error logs then? If the error is still “chainloading…s to continue” or whatever it is, likely there’s some error being displayed that’s “breaking” things right now.

        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

        D 1 Reply Last reply Reply Quote 0
        • D
          dholtz-docbox @Tom Elliott
          last edited by

          @Tom-Elliott : Okay. Let me purge this log and get a clean log for you.

          -Dustin

          1 Reply Last reply Reply Quote 0
          • D
            dholtz-docbox
            last edited by dholtz-docbox

            @Tom-Elliott : I unfortunately have no errors in my /var/log/apache2/error.log file after cleaning it and running through the process again. Would they be generated somewhere else?

            -Dustin

            1 Reply Last reply Reply Quote 0
            • D
              dholtz-docbox
              last edited by

              I tried playing around with other types, and none appear to work. The machine uses GRUB boot loader, so I thought I would try to boot into GRUB, but it leaves me in the GRUB interface where I appear to be able to do nothing. I am not quite sure how to configure this so that it boots into the drive directly when no tasks are present.

              -Dustin

              1 Reply Last reply Reply Quote 0
              • D
                dholtz-docbox
                last edited by

                I have new errors after reformatting the machine in question and starting over. To iterate, the machine has two drives, is running Ubuntu Server 14.04, and is a LVM installation. The first drive is ignored, so I am using Single Disk - Resizable, setting its Primary Disk to /dev/sdb. Last, the host is set to exit its BIOS w/ type SANBOOT.

                If there is a task to capture an image, there is no issue from what I can tell. The machine boots into Partimage and begins cloning /dev/sdb without issues. However, when I go to boot into the system w/o tasks, the system NEVER boots properly.

                So… the new error. Upon reformatting, I switched the BIOS exit type back to SANDISK - after exhausting the initial selections prior. This time when I boot into the system, I am prompted with the following messages…

                Booting from SAN device 0x80
                Boot from SAN device 0x80 failed: Exec format error (http://ipxe.org/2e852001)
                Could not boot: Exec format error (http://ipxe.org/2e852001)
                Could not boot: Exec format error (http://ipxe.org/2e852001)
                

                Looking into what this error means, so far I am reading that it regards the kernel. This doesn’t make sense to me. I am not sure why the system can’t just resume its boot process, I guess; or what the impediment is - when using BIOS exit type = ‘EXIT’ - if that is the standard course of action.

                -Dustin

                1 Reply Last reply Reply Quote 0
                • D
                  dholtz-docbox
                  last edited by

                  Okay… I may have solved this at the end of the day, finally.

                  I believe it was a sequence of a few items not matching up once I tested certain phases. In the end, I had to switch the boot priority so that the drive with the OS had priority over the data drive. I tried this earlier, but it was after already moving past SANBOOT and when looking into EXIT as an option instead. Now that I have corrected the drive and changed the boot priority, SANBOOT is functioning as intended. I will do a few more tests before I officially resolve this, so I will post back by tomorrow morning on my results - time is limited today.

                  -Dustin

                  1 Reply Last reply Reply Quote 2
                  • Wayne WorkmanW
                    Wayne Workman
                    last edited by

                    So it was not a fog issue?

                    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/

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

                      @Wayne-Workman There was a fog issue, which I fixed. The issue in fog initially was the “exit” type wasn’t being populated into the exit types.

                      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
                      • D
                        dholtz-docbox
                        last edited by

                        Everything here works now though - including EXIT where I need it. Thanks again.

                        -Dustin

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

                        229

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project