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

    Chainloading Failed on EXIT - Hangs on REFIND_EFI

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    6
    21
    5.4k
    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.
    • 8
      88fingerslukee
      last edited by

      No RAID. There are 2 drives, one SSD with Windows on it, the other as a general storage drive:

      System Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: CRUCIAL_CT256M225
      Drive Revision: 1819
      Drive Capacity: 244,198 MBytes (256 GB)
      Media Rotation Rate: SSD Drive (Non-rotating)

      Storage Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: WDC WD3200AAKS-00L9A0
      Drive Revision: 01.03E01
      Drive Capacity: 305,245 MBytes (320 GB)

      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        OK here is what I want you to do here.

        Schedule a debug capture/deploy I don’t care which to this hardware. (Hint: ensure the debug check box is selected when scheduling the task) Then pxe boot the target computer. You may have to manually register this computer if you can’t get that far. When you pxe boot this computer you will see several screens of text, which you clear by pressing the enter key. Eventually you will be dropped to a linux command prompt on the target computer.

        Then key in lsblk to show the disk structure of this ssd/hdd combination.

        You don’t need to use refind_efi if this is a bios (legacy) firmware. If this is a uefi system then you might need to use refind to find the proper boot blocks.

        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 1
        • Wayne WorkmanW
          Wayne Workman
          last edited by

          It’s most likely due to the multiple disks. Once you identify the OS disk (as George asked), you can specify that as the primary disk for hosts of this type. Of course it’s possible that the FOG linux kernel isn’t even seeing the SSD, though I doubt this.

          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
          • 8
            88fingerslukee
            last edited by

            Okay, now it’s getting weird.

            When I create a capture task I get a TFTP Open Timeout error. So it’ll TFTP just fine into the menu without any task enabled but it has an issue with a task? How does that work?

            1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator
              last edited by

              What do you get when you key this url into a browser. Make sure you still have the capture/deploy task still scheduled.

              http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=<mac_of_broken_system>

              That should spit out the fog iPXE configuration menu for that target computer. If its incomplete then we’ll need to tail the apache error.log file.

              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
              • 8
                88fingerslukee
                last edited by 88fingerslukee

                I get this:

                #!ipxe
                set fog-ip 192.168.1.184
                set fog-webroot fog
                set boot-url http://${fog-ip}/${fog-webroot}
                cpuid --ext 29 && set arch x86_64 || set arch i386
                goto get_console
                :console_set
                colour --rgb 0x00567a 1 ||
                colour --rgb 0x00567a 2 ||
                colour --rgb 0x00567a 4 ||
                cpair --foreground 7 --background 2 2 ||
                goto MENU
                :alt_console
                cpair --background 0 1 ||
                cpair --background 1 2 ||
                goto MENU
                :get_console
                console --picture http://192.168.1.184/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
                :MENU
                menu
                colour --rgb 0x00567a 0 ||
                cpair --foreground 1 1 ||
                cpair --foreground 0 3 ||
                cpair --foreground 4 4 ||
                item --gap Host is registered as PSI1!
                item --gap -- -------------------------------------
                item fog.local Boot from hard disk
                item fog.memtest Run Memtest86+
                item fog.keyreg Update Product Key
                item fog.deployimage Deploy Image
                item fog.multijoin Join Multicast Session
                item fog.quickdel Quick Host Deletion
                item fog.sysinfo Client System Information (Compatibility)
                choose --default fog.local --timeout 5000 target && goto ${target}
                :fog.local
                imgfetch ${boot-url}/service/ipxe/refind.conf
                chain -ar ${boot-url}/service/ipxe/refind.efi || goto MENU
                kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
                imgfetch init_32.xz
                boot || goto MENU
                :fog.memtest
                kernel memdisk iso raw
                initrd memtest.bin
                boot || goto MENU
                kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
                imgfetch init_32.xz
                boot || goto MENU
                :fog.keyreg
                login
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                param username ${username}
                param password ${password}
                param keyreg 1
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :fog.deployimage
                login
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                param username ${username}
                param password ${password}
                param qihost 1
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :fog.multijoin
                login
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                param username ${username}
                param password ${password}
                param sessionJoin 1
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :fog.quickdel
                login
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                param username ${username}
                param password ${password}
                param delhost 1
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :fog.sysinfo
                kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
                imgfetch init_32.xz
                boot || goto MENU
                :bootme
                chain -ar http://192.168.1.184/fog/service/ipxe/boot.php##params ||
                goto MENU
                autoboot
                
                1 Reply Last reply Reply Quote 0
                • 8
                  88fingerslukee
                  last edited by

                  Sorry, that was without the capture task . Here is what you actually asked for:

                  #!ipxe
                  set fog-ip 192.168.1.184
                  set fog-webroot fog
                  set boot-url http://${fog-ip}/${fog-webroot}
                  kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 mac=xx:xx:xx:xx:xx:xx ftp=192.168.1.184 storage=192.168.1.184://files/images/dev/ storageip=192.168.1.184 osid=7 irqpoll hostname=HOST chkdsk=0 img=IMG imgType=n imgPartitionType=all imgid=10 imgFormat= PIGZ_COMP=-6 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
                  imgfetch init_32.xz
                  boot

                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @88fingerslukee
                    last edited by

                    @88fingerslukee Interesting, this looks like a normal capture menu. This is giving you a tftp timeout error?

                    I’m not seeing any tftp image pulls here, only http (which it should). Can you inspect the Apache error.log file and see if there is anything useful at the end of that file (if everything is working perfectly this file should be empty).

                    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
                    • 8
                      88fingerslukee
                      last edited by 88fingerslukee

                      Okay, so totally weird. It must’ve worked at some point because I had to leave for a while but when I came back it was at the linux prompt. Here’s the lsblk command, sda is the system SSD.

                      NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
                      sdb       8:16    0   298.1G  0 disk
                      └─sdb1    8:17    0   298.1G 0 part
                        sda      8:0   0   238.5G  0 disk
                      └─sda4    8:4   0    238G   0 part
                      └─sda2    8:2   0   100M  0 part
                      └─sda3    8:3   0   128M  0 part
                      └─sda1    8:1   0   300M   0 part
                      
                      

                      When I rebooted it went back to the open timeout. So I have no idea what the deal is here.

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

                        @88fingerslukee do you use the location plugin by chance? RC-26 fixed an issue of a method call, of which the sounds like it’s failing rc25 s bug.

                        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
                        • 8
                          88fingerslukee
                          last edited by

                          Unfortunately, no. I don’t use any plugins at all.

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

                            @88fingerslukee then are there any errors that might seem relevant in the Apache error logs?

                            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

                            8 1 Reply Last reply Reply Quote 0
                            • 8
                              88fingerslukee @Tom Elliott
                              last edited by

                              @Tom-Elliott no error logs at all. I only have ssl_error_log or access_log. Neither of them have anything relevant.

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

                                Also, another possibility, for the open timeout isn’t because of a problem with the exit type, rather how it’s being told to pass the exit based on how the system is seen. For example booting something in legacy mode would, from what I can guess, would not be able to return the UEFI based data to the system.
                                It suddenly thinks there’s no os to load into and restarts the system to try again. I believe you can boot down though (from EFI to legacy), just as long as the data can be found to boot up.

                                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

                                8 1 Reply Last reply Reply Quote 0
                                • 8
                                  88fingerslukee @Tom Elliott
                                  last edited by

                                  @Tom-Elliott the BIOS has two different network boots, iPXE and Legacy LAN. Both of them exhibit the same behaviour

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

                                    @88fingerslukee if your system is expecting to boot in UEFI, but your release from ipxe to system is in legacy it doesn’t matter which form of pxe on nic you’re using.

                                    UEFI/EFI as far as I know uses the onboard ‘nvram’ to know how to boot the system but in legacy mode that element would not be accessible.

                                    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

                                    8 sudburrS 2 Replies Last reply Reply Quote 0
                                    • 8
                                      88fingerslukee @Tom Elliott
                                      last edited by

                                      @Tom-Elliott I’m not certain I understand what you’re saying here. Are you suggesting an issue with the motherboard’s implementation of iPXE or something to do with FOG?

                                      1 Reply Last reply Reply Quote 0
                                      • sudburrS
                                        sudburr @Tom Elliott
                                        last edited by

                                        @Tom-Elliott This depends on the motherboard / BIOS.

                                        I have several models of Lenovo set to UEFI, but allow booting to both. I can drop a Legacy/CSM or UEFI image onto these systems and they will boot either OS fine.

                                        In fact I just Legacy PXE booted an M73z with undionly.kpxe to transfer an OEM UEFI image. It transferred and booted fine and runs as a UEFI OS.

                                        [ Standing in between extinction in the cold and explosive radiating growth ]

                                        1 Reply Last reply Reply Quote 0
                                        • JJ FullmerJ
                                          JJ Fullmer Testers
                                          last edited by

                                          @88fingerslukee In the bios/uefi firmware settings, what is the boot order?

                                          i.e and or also…

                                          Is UEFI enabled and Legacy enabled, or just UEFI?
                                          What pxe boot file are you using? I’ve seen that make a difference. I haves some cheaper HP’s that won’t boot with sanboot to the hard drive if you use ipxe.kkpxe, but they work fine with ipxe.pxe or ipxe.kpxe.

                                          Also have you played with the refind boot settings? There’s a file on the fog server at
                                          /var/www/fog/service/ipxe/refind.conf
                                          there is a line that starts with scanfor I’ve changed mine to only look for internal,external which means it only looks for uefi options and not legacy options. On a few of my devices, if I have it set as uefi only it has a pause on the host every boot if UEFI CSM isn’t set and it searches for the bios options that are enabled in fog by default.

                                          Have you tried the FogApi powershell module? It's pretty cool IMHO
                                          https://github.com/darksidemilk/FogApi
                                          https://fogapi.readthedocs.io/en/latest/
                                          https://www.powershellgallery.com/packages/FogApi
                                          https://forums.fogproject.org/topic/12026/powershell-api-module

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

                                          206

                                          Online

                                          12.1k

                                          Users

                                          17.3k

                                          Topics

                                          155.3k

                                          Posts
                                          Copyright © 2012-2024 FOG Project