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

UEFI local disk chainloading error

Scheduled Pinned Locked Moved Solved
FOG Problems
3
27
3.6k
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
    plegrand
    last edited by plegrand Sep 20, 2018, 3:16 AM Sep 20, 2018, 9:07 AM

    FOG 1.5.0

    Hello,
    i’ve got again the same problem with uefi computer (Dell).
    Before it was possible to use legacy boot with internal device, with new computer Dell, it’s impossible now to use internal device.
    Then i have to use UEFI settings.

    The computer boot PXE correctly and i’ve got the PXE menu.
    Everything works fine except “Boot from hard disk”.
    When i choose “Boot from hard disk”, i’ve got the “chainloading failed…” error message.

    For this host, i tryed :
    Exit : no success
    Sanboot : no success
    REFIND_EFI : no success

    Have you got a solution for that ?

    Thanks for your help

    0_1537434387585_499e99e8-64a1-423c-a20e-e50782f83388-image.png

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Sep 20, 2018, 9:57 AM

      For each host as well as on a global level, there are exit modes for both bios and uefi based systems. By default your exit mode for bios should be sanboot, the default exit mode uefi is refind. The chain loading failure is a bit confusing since that means iPXE could not call the exit mode.

      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
      • P
        plegrand
        last edited by Sep 20, 2018, 11:36 AM

        Actually on the global level :
        exit mode for bios is sanboot
        exit mode uefi is exit.

        On the host level configuration, i tryed :
        Exit : “chainloading failed…” error message.
        Sanboot : loop on the main menu
        REFIND_EFI : It seems that the partitions choosen is the repair partition

        What kind of informations do you need to help me ?

        Thanks for your answers

        G 1 Reply Last reply Sep 20, 2018, 12:23 PM Reply Quote 0
        • G
          george1421 Moderator @plegrand
          last edited by Sep 20, 2018, 12:23 PM

          @plegrand said in UEFI local disk chainloading error:

          REFIND_EFI : It seems that the partitions choosen is the repair partition

          OK so refind IS NOT giving you the chain loading error, but just selecting the wrong partition. Is that correct?

          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!

          P 2 Replies Last reply Sep 20, 2018, 12:48 PM Reply Quote 0
          • P
            plegrand @george1421
            last edited by Sep 20, 2018, 12:48 PM

            @george1421 I’m not really sure but i think this is the problem

            1 Reply Last reply Reply Quote 0
            • P
              plegrand @george1421
              last edited by Sep 20, 2018, 12:54 PM

              @george1421

              After the PXE boot menu
              It display refind logo
              then scan disk
              It display 2 time dell logo
              at the third time :
              DELL logo and preparation of the automatic repair

              G 1 Reply Last reply Sep 20, 2018, 1:08 PM Reply Quote 0
              • G
                george1421 Moderator @plegrand
                last edited by Sep 20, 2018, 1:08 PM

                @plegrand Well it IS a different issue. Basically, a chain loading error is roughly equivalent to a blue screen in windows. Where refind not identifying the proper boot partition is a problem. The end result is that it doesn’t boot, but for different reasons.

                If you change the default boot order in the firmware to the hard drive first does it boot as expected?

                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!

                P 1 Reply Last reply Sep 20, 2018, 1:09 PM Reply Quote 0
                • P
                  plegrand @george1421
                  last edited by plegrand Sep 20, 2018, 7:33 AM Sep 20, 2018, 1:09 PM

                  @george1421

                  If i dont boot PXE it boot well
                  if i boot directly on hard disk it boot well

                  G 1 Reply Last reply Sep 20, 2018, 2:25 PM Reply Quote 0
                  • G
                    george1421 Moderator @plegrand
                    last edited by Sep 20, 2018, 2:25 PM

                    @plegrand Ok, so we need to understand why refind is incorrectly selecting the recovery partition.

                    From a windows computer, can you give us a screen shot of the disk partition layout? You can do this from the Computer Management-> Disk Management plugin. Is your disk layout unique or just what ever windows picks when you install it?

                    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!

                    P 2 Replies Last reply Sep 20, 2018, 2:36 PM Reply Quote 0
                    • P
                      plegrand @george1421
                      last edited by plegrand Sep 20, 2018, 8:40 AM Sep 20, 2018, 2:36 PM

                      @george1421

                      0_1537454182615_c81e4c8c-653c-41fc-9716-2e2810238a63-image.png

                      0_1537454164092_3f513ede-ea09-4901-baeb-e02e4d376e56-image.png

                      G 1 Reply Last reply Sep 20, 2018, 2:40 PM Reply Quote 0
                      • G
                        george1421 Moderator @plegrand
                        last edited by george1421 Sep 20, 2018, 8:40 AM Sep 20, 2018, 2:40 PM

                        @plegrand Are these from 2 different computers?

                        In the top picture the partitions go

                        1. efi,
                        2. 😄
                        3. reserved
                        4. extra

                        In the bottom picture

                        1. efi
                        2. reserved
                        3. 😄
                        4. extra

                        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!

                        P 3 Replies Last reply Sep 20, 2018, 2:41 PM Reply Quote 0
                        • P
                          plegrand @george1421
                          last edited by Sep 20, 2018, 2:41 PM

                          @george1421
                          No it’s the same computer
                          The photo come from boot pxe and Information computer fog utility

                          1 Reply Last reply Reply Quote 0
                          • P
                            plegrand @george1421
                            last edited by Sep 21, 2018, 7:50 AM

                            @george1421
                            Do you think i should upgrade FOG to the latest version ?
                            I’m using fog 1.5.0
                            Is there some risks to upgrade to 1.5.4 ?
                            Thanks

                            G 1 Reply Last reply Oct 19, 2018, 12:21 PM Reply Quote 0
                            • P
                              plegrand @george1421
                              last edited by plegrand Sep 21, 2018, 2:45 AM Sep 21, 2018, 8:44 AM

                              @george1421
                              0_1537519486624_ae4a9c13-8f4c-4777-bea0-8b1c43694e06-image.png

                              1 Reply Last reply Reply Quote 0
                              • P
                                plegrand @george1421
                                last edited by plegrand Sep 21, 2018, 6:29 AM Sep 21, 2018, 12:02 PM

                                @george1421
                                Hello,
                                i found this in the forum:
                                https://forums.fogproject.org/topic/12115/dell-optiplex-3050-avec-windows-10-uefi/6
                                Then i made a try by modify the “/var/www/fog/service/ipxe/refind.conf” file

                                # scanfor internal,hdbios
                                

                                Now it works :
                                After the PXE boot menu
                                It display refind logo
                                then it display "Pausing before disk scan; please wait…
                                It display 2 time dell logo
                                at the third time : It launch windows 10.

                                Could you explain me why :

                                • Could you explain me why it works now ?
                                • It display “Pausing before disk scan; please wait…”, while i disabled it
                                # scanfor internal,hdbios
                                
                                • Why it display 3 times the DELL logo ?

                                Thanks for your help

                                1 Reply Last reply Reply Quote 0
                                • P
                                  plegrand
                                  last edited by Oct 19, 2018, 11:47 AM

                                  @george1421
                                  In fact here is the situation.
                                  The only problem i have is with uefi local boot.
                                  i tried Exit Sanboot REFIND_EFI without success.
                                  Is there a way to solve that?

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    george1421 Moderator @plegrand
                                    last edited by Oct 19, 2018, 12:21 PM

                                    @plegrand said in UEFI local disk chainloading error:

                                    Is there some risks to upgrade to 1.5.4 ?

                                    Wow sorry I did not see this until now. Let me try to catch up.

                                    1. Yes you should always be on the latest release. Currently its 1.5.4, the developers are working on some fixes to 1.5.4 with the 1.5.5 release but upgrade to 1.5.4 and then I can help you with the fixes to 1.5.4.

                                    2. If you disable options in the refind.conf file it will take what ever the defaults are built into the program. I’m trying to remember, I believe there was an issue with refind 0.11.2 where downgrading refind to 0.11.0 solve the user’s issue, but I can’t seem to remember what the problem was that this is a fix for.

                                    3. Sometimes the uefi firmware needs a little settling time before refind scans for hardware. There is an option in refind.conf to have refind pause for a bit then attempt to detect hardware.

                                    4. For uefi systems your only options are refind and grub the rest are mainly for bios mode computers.

                                    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!

                                    P 1 Reply Last reply Oct 19, 2018, 12:26 PM Reply Quote 0
                                    • P
                                      plegrand @george1421
                                      last edited by Oct 19, 2018, 12:26 PM

                                      @george1421
                                      No problem 🙂
                                      i saw that there was some problem : Erasing current MBR/GPT tables.
                                      If i follow this everything will work fine :
                                      https://forums.fogproject.org/topic/12370/it-takes-longer-time-more-than-5-minutes-erasing-current-mbr-gpt-tables/15

                                      thanks for your help

                                      G 1 Reply Last reply Oct 19, 2018, 12:33 PM Reply Quote 0
                                      • G
                                        george1421 Moderator @plegrand
                                        last edited by Oct 19, 2018, 12:33 PM

                                        @plegrand said in UEFI local disk chainloading error:

                                        i saw that there was some problem : Erasing current MBR/GPT tables.

                                        To fix, you must just download to FOS kernel 4.15.2. The developers found what was causing the issue in a third party application. They are currently working with that third party application to resolve the issue. That fix will be rolled out with FOG 1.5.5 and the linux kernel 4.18.x.

                                        There also is an out of memory condition that is fixed by adding a line to a php-fpm config file. With these two fixes FOG 1.5.4 works pretty well. There is still an issue with multicasting with 1.5.4 that has been fixed for 1.5.5. I believe the developers are trying to track down a FOG image replicator issue at the moment.

                                        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!

                                        P 2 Replies Last reply Oct 19, 2018, 12:57 PM Reply Quote 0
                                        • P
                                          plegrand @george1421
                                          last edited by Oct 19, 2018, 12:57 PM

                                          @george1421
                                          Can you explain me how you do that ?
                                          Kernel 4.15.2 and php-fpm config file

                                          G 1 Reply Last reply Oct 19, 2018, 1:01 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          • First post
                                            Last post

                                          164

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project