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

    Unsolved RHEL Initramfs unpacking failed: & Kernel panic - not syncing:

    Linux Problems
    7
    17
    509
    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.
    • W
      WT_101 @Tom Elliott
      last edited by

      @Tom-Elliott
      Have new finding, I tested the snp.efi from Fogproject 1.5.7 & 1.5.8 there is no issue booting into RHEL while from 1.5.9 and 1.5.10 having the kernel panic issue

      george1421G one-reply-to-this-post Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @WT_101
        last edited by

        @WT_101 said in RHEL Initramfs unpacking failed: & Kernel panic - not syncing::

        snp.efi from Fogproject 1.5.7 & 1.5.8

        Unless you are using SANBOOT or EXIT (exit) modes, snp.efi or iPXE for that matter is not responsible for booting a uefi computer. The responsibility for booting uefi computers is handed over to rEFInd. I might suspect that refind version changed between 1.5.8 and 1.5,10.

        So do you mean to say if you take snp.efi from fog 1.5.7 or .8 and copy it over to FOG 1.5.10 install you can boot rhel 9?

        If you were to recompile iPXE with the very latest code doe it boot rhel 9 correctly (assuming that iPXE is at fault here)?

        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!

        W topic:replies-to-this-post, 2 Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by

          @WT_101 @hutch Looks like we have a very similar issue with Ubuntu 22.04 installs as well: https://forums.fogproject.org/topic/16850/problem-after-deployment-with-release-1-5-10

          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

          one-reply-to-this-post Last reply Reply Quote 0
          • S Sebastian Roth referenced this topic on
          • W
            WT_101 @george1421
            last edited by

            @george1421 im not using both SANBOOT or EXIT.

            Im using REFIND_EFI and yes im just replacing the snp.efi in the tftp folder getting from 1.5.8 (success boot into Redhat i just try again few min ago) and 1.5.10 (failed with kernel panic)

            EXIT i already tried. It wont boot into the OS. it will just exit into the BIOS screen

            H one-reply-to-this-post Last reply Reply Quote 0
            • H
              hutch @WT_101
              last edited by

              @WT_101 Thanks! The old install didn’t seem to work, but I just grabbed the files directly out of the installation folder and it booted just fine.

              C one-reply-to-this-post Last reply Reply Quote 0
              • W
                WT_101 @george1421
                last edited by

                @george1421 sorry there are some wrong info provided 1.5.9 is working as well due to some mistakes i made causing i providing wrong info.

                New finding i found was 1.5.9 snp.efi came with ipxe 1.20.1 there is no issue on booting into the RHEL OS with REFIND_EFI
                while 1.5.10 snp.efi that are using ipxe 1.21.1 having issue to boot into RHEL OS

                As there are only 3 file being dl into the system
                1 snp.efi
                2. refind.conf
                3. refind_x64.efi

                i perform comparison between these 3 file 1.5.9 vs 1.5.10
                484d5f83-8244-4eee-ac4b-947eb83bd3a2-image.png
                Is it possible that iPXE 1.21.1 require a newer version of refind_x64.efi ? Could you guide me on how can i troubleshoot further?

                Tom ElliottT one-reply-to-this-post Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott @WT_101
                  last edited by

                  @WT_101 There were a lot of changes between v1.20.1 and v1.21.1 though we (FOG) don’t manage the repository of ipxe itself.

                  Here’s the code where I believe things might’ve broken the boot capabilities, but this is still just a best guess based on the changed code, not really an “assured” here’s what’s definitely broke.

                  A git bisect might be useful so we can see potentially where things are good -> bad and indicate to ipxe development so a more proper fix might be addressable.
                  https://github.com/ipxe/ipxe/compare/v1.20.1...v1.21.1#diff-9ec49bac9202333b51ea932869865503ace555e43797e9e26898e4a5b813944e

                  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

                  one-reply-to-this-post Last reply Reply Quote 1
                  • C
                    CedricoR @hutch
                    last edited by

                    @hutch Hello, on my side, when i try tu use snp.efi from the 1.5.8 tarball, I have a permission issue on the boot.php file… But if i use original snp.efi i don’t have permission problem, but i get kernel panic message like with ipxe.efi. I try to troubleshoot this permission issue, but everything looks good, (chown -R fogproject:apache /var/www/html/fog/service/ipxe + chmod -R 775 /var/www/html/fog/service/ipxe)
                    Did i forget something ? Is there any other changes to make for it to work?

                    C one-reply-to-this-post Last reply Reply Quote 0
                    • C
                      CedricoR @CedricoR
                      last edited by

                      @CedricoR Hi everyone! I did not find a solution, I tried to change kernel side server and client, I also tried several versions of ipxe.efi and snp.efi (1.5.8, 1.5 .9 and 1.5.10), I increased the size KERNEL RAMDISK SIZE, same result, and I see nothing more when I launch a task in debug mode and when I launch the memtest I have the following message “could not boot, exec format error (https://ipxe…)”
                      I also launched wireshark, I share the .pcap with you, nothing abnormal except that I don’t see anything happening in http when it retrieves the refind.conf and refind_x64.
                      TEST2.pcap
                      Finally if I try a reinstallation with version 1.5.8, the network card is not recognized with default kernel.
                      So it’s either a kernel problem, or permission on boot.php or a hardware problem. I remain stuck, do you have any ideas where I could look to fix this problem?
                      What’s weird is that the grub launches correctly after refind is loaded. I can navigate in the menus, but as soon as I launch “ubuntu”, the kernel panic appears

                      one-reply-to-this-post Last reply Reply Quote 0
                      • T
                        thomGee
                        last edited by thomGee

                        Hi there,
                        this Problem allready existed in this forum and has been signed solved, as the threadstarter resigned and used the EXIT-way in Fog
                        (https://forums.fogproject.org/topic/16762/local-grub-booting-fails-from-fog-menu-pxe-uefi/7)

                        For me the problem persisted, as I need the features in refind for dualbooting the systems.

                        Meanwhile I tried some more scenarios.
                        My PC’s have 2 OS’s : Windows 10 and Ubuntu

                        With Ubuntu 20.04 everything was fine untill one Update (still have the Image) and all version from there on show the the Kernel panic.

                        I tried several configs in initramfs - different compressions, I thought it is a bug

                        I think I followed all descriptions from all experts in the net for this Error.

                        But the system (as you allready know) boots fine, when booted directly

                        So I start to ask myself - what is the difference?

                        refind and booting from the memory fog-pxe presents.

                        is it possible, the compression gots worse?
                        that for some reason the initramfs gots bigger
                        is there a way to reduce the initramfs filesize

                        It is a pitty ther is not enough logging

                        one-reply-to-this-post Last reply Reply Quote 0
                        • S Sebastian Roth referenced this topic on
                        • 1 / 1
                        • First post
                          Last post

                        223

                        Online

                        11.1k

                        Users

                        16.7k

                        Topics

                        152.4k

                        Posts
                        Copyright © 2012-2023 FOG Project