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

    2.4.4 fails upgrade and fresh installation

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    42 Posts 6 Posters 6.3k 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.
    • RicoR
      Rico LAYER 8 Rebel Alliance
      last edited by

      You don't even see this screen when booting the Installer?
      0_1552761907747_pfSense_boot.png

      -Rico

      1 Reply Last reply Reply Quote 0
      • GrimsonG
        Grimson Banned @jbhowlesr
        last edited by

        @jbhowlesr said in 2.4.4 fails upgrade and fresh installation:

        So let’s leave “better hardware” comments out shall we.

        Your current hardware has issues booting with FreeBSD 11.2, so your choices for running pfSense on it are:

        • Try workarounds like the ones mentioned here.
        • Use different hardware
        • Create a bug report with the FreeBSD devs and hope they can fix it, after that wait for a pfSense version that uses a FreeBSD base containing the fix.

        Try to boot FreeBSD 12, if that works you could be lucky and use the upcoming pfSense 2.5.0 builds.

        1 Reply Last reply Reply Quote 0
        • J
          jbhowlesr
          last edited by

          @rico it will appear briefly but not show a spinning pipe (I) symbol.

          The system is a Intel 7th gen Quad Core with 16gb Ram and SSD. It’s really fast.

          GrimsonG 1 Reply Last reply Reply Quote 0
          • J
            jbhowlesr
            last edited by jbhowlesr

            @grimson I hope this works out. When is 2.50 coming?

            Boot FreeBSD 12? I’ll try that and see what happens.

            Do you have a link for a distro I can download?

            Is it possible that my hardware is just too new? It worked fine in 2.4.2 and 2.4.3

            1 Reply Last reply Reply Quote 0
            • RicoR
              Rico LAYER 8 Rebel Alliance
              last edited by

              Well you can try now by booting and install https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-RELEASE-amd64-bootonly.iso

              -Rico

              J 1 Reply Last reply Reply Quote 1
              • RicoR
                Rico LAYER 8 Rebel Alliance
                last edited by

                And with this image you can verify the problem with your hardware is upstream pfSense in FreeBSD 11.2: https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.2/FreeBSD-11.2-RELEASE-amd64-bootonly.iso

                -Rico

                1 Reply Last reply Reply Quote 0
                • GrimsonG
                  Grimson Banned @jbhowlesr
                  last edited by

                  @jbhowlesr said in 2.4.4 fails upgrade and fresh installation:

                  Let’s take a step back. I create the install media and boot the system off of it. It boots the media and before giving any prompts or (I) spinning pipes, I get the error in the photo in the beginning of this thread.

                  @jbhowlesr said in 2.4.4 fails upgrade and fresh installation:

                  @rico it will appear briefly but not show a spinning pipe (I) symbol.

                  You said nothing shows up, and now it does show up? What is it now?

                  If it does show do what it tells, hit Escape and go from there.

                  1 Reply Last reply Reply Quote 0
                  • J
                    jbhowlesr @Rico
                    last edited by

                    @rico

                    I’ll try that when I get home.

                    I’m a huge fan of snort and is one of about 3 reasons I push pfsense but fact remains that I’m getting this errors on a lot of systems that all worked with previous version of pfsense

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      As it boots, just keep whacking the space bar.

                      In the next few days we'll have 2.5.0 snapshots to try, based on FreeBSD 12, which is more likely to help.

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        jbhowlesr @jimp
                        last edited by

                        @jimp if I do this and if i get a prompt, I’m unclear as to what I need to do with this file that’s been mentioned

                        /boot/loader.conf.local

                        1 Reply Last reply Reply Quote 0
                        • RicoR
                          Rico LAYER 8 Rebel Alliance
                          last edited by

                          0_1552762937805_pfSense_boot_loader-prompt.png

                          -Rico

                          J 3 Replies Last reply Reply Quote 1
                          • J
                            jbhowlesr @Rico
                            last edited by

                            @rico

                            Perfect. This is exactly what I have been asking for. Thank you so much.

                            On my way home and will give that a shot when I get there.

                            1 Reply Last reply Reply Quote 0
                            • J
                              jbhowlesr @Rico
                              last edited by

                              @rico

                              Big shout out here cause this worked and the system is installing now.

                              I’ll post again after it’s all up and running and report any further issues

                              1 Reply Last reply Reply Quote 0
                              • J
                                jbhowlesr @Rico
                                last edited by

                                @rico

                                Sir, pfsense is running great. However, anytime a reboot occurs, I gotta enter the disable=1 string in your photo. How do I automate this so it can reboot unattended?

                                1 Reply Last reply Reply Quote 0
                                • RicoR
                                  Rico LAYER 8 Rebel Alliance
                                  last edited by Rico

                                  Now to make it persistent run
                                  echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
                                  after booting from console or SSH.

                                  -Rico

                                  J 1 Reply Last reply Reply Quote 0
                                  • J
                                    jbhowlesr @Rico
                                    last edited by jbhowlesr

                                    @rico

                                    To make sure I’m following you

                                    Open >> "/boot/loader.conf.local” using the pfsense file editor”

                                    And add echo "hint.sdhci_pci.1.disabled="1"" to the bottom of the file.

                                    Save then restart the system.

                                    1 Reply Last reply Reply Quote 0
                                    • GertjanG
                                      Gertjan
                                      last edited by

                                      echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
                                      

                                      is the same thing as opening the file /boot/loader.conf.local and adding
                                      hint.sdhci_pci.1.disabled="1"
                                      in it.

                                      No "help me" PM's please. Use the forum, the community will thank you.
                                      Edit : and where are the logs ??

                                      J 1 Reply Last reply Reply Quote 0
                                      • J
                                        jbhowlesr @Gertjan
                                        last edited by jbhowlesr

                                        @gertjan

                                        I’m in the file system now. A file called loader.conf.local does not exist. However, a file called loader.conf exists and I made a copy of it and renamed to loader.conf.local and edited that file with the line above.

                                        EDIT: just tried this and it didn’t work. Obviously I’m missing something?

                                        1 Reply Last reply Reply Quote 0
                                        • RicoR
                                          Rico LAYER 8 Rebel Alliance
                                          last edited by

                                          Just login via SSH and type or copy/paste
                                          echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
                                          reboot and thats it.

                                          -Rico

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            The file: /boot/loader.conf.local should contain only the line:
                                            hint.sdhci_pci.1.disabled=1

                                            You might add more stuff to it later but since you had to just create it it shouldn't right now.

                                            Steve

                                            J 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.