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

    Thanks for the utterly broken 2.1 update.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    42 Posts 8 Posters 10.1k 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.
    • A
      adegans
      last edited by

      Today I "fixed" the other soekris with the Memstick version which went without a hitch. yay!
      Both are now running pfSense 2.1.

      As mentioned earlier; Neither was upgradable from 2.0.3 using the 4G nanoBSD variant. Still not sure why.
      However, with the tips/ideas given here I think both systems now run faster than before. So it's not all bad. Just a day wasted on fixing stuff  :-\

      See attached image if you're curious where your help went :)

      patchkast.jpg
      patchkast.jpg_thumb

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

        It looks considerably more neat than my table-o-network down in the basement  ;D

        Mine is old 65w dual core dell with a motley collection of Intel NICs, a 19inch CRT (with a tube) from before my kids were born and a keyboard from the 90s that just keeps going…  Looks like steampunk pfsense...

        Switches are all pretty new stuff - I couldn't find any 90s looking gigabit managed switches to match  :P

        1 Reply Last reply Reply Quote 0
        • S
          Supermule Banned
          last edited by

          HAHAHAHAHAHAHAHAHA!!

          1 Reply Last reply Reply Quote 0
          • G
            Gradius
            last edited by

            Cute installation there.

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

              Supermule - I assume you are laughing with me…  not at me...  Hmmmmm???  ::)

              The other day my 17 year old boy asked me "Daddy - What is that big thing on the front of your car?"  I said "Thats called a bumper".

              Yeah...  I'm nostalgic you might say.

              1 Reply Last reply Reply Quote 0
              • A
                adegans
                last edited by

                The cases + half of the interior came with the building i'm renting :) All the cabling into the office space was already in place too. Luckily… Saved us a ton of money.
                I just had to fill the gaps with switches and stuff to make it work!

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

                  So, now that all is right with your pfsense the moderators can rename this thread "Thanks for the utterly awesome 2.1 update."?

                  1 Reply Last reply Reply Quote 0
                  • A
                    adegans
                    last edited by

                    Well the update never worked. As mentioned above. Failed multiple times.
                    But fresh installs did work.

                    1 Reply Last reply Reply Quote 0
                    • D
                      DimitriRodis
                      last edited by

                      So I had the same problem as the OP. Here is some more information. Sorry I don't have more–I had to get it up and running and I didn't have a whole lot of time to troubleshoot, but here is what happened:

                      I have a Firebox that is booting from a 2GB CF card that was originally flashed with a 2.0.1 image. I performed an update through the GUI. It went successfully (supposedly). When I rebooted, the box would not respond on the network. I attached a serial cable and found that all 3 of my interfaces were not showing their IPs. I tried setting my LAN interface using the serial console--and it showed up, but it still would not respond on the network. So, I used the menu option to "restore an earlier configuration" figuring that maybe the config got botched somehow during the upgrade. After the reboot, no dice--same thing--none of the interfaces showed their IP addresses. I then rebooted it from the previous slice, and 2.0.1 booted up perfectly with my config working. So, I ran the update to 2.1 again, and got the exact same results--the interfaces had no IPs on them. So, I then used the console to reset everything to defaults, and set the config from scratch on 2.1 and it worked just fine.

                      The config on that box was NOT complicated--had 1 firewall rule, a WAN interface set to DHCP, and two LAN interfaces bridged eith DHCP server running on the LAN side.

                      Hopefully that gives someone an idea of what could be happening.

                      I do have other boxes like this to upgrade--if someone wants me to collect more information, just tell me what you want me to collect so that if it happens again I will collect the information and then proceed to get my box working!

                      Dimitri Rodis
                      Integrita Systems LLC
                      http://www.integritasystems.com

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

                        Which firebox? How much RAM?
                        Key to this seems to be the backing up of RRD files in combination with the update/reinstalling packages. If you have either a lot of interfaces or a lot of data you may run out of space. How far back does your RRD data go?

                        http://forum.pfsense.org/index.php/topic,66571.msg364374.html#msg364374

                        Steve

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