[SOLVED] Update from 2.3.1 failed
-
I manually updated from 2.2.x to 2.3.1 (NanoBSD 2GB, VGA) and tried to update to the latest tonight via System/Update/System Update. This was the result. It's reproducible.
Could this be the result of the 2.3.1_2 snafu? Any other ideas?
There appears to be a pfSense-Status_Monitoring_1.4.2_1.txz in the update directory.
>>> 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. >>> 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 (7 candidates): ....... done Processing candidates (7 candidates): ....... done The following 6 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-rc: 2.3.1 -> 2.3.1_1 [pfSense-core] pfSense-kernel-pfSense: 2.3.1 -> 2.3.1_1 [pfSense-core] pfSense-default-config: 2.3.1 -> 2.3.1_1 [pfSense-core] pfSense-base-nanobsd: 2.3.1 -> 2.3.1_1 [pfSense-core] pfSense-Status_Monitoring: 1.3_1 -> 1.4.1_1 [pfSense] pfSense: 2.3.1 -> 2.3.1_1 [pfSense] 40 MiB to be downloaded. 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 pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pfSense-Status_Monitoring-1.4.1_1.txz: Not Found >>> Locking package pfSense-kernel-pfSense... done. Failed
-
https://forum.pfsense.org/index.php?topic=113435.msg630835#msg630835
Runningpkg update -f
did it for me.
-
Thanks Gertjan, that fixed it for me.
-
I also am having problems. There is a prompt in the dashboard to update 2.3.1 to 2.3.1_1, however the update fails with the following last few lines:
pfSense: 2.3.1 -> 2.3.1_2 [pfSense]
ntp: 4.2.8p7 -> 4.2.8p8 [pfSense]
expat: 2.1.0_3 -> 2.1.1_1 [pfSense]563 KiB to be downloaded.
pkg: https://pkg.pfsense.org/pfSense_v2_3_1_i386-pfSense_v2_3_1/All/pfSense-2.3.1_2.txz: Not FoundLocking package pfSense-kernel-pfSense… done.
FailedI suspect the is still some ghost referernces to the 2.3.1_2 update that never was here.
-
…..
I suspect the is still some ghost referernces to the 2.3.1_2 update that never was here.2.3.1_2 existed a couple of hours.
https://pkg.pfsense.org/pfSense_v2_3_1_i386-pfSense_v2_3_1/All/pfSense-2.3.1_2.txz did exist for a while.
Read the entire thread https://forum.pfsense.org/index.php?topic=113435.msg630835#msg630835 ( and apply the proposed solution ).