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

    rEFInd reboots instead of loading windows

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    11
    740
    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.
    • Wayne WorkmanW
      Wayne Workman @Gordon Taylor
      last edited by

      @gordon-taylor Check the apache error logs on your fog server from the times when you know reboots have happened, please share anything interesting from that time period here in a code block.

      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
      • Gordon TaylorG
        Gordon Taylor
        last edited by

        ok there isn’t anything in the apache log (/var/log/apache2/error.log) unless i change it to debug then there is lots but nothing that looks bad

        [Mon Mar 19 15:58:22.168627 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
        [Mon Mar 19 15:58:22.283609 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
        [Mon Mar 19 15:58:22.283653 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
        [Mon Mar 19 15:58:22.439171 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
        [Mon Mar 19 15:58:22.439192 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
        [Mon Mar 19 15:58:22.486550 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
        [Mon Mar 19 15:58:22.486570 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
        
        

        some of the workstations after rebooting once then get stuck with the windows boot splash screen and saying Perpairing Automatic Repair at the bottom… almost like its maybe booting the recovery partition… but its not doing anything no disk activity just stuck untill rebooted…

        the only os I’ve tried so far is Win10 1709 i think i might have a uefi 1607 or 1703 image i can try see if it happens across different host oses…

        Gordon TaylorG 1 Reply Last reply Reply Quote 0
        • Gordon TaylorG
          Gordon Taylor @Gordon Taylor
          last edited by

          ok i did have a 1703 image but it does similar now it reboots then drops through to automatic repair blue screen in this case (but then its a sealed sysprep image - rather than a image that has been through the whole process) - if i pull the lan out to let it finish the windows setup then the behaviour is the same as 1709 - reboot then next time sat on preparing automatic repair splash screen.

          i also have slightly different behaviour from NUC6i5SYK which doesn’t reboot but just sits with the windows logo on the screen and doesn’t boot up (no disk activity) again saying preparing automatic repair

          i think there is a message from rEFInd but it flashes to quickly is there a way to interactively watch that step by step by editing refind.conf?

          of course if you pull the LAN cable out so it doesn’t network boot they all boot fine.

          Wayne WorkmanW Tom ElliottT 3 Replies Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman @Gordon Taylor
            last edited by

            @developers has the way partitions are handled changed between 1.5 RC12 and 1.5 release?

            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 no

              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
              • Wayne WorkmanW
                Wayne Workman @Gordon Taylor
                last edited by Wayne Workman

                @gordon-taylor So to summarize my understanding (and correct me if I’m wrong), you seem to be having two problems.

                First problem:

                the Intel NUCs i have that are UEFI boot have now started rebooting instead of loading windows after rEFInd.

                Second problem:

                it does similar now it reboots then drops through to automatic repair blue screen in this case

                Which one is the real problem? Is there actually something wrong with rEFInd or do you think it’s image related? Or are you having both of these problems?

                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/

                Gordon TaylorG 1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott @Gordon Taylor
                  last edited by

                  @gordon-taylor please try editing the /var/www/fog/service/ipxe/refind.conf file and set the scan_delay to 0. I’ve heard of this seeming to be a fix for this type of problem.

                  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

                  Gordon TaylorG 1 Reply Last reply Reply Quote 1
                  • Gordon TaylorG
                    Gordon Taylor @Tom Elliott
                    last edited by

                    @tom-elliott Thanks that does seem to have done the trick 🙂

                    1 Reply Last reply Reply Quote 0
                    • Gordon TaylorG
                      Gordon Taylor @Wayne Workman
                      last edited by

                      @wayne-workman it was really just the first but the scan_delay line seemed to fix it… but whats odd is i know there was a 5 second delay before i upgraded fog cause id see it say so on the workstations… and they booted fine 😕 until after the upgrade.

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

                        @gordon-taylor The binary might have changes (refind.efi) though we don’t know what changed (we don’t write the refind program stuff.)

                        I’ve made scan_delay = 0 the default when 1.5.1 releases.

                        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 1
                        • 1 / 1
                        • First post
                          Last post

                        172

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project