Unable to upgrade 2.6.0 to 2.7.2
-
Have a box on 2.6.0release that will not directly upgrade to 2.7.2
Tried rebooting - DNS is healthy.
Upgrade only shows 2.7.0 release as an upgrade path
Tried reading the documentation and a few tests.pkg-static info -x pfsen se-upgrade
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pfSense-upgrade-1.0_33Does not seem to tell me anything about the latest release as stated in the document.
This also seems to be another rabbithole:This is just looking totally broken.
But I don't really get what I did wrong to end up in this situation.
Looks like it's going to need a re-install.
But was hoping to learn or better understand why the upgrade seems to be wonky and broken in the first place.
The WebUI says I can upgrade it to 2.7.0 but I'm pretty sure that's broken and will totally fail if I try it.pkgstatic clean -ay; pkg-static install -fy pkg prsense-repo pfsense-upgrade
pkgstatic: Command not found.
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.
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg-static: No packages available to install matching 'prsense-repo' have been found in the repositories -
@N8LBV Dashboard continues to show 2.7.0 is available.
But if I go to select branch, all there is - is 2.6.0 Release and 2.7.0 Release.
And if I select 2.7.0 then is says unable to check for updates.
But if I put it back to 2.6.0 it check and then says "you are on the latest version". -
@N8LBV Hey there, I had same situation without any reply or solution so, installed second pfSense VM v2.7.2 and imported the most of settings from 2.6.0. Now is working fine.
Regards Leo.
-
You have to go through 2.7.0 because that's the first version that included the dynamic repository system.
-
@stephenw10 OK so then should be "safe" to just try upgrading to 2.7.0 then then do the next upgrade after that upgrades?
I thought maybe it was borked and need to re-install and restore from a backup config.
But with that I can at least try before it gets messed up further :)
I also wanted to learn something vs. just re-installing and restoring.
With that said I also kinda want to re-install ZFS to avoid bootup pauses etc. on FS not checked in forever types stuff.
It's currently UFS and has been upgraded a number of times.
They key here is that I did actually learn something already that I should probably have known: <You have to go through 2.7.0 because that's the first version that included the dynamic repository system> -
Yup, I just verified that on a VM here.
-
@lexposito1986 Yeah - I have my finger on the trigger to do that after I try messing it up a little first :)
-
@stephenw10 Although I get that "unable to check for updates" error if I try plopping the branch onto 2.7.0 So I can't just "simply" upgrade it from 2.6.0 --> 2.7.0 in its current state.
I'm guessing there's a "fix" for this that I can search for, but reboots (and a few other surface things) did not fix that. DNS resolution is healthy and working properly. and does it's thing while the 2.6.0 branch is selected. -
Just refresh the page. When you first change branch it refreshes the pkg system in the background.
