2.3.2-RELEASE to 2.3.3_1 upgrade fails.



  • Hi

    I have a ALIX APU system currently running  the NanoBSD version of 2.3.2-RELEASE, but I can't get it to upgrade (I am trying t upgrade it to 2.3.3_1). I have tried both the WebUI and console. Here's the output from the latest console output:

    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.
    **** 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.
    Copying resolv.conf to upgrade partition... done.
    Downloading upgrade packages...
    Updating pfSense-core repository catalogue...
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    Unable to update repository pfSense
    All repositories are up-to-date.
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    Checking for upgrades (0 candidates): . done
    Processing candidates (0 candidates): . done
    Checking integrity... done (0 conflicting)
    Your packages are up to date.

    Upgrading pfSense kernel...
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    pkg: No packages available to upgrade matching 'pfSense-kernel-pfSense' have been found in the repositories

    Locking package pfSense-kernel-pfSense... done.
    *** Welcome to pfSense 2.3.2-RELEASE (amd64 nanobsd) on internet ***

    Can anyone suggest what might be the problem? We actually have two devices, the other one has upgraded fine, this one, however seems to have a problem. The system is online, and DNS is working. I have tried pkg update from a shell, which says everything is up to date.

    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.
    Any help would be appreciated.


  • Banned

    Try

    pkg update -f
    


  • pkg update -f itself worked

    pkg update -f
    Updating pfSense-core repository catalogue…
    Fetching meta.txz: 100%    944 B  0.9kB/s    00:01   
    Fetching packagesite.txz: 100%    2 KiB  1.8kB/s    00:01   
    Processing entries: 100%
    pfSense-core repository update completed. 8 packages processed.
    Updating pfSense repository catalogue...
    Fetching meta.txz: 100%    944 B  0.9kB/s    00:01   
    Fetching packagesite.txz: 100%  119 KiB 122.0kB/s    00:01   
    Processing entries: 100%
    pfSense repository update completed. 436 packages processed.

    However 'Update from console' still tells me that a pkg update is required. it seems to think it's worked and rebooted, but is still on 2.3.2

    ]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.
    **** 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.
    Copying resolv.conf to upgrade partition... done.
    Downloading upgrade packages...
    Updating pfSense-core repository catalogue...
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    Unable to update repository pfSense
    All repositories are up-to-date.
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    Checking for upgrades (0 candidates): . done
    Processing candidates (0 candidates): . done
    Checking integrity... done (0 conflicting)
    Your packages are up to date.

    Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.


  • Banned

    Well, I'd suggest to ditch the dead nanoBSD (not a viable option with 2.4 anyway.) After that, there's a whole slew of threads here about the upgrade code being super-buggy and pkg just braindead, and a bunch of bugs filed as well – but it's a whole lot worse with nanobsd and the duplicate slice stupidity wasting time over and over again.



  • I have the same error while trying tp upgrade the Version from 2.3.2-RELEASE to  2.3.3_1. I cant ditch the nanoBSD because the System is running on Hardware without vga-port or something like that. Comparable to this HW: https://www.netgate.com//products/sg-2440.html
    What are the other Options instead of nanoBSD ?



  • This is running on a similar bit of kit. I think there is a serial console, perhaps it may be possible to install using that.


  • Banned

    Yeah, use the serial console with proper memstick image (not the VGA one).