Upgrade to 2.3.4 on Alix



  • My Alix upgrade is in progress, but it takes so long that I will write some progress notes here so others are aware, and come back in an hour or 2 and post the result.

    Old Alix 32-bit nanoBSD systems are not supported on the upcoming 2.4 release. So the 2.3.* release series is their end-of-life. They have CF cards for non-volatile storage. Many of those CF cards are getting old these days and their write performance gets worse over time. For example, my CF card took somewhere around 90 to 120 minutes to do the "duplicate slice" operation and then download and write all the package components to be installed.

    Now it has rebooted from the duplicated slice and is slowly applying all the package upgrades to the running system. Note that the boot process starts up the router/firewall functionality (with the old version binaries/code) and then starts running the package upgrade/installs. So I am able to connect to the webGUI and internet during this time. But the webGUI still says version 2.3.3-p1, because actually the system underneath is still processing the 2.3.4 upgrade.

    So for Alix/nanoBSD systems it goes like:

    1. Start the upgrade process (I use console menu option 13, because the process takes so long to run that I tend to lose it in a webGUI browser tab).

    2. Wait patiently for it to duplicate to the other slice.

    3. Wait patiently again as it downloads and writes all the package files to the other slice
      Note: At this point it is a pain if your internet goes down, or for some other reason you lose connection to the package server and the process times out. Nothing breaks, but when you start again, the process will do "duplicate slice" again and have to download the packages all over. There is no nice way to get it to resume, keeping whatever packages it had downloaded so far.

    4. pfSense reboots on the other slice.

    5. Ordinary boot actions happen, making the webGUI and internet available, with version 2.3.3-p1 showing.

    6. Package upgrade/installs happen underneath. Progress is visible in the system log. Be patient again.

    I am currently in step 6. I will update "soon" with the final result.



  • Here is a sample of the system log at step 6, to illustrate how painfully slow a CF card can get:

    
    May 5 10:49:36 	kernel 		.
    May 5 10:49:37 	kernel 		.
    May 5 10:49:38 	kernel 		.
    May 5 10:49:41 	kernel 		.
    May 5 10:49:41 	kernel 		.
    May 5 10:49:43 	kernel 		.
    May 5 10:49:44 	kernel 		..
    May 5 10:49:45 	kernel 		.
    May 5 10:49:45 	kernel 		. done
    May 5 10:49:54 	pkg 		libffi reinstalled: 3.2.1 -> 3.2.1
    May 5 10:50:06 	kernel 		.
    May 5 10:50:09 	kernel 		.
    May 5 10:50:12 	kernel 		.
    May 5 10:50:14 	kernel 		.
    May 5 10:50:20 	kernel 		.
    May 5 10:50:26 	kernel 		.
    May 5 10:50:38 	kernel 		.
    May 5 10:50:42 	kernel 		.
    May 5 10:50:48 	kernel 		.
    May 5 10:50:53 	kernel 		. done
    May 5 10:51:15 	pkg 		gettext-runtime reinstalled: 0.19.8.1_1 -> 0.19.8.1_1
    May 5 10:51:18 	kernel 		..
    May 5 10:51:18 	kernel 		..
    May 5 10:51:19 	kernel 		.
    May 5 10:51:21 	kernel 		.
    May 5 10:51:21 	kernel 		.
    May 5 10:51:21 	kernel 		.
    May 5 10:51:23 	kernel 		.
    May 5 10:51:24 	kernel 		.
    May 5 10:51:24 	kernel 		done
    May 5 10:51:25 	pkg 		libevent2-2.0.22_1 deinstalled
    May 5 10:53:28 	kernel 		.
    May 5 10:54:12 	kernel 		.
    May 5 10:54:55 	kernel 		.
    May 5 10:56:00 	kernel 		.
    May 5 10:57:13 	kernel 		.
    May 5 10:58:42 	kernel 		.
    May 5 10:59:45 	kernel 		.
    May 5 11:00:48 	kernel 		.
    May 5 11:02:00 	kernel 		.
    May 5 11:03:34 	kernel 		. done
    May 5 11:07:35 	pkg 		python27 upgraded: 2.7.13_1 -> 2.7.13_3
    May 5 11:09:20 	kernel 		.
    May 5 11:10:17 	kernel 		.
    May 5 11:12:00 	kernel 		.
    May 5 11:12:25 	kernel 		.
    May 5 11:13:07 	kernel 		.
    May 5 11:14:14 	kernel 		.
    May 5 11:14:33 	kernel 		. 
    
    

    and finally after some time I think it has finished:

    May 5 11:46:05 	kernel 		. done
    May 5 11:46:13 	pkg 		bind-tools upgraded: 9.11.0P3 -> 9.11.1
    May 5 11:46:30 	kernel 		.
    May 5 11:46:30 	kernel 		..
    May 5 11:46:31 	kernel 		.
    May 5 11:46:31 	kernel 		..
    May 5 11:46:31 	kernel 		.... done
    May 5 11:46:40 	check_reload_status 		Syncing firewall
    May 5 11:46:46 	php 		/etc/rc.packages: Beginning package installation for Cron .
    May 5 11:46:49 	check_reload_status 		Syncing firewall
    May 5 11:46:50 	kernel 		done.
    May 5 11:46:52 	check_reload_status 		Syncing firewall
    May 5 11:46:52 	php 		/etc/rc.packages: Successfully installed package: Cron.
    May 5 11:46:52 	pkg 		pfSense-pkg-Cron upgraded: 0.3.7_1 -> 0.3.7_2
    May 5 11:46:52 	kernel 		done.
    May 5 11:47:00 	kernel 		.
    May 5 11:47:01 	kernel 		.
    May 5 11:47:02 	kernel 		..
    May 5 11:47:02 	kernel 		. done
    May 5 11:47:06 	pkg 		pfSense-default-config-serial upgraded: 2.3.3_1 -> 2.3.4
    May 5 11:48:57 	kernel 		.
    May 5 11:48:59 	kernel 		.
    May 5 11:49:01 	kernel 		.
    May 5 11:49:02 	kernel 		.
    May 5 11:49:02 	kernel 		. done
    May 5 12:04:57 	php-fpm 	83475 	/index.php: User logged out for user 'admin' from: 10.49.213.10
    May 5 12:05:12 	php-fpm 	7429 	/index.php: Successful login for user 'admin' from: 10.49.213.10 
    

    The dashboard still showed 2.3.3-p1, so I logged out and logged in again. Then it showed 2.3.4-RELEASE-p1 (hmmm - the "p1" is a hangover from 2.3.3).

    So I did a full reboot to make sure everything comes up properly and works after all those pkg installs. Now the dashboard shows just the correct 2.3.4-RELEASE.





  • Banned

    I find it a complete no-go on a test system, it runs out of RAM when unpacking python. This is on a box that runs no packages whatsoever and very few services as well. Granted, I could kill pretty much everything incl. ntpd and nginx before upgrading from console, but it's just faster to re-image.

    The Alix HW is getting very much unusable lately for pfSense.



  • I noticed that the dashboard says only FreeBSD 10.3-RELEASE-p16, but a "proper" 64-bit VM that I upgraded has the expected FreeBSD 10.3-RELEASE-p19 as in the release notes at https://doc.pfsense.org/index.php/2.3.4_New_Features_and_Changes

    So I did console option 13 again, and it tries to do something more:

    Enter an option: 13
    
    >>> 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_wrap... 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.
    
    Proceed with upgrade? (y/N) y
    >>> Cleaning secondary partition... done.
    >>> Duplicating current slice... done.
    >>> Restoring slice label... done.
    >>> Testing duplicated partition integrity... done.
    >>> Mounting second partition to run upgrade... done.
    >>> Removing resolv.conf symlink from upgrade partition... done.
    >>> Copying resolv.conf to upgrade partition... 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 (95 candidates): .......... done
    Processing candidates (95 candidates): . done
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
            pfSense-kernel-pfSense_wrap: 2.3.3 -> 2.3.4 [pfSense-core]
    
    Number of packages to be upgraded: 1
    >>> Locking package pfSense-pkg-Cron... done.
    >>> Locking package pfSense-pkg-System_Patches... done.
    >>> Locking package pfSense-pkg-sudo... done.
    >>> Unlocking package pfSense-pkg-Cron... done.
    >>> Unlocking package pfSense-pkg-System_Patches... done.
    >>> Unlocking package pfSense-pkg-sudo... done.
    >>> Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    
    Broadcast Message from root@testoffice-rt-01.np.net.inf.org
            (/dev/pts/0) at 13:22 NPT...
    
    Upgrade is complete.  Rebooting in 10 seconds.
    
    >>> Locking package pfSense-kernel-pfSense_wrap... done.
    

    But after it reboots it is still FreeBSD 10.3-RELEASE-p16.

    I did console option 13 again, just because it is so much fun. Things are no better. It keeps giving a clue that it wants to upgrade some pfSense-wrap version:

    
    Installed packages to be UPGRADED:
            pfSense-kernel-pfSense_wrap: 2.3.3 -> 2.3.4 [pfSense-core]
    
    

    but never seems to actually achieve it.

    Note: I have also tried doing "switch slice" from the Diag->nanoBSD page and rebooting. I wanted to see if it might be doing the FreeBSD patch upgrades on the current slice rather than the duplicated slice. If that had been so, then switching the slice back would show new patches. But no joy there - both slices are on FreeBSD 10.3-RELEASE-p16.


  • Rebel Alliance Developer Netgate

    I had tried to upgrade my ALIX yesterday but got sidetracked so never got around to it. I just tried now and it worked here.

    [2.3.4-RELEASE][root@me.dw.example.com]/root: pkg info -x pfSense
    pfSense-2.3.4
    pfSense-Status_Monitoring-1.6.1_3
    pfSense-base-nanobsd-2.3.4
    pfSense-default-config-serial-alix-2.3.4
    pfSense-kernel-pfSense_wrap-2.3.4
    pfSense-pkg-AutoConfigBackup-1.47
    pfSense-pkg-Cron-0.3.7_2
    pfSense-pkg-System_Patches-1.1.6_1
    pfSense-pkg-acme-0.1.16
    pfSense-pkg-aws-wizard-0.5_1
    pfSense-pkg-ipsec-profile-wizard-0.9_4
    pfSense-rc-2.3.4
    pfSense-repo-2.3.4
    pfSense-upgrade-0.22_1
    php56-pfSense-module-0.13
    [2.3.4-RELEASE][root@me.dw.example.com]/root: uname -a
    FreeBSD me.dw.example.com 10.3-RELEASE-p19 FreeBSD 10.3-RELEASE-p19 #0 bbfdb9a1d(RELENG_2_3_4): Wed May  3 16:58:13 CDT 2017     root@factory23-i386-builder:/builder/factory-234/tmp/obj/builder/factory-234/tmp/FreeBSD-src/sys/pfSense_wrap  i386
    
    

    Try running "pfSense-upgrade -d" from a shell prompt rather than using option 13, see if it prints anything more useful.



  • Output from pfSense-upgrade -d to when it reboots:

    
    [2.3.4-RELEASE][root@testoffice]/root: pfSense-upgrade -d
    >>> 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.
    **** 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.
    
    Proceed with upgrade? (y/N) y
    >>> Cleaning secondary partition...
    1+0 records in
    1+0 records out
    1048576 bytes transferred in 0.894504 secs (1172243 bytes/sec)
    >>> Duplicating current slice...
    14772+1 records in
    14772+1 records out
    968155648 bytes transferred in 552.683673 secs (1751736 bytes/sec)
    >>> Restoring slice label...
    >>> Testing duplicated partition integrity...
    ** /dev/ufs/pfsense1
    ** Last Mounted on /
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Cyl groups
    16594 files, 1153939 used, 705419 free (10907 frags, 86814 blocks, 0.6% fragmentation)
    
    ***** FILE SYSTEM IS CLEAN *****
    >>> Mounting second partition to run upgrade...
    >>> Removing resolv.conf symlink from upgrade partition...
    >>> Copying resolv.conf to upgrade partition...
    >>> 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 (95 candidates): .......... done
    Processing candidates (95 candidates): . done
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
            pfSense-kernel-pfSense_wrap: 2.3.3 -> 2.3.4 [pfSense-core]
    
    Number of packages to be upgraded: 1
    >>> Locking package pfSense-pkg-Cron...
    Locking pfSense-pkg-Cron-0.3.7_2
    >>> Locking package pfSense-pkg-System_Patches...
    Locking pfSense-pkg-System_Patches-1.1.6_1
    >>> Locking package pfSense-pkg-sudo...
    Locking pfSense-pkg-sudo-0.3
    >>> Unlocking package pfSense-pkg-Cron...
    Unlocking pfSense-pkg-Cron-0.3.7_2
    >>> Unlocking package pfSense-pkg-System_Patches...
    Unlocking pfSense-pkg-System_Patches-1.1.6_1
    >>> Unlocking package pfSense-pkg-sudo...
    Unlocking pfSense-pkg-sudo-0.3
    >>> Setting secondary partition as active...
    active set on ada0s2
    Upgrade is complete.  Rebooting in 10 seconds.
    
    Broadcast Message from root@testoffice-rt-01.np.net.inf.org
            (/dev/pts/0) at 21:02 NPT...
    
    Upgrade is complete.  Rebooting in 10 seconds.
    
    >>> Locking package pfSense-kernel-pfSense_wrap...
    Locking pfSense-kernel-pfSense_wrap-2.3.3
    [2.3.4-RELEASE][root@testoffice]/root: Shutdown NOW!
    shutdown: [pid 18551]
    
    

    then /var/log/system.log after it comes up:

    
    [2.3.4-RELEASE][root@testoffice]/root: clog /var/log/system.log
    May  5 21:07:11 testoffice-rt-01 syslogd: kernel boot file is /boot/kernel/kernel
    May  5 21:07:11 testoffice-rt-01 kernel: Copyright (c) 1992-2016 The FreeBSD Project.
    May  5 21:07:11 testoffice-rt-01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    May  5 21:07:11 testoffice-rt-01 kernel: The Regents of the University of California. All rights reserved.
    May  5 21:07:11 testoffice-rt-01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
    May  5 21:07:11 testoffice-rt-01 kernel: FreeBSD 10.3-RELEASE-p16 #9 d88504507(RELENG_2_3_3): Wed Feb 15 11:21:24 CST 2017
    May  5 21:07:11 testoffice-rt-01 kernel: root@ce23-i386-builder:/builder/pfsense-233/tmp/obj/builder/pfsense-233/tmp/FreeBSD-src/sys/pfSense_wrap i386
    May  5 21:07:11 testoffice-rt-01 kernel: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
    May  5 21:07:11 testoffice-rt-01 kernel: CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU)
    May  5 21:07:11 testoffice-rt-01 kernel: Origin="AuthenticAMD"  Id=0x5a2  Family=0x5  Model=0xa  Stepping=2
    May  5 21:07:11 testoffice-rt-01 kernel: Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>May  5 21:07:11 testoffice-rt-01 kernel: AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>May  5 21:07:11 testoffice-rt-01 kernel: real memory  = 268435456 (256 MB)
    May  5 21:07:11 testoffice-rt-01 kernel: avail memory = 226562048 (216 MB)
    May  5 21:07:11 testoffice-rt-01 kernel: pnpbios: Bad PnP BIOS data checksum
    May  5 21:07:11 testoffice-rt-01 kernel: random: <software, yarrow="">initialized
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0814fa0, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0815050, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (iwi_bss_fw, 0xc083ca40, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc083caf0, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
    May  5 21:07:11 testoffice-rt-01 kernel: iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc083cba0, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: wlan: mac acl policy registered
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    May  5 21:07:11 testoffice-rt-01 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May  5 21:07:11 testoffice-rt-01 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0814ef0, 0) error 1
    May  5 21:07:11 testoffice-rt-01 kernel: K6-family MTRR support enabled (2 registers)
    May  5 21:07:11 testoffice-rt-01 kernel: kbd0 at kbdmux0
    May  5 21:07:11 testoffice-rt-01 kernel: ACPI BIOS Error (bug): A valid RSDP was not found (20150515/tbxfroot-258)
    May  5 21:07:11 testoffice-rt-01 kernel: ACPI: Table initialisation failed: AE_NOT_FOUND
    May  5 21:07:11 testoffice-rt-01 kernel: ACPI: Try disabling either ACPI or apic support.
    May  5 21:07:11 testoffice-rt-01 kernel: cryptosoft0: <software crypto="">on motherboard
    May  5 21:07:11 testoffice-rt-01 kernel: padlock0: No ACE support.
    May  5 21:07:11 testoffice-rt-01 kernel: pcib0 pcibus 0 on motherboard
    May  5 21:07:11 testoffice-rt-01 kernel: pci0: <pci bus="">on pcib0
    May  5 21:07:11 testoffice-rt-01 kernel: Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007
    May  5 21:07:11 testoffice-rt-01 kernel: pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached)
    May  5 21:07:11 testoffice-rt-01 kernel: vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: vr0: Quirks: 0x2
    May  5 21:07:11 testoffice-rt-01 kernel: vr0: Revision: 0x96
    May  5 21:07:11 testoffice-rt-01 kernel: miibus0: <mii bus="">on vr0
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
    May  5 21:07:11 testoffice-rt-01 kernel: vr0: Ethernet address: 00:0d:b9:24:59:c0
    May  5 21:07:11 testoffice-rt-01 kernel: vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: vr1: Quirks: 0x2
    May  5 21:07:11 testoffice-rt-01 kernel: vr1: Revision: 0x96
    May  5 21:07:11 testoffice-rt-01 kernel: miibus1: <mii bus="">on vr1
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
    May  5 21:07:11 testoffice-rt-01 kernel: vr1: Ethernet address: 00:0d:b9:24:59:c1
    May  5 21:07:11 testoffice-rt-01 kernel: vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 15 at device 11.0 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: vr2: Quirks: 0x2
    May  5 21:07:11 testoffice-rt-01 kernel: vr2: Revision: 0x96
    May  5 21:07:11 testoffice-rt-01 kernel: miibus2: <mii bus="">on vr2
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy2: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus2
    May  5 21:07:11 testoffice-rt-01 kernel: ukphy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
    May  5 21:07:11 testoffice-rt-01 kernel: vr2: Ethernet address: 00:0d:b9:24:59:c2
    May  5 21:07:11 testoffice-rt-01 kernel: ath0: <atheros 5212="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: ath0: AR5212 mac 5.9 RF5112 phy 4.3
    May  5 21:07:11 testoffice-rt-01 kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0036
    May  5 21:07:11 testoffice-rt-01 kernel: isab0: <pci-isa bridge="">port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: isa0: <isa bus="">on isab0
    May  5 21:07:11 testoffice-rt-01 kernel: atapci0: <amd cs5536="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: ata0: <ata channel="">at channel 0 on atapci0
    May  5 21:07:11 testoffice-rt-01 kernel: ata1: <ata channel="">at channel 1 on atapci0
    May  5 21:07:11 testoffice-rt-01 kernel: ohci0: <ohci (generic)="" usb="" controller="">mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: usbus0 on ohci0
    May  5 21:07:11 testoffice-rt-01 kernel: ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0
    May  5 21:07:11 testoffice-rt-01 kernel: usbus1: EHCI version 1.0
    May  5 21:07:11 testoffice-rt-01 kernel: usbus1 on ehci0
    May  5 21:07:11 testoffice-rt-01 kernel: cpu0 on motherboard
    May  5 21:07:11 testoffice-rt-01 kernel: pmtimer0 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: orm0: <isa option="" rom="">at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: atrtc0: <at realtime="" clock="">at port 0x70 irq 8 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: Event timer "RTC" frequency 32768 Hz quality 0
    May  5 21:07:11 testoffice-rt-01 kernel: attimer0: <at timer="">at port 0x40 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
    May  5 21:07:11 testoffice-rt-01 kernel: Event timer "i8254" frequency 1193182 Hz quality 100
    May  5 21:07:11 testoffice-rt-01 kernel: ppc0: parallel port not found.
    May  5 21:07:11 testoffice-rt-01 kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: uart0: console (115200,n,8,1)
    May  5 21:07:11 testoffice-rt-01 kernel: uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
    May  5 21:07:11 testoffice-rt-01 kernel: Timecounters tick every 1.000 msec
    May  5 21:07:11 testoffice-rt-01 kernel: usbus0: 12Mbps Full Speed USB v1.0
    May  5 21:07:11 testoffice-rt-01 kernel: usbus1: 480Mbps High Speed USB v2.0
    May  5 21:07:11 testoffice-rt-01 kernel: ugen0.1: <amd>at usbus0
    May  5 21:07:11 testoffice-rt-01 kernel: uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
    May  5 21:07:11 testoffice-rt-01 kernel: ugen1.1: <amd>at usbus1
    May  5 21:07:11 testoffice-rt-01 kernel: uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
    May  5 21:07:11 testoffice-rt-01 kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0
    May  5 21:07:11 testoffice-rt-01 kernel: ada0: <elite pro="" cf="" card="" ver6.04k="">ATA-5 device
    May  5 21:07:11 testoffice-rt-01 kernel: ada0: Serial Number 5B2719950011A6D4
    May  5 21:07:11 testoffice-rt-01 kernel: ada0: 16.700MB/s transfers (PIO4, PIO 512bytes)
    May  5 21:07:11 testoffice-rt-01 kernel: ada0: 3811MB (7806960 512 byte sectors)
    May  5 21:07:11 testoffice-rt-01 kernel: ada0: Previously was known as ad0
    May  5 21:07:11 testoffice-rt-01 kernel: random: unblocking device.
    May  5 21:07:11 testoffice-rt-01 kernel: Timecounter "TSC" frequency 498061803 Hz quality 800
    May  5 21:07:11 testoffice-rt-01 kernel: uhub0: 4 ports with 4 removable, self powered
    May  5 21:07:11 testoffice-rt-01 kernel: Root mount waiting for: usbus1
    May  5 21:07:11 testoffice-rt-01 kernel: Root mount waiting for: usbus1
    May  5 21:07:11 testoffice-rt-01 kernel: uhub1: 4 ports with 4 removable, self powered
    May  5 21:07:11 testoffice-rt-01 kernel: Trying to mount root from ufs:/dev/ufs/pfsense1 [ro,sync,noatime]...
    May  5 21:07:11 testoffice-rt-01 php-cgi: rc.bootup: Alias table restore succeeded exited with 0, the result is:  /var/db/aliastables/TestUTP.txt
    May  5 21:07:11 testoffice-rt-01 check_reload_status: starting sshd
    May  5 21:07:11 testoffice-rt-01 kernel: done.
    May  5 21:07:11 testoffice-rt-01 kernel: done.
    May  5 21:07:11 testoffice-rt-01 php-cgi: rc.bootup: Cloning new wireless interface ath0_wlan0
    May  5 21:07:11 testoffice-rt-01 kernel: done.
    May  5 21:07:11 testoffice-rt-01 php-cgi: rc.bootup: Cloning new wireless interface ath0_wlan1
    May  5 21:07:11 testoffice-rt-01 kernel:
    May  5 21:07:11 testoffice-rt-01 kernel: wlan0: Ethernet address: 60:02:b4:0c:45:39
    May  5 21:07:11 testoffice-rt-01 kernel: wlan0: changing name to 'ath0_wlan0'
    May  5 21:07:11 testoffice-rt-01 kernel: wlan1: Ethernet address: 66:02:b4:0c:45:39
    May  5 21:07:11 testoffice-rt-01 kernel: wlan1: changing name to 'ath0_wlan1'
    May  5 21:07:11 testoffice-rt-01 kernel: vr2: link state changed to DOWN
    May  5 21:07:11 testoffice-rt-01 check_reload_status: Linkup starting vr2
    May  5 21:07:13 testoffice-rt-01 sshd[6799]: Server listening on :: port 22.
    May  5 21:07:13 testoffice-rt-01 sshd[6799]: Server listening on 0.0.0.0 port 22.
    May  5 21:07:13 testoffice-rt-01 sshlockout[7306]: sshlockout/webConfigurator v3.0 starting up
    May  5 21:07:14 testoffice-rt-01 check_reload_status: Linkup starting vr2
    May  5 21:07:14 testoffice-rt-01 kernel: vr2: link state changed to UP
    May  5 21:07:16 testoffice-rt-01 check_reload_status: rc.newwanip starting vr2
    May  5 21:07:16 testoffice-rt-01 check_reload_status: Linkup starting vr0
    May  5 21:07:16 testoffice-rt-01 kernel: vr0: link state changed to DOWN
    May  5 21:07:17 testoffice-rt-01 php-cgi: rc.bootup: The command '/sbin/ifconfig 'ath0_wlan0' regdomain 'row' country 'NP' 'indoor'' returned exit code '1', the output was 'ifconfig: SIOCS80211: Invalid argument'
    May  5 21:07:18 testoffice-rt-01 php-fpm[5774]: /rc.newwanip: rc.newwanip: Info: starting on vr2.
    May  5 21:07:18 testoffice-rt-01 php-fpm[5774]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.1.6) (interface: WAN[wan]) (real interface: vr2).
    May  5 21:07:18 testoffice-rt-01 php-fpm[5774]: /rc.newwanip: ROUTING: setting IPv6 default route to 2001:470:35:aa0::1
    May  5 21:07:18 testoffice-rt-01 kernel:
    May  5 21:07:18 testoffice-rt-01 kernel: gif0: link state changed to UP
    May  5 21:07:18 testoffice-rt-01 php-fpm[5774]: /rc.newwanip: Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1
    May  5 21:07:19 testoffice-rt-01 php-cgi: rc.bootup: The command '/sbin/ifconfig 'ath0_wlan1' regdomain 'row' country 'NP' 'indoor'' returned exit code '1', the output was 'ifconfig: SIOCS80211: Invalid argument'
    May  5 21:07:20 testoffice-rt-01 check_reload_status: Linkup starting vr1
    May  5 21:07:20 testoffice-rt-01 kernel: done.
    May  5 21:07:20 testoffice-rt-01 kernel: vr1: link state changed to DOWN
    May  5 21:07:21 testoffice-rt-01 kernel: gif0: link state changed to DOWN
    May  5 21:07:21 testoffice-rt-01 kernel: gif0: link state changed to UP
    May  5 21:07:21 testoffice-rt-01 php-cgi: rc.bootup: Resyncing OpenVPN instances.
    May  5 21:07:21 testoffice-rt-01 kernel: done.
    May  5 21:07:21 testoffice-rt-01 kernel:
    May  5 21:07:21 testoffice-rt-01 kernel: tun1: changing name to 'ovpnc1'
    May  5 21:07:21 testoffice-rt-01 kernel: tun2: changing name to 'ovpnc2'
    May  5 21:07:22 testoffice-rt-01 kernel: tun3: changing name to 'ovpnc3'
    May  5 21:07:22 testoffice-rt-01 kernel: pflog0: promiscuous mode enabled
    May  5 21:07:22 testoffice-rt-01 kernel: .
    May  5 21:07:22 testoffice-rt-01 kernel: DUMMYNET 0 with IPv6 initialized (100409)
    May  5 21:07:22 testoffice-rt-01 kernel: load_dn_sched dn_sched FIFO loaded
    May  5 21:07:22 testoffice-rt-01 kernel: load_dn_sched dn_sched QFQ loaded
    May  5 21:07:22 testoffice-rt-01 kernel: load_dn_sched dn_sched RR loaded
    May  5 21:07:22 testoffice-rt-01 kernel: load_dn_sched dn_sched WF2Q+ loaded
    May  5 21:07:22 testoffice-rt-01 kernel: load_dn_sched dn_sched PRIO loaded
    May  5 21:07:23 testoffice-rt-01 kernel: ..
    May  5 21:07:27 testoffice-rt-01 kernel:
    May  5 21:07:27 testoffice-rt-01 kernel: ovpnc1: link state changed to UP
    May  5 21:07:27 testoffice-rt-01 check_reload_status: rc.newwanip starting ovpnc1
    May  5 21:07:27 testoffice-rt-01 php-cgi: rc.bootup: Removing static route for monitor 8.8.8.8 and adding a new route through 192.168.1.1
    May  5 21:07:27 testoffice-rt-01 kernel: done.
    May  5 21:07:28 testoffice-rt-01 php-cgi: rc.bootup: ROUTING: setting default route to 192.168.1.1
    May  5 21:07:28 testoffice-rt-01 php-cgi: rc.bootup: ROUTING: setting IPv6 default route to 2001:470:35:aa0::1
    May  5 21:07:28 testoffice-rt-01 kernel: done.
    May  5 21:07:28 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc1.
    May  5 21:07:28 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: on (IP address: 10.51.45.2) (interface: []) (real interface: ovpnc1).
    May  5 21:07:28 testoffice-rt-01 kernel:
    May  5 21:07:28 testoffice-rt-01 kernel: ovpnc2: link state changed to UP
    May  5 21:07:28 testoffice-rt-01 check_reload_status: rc.newwanip starting ovpnc2
    May  5 21:07:28 testoffice-rt-01 kernel: ovpnc3: link state changed to UP
    May  5 21:07:29 testoffice-rt-01 check_reload_status: rc.newwanip starting ovpnc3
    May  5 21:07:29 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc2.
    May  5 21:07:29 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: on (IP address: 10.51.93.2) (interface: []) (real interface: ovpnc2).
    May  5 21:07:30 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc3.
    May  5 21:07:30 testoffice-rt-01 php-fpm[31472]: /rc.newwanip: rc.newwanip: on (IP address: 10.51.13.2) (interface: []) (real interface: ovpnc3).
    May  5 21:07:38 testoffice-rt-01 kernel: done.
    May  5 21:07:38 testoffice-rt-01 kernel: done.
    May  5 21:07:39 testoffice-rt-01 php-cgi: rc.bootup: NTPD is starting up.
    May  5 21:07:39 testoffice-rt-01 kernel: done.
    May  5 21:07:45 testoffice-rt-01 kernel: done.
    May  5 21:07:45 testoffice-rt-01 check_reload_status: Updating all dyndns
    May  5 21:07:45 testoffice-rt-01 kernel: ..
    May  5 21:07:46 testoffice-rt-01 kernel: ..
    May  5 21:07:51 testoffice-rt-01 kernel: .done.
    May  5 21:07:56 testoffice-rt-01 snmpd[53783]: disk_OS_get_disks: adding device 'ada0' to device list
    May  5 21:09:14 testoffice-rt-01 php-cgi: rc.bootup: Creating rrd update script
    May  5 21:09:15 testoffice-rt-01 kernel: done.
    May  5 21:09:16 testoffice-rt-01 syslogd: exiting on signal 15
    May  5 21:09:17 testoffice-rt-01 syslogd: kernel boot file is /boot/kernel/kernel
    May  5 21:09:17 testoffice-rt-01 kernel: done.
    May  5 21:09:17 testoffice-rt-01 php-fpm[79063]: /rc.start_packages: Restarting/Starting all packages.
    May  5 21:09:32 testoffice-rt-01 kernel: done.
    May  5 21:09:32 testoffice-rt-01 kernel: done.
    May  5 21:09:35 testoffice-rt-01 getty[12350]: open /dev/ttyv0: No such file or directory
    May  5 21:09:35 testoffice-rt-01 sshlockout[12635]: sshlockout/webConfigurator v3.0 starting up
    May  5 21:09:35 testoffice-rt-01 login: login on ttyu0 as root
    May  5 21:15:56 testoffice-rt-01 php-fpm[58007]: /index.php: Successful login for user 'admin' from: 10.49.213.10
    May  5 21:16:35 testoffice-rt-01 sshd[92186]: Accepted keyboard-interactive/pam for root from 10.49.213.10 port 52838 ssh2</elite></amd></amd></amd></amd></at></at></isa></amd></ohci></ata></ata></amd></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></generic></mii></via></encrypt></pci></software></software,></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx> 
    

    and

    
    [2.3.4-RELEASE][root@testoffice]/root: pkg info -x pfSense
    pfSense-2.3.4
    pfSense-Status_Monitoring-1.6.1_3
    pfSense-base-nanobsd-2.3.4
    pfSense-default-config-serial-2.3.4
    pfSense-kernel-pfSense_wrap-2.3.3
    pfSense-pkg-Cron-0.3.7_2
    pfSense-pkg-System_Patches-1.1.6_1
    pfSense-pkg-sudo-0.3
    pfSense-rc-2.3.4
    pfSense-repo-2.3.4
    pfSense-upgrade-0.22_1
    php56-pfSense-module-0.13
    [2.3.4-RELEASE][root@testoffice]/root: uname -a
    FreeBSD testoffice.aa.bb.cc.dd 10.3-RELEASE-p16 FreeBSD 10.3-RELEASE-p16 #9 d88504507(RELENG_2_3_3): Wed Feb 15 11:21:24 CST 2017     root@ce23-i386-builder:/builder/pfsense-233/tmp/obj/builder/pfsense-233/tmp/FreeBSD-src/sys/pfSense_wrap  i386
    
    

    It looks like it wants to bump the pfSense_wrap from 2.3.3 to 2.3.4 but does not do it, and seems to leave no reason why in the command or log output. Hmmm…


  • Rebel Alliance Developer Netgate

    Strange. Anything in /conf/upgrade_log.txt ?

    You could unlock the kernel package by hand and for it to update with pkg, but I'm curious why it isn't happening automatically.



  • /conf/upgrade_log.txt (below) has the same stuff as came out interactively on the console (above):

    
    >>> 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.
    **** 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.
    
    Proceed with upgrade? (y/N) >>> Cleaning secondary partition... 
    1+0 records in
    1+0 records out
    1048576 bytes transferred in 0.894504 secs (1172243 bytes/sec)
    >>> Duplicating current slice... 
    14772+1 records in
    14772+1 records out
    968155648 bytes transferred in 552.683673 secs (1751736 bytes/sec)
    >>> Restoring slice label... 
    >>> Testing duplicated partition integrity... 
    ** /dev/ufs/pfsense1
    ** Last Mounted on /
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Cyl groups
    16594 files, 1153939 used, 705419 free (10907 frags, 86814 blocks, 0.6% fragmentation)
    
    ***** FILE SYSTEM IS CLEAN *****
    >>> Mounting second partition to run upgrade... 
    >>> Removing resolv.conf symlink from upgrade partition... 
    >>> Copying resolv.conf to upgrade partition... 
    >>> 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 (95 candidates): .......... done
    Processing candidates (95 candidates): . done
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-kernel-pfSense_wrap: 2.3.3 -> 2.3.4 [pfSense-core]
    
    Number of packages to be upgraded: 1
    >>> Locking package pfSense-pkg-Cron... 
    Locking pfSense-pkg-Cron-0.3.7_2
    >>> Locking package pfSense-pkg-System_Patches... 
    Locking pfSense-pkg-System_Patches-1.1.6_1
    >>> Locking package pfSense-pkg-sudo... 
    Locking pfSense-pkg-sudo-0.3
    >>> Unlocking package pfSense-pkg-Cron... 
    Unlocking pfSense-pkg-Cron-0.3.7_2
    >>> Unlocking package pfSense-pkg-System_Patches... 
    Unlocking pfSense-pkg-System_Patches-1.1.6_1
    >>> Unlocking package pfSense-pkg-sudo... 
    Unlocking pfSense-pkg-sudo-0.3
    >>> Setting secondary partition as active... 
    active set on ada0s2
    Upgrade is complete.  Rebooting in 10 seconds.
    >>> Locking package pfSense-kernel-pfSense_wrap... 
    Locking pfSense-kernel-pfSense_wrap-2.3.3
    >>> Removing unnecessary packages... done.
    >>> Cleanup pkg cache... done.
    
    


  • At least I am not alone in the world. Another nanoBSD with the same "stuck on p16":
    https://forum.pfsense.org/index.php?topic=129994.msg716584#msg716584


Log in to reply