[Fixed] SG1000 Won't boot after latest update



  • I am trying to boot after updating my SG1000 to the latest snapshot and now all I get is "CCCCCCCC..." when I connect to serial on the device.

    >>> 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.
    >>> Removing vital flag from lang/php72... 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 (27 candidates): .......... done
    Processing candidates (27 candidates): .......... done
    The following 31 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    	isc-dhcp44-server: 4.4.1_3 [pfSense]
    	isc-dhcp44-relay: 4.4.1 [pfSense]
    	isc-dhcp44-client: 4.4.1 [pfSense]
    
    Installed packages to be UPGRADED:
    	wpa_supplicant: 2.6_2 -> 2.6_3 [pfSense]
    	unbound: 1.7.3 -> 1.8.0 [pfSense]
    	sqlite3: 3.24.0_1 -> 3.25.1 [pfSense]
    	smartmontools: 6.6_1 -> 6.6_2 [pfSense]
    	relayd: 5.5.20140810_2 -> 5.5.20140810_3 [pfSense]
    	py27-setuptools: 39.2.0 -> 40.0.0 [pfSense]
    	php72-pear-XML_RPC2: 1.1.3_1 -> 1.1.4 [pfSense]
    	php72-pear-Net_SMTP: 1.8.0 -> 1.8.1 [pfSense]
    	pfSense-u-boot-ufw: 2.4.5.a.20181008.0501 -> 20180905 [pfSense]
    	pfSense-rc: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense-kernel-pfSense-uFW: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense-default-config-serial: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense-base: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense: 2.4.5.a.20181007.1230 -> 2.4.5.a.20181015.0836 [pfSense]
    	openvpn: 2.4.6_1 -> 2.4.6_3 [pfSense]
    	oniguruma: 6.8.1 -> 6.9.0 [pfSense]
    	nginx: 1.14.0_6,2 -> 1.14.0_12,2 [pfSense]
    	links: 2.16,1 -> 2.16_1,1 [pfSense]
    	libnghttp2: 1.32.0 -> 1.33.0 [pfSense]
    	liblz4: 1.8.2,1 -> 1.8.3,1 [pfSense]
    	libevent: 2.1.8_1 -> 2.1.8_2 [pfSense]
    	json-c: 0.13 -> 0.13.1 [pfSense]
    	glib: 2.50.3_4,1 -> 2.56.1_1,1 [pfSense]
    	expat: 2.2.5 -> 2.2.6_1 [pfSense]
    	dhcp6: 20080615.2 -> 20080615.2_2 [pfSense]
    	bind-tools: 9.12.2P1 -> 9.12.2P2 [pfSense]
    
    Installed packages to be REINSTALLED:
    	strongswan-5.7.1 [pfSense] (needed shared library changed)
    
    Number of packages to be installed: 4
    Number of packages to be upgraded: 26
    Number of packages to be reinstalled: 1
    
    The process will require 12 MiB more space.
    54 MiB to be downloaded.
    [1/31] Fetching wpa_supplicant-2.6_3.txz: .......... done
    [2/31] Fetching unbound-1.8.0.txz: .......... done
    [3/31] Fetching strongswan-5.7.1.txz: .......... done
    [4/31] Fetching sqlite3-3.25.1.txz: .......... done
    [5/31] Fetching smartmontools-6.6_2.txz: .......... done
    [6/31] Fetching relayd-5.5.20140810_3.txz: .......... done
    [7/31] Fetching py27-setuptools-40.0.0.txz: .......... done
    [8/31] Fetching php72-pear-XML_RPC2-1.1.4.txz: ........ done
    [9/31] Fetching php72-pear-Net_SMTP-1.8.1.txz: .. done
    [10/31] Fetching pfSense-u-boot-ufw-20180905.txz: .......... done
    [11/31] Fetching pfSense-rc-2.4.5.a.20181015.0747.txz: .. done
    [12/31] Fetching pfSense-kernel-pfSense-uFW-2.4.5.a.20181015.0747.txz: .......... done
    [13/31] Fetching pfSense-default-config-serial-2.4.5.a.20181015.0747.txz: . done
    [14/31] Fetching pfSense-base-2.4.5.a.20181015.0747.txz: .......... done
    [15/31] Fetching pfSense-2.4.5.a.20181015.0836.txz: . done
    [16/31] Fetching openvpn-2.4.6_3.txz: .......... done
    [17/31] Fetching oniguruma-6.9.0.txz: .......... done
    [18/31] Fetching nginx-1.14.0_12,2.txz: .......... done
    [19/31] Fetching links-2.16_1,1.txz: .......... done
    [20/31] Fetching libnghttp2-1.33.0.txz: .......... done
    [21/31] Fetching liblz4-1.8.3,1.txz: .......... done
    [22/31] Fetching libevent-2.1.8_2.txz: .......... done
    [23/31] Fetching json-c-0.13.1.txz: ....... done
    [24/31] Fetching glib-2.56.1_1,1.txz: .......... done
    [25/31] Fetching expat-2.2.6_1.txz: .......... done
    [26/31] Fetching dhcp6-20080615.2_2.txz: .......... done
    [27/31] Fetching bind-tools-9.12.2P2.txz: .......... done
    [28/31] Fetching pfSense-u-boot-env-20180904.txz: ... done
    [29/31] Fetching isc-dhcp44-server-4.4.1_3.txz: .......... done
    [30/31] Fetching isc-dhcp44-relay-4.4.1.txz: .......... done
    [31/31] Fetching isc-dhcp44-client-4.4.1.txz: .......... done
    Checking integrity... done (3 conflicting)
      - isc-dhcp44-server-4.4.1_3 [pfSense] conflicts with isc-dhcp43-server-4.3.6P1_1 [installed] on /usr/local/etc/dhcpd.conf.sample
      - isc-dhcp44-relay-4.4.1 [pfSense] conflicts with isc-dhcp43-relay-4.3.6P1_1 [installed] on /usr/local/etc/rc.d/isc-dhcrelay6
      - isc-dhcp44-client-4.4.1 [pfSense] conflicts with isc-dhcp43-client-4.3.6P1 [installed] on /usr/local/sbin/dhclient
    Checking integrity... done (0 conflicting)
    Conflicts with the existing packages have been found.
    One more solver iteration is needed to resolve them.
    The following 34 package(s) will be affected (of 0 checked):
    
    Installed packages to be REMOVED:
    	isc-dhcp43-server-4.3.6P1_1
    	isc-dhcp43-relay-4.3.6P1_1
    	isc-dhcp43-client-4.3.6P1
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    	isc-dhcp44-server: 4.4.1_3 [pfSense]
    	isc-dhcp44-relay: 4.4.1 [pfSense]
    	isc-dhcp44-client: 4.4.1 [pfSense]
    
    Installed packages to be UPGRADED:
    	libnghttp2: 1.32.0 -> 1.33.0 [pfSense]
    	libevent: 2.1.8_1 -> 2.1.8_2 [pfSense]
    	glib: 2.50.3_4,1 -> 2.56.1_1,1 [pfSense]
    	expat: 2.2.5 -> 2.2.6_1 [pfSense]
    	unbound: 1.7.3 -> 1.8.0 [pfSense]
    	py27-setuptools: 39.2.0 -> 40.0.0 [pfSense]
    	oniguruma: 6.8.1 -> 6.9.0 [pfSense]
    	sqlite3: 3.24.0_1 -> 3.25.1 [pfSense]
    	php72-pear-Net_SMTP: 1.8.0 -> 1.8.1 [pfSense]
    	liblz4: 1.8.2,1 -> 1.8.3,1 [pfSense]
    	json-c: 0.13 -> 0.13.1 [pfSense]
    	wpa_supplicant: 2.6_2 -> 2.6_3 [pfSense]
    	smartmontools: 6.6_1 -> 6.6_2 [pfSense]
    	relayd: 5.5.20140810_2 -> 5.5.20140810_3 [pfSense]
    	php72-pear-XML_RPC2: 1.1.3_1 -> 1.1.4 [pfSense]
    	pfSense-rc: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	openvpn: 2.4.6_1 -> 2.4.6_3 [pfSense]
    	nginx: 1.14.0_6,2 -> 1.14.0_12,2 [pfSense]
    	links: 2.16,1 -> 2.16_1,1 [pfSense]
    	dhcp6: 20080615.2 -> 20080615.2_2 [pfSense]
    	bind-tools: 9.12.2P1 -> 9.12.2P2 [pfSense]
    	pfSense-u-boot-ufw: 2.4.5.a.20181008.0501 -> 20180905 [pfSense]
    	pfSense-kernel-pfSense-uFW: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense-default-config-serial: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense-base: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    	pfSense: 2.4.5.a.20181007.1230 -> 2.4.5.a.20181015.0836 [pfSense]
    
    Installed packages to be REINSTALLED:
    	strongswan-5.7.1 [pfSense] (needed shared library changed)
    
    Number of packages to be removed: 3
    Number of packages to be installed: 4
    Number of packages to be upgraded: 26
    Number of packages to be reinstalled: 1
    
    The process will require 5 MiB more space.
    >>> Upgrading pfSense-rc... 
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-rc: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-rc from 2.4.5.a.20181008.0501 to 2.4.5.a.20181015.0747...
    [1/1] Extracting pfSense-rc-2.4.5.a.20181015.0747: ...... done
    >>> Upgrading pfSense kernel... 
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-kernel-pfSense-uFW: 2.4.5.a.20181008.0501 -> 2.4.5.a.20181015.0747 [pfSense-core]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-kernel-pfSense-uFW from 2.4.5.a.20181008.0501 to 2.4.5.a.20181015.0747...
    [1/1] Extracting pfSense-kernel-pfSense-uFW-2.4.5.a.20181015.0747: .......... done
    ===> Keeping a copy of current kernel in /boot/kernel.old
    ===> Updating /boot/loader.rc.local
    >>> Upgrading pfSense u-boot... 
    Checking integrity... done (0 conflicting)
    The following 2 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    
    Installed packages to be UPGRADED:
    	pfSense-u-boot-ufw: 2.4.5.a.20181008.0501 -> 20180905 [pfSense]
    
    Number of packages to be installed: 1
    Number of packages to be upgraded: 1
    [1/2] Installing pfSense-u-boot-env-20180904...
    [1/2] Extracting pfSense-u-boot-env-20180904: ....... done
    [2/2] Upgrading pfSense-u-boot-ufw from 2.4.5.a.20181008.0501 to 20180905...
    [2/2] Extracting pfSense-u-boot-ufw-20180905: ...... done
    >>> Removing unnecessary packages... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    Success
    

  • Rebel Alliance Developer Netgate

    The CCCCCCC text is what the SG-1000 prints when it can't find a proper boot environment, it's trying to trigger a serial transfer of u-boot. You might need to install fresh from a recovery image on there. Worst case, you might need to put the recovery image on an SD card and boot from that.



  • @jimp That's what I'm working on right now as it refuses to boot from USB and I am just finishing up a mSD reinstall which is working. What would have caused the uFW to be backported or am I reading it incorrectly?

    Installed packages to be UPGRADED:
    	pfSense-u-boot-ufw: 2.4.5.a.20181008.0501 -> 20180905 [pfSense]
    

  • Rebel Alliance Developer Netgate

    The version number scheme changed on that package but I'm not sure why it would have gone backward on the date when doing so. I've raised the issue internally to see if the devs working in that area have any input.



  • @jimp I have confirmed an issue with upgrading. Again, it had changed the uFW to the above one when changing to the dev builds.

    >>> 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.
    >>> Removing vital flag from lang/php72... 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 (32 candidates): .......... done
    Processing candidates (32 candidates): .......... done
    The following 35 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    	isc-dhcp44-server: 4.4.1_3 [pfSense]
    	isc-dhcp44-relay: 4.4.1 [pfSense]
    	isc-dhcp44-client: 4.4.1 [pfSense]
    
    Installed packages to be UPGRADED:
    	wpa_supplicant: 2.6_2 -> 2.6_3 [pfSense]
    	unbound: 1.7.3 -> 1.8.0 [pfSense]
    	strongswan: 5.6.3 -> 5.7.1 [pfSense]
    	sqlite3: 3.24.0_1 -> 3.25.1 [pfSense]
    	smartmontools: 6.6_1 -> 6.6_2 [pfSense]
    	relayd: 5.5.20140810_2 -> 5.5.20140810_3 [pfSense]
    	py27-setuptools: 39.2.0 -> 40.0.0 [pfSense]
    	php72-pear-XML_RPC2: 1.1.3_1 -> 1.1.4 [pfSense]
    	php72-pear-Net_SMTP: 1.8.0 -> 1.8.1 [pfSense]
    	pfSense-u-boot-ufw: 2.4.4 -> 20180905 [pfSense]
    	pfSense-rc: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense-kernel-pfSense-uFW: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense-default-config-serial: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense-base: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense: 2.4.4 -> 2.4.5.a.20181015.1338 [pfSense]
    	openvpn: 2.4.6_1 -> 2.4.6_3 [pfSense]
    	oniguruma: 6.8.1 -> 6.9.0 [pfSense]
    	ntp: 4.2.8p12 -> 4.2.8p12_3 [pfSense]
    	nginx: 1.14.0_6,2 -> 1.14.0_12,2 [pfSense]
    	mpd5: 5.8_7 -> 5.8_8 [pfSense]
    	links: 2.16,1 -> 2.16_1,1 [pfSense]
    	libnghttp2: 1.32.0 -> 1.33.0 [pfSense]
    	liblz4: 1.8.2,1 -> 1.8.3,1 [pfSense]
    	libevent: 2.1.8_1 -> 2.1.8_2 [pfSense]
    	libargon2: 20171227 -> 20171227_1 [pfSense]
    	json-c: 0.13 -> 0.13.1 [pfSense]
    	igmpproxy: 0.2.1,1 -> 0.2.1_1,1 [pfSense]
    	glib: 2.50.3_4,1 -> 2.56.1_1,1 [pfSense]
    	expat: 2.2.5 -> 2.2.6_1 [pfSense]
    	dhcp6: 20080615.2 -> 20080615.2_2 [pfSense]
    	bind-tools: 9.12.2P1 -> 9.12.2P2 [pfSense]
    
    Number of packages to be installed: 4
    Number of packages to be upgraded: 31
    
    The process will require 11 MiB more space.
    54 MiB to be downloaded.
    [1/35] Fetching wpa_supplicant-2.6_3.txz: .......... done
    [2/35] Fetching unbound-1.8.0.txz: .......... done
    [3/35] Fetching strongswan-5.7.1.txz: .......... done
    [4/35] Fetching sqlite3-3.25.1.txz: .......... done
    [5/35] Fetching smartmontools-6.6_2.txz: .......... done
    [6/35] Fetching relayd-5.5.20140810_3.txz: .......... done
    [7/35] Fetching py27-setuptools-40.0.0.txz: .......... done
    [8/35] Fetching php72-pear-XML_RPC2-1.1.4.txz: ........ done
    [9/35] Fetching php72-pear-Net_SMTP-1.8.1.txz: .. done
    [10/35] Fetching pfSense-u-boot-ufw-20180905.txz: .......... done
    [11/35] Fetching pfSense-rc-2.4.5.a.20181015.1355.txz: .. done
    [12/35] Fetching pfSense-kernel-pfSense-uFW-2.4.5.a.20181015.1355.txz: .......... done
    [13/35] Fetching pfSense-default-config-serial-2.4.5.a.20181015.1355.txz: . done
    [14/35] Fetching pfSense-base-2.4.5.a.20181015.1355.txz: .......... done
    [15/35] Fetching pfSense-2.4.5.a.20181015.1338.txz: . done
    [16/35] Fetching openvpn-2.4.6_3.txz: .......... done
    [17/35] Fetching oniguruma-6.9.0.txz: .......... done
    [18/35] Fetching ntp-4.2.8p12_3.txz: .......... done
    [19/35] Fetching nginx-1.14.0_12,2.txz: .......... done
    [20/35] Fetching mpd5-5.8_8.txz: .......... done
    [21/35] Fetching links-2.16_1,1.txz: .......... done
    [22/35] Fetching libnghttp2-1.33.0.txz: .......... done
    [23/35] Fetching liblz4-1.8.3,1.txz: .......... done
    [24/35] Fetching libevent-2.1.8_2.txz: .......... done
    [25/35] Fetching libargon2-20171227_1.txz: ........ done
    [26/35] Fetching json-c-0.13.1.txz: ....... done
    [27/35] Fetching igmpproxy-0.2.1_1,1.txz: ... done
    [28/35] Fetching glib-2.56.1_1,1.txz: .......... done
    [29/35] Fetching expat-2.2.6_1.txz: .......... done
    [30/35] Fetching dhcp6-20080615.2_2.txz: .......... done
    [31/35] Fetching bind-tools-9.12.2P2.txz: .......... done
    [32/35] Fetching pfSense-u-boot-env-20180904.txz: ... done
    [33/35] Fetching isc-dhcp44-server-4.4.1_3.txz: .......... done
    [34/35] Fetching isc-dhcp44-relay-4.4.1.txz: .......... done
    [35/35] Fetching isc-dhcp44-client-4.4.1.txz: .......... done
    Checking integrity... done (3 conflicting)
      - isc-dhcp44-server-4.4.1_3 [pfSense] conflicts with isc-dhcp43-server-4.3.6P1_1 [installed] on /usr/local/etc/dhcpd.conf.sample
      - isc-dhcp44-relay-4.4.1 [pfSense] conflicts with isc-dhcp43-relay-4.3.6P1_1 [installed] on /usr/local/etc/rc.d/isc-dhcrelay6
      - isc-dhcp44-client-4.4.1 [pfSense] conflicts with isc-dhcp43-client-4.3.6P1 [installed] on /usr/local/sbin/dhclient
    Checking integrity... done (0 conflicting)
    Conflicts with the existing packages have been found.
    One more solver iteration is needed to resolve them.
    The following 38 package(s) will be affected (of 0 checked):
    
    Installed packages to be REMOVED:
    	isc-dhcp43-server-4.3.6P1_1
    	isc-dhcp43-relay-4.3.6P1_1
    	isc-dhcp43-client-4.3.6P1
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    	isc-dhcp44-server: 4.4.1_3 [pfSense]
    	isc-dhcp44-relay: 4.4.1 [pfSense]
    	isc-dhcp44-client: 4.4.1 [pfSense]
    
    Installed packages to be UPGRADED:
    	libargon2: 20171227 -> 20171227_1 [pfSense]
    	libnghttp2: 1.32.0 -> 1.33.0 [pfSense]
    	libevent: 2.1.8_1 -> 2.1.8_2 [pfSense]
    	glib: 2.50.3_4,1 -> 2.56.1_1,1 [pfSense]
    	expat: 2.2.5 -> 2.2.6_1 [pfSense]
    	unbound: 1.7.3 -> 1.8.0 [pfSense]
    	py27-setuptools: 39.2.0 -> 40.0.0 [pfSense]
    	oniguruma: 6.8.1 -> 6.9.0 [pfSense]
    	strongswan: 5.6.3 -> 5.7.1 [pfSense]
    	sqlite3: 3.24.0_1 -> 3.25.1 [pfSense]
    	php72-pear-Net_SMTP: 1.8.0 -> 1.8.1 [pfSense]
    	liblz4: 1.8.2,1 -> 1.8.3,1 [pfSense]
    	json-c: 0.13 -> 0.13.1 [pfSense]
    	wpa_supplicant: 2.6_2 -> 2.6_3 [pfSense]
    	smartmontools: 6.6_1 -> 6.6_2 [pfSense]
    	relayd: 5.5.20140810_2 -> 5.5.20140810_3 [pfSense]
    	php72-pear-XML_RPC2: 1.1.3_1 -> 1.1.4 [pfSense]
    	pfSense-rc: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	openvpn: 2.4.6_1 -> 2.4.6_3 [pfSense]
    	ntp: 4.2.8p12 -> 4.2.8p12_3 [pfSense]
    	nginx: 1.14.0_6,2 -> 1.14.0_12,2 [pfSense]
    	mpd5: 5.8_7 -> 5.8_8 [pfSense]
    	links: 2.16,1 -> 2.16_1,1 [pfSense]
    	igmpproxy: 0.2.1,1 -> 0.2.1_1,1 [pfSense]
    	dhcp6: 20080615.2 -> 20080615.2_2 [pfSense]
    	bind-tools: 9.12.2P1 -> 9.12.2P2 [pfSense]
    	pfSense-u-boot-ufw: 2.4.4 -> 20180905 [pfSense]
    	pfSense-kernel-pfSense-uFW: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense-default-config-serial: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense-base: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    	pfSense: 2.4.4 -> 2.4.5.a.20181015.1338 [pfSense]
    
    Number of packages to be removed: 3
    Number of packages to be installed: 4
    Number of packages to be upgraded: 31
    
    The process will require 4 MiB more space.
    >>> Upgrading pfSense-rc... 
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-rc: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-rc from 2.4.4 to 2.4.5.a.20181015.1355...
    [1/1] Extracting pfSense-rc-2.4.5.a.20181015.1355: ...... done
    >>> Upgrading pfSense kernel... 
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-kernel-pfSense-uFW: 2.4.4 -> 2.4.5.a.20181015.1355 [pfSense-core]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-kernel-pfSense-uFW from 2.4.4 to 2.4.5.a.20181015.1355...
    [1/1] Extracting pfSense-kernel-pfSense-uFW-2.4.5.a.20181015.1355: .......... done
    ===> Keeping a copy of current kernel in /boot/kernel.old
    ===> Updating /boot/loader.rc.local
    >>> Upgrading pfSense u-boot... 
    Checking integrity... done (0 conflicting)
    The following 2 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-u-boot-env: 20180904 [pfSense]
    
    Installed packages to be UPGRADED:
    	pfSense-u-boot-ufw: 2.4.4 -> 20180905 [pfSense]
    
    Number of packages to be installed: 1
    Number of packages to be upgraded: 1
    [1/2] Installing pfSense-u-boot-env-20180904...
    [1/2] Extracting pfSense-u-boot-env-20180904: ....... done
    [2/2] Upgrading pfSense-u-boot-ufw from 2.4.4 to 20180905...
    [2/2] Extracting pfSense-u-boot-ufw-20180905: ...... done
    >>> Removing unnecessary packages... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    Success
    
    

  • Rebel Alliance Developer Netgate

    We've been able to replicate this internally now and we're looking into it. Thanks for reporting the issue, we'll have it fixed ASAP.



  • @jimp Do you have any bug tracking info for this issue?


  • Rebel Alliance Developer Netgate

    No, it's in our internal tracking system since it only affects our hardware. We're still working on it but there is another more time-sensitive ahead of it.



  • @jimp Can you let me know when this issue becomes fixed so I can get back to finding bugs 😉


  • Rebel Alliance Developer Netgate

    Still working on it. Waiting on the latest snapshot to come out today to test the recovery image and then to test upgrades as well. Hopefully should be OK today.