• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

How to have pfsense automatically boot into multi?

Scheduled Pinned Locked Moved General pfSense Questions
13 Posts 3 Posters 1.4k Views
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.
  • L
    lukeai
    last edited by stephenw10 Nov 1, 2019, 12:00 PM Oct 31, 2019, 4:49 PM

    How to have pfsense automatically boot in multi user mode after a short timeout instead of waiting for me to plug in a keyboard and press "1"?

    (2.4.4-p3 on pondesk Intel-E3845-4-LAN-1-COM-AESNI-4G-Fanless-Firewall-Router_MNHO-073)

    1 Reply Last reply Reply Quote 0
    • P
      provels
      last edited by provels Oct 31, 2019, 6:04 PM Oct 31, 2019, 6:00 PM

      Check /boot/loader.conf and make sure

      autoboot_delay="3"
      

      is present. But the stock install should have done that...

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 0
      • L
        lukeai
        last edited by lukeai Nov 1, 2019, 10:17 AM Nov 1, 2019, 10:16 AM

        Thanks for replying, I can confirm that autoboot_delay="3" is present in /boot/loader.conf and that I have made no changes at all to the stock configuration.

        1 Reply Last reply Reply Quote 0
        • P
          provels
          last edited by Nov 1, 2019, 10:21 AM

          All righty. I'm not familiar with your specific hardware, but is there a BIOS setting to "Halt on error"? If so, can you set to "Halt on error except keyboard"?

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          1 Reply Last reply Reply Quote 0
          • L
            lukeai
            last edited by Nov 1, 2019, 11:50 AM

            I have looked thoroughly through the BIOS and cannot find any option relating to Halting or Errors. Is there anything else it could be called?

            dmidecode tells me that I have v. 5.5.5 American Megatrends although if I press 'Del' and enter setup on boot I get Aptio Setup Utility 2.17.1249

            1 Reply Last reply Reply Quote 0
            • P
              provels
              last edited by provels Nov 1, 2019, 12:05 PM Nov 1, 2019, 11:56 AM

              Anything like this? Or "Integrated Peripherals" or "Device Options"?
              c5017392-7dba-4414-96de-b18699de3258-image.png

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Nov 1, 2019, 12:02 PM

                It would halt in the BIOS not the boot loader if that were the case.

                It should normally continue past that point automatically. Has this always happened? It has stopped there everytime after you installed? What exact image did you install from?

                Steve

                L 1 Reply Last reply Nov 1, 2019, 12:09 PM Reply Quote 0
                • L
                  lukeai @stephenw10
                  last edited by Nov 1, 2019, 12:09 PM

                  @stephenw10
                  I installed two days ago from the latest image 2.4.4-p3 amd64, usb memstick installer, console VGA - the sha256 sum confirms the image was correct. I used GPT on the USB drive. This is how it has been since I installed. I have tried installing twice (only difference was using a different USB port usb2 and usb3 for the installer, had a wild idea that this might somehow affect something), Both installs had this behaviour.

                  1 Reply Last reply Reply Quote 0
                  • S
                    stephenw10 Netgate Administrator
                    last edited by Nov 1, 2019, 12:12 PM

                    Hmm, it should only stop there if it sees some input at that point.

                    You could try setting autoboot_delay="0" to stop it waiting there at all.

                    Steve

                    L 1 Reply Last reply Nov 1, 2019, 12:27 PM Reply Quote 0
                    • L
                      lukeai @stephenw10
                      last edited by Nov 1, 2019, 12:27 PM

                      @stephenw10 I have set auto_boot_delay="0", this did not chang the boot behaviour at all as described earlier.

                      1 Reply Last reply Reply Quote 0
                      • S
                        stephenw10 Netgate Administrator
                        last edited by Nov 1, 2019, 12:35 PM

                        Hmm, well you might try installing using MBR instead, that does make it boot slightly differently.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • L
                          lukeai
                          last edited by Nov 1, 2019, 1:17 PM

                          OK I reinstalled with an MBR disk layout and that enabled a visible timeout which gave way to a hanging "boot..." which was resolved with this I guess this was the issue all along but I now have a working system so I'm not going to reinstall yet again. Thanks for suggestions both.

                          1 Reply Last reply Reply Quote 0
                          • S
                            stephenw10 Netgate Administrator
                            last edited by stephenw10 Nov 1, 2019, 2:21 PM Nov 1, 2019, 2:20 PM

                            That blog post is wrong (at least partially 😉 ). You should add that to /boot/loader.conf.local to avoid it being overwritten.

                            See our intructions for that here: https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html?highlight=kern%20vty#upgrading-from-versions-older-than-pfsense-2-4-4

                            Steve

                            1 Reply Last reply Reply Quote 0
                            13 out of 13
                            • First post
                              13/13
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                              This community forum collects and processes your personal information.
                              consent.not_received