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

    2.3.1_1 update problem

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    11 Posts 9 Posters 3.9k 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.
    • C Offline
      cmb
      last edited by

      Going to need some more specifics. By "freezing", what's happening? No longer reachable over the network at all, or?

      2.3.1 to 2.3.1_1 didn't change OS components, or really much at all outside a few changes in the web GUI which couldn't make the box freeze.

      1 Reply Last reply Reply Quote 0
      • B Offline
        bschapin
        last edited by

        The system would not finish the boot process. It appeared to hang as soon as it tried to boot from the internal flash (past the boot loader prompt). I should have saved a screen shot. I was plugged into the console for troubleshooting. No console menu, no GUI, no DHCP address delivered to the LAN port. Nothing. Multiple power cycles and hard resets had no effect at all. I downloaded a fresh install of 2.3.1 to a USB stick and the system booted off the USB with no issue. I completed a fresh install to the flash drive and added no packages and only minimal configuration changes like, WAN, LAN and DHCP setup. I tried the 2.3.1_1 update again later and system never completed a boot process again after the install completed. I reinstalled a fresh copy like above and the system is operating normally on 2.3.1.

        1 Reply Last reply Reply Quote 0
        • C Offline
          cmb
          last edited by

          Hm, can't think of anything along those lines. You recall where it stopped during the boot process?

          1 Reply Last reply Reply Quote 0
          • B Offline
            burdandrei
            last edited by

            Hi, i got maybe the same problem.
            Pfsense SG-8860 stuck during the boot, i connected console cable andthe last line was syncing OpenVPN.
            I rebooted again, and it took him ~20 minutes to make all the dots in Syncing OpenVPN.
            I managed to boot it only with all the interfaces disconnected, after it everything works perfect.
            i have no HA configured, but i had one carp address configured.

            1 Reply Last reply Reply Quote 0
            • PerforadoP Offline
              Perforado Rebel Alliance
              last edited by

              ADI or normal CE version?

              1 Reply Last reply Reply Quote 0
              • B Offline
                Blade Runner
                last edited by

                I experienced a similar problem updating to 2.3.1_1 from 2.3.1. Download failed several times before installation. The word 'catalogue' was underlined in red during failed attempts. It was not underlined when update was downloaded and installed.

                5/27/2016

                Updating repositories metadata…
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Upgrading pfSense-repo... done.
                Unlocking package pfSense-kernel-pfSense... done.
                Downloading upgrade packages...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Checking for upgrades (5 candidates): ..... done
                Processing candidates (5 candidates): ..... done
                The following 5 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

                40 MiB to be downloaded.
                Fetching pfSense-rc-2.3.1_1.txz: . done
                Fetching pfSense-kernel-pfSense-2.3.1_1.txz: …....... done
                Fetching pfSense-default-config-2.3.1_1.txz: . done
                Fetching pfSense-base-2.3.1_1.txz: .. done
                pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/All/pfSense-base-2.3.1_1.txz: Operation timed out

                Locking package pfSense-kernel-pfSense... done.
                Failed

                5/29/2016

                Updating repositories metadata...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Unlocking package pfSense-kernel-pfSense... done.
                Downloading upgrade packages...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Checking for upgrades (5 candidates): ..... done
                Processing candidates (5 candidates): ..... done
                The following 5 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

                25 MiB to be downloaded.
                Fetching pfSense-base-2.3.1_1.txz: ….... done
                pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/All/pfSense-base-2.3.1_1.txz: Operation timed out

                Locking package pfSense-kernel-pfSense... done.
                Failed

                Updating repositories metadata...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Unlocking package pfSense-kernel-pfSense... done.
                Downloading upgrade packages...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Checking for upgrades (5 candidates): ..... done
                Processing candidates (5 candidates): ..... done
                The following 5 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

                25 MiB to be downloaded.
                Fetching pfSense-base-2.3.1_1.txz: . done
                pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/All/pfSense-base-2.3.1_1.txz: Operation timed out

                Locking package pfSense-kernel-pfSense… done.
                Failed

                Updating repositories metadata...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Unlocking package pfSense-kernel-pfSense... done.
                Downloading upgrade packages...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Checking for upgrades (5 candidates): ..... done
                Processing candidates (5 candidates): ..... done
                The following 5 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-base: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense: 2.3.1 -> 2.3.1_1 [pfSense]

                25 MiB to be downloaded.
                Fetching pfSense-base-2.3.1_1.txz: …....... done
                Fetching pfSense-2.3.1_1.txz: . done
                Checking integrity... done (0 conflicting)

                Upgrading pfSense kernel...
                Updating pfSense-core repository catalogue...
                pfSense-core repository is up-to-date.
                Updating pfSense repository catalogue...
                pfSense repository is up-to-date.
                All repositories are up-to-date.
                Checking integrity... done (0 conflicting)
                The following 2 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core]
                pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core]
                [1/2] Upgrading pfSense-rc from 2.3.1 to 2.3.1_1…
                [1/2] Extracting pfSense-rc-2.3.1_1: …. done
                [2/2] Upgrading pfSense-kernel-pfSense from 2.3.1 to 2.3.1_1…
                ===> Keeping a copy of current kernel in /boot/kernel.old
                [2/2] Extracting pfSense-kernel-pfSense-2.3.1_1: …....... done
                Upgrade is complete.  Rebooting in 10 seconds.

                Locking package pfSense-kernel-pfSense... done.
                Success

                Do not be afraid to fail.

                1 Reply Last reply Reply Quote 0
                • E Offline
                  eric.barry
                  last edited by

                  This is happening to me as well.

                  SG-2440

                  2.3 (stock) -> 2.3.1_1

                  Console gives me nothing after the loading of the kernel.

                  Not as specific as "It appeared to hang as soon as it tried to boot from the internal flash (past the boot loader prompt)." (bschapin)

                  Output below:

                  /boot/kernel/kernel text=0x1292d98 data=0x8a1bb0+0x23ec10 syms=[0x8+0x1776d8+0x8
                  +0x173ea6]
                  Booting…
                  \

                  If you leave it alone it will reboot every ~40 seconds.

                  1 Reply Last reply Reply Quote 0
                  • T Offline
                    tarakesh
                    last edited by

                    @eric.barry:

                    This is happening to me as well.

                    SG-2440

                    2.3 (stock) -> 2.3.1_1

                    Console gives me nothing after the loading of the kernel.

                    Not as specific as "It appeared to hang as soon as it tried to boot from the internal flash (past the boot loader prompt)." (bschapin)

                    Output below:

                    /boot/kernel/kernel text=0x1292d98 data=0x8a1bb0+0x23ec10 syms=[0x8+0x1776d8+0x8
                    +0x173ea6]
                    Booting…
                    \

                    If you leave it alone it will reboot every ~40 seconds.

                    Exactly the same happend on my self build box with the 2.3.1 update.. also running nanobsd

                    2.4.1-RELEASE (amd64) on Intel D2500CCE Board Intel Atom D2500 DC @1.86GHz, 2GB RAM, 64GB Transcend SSD370
                    Internet Connection: UnityMedia 200Mbit/10Mbit Cable

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      ph32
                      last edited by

                      Oh shit, my server is offline since updating last week. Take a guess what hardware I have: SG-2440

                      It fits perfectly well that I am 10 000 km away from the box until November.

                      I will have plenty of fun instructing another person to do a reinstall :)

                      1 Reply Last reply Reply Quote 0
                      • U Offline
                        uaxero
                        last edited by

                        disable ipv6 and try again

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