Can't seem to upgrade to 2.3.2 from 2.3.1_5



  • Whenever I attempt to upgrade from 2.3.1_5 to 2.3.2 I get:

    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... failed.
    Failed

    I tried to troubleshoot some and from the console when I run pfSenseUpgrade -d I get:

    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...
    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 1 package(s) will be affected (of 0 checked):

    Installed packages to be UPGRADED:
            pfSense-repo: 2.3.1_5 -> 2.3.2 [pfSense-core]

    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-repo from 2.3.1_5 to 2.3.2…
    [1/1] Extracting pfSense-repo-2.3.2:
    pkg: Fail to set time on /usr/local/share/pfSense/pkg/repos/.pfSense-repo-devel.conf.RsvCr2Z1sEZb: Operation not supported
    [1/1] Extracting pfSense-repo-2.3.2… done
    ]

    I've tried to google this error and not found anything. I tried to force an upgrade through pkg update -f and pkg upgrade -f and that did not work (Got the same Failed to set time …. Operation not supported error on a different file.

    Just a little background here:

    I'm running PFsense in a Hyper-V VM on Windows Server 2008. I've had issues with the PFsense kernel 2.3 and greater (It won't find the HD when it boots and can't seem to see more than 3 NICs), so I've been manually copying the kernel from 2.2.6 to the VM so things continue to work correctly. Possibly this is the issue? I'm not opposed to a reinstall at this point.

    Thanks for any help you can provide.



  • I've been manually copying the kernel from 2.2.6 to the VM so things continue to work correctly

    Most likely this is the cause for your issue.

    Backup configuration and install 2.3.2 from scratch.
    If you have extra courage, try 2.3.3 amd64 development snapshots which contain some fixes specific to Hyper-V.

    Regards,
    Jorge M. Oliveira



  • I tried a fresh install and it doesn't work correctly. I have to do some magic for it to see the hard disks (See https://forum.pfsense.org/index.php?topic=109952.msg613371#msg613371). After it can see the hard disk, it can only see 3 of the 5 NICs I've setup for it. I tried 2.3.3 and it had the same issues.