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

    Lost Interfaces When Upgrading to 2.4.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 6 Posters 1.2k 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.
    • ghostshellG
      ghostshell
      last edited by

      After upgrading to 2.4.1 I lost any nic past em3, all I have now is em0 em1 em2 em3

      During the upgrade the box got stuck and I consoled in and it was at the screen asking to setup VLANs and that it could not find interfaces em4 em5 em6 em7.

      When going to Interfaces I cannot add them back as they are not listed anymore.

      I am using a Talari T750 as hardware.

      Sorry I do not know the board or NICs off-hand.

      I will test 2.4.1 on my backup box a Checkpoint U Series

      Since I use the missing ports I am reinstalling 2.4.

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

        You'll need to provide a lot more information, at least details about the hardware in use and a dmesg output would be usefull too.

        1 Reply Last reply Reply Quote 0
        • ghostshellG
          ghostshell
          last edited by

          Going back to 2.4 got me them all back.

          I cannot upgrade to 2.4.1 to troubleshoot as I use some of the missing ports.

          I can test it on another box when I get home.

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            Going back to 2.4 got me them all back.

            Fine to hear about that.

            I cannot upgrade to 2.4.1 to troubleshoot as I use some of the missing ports.

            One question on my own interest will be, what is this for hardware? Are also 32Bit "only" cards are inside?

            I can test it on another box when I get home.

            Will be not the same and brings you nothing about the failure on the other box!

            Be sure you have not one of the following points given to oyur network:

            • It was not a NanoBSD install
            • It was not a 32Bit install on 32Bit only or mixed up hardware!
              Since since pfsense version 2.4.x all must be 64Bit based, 100%
            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              @ghostshell:

              Going back to 2.4 got me them all back.

              I cannot upgrade to 2.4.1 to troubleshoot as I use some of the missing ports.

              I can test it on another box when I get home.

              "missing" how? What interfaces?

              What exactly is the hardware? There were no driver differences between 2.4.0 and 2.4.1.

              Without any supporting detail this report is questionable at best.

              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!

              1 Reply Last reply Reply Quote 0
              • ghostshellG
                ghostshell
                last edited by

                @jimp:

                @ghostshell:

                Going back to 2.4 got me them all back.

                I cannot upgrade to 2.4.1 to troubleshoot as I use some of the missing ports.

                I can test it on another box when I get home.

                "missing" how? What interfaces?

                What exactly is the hardware? There were no driver differences between 2.4.0 and 2.4.1.

                Without any supporting detail this report is questionable at best.

                I mentioned in the OP when upgrading it got stuck and said it could not find interfaces em4 em5 em6 em7, basically anything past em3 it could not find and when going to Interfaces they were no longer listed.

                I can try upgrading again, I fresh installed 2.4 and restored my config from 2.4.

                1 Reply Last reply Reply Quote 0
                • ghostshellG
                  ghostshell
                  last edited by

                  @BlueKobold:

                  Going back to 2.4 got me them all back.

                  Fine to hear about that.

                  I cannot upgrade to 2.4.1 to troubleshoot as I use some of the missing ports.

                  One question on my own interest will be, what is this for hardware? Are also 32Bit "only" cards are inside?

                  I can test it on another box when I get home.

                  Will be not the same and brings you nothing about the failure on the other box!

                  Be sure you have not one of the following points given to oyur network:

                  • It was not a NanoBSD install
                  • It was not a 32Bit install on 32Bit only or mixed up hardware!
                    Since since pfsense version 2.4.x all must be 64Bit based, 100%

                  Since I bought the hardware I have always used 64-bit.

                  The Talari T750 was a Talari firewall and I removed the HDD and added an SSD with 2.3.X pfsense 64-bit

                  1 Reply Last reply Reply Quote 0
                  • jahonixJ
                    jahonix
                    last edited by

                    Do you use VLANs?

                    1 Reply Last reply Reply Quote 0
                    • ghostshellG
                      ghostshell
                      last edited by

                      @jahonix:

                      Do you use VLANs?

                      I do not.

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

                        "I lost any nic past em3, all I have now is em0 em1 em2 em3" does not accurately convey that they were all em NICs nor does it state how many were missing.

                        Still, there were no driver changes so it's not likely to be related. Try a fresh install of 2.4.1 instead to make sure it wasn't a problem when upgrading.

                        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!

                        1 Reply Last reply Reply Quote 0
                        • ghostshellG
                          ghostshell
                          last edited by

                          @jimp:

                          "I lost any nic past em3, all I have now is em0 em1 em2 em3" does not accurately convey that they were all em NICs nor does it state how many were missing.

                          Still, there were no driver changes so it's not likely to be related. Try a fresh install of 2.4.1 instead to make sure it wasn't a problem when upgrading.

                          OK will do.

                          Sorry I do not know what info you need as I have never had upgrade issues before with any hardware I have used since starting with pfsense 2.1.X.

                          If you would tell me what you need I will happily get it.

                          To more clear from the OP. I right now with 2.4 have em0-em7. When updating from 2.4 to 2.4.1 I only had em0-em3 and during the upgrade it was stuck on a screen during start stating that it could not find em4 em5 em6 em7.

                          I thought mentioning what I have listed and what was missing would have been clear, sorry.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kejianshi
                            last edited by

                            Stay on 2.4  Wait for 2.4.2

                            Long experience…  The problem will appear to enough people and be solved in a soon future update.

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