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

    2.3.1_1 Update completly borked

    Problems Installing or Upgrading pfSense Software
    6
    12
    3.3k
    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.
    • T
      tarakesh
      last edited by

      So this is the second update in a row that complety killed my pfsense box.

      First 2.3.1 killed the slice to a point where it could not even find the kernel and rebooted without any error message.

      2.3.1_1 now kills the slice again (see attachment)

      Tech specs see Signature.

      Full update log:

      >>> 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.
      **** WARNING ****
      Duplicate slice required!!
      
      Before starting the upgrade process, the currently mounted nanobsd partition
      needs to be cloned to the secondary partition, where the update will happen
      
      After installation a reboot will be required to switch partition.
      
      >>> Cleaning secondary partition... done.
      >>> Duplicating current slice... done.
      >>> Restoring slice label... done.
      >>> Testing duplicated partition integrity... done.
      >>> Mounting second partition to run upgrade... 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 (61 candidates): .......... done
      Processing candidates (61 candidates): .......... done
      The following 63 package(s) will be affected (of 0 checked):
      
      New packages to be INSTALLED:
      	uclcmd: 0.1 [pfSense]
      	libucl: 0.8.0 [pfSense]
      
      Installed packages to be UPGRADED:
      	unbound: 1.5.5 -> 1.5.8 [pfSense]
      	sqlite3: 3.9.2 -> 3.11.1 [pfSense]
      	smartmontools: 6.4_1 -> 6.4_2 [pfSense]
      	rate: 0.9 -> 0.9_1 [pfSense]
      	python27: 2.7.11_1 -> 2.7.11_2 [pfSense]
      	php56-zlib: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xmlwriter: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xmlreader: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xml: 5.6.20 -> 5.6.21 [pfSense]
      	php56-tokenizer: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvshm: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvsem: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvmsg: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sqlite3: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sockets: 5.6.20 -> 5.6.21 [pfSense]
      	php56-simplexml: 5.6.20 -> 5.6.21 [pfSense]
      	php56-shmop: 5.6.20 -> 5.6.21 [pfSense]
      	php56-session: 5.6.20 -> 5.6.21 [pfSense]
      	php56-readline: 5.6.20 -> 5.6.21 [pfSense]
      	php56-posix: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pdo_sqlite: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pdo: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pcntl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-openssl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-opcache: 5.6.20 -> 5.6.21 [pfSense]
      	php56-mcrypt: 5.6.20 -> 5.6.21 [pfSense]
      	php56-mbstring: 5.6.20 -> 5.6.21 [pfSense]
      	php56-ldap: 5.6.20 -> 5.6.21 [pfSense]
      	php56-json: 5.6.20 -> 5.6.21 [pfSense]
      	php56-hash: 5.6.20 -> 5.6.21 [pfSense]
      	php56-gettext: 5.6.20 -> 5.6.21 [pfSense]
      	php56-filter: 5.6.20 -> 5.6.21 [pfSense]
      	php56-dom: 5.6.20 -> 5.6.21 [pfSense]
      	php56-curl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-ctype: 5.6.20 -> 5.6.21 [pfSense]
      	php56-bz2: 5.6.20 -> 5.6.21 [pfSense]
      	php56-bcmath: 5.6.20 -> 5.6.21 [pfSense]
      	php56: 5.6.20 -> 5.6.21 [pfSense]
      	pfSense-rc: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-kernel-pfSense: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-default-config: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-base-nanobsd: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-Status_Monitoring: 1.0_1 -> 1.3_1 [pfSense]
      	pfSense: 2.3_1 -> 2.3.1_1 [pfSense]
      	perl5: 5.20.3_8 -> 5.20.3_12 [pfSense]
      	pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense]
      	openvpn: 2.3.9 -> 2.3.11 [pfSense]
      	nettle: 2.7.1 -> 3.2 [pfSense]
      	libzmq4: 4.1.3 -> 4.1.4_1 [pfSense]
      	libsodium: 1.0.3 -> 1.0.8 [pfSense]
      	libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense]
      	gmp: 5.1.3_2 -> 5.1.3_3 [pfSense]
      	glib: 2.44.1_3 -> 2.46.2 [pfSense]
      	gettext-runtime: 0.19.6 -> 0.19.7 [pfSense]
      	filterlog: 0.1_1 -> 0.1_2 [pfSense]
      	dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense]
      	curl: 7.47.0 -> 7.48.0_1 [pfSense]
      	cpdup: 1.17_2 -> 1.18 [pfSense]
      	bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense]
      
      Installed packages to be REINSTALLED:
      	rrdtool-1.5.5_1 [pfSense] (options changed)
      	nginx-1.8.1,2 [pfSense] (options changed)
      
      74 MiB to be downloaded.
      Fetching unbound-1.5.8.txz: .......... done
      Fetching sqlite3-3.11.1.txz: .......... done
      Fetching smartmontools-6.4_2.txz: .......... done
      Fetching rrdtool-1.5.5_1.txz: .......... done
      Fetching rate-0.9_1.txz: ..... done
      Fetching python27-2.7.11_2.txz: .......... done
      Fetching php56-zlib-5.6.21.txz: .. done
      Fetching php56-xmlwriter-5.6.21.txz: .. done
      Fetching php56-xmlreader-5.6.21.txz: .. done
      Fetching php56-xml-5.6.21.txz: .. done
      Fetching php56-tokenizer-5.6.21.txz: . done
      Fetching php56-sysvshm-5.6.21.txz: . done
      Fetching php56-sysvsem-5.6.21.txz: . done
      Fetching php56-sysvmsg-5.6.21.txz: . done
      Fetching php56-sqlite3-5.6.21.txz: .. done
      Fetching php56-sockets-5.6.21.txz: .... done
      Fetching php56-simplexml-5.6.21.txz: ... done
      Fetching php56-shmop-5.6.21.txz: . done
      Fetching php56-session-5.6.21.txz: ... done
      Fetching php56-readline-5.6.21.txz: .. done
      Fetching php56-posix-5.6.21.txz: .. done
      Fetching php56-pdo_sqlite-5.6.21.txz: .. done
      Fetching php56-pdo-5.6.21.txz: ..... done
      Fetching php56-pcntl-5.6.21.txz: .. done
      Fetching php56-openssl-5.6.21.txz: ..... done
      Fetching php56-opcache-5.6.21.txz: ....... done
      Fetching php56-mcrypt-5.6.21.txz: .. done
      Fetching php56-mbstring-5.6.21.txz: .......... done
      Fetching php56-ldap-5.6.21.txz: .. done
      Fetching php56-json-5.6.21.txz: .. done
      Fetching php56-hash-5.6.21.txz: .......... done
      Fetching php56-gettext-5.6.21.txz: . done
      Fetching php56-filter-5.6.21.txz: .. done
      Fetching php56-dom-5.6.21.txz: ...... done
      Fetching php56-curl-5.6.21.txz: ... done
      Fetching php56-ctype-5.6.21.txz: . done
      Fetching php56-bz2-5.6.21.txz: .. done
      Fetching php56-bcmath-5.6.21.txz: .. done
      Fetching php56-5.6.21.txz: .......... done
      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-nanobsd-2.3.1_1.txz: .......... done
      Fetching pfSense-Status_Monitoring-1.3_1.txz: .. done
      Fetching pfSense-2.3.1_1.txz: . done
      Fetching perl5-5.20.3_12.txz: .......... done
      Fetching pecl-zmq-1.1.3_1.txz: ... done
      Fetching openvpn-2.3.11.txz: .......... done
      Fetching nginx-1.8.1,2.txz: .......... done
      Fetching nettle-3.2.txz: .......... done
      Fetching libzmq4-4.1.4_1.txz: .......... done
      Fetching libsodium-1.0.8.txz: .......... done
      Fetching libedit-3.1.20150325_2.txz: .......... done
      Fetching gmp-5.1.3_3.txz: .......... done
      Fetching glib-2.46.2.txz: .......... done
      Fetching gettext-runtime-0.19.7.txz: .......... done
      Fetching filterlog-0.1_2.txz: . done
      Fetching dnsmasq-devel-2.76.0test12.txz: .......... done
      Fetching curl-7.48.0_1.txz: .......... done
      Fetching cpdup-1.18.txz: ... done
      Fetching bsnmp-ucd-0.4.2.txz: .. done
      Fetching uclcmd-0.1.txz: .. done
      Fetching libucl-0.8.0.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 -> 2.3.1_1 [pfSense-core]
      	pfSense-rc: 2.3 -> 2.3.1_1 [pfSense-core]
      [1/2] Upgrading pfSense-rc from 2.3 to 2.3.1_1...
      [1/2] Extracting pfSense-rc-2.3.1_1: .... done
      [2/2] Upgrading pfSense-kernel-pfSense from 2.3 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
      >>> Upgrading necessary 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 (59 candidates): .......... done
      Processing candidates (59 candidates): .......... done
      Checking integrity... done (0 conflicting)
      The following 61 package(s) will be affected (of 0 checked):
      
      New packages to be INSTALLED:
      	uclcmd: 0.1 [pfSense]
      	libucl: 0.8.0 [pfSense]
      
      Installed packages to be UPGRADED:
      	unbound: 1.5.5 -> 1.5.8 [pfSense]
      	sqlite3: 3.9.2 -> 3.11.1 [pfSense]
      	smartmontools: 6.4_1 -> 6.4_2 [pfSense]
      	rate: 0.9 -> 0.9_1 [pfSense]
      	python27: 2.7.11_1 -> 2.7.11_2 [pfSense]
      	php56-zlib: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xmlwriter: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xmlreader: 5.6.20 -> 5.6.21 [pfSense]
      	php56-xml: 5.6.20 -> 5.6.21 [pfSense]
      	php56-tokenizer: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvshm: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvsem: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sysvmsg: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sqlite3: 5.6.20 -> 5.6.21 [pfSense]
      	php56-sockets: 5.6.20 -> 5.6.21 [pfSense]
      	php56-simplexml: 5.6.20 -> 5.6.21 [pfSense]
      	php56-shmop: 5.6.20 -> 5.6.21 [pfSense]
      	php56-session: 5.6.20 -> 5.6.21 [pfSense]
      	php56-readline: 5.6.20 -> 5.6.21 [pfSense]
      	php56-posix: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pdo_sqlite: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pdo: 5.6.20 -> 5.6.21 [pfSense]
      	php56-pcntl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-openssl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-opcache: 5.6.20 -> 5.6.21 [pfSense]
      	php56-mcrypt: 5.6.20 -> 5.6.21 [pfSense]
      	php56-mbstring: 5.6.20 -> 5.6.21 [pfSense]
      	php56-ldap: 5.6.20 -> 5.6.21 [pfSense]
      	php56-json: 5.6.20 -> 5.6.21 [pfSense]
      	php56-hash: 5.6.20 -> 5.6.21 [pfSense]
      	php56-gettext: 5.6.20 -> 5.6.21 [pfSense]
      	php56-filter: 5.6.20 -> 5.6.21 [pfSense]
      	php56-dom: 5.6.20 -> 5.6.21 [pfSense]
      	php56-curl: 5.6.20 -> 5.6.21 [pfSense]
      	php56-ctype: 5.6.20 -> 5.6.21 [pfSense]
      	php56-bz2: 5.6.20 -> 5.6.21 [pfSense]
      	php56-bcmath: 5.6.20 -> 5.6.21 [pfSense]
      	php56: 5.6.20 -> 5.6.21 [pfSense]
      	pfSense-default-config: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-base-nanobsd: 2.3 -> 2.3.1_1 [pfSense-core]
      	pfSense-Status_Monitoring: 1.0_1 -> 1.3_1 [pfSense]
      	pfSense: 2.3_1 -> 2.3.1_1 [pfSense]
      	perl5: 5.20.3_8 -> 5.20.3_12 [pfSense]
      	pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense]
      	openvpn: 2.3.9 -> 2.3.11 [pfSense]
      	nettle: 2.7.1 -> 3.2 [pfSense]
      	libzmq4: 4.1.3 -> 4.1.4_1 [pfSense]
      	libsodium: 1.0.3 -> 1.0.8 [pfSense]
      	libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense]
      	gmp: 5.1.3_2 -> 5.1.3_3 [pfSense]
      	glib: 2.44.1_3 -> 2.46.2 [pfSense]
      	gettext-runtime: 0.19.6 -> 0.19.7 [pfSense]
      	filterlog: 0.1_1 -> 0.1_2 [pfSense]
      	dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense]
      	curl: 7.47.0 -> 7.48.0_1 [pfSense]
      	cpdup: 1.17_2 -> 1.18 [pfSense]
      	bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense]
      
      Installed packages to be REINSTALLED:
      	rrdtool-1.5.5_1 [pfSense] (options changed)
      	nginx-1.8.1,2 [pfSense] (options changed)
      [1/61] Upgrading gettext-runtime from 0.19.6 to 0.19.7...
      [1/61] Extracting gettext-runtime-0.19.7: .......... done
      [2/61] Upgrading python27 from 2.7.11_1 to 2.7.11_2...
      [2/61] Extracting python27-2.7.11_2: .......... done
      [3/61] Upgrading perl5 from 5.20.3_8 to 5.20.3_12...
      [3/61] Extracting perl5-5.20.3_12: .......... done
      makewhatis: not found
      makewhatis: not found
      pkg: POST-INSTALL script failed
      [4/61] Upgrading glib from 2.44.1_3 to 2.46.2...
      [4/61] Extracting glib-2.46.2: .......... done
      No schema files found: doing nothing.
      [5/61] Upgrading unbound from 1.5.5 to 1.5.8...
      ==> You should manually remove the "unbound" user. 
      ===> Creating users and/or groups.
      Using existing group 'unbound'.
      Using existing user 'unbound'.
      [5/61] Extracting unbound-1.5.8: .......... done
      [6/61] Reinstalling rrdtool-1.5.5_1...
      [6/61] Extracting rrdtool-1.5.5_1: .......... done
      [7/61] Upgrading php56 from 5.6.20 to 5.6.21...
      [7/61] Extracting php56-5.6.21: .......... done
      [8/61] Upgrading libsodium from 1.0.3 to 1.0.8...
      [8/61] Extracting libsodium-1.0.8: .......... done
      [9/61] Upgrading gmp from 5.1.3_2 to 5.1.3_3...
      [9/61] Extracting gmp-5.1.3_3: .......... done
      [10/61] Upgrading curl from 7.47.0 to 7.48.0_1...
      [10/61] Extracting curl-7.48.0_1: .......... done
      [11/61] Upgrading sqlite3 from 3.9.2 to 3.11.1...
      [11/61] Extracting sqlite3-3.11.1: .......... done
      [12/61] Upgrading php56-session from 5.6.20 to 5.6.21...
      [12/61] Extracting php56-session-5.6.21: ......... done
      [13/61] Upgrading php56-pdo from 5.6.20 to 5.6.21...
      [13/61] Extracting php56-pdo-5.6.21: ......... done
      [14/61] Upgrading php56-dom from 5.6.20 to 5.6.21...
      [14/61] Extracting php56-dom-5.6.21: .......... done
      [15/61] Upgrading nettle from 2.7.1 to 3.2...
      [15/61] Extracting nettle-3.2: .......... done
      [16/61] Upgrading libzmq4 from 4.1.3 to 4.1.4_1...
      [16/61] Extracting libzmq4-4.1.4_1: .......... done
      [17/61] Upgrading libedit from 3.1.20150325_1 to 3.1.20150325_2...
      [17/61] Extracting libedit-3.1.20150325_2: .......... done
      [18/61] Installing libucl-0.8.0...
      [18/61] Extracting libucl-0.8.0: .......... done
      [19/61] Upgrading smartmontools from 6.4_1 to 6.4_2...
      [19/61] Extracting smartmontools-6.4_2: .......... done
      [20/61] Upgrading rate from 0.9 to 0.9_1...
      [20/61] Extracting rate-0.9_1: ..... done
      [21/61] Upgrading php56-zlib from 5.6.20 to 5.6.21...
      [21/61] Extracting php56-zlib-5.6.21: ...... done
      [22/61] Upgrading php56-xmlwriter from 5.6.20 to 5.6.21...
      [22/61] Extracting php56-xmlwriter-5.6.21: ...... done
      [23/61] Upgrading php56-xmlreader from 5.6.20 to 5.6.21...
      [23/61] Extracting php56-xmlreader-5.6.21: ...... done
      [24/61] Upgrading php56-xml from 5.6.20 to 5.6.21...
      [24/61] Extracting php56-xml-5.6.21: ....... done
      [25/61] Upgrading php56-tokenizer from 5.6.20 to 5.6.21...
      [25/61] Extracting php56-tokenizer-5.6.21: ...... done
      [26/61] Upgrading php56-sysvshm from 5.6.20 to 5.6.21...
      [26/61] Extracting php56-sysvshm-5.6.21: ...... done
      [27/61] Upgrading php56-sysvsem from 5.6.20 to 5.6.21...
      [27/61] Extracting php56-sysvsem-5.6.21: ...... done
      [28/61] Upgrading php56-sysvmsg from 5.6.20 to 5.6.21...
      [28/61] Extracting php56-sysvmsg-5.6.21: ...... done
      [29/61] Upgrading php56-sqlite3 from 5.6.20 to 5.6.21...
      [29/61] Extracting php56-sqlite3-5.6.21: ....... done
      [30/61] Upgrading php56-sockets from 5.6.20 to 5.6.21...
      [30/61] Extracting php56-sockets-5.6.21: .......... done
      [31/61] Upgrading php56-simplexml from 5.6.20 to 5.6.21...
      [31/61] Extracting php56-simplexml-5.6.21: ........ done
      [32/61] Upgrading php56-shmop from 5.6.20 to 5.6.21...
      [32/61] Extracting php56-shmop-5.6.21: ...... done
      [33/61] Upgrading php56-readline from 5.6.20 to 5.6.21...
      [33/61] Extracting php56-readline-5.6.21: ....... done
      [34/61] Upgrading php56-posix from 5.6.20 to 5.6.21...
      [34/61] Extracting php56-posix-5.6.21: ...... done
      [35/61] Upgrading php56-pdo_sqlite from 5.6.20 to 5.6.21...
      [35/61] Extracting php56-pdo_sqlite-5.6.21: ....... done
      [36/61] Upgrading php56-pcntl from 5.6.20 to 5.6.21...
      [36/61] Extracting php56-pcntl-5.6.21: ....... done
      [37/61] Upgrading php56-openssl from 5.6.20 to 5.6.21...
      [37/61] Extracting php56-openssl-5.6.21: ...... done
      [38/61] Upgrading php56-opcache from 5.6.20 to 5.6.21...
      [38/61] Extracting php56-opcache-5.6.21: .......... done
      [39/61] Upgrading php56-mcrypt from 5.6.20 to 5.6.21...
      [39/61] Extracting php56-mcrypt-5.6.21: ....... done
      [40/61] Upgrading php56-mbstring from 5.6.20 to 5.6.21...
      [40/61] Extracting php56-mbstring-5.6.21: .......... done
      [41/61] Upgrading php56-ldap from 5.6.20 to 5.6.21...
      [41/61] Extracting php56-ldap-5.6.21: ...... done
      [42/61] Upgrading php56-json from 5.6.20 to 5.6.21...
      [42/61] Extracting php56-json-5.6.21: ....... done
      [43/61] Upgrading php56-hash from 5.6.20 to 5.6.21...
      [43/61] Extracting php56-hash-5.6.21: .......... done
      [44/61] Upgrading php56-gettext from 5.6.20 to 5.6.21...
      [44/61] Extracting php56-gettext-5.6.21: ...... done
      [45/61] Upgrading php56-filter from 5.6.20 to 5.6.21...
      [45/61] Extracting php56-filter-5.6.21: ....... done
      [46/61] Upgrading php56-curl from 5.6.20 to 5.6.21...
      [46/61] Extracting php56-curl-5.6.21: ...... done
      [47/61] Upgrading php56-ctype from 5.6.20 to 5.6.21...
      [47/61] Extracting php56-ctype-5.6.21: ...... done
      [48/61] Upgrading php56-bz2 from 5.6.20 to 5.6.21...
      [48/61] Extracting php56-bz2-5.6.21: ...... done
      [49/61] Upgrading php56-bcmath from 5.6.20 to 5.6.21...
      [49/61] Extracting php56-bcmath-5.6.21: .......... done
      [50/61] Upgrading pfSense-Status_Monitoring from 1.0_1 to 1.3_1...
      [50/61] Extracting pfSense-Status_Monitoring-1.3_1: ....... done
      [51/61] Upgrading pecl-zmq from 1.1.3 to 1.1.3_1...
      [51/61] Extracting pecl-zmq-1.1.3_1: ........ done
      [52/61] Upgrading openvpn from 2.3.9 to 2.3.11...
      [52/61] Extracting openvpn-2.3.11: .......... done
      [53/61] Reinstalling nginx-1.8.1,2...
      ===> Creating users and/or groups.
      Using existing group 'www'.
      Using existing user 'www'.
      [53/61] Extracting nginx-1.8.1,2: .......... done
      [54/61] Upgrading filterlog from 0.1_1 to 0.1_2...
      [54/61] Extracting filterlog-0.1_2: . done
      [55/61] Upgrading dnsmasq-devel from 2.76.0test8 to 2.76.0test12...
      [55/61] Extracting dnsmasq-devel-2.76.0test12: .......... done
      [56/61] Upgrading cpdup from 1.17_2 to 1.18...
      [56/61] Extracting cpdup-1.18: .. done
      [57/61] Upgrading bsnmp-ucd from 0.4.1 to 0.4.2...
      [57/61] Extracting bsnmp-ucd-0.4.2: ...... done
      [58/61] Installing uclcmd-0.1...
      [58/61] Extracting uclcmd-0.1: .... done
      [59/61] Upgrading pfSense-default-config from 2.3 to 2.3.1_1...
      [59/61] Extracting pfSense-default-config-2.3.1_1: .... done
      [60/61] Upgrading pfSense-base-nanobsd from 2.3 to 2.3.1_1...
      ===> Keeping a copy of current version mtree
      [60/61] Extracting pfSense-base-nanobsd-2.3.1_1: ..... done
      ===> Removing schg flag from base files
      ===> Extracting new base tarball
      ===> Removing static obsoleted files
      [61/61] Upgrading pfSense from 2.3_1 to 2.3.1_1...
      [61/61] Extracting pfSense-2.3.1_1: .... done
      Message from python27-2.7.11_2:
      ===========================================================================
      
      Note that some standard Python modules are provided as separate ports
      as they require additional dependencies. They are available as:
      
      bsddb           databases/py-bsddb
      gdbm            databases/py-gdbm
      sqlite3         databases/py-sqlite3
      tkinter         x11-toolkits/py-tkinter
      
      ===========================================================================
      Message from perl5-5.20.3_12:
      The /usr/bin/perl symlink has been removed starting with Perl 5.20.
      For shebangs, you should either use:
      
      #!/usr/local/bin/perl
      
      or
      
      #!/usr/bin/env perl
      
      The first one will only work if you have a /usr/local/bin/perl,
      the second will work as long as perl is in PATH.
      Message from smartmontools-6.4_2:
      smartmontools has been installed
      
      To check the status of drives, use the following:
      
      	/usr/local/sbin/smartctl -a /dev/ad0	for first ATA/SATA drive
      	/usr/local/sbin/smartctl -a /dev/da0	for first SCSI drive
      	/usr/local/sbin/smartctl -a /dev/ada0	for first SATA drive
      
      To include drive health information in your daily status reports,
      add a line like the following to /etc/periodic.conf:
      	daily_status_smart_devices="/dev/ad0 /dev/da0"
      substituting the appropriate device names for your SMART-capable disks.
      
      To enable drive monitoring, you can use /usr/local/sbin/smartd.
      A sample configuration file has been installed as 
      /usr/local/etc/smartd.conf.sample
      Copy this file to /usr/local/etc/smartd.conf and edit appropriately
      
      To have smartd start at boot
      	echo 'smartd_enable="YES"' >> /etc/rc.conf
      Message from openvpn-2.3.11:
      ### ------------------------------------------------------------------------
      ###  Edit /etc/rc.conf[.local] to start OpenVPN automatically at system
      ###  startup. See /usr/local/etc/rc.d/openvpn for details.
      ### ------------------------------------------------------------------------
      ###  Connect to VPN server as a client with this command to include
      ###  the client.up/down scripts in the initialization:
      ###  openvpn-client <spec>.ovpn
      ### ------------------------------------------------------------------------
      ###  For compatibility notes when interoperating with older OpenVPN
      ###  versions, please, see <http: openvpn.net="" relnotes.html="">### ------------------------------------------------------------------------
      Message from dnsmasq-devel-2.76.0test12:
      *** To enable dnsmasq, edit /usr/local/etc/dnsmasq.conf and
      *** set dnsmasq_enable="YES" in /etc/rc.conf[.local]
      ***
      *** Further options and actions are documented inside
      *** /usr/local/etc/rc.d/dnsmasq
      >>> Setting secondary partition as active... done.
      Upgrade is complete.  Rebooting in 10 seconds.
      >>> Locking package pfSense-kernel-pfSense... done.
      Success</http:></spec> 
      

      I had NEVER any issues with updating any pfsense box.
      Now you completly screwd 2 updates in a row…
      I would suggest that you guys start doing things right again.

      Sorry for my tone but i am a little pissed at the momemt from resetting to 2.3.0
      IMAG0745.jpg
      IMAG0745.jpg_thumb
      updatelog.txt

      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
      • G
        gerdesj
        last edited by

        I suggest you don't storm in here with a rant.  That is not going to ingratiate you to anyone.  Bear in mind that many, many thousands of pfSense installs and upgrades work flawlessly.  I have personally updated 20 odd so far.

        What the hell does "kill the slice" mean?
        What hardware - bugger your signature: spell it out?
        What version prior to 2.3.1?
        How did you get to 2.3.1 if it was broken on update?

        Calm down and let's see if we can help you.

        Cheers
        Jon

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

          I've just done a 2.3.1 -> 2.3.1_1 update on the router between you and me.

          Earlier tonight (GMT+1) I finally got around to update i386 -> amd64 on a NanoBSD install.  I had previously upgraded 2.3.1 to 2.3.1_1 on i386.

          However the installer is still 2.3.1.  I dumped the config, wrote a new CF card, put it in and booted, messed with VLANs, addresses etc, put the previous config in and restarted it.  Then I ran the upgrade 2.3.1 -> 2.3.1_1.

          I didn't even notice the drop because I was still writing the above comment.

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

            I already said sorry…

            Box is atm at 2.3.0
            2.3.0 -> 2.3.1 did not work
            2.3.0 -> 2.3.1_1 did not work either
            the 2.3.1_1 is the only available update

            Hardware: 2.3-RELEASE (amd64) on Intel D2500CCE Board Intel Atom D2500 DC @1.86GHz, 2GB RAM, 32GB CF Card with NanoBSD (4GB)

            Both (2.3.1 and 2.3.1_1) killed the second slice of the nano bsd installation as the update took place there.

            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
            • PerforadoP
              Perforado Rebel Alliance
              last edited by

              Did you try to save your config reinstall with 2.3.1 and then update to 2.3.1_1?

              Had some troubles here with a 32gb cfcard also (2.3.1-> 2.3.1, but 2.3.1-> 2.3.1_1 worked). 4gb and 8b worked ok.

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

                Looks like the disk itself is not able to be read, or at least the filesystem. Personally I would not trust the card/disk at this point. At a minimum it should have some diagnostics run and a full dd style zero wipe of the entire disk before it's used again.

                The vast majority of unexplained cases such as this – especially with flash media -- end up being failing disks.

                CF is cheap, just get a new one.

                Or use the opportunity to upgrade to a real SSD and ditch NanoBSD as well.

                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
                • w0wW
                  w0w
                  last edited by

                  I have 2500CC and SSD installed, AHCI mode, no problem at all with updates. For me it looks like CF problem as jimp mentioned or some kind of compatibility issue that I have had with an older BIOS version.

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

                    The CF Card is absolutly fine.
                    Clone Slice from running system does not throw any errors.
                    Second slice boots perfect after clone…
                    Only the update does not work ;-)

                    PS: If you wanna let nano bsd die then say so ;)

                    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
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)

                      Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.

                      It's still worth using a fresh CF. And I still wouldn't trust it.

                      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
                      • T
                        tarakesh
                        last edited by

                        @jimp:

                        We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)

                        Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.

                        It's still worth using a fresh CF. And I still wouldn't trust it.

                        No Pun intended here..
                        I have ordered a SSD Yesterday and will reinstall tonight..

                        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
                        • R
                          ricle
                          last edited by

                          @jimp:

                          We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)

                          Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.

                          If nano dies i have to shredder my alix? Or is there a way to use a usb stick?

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

                            @ricle:

                            If nano dies i have to shredder my alix? Or is there a way to use a usb stick?

                            You can keep running whatever the last release is that has NanoBSD. Current plan is to keep maintaining that branch for a while. IIRC when we drop NanoBSD, i386 is also being dropped, so either way the ALIX can't move forward. It's past time to be seeking a replacement for that hardware, it's been EOL for some time now.

                            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
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.