Upgraded Package before Upgrading to 2.7.1 - System screwed!
-
It may well be fastest to install 2.7.1 clean and restore your config.
However you may be able to switch the update repo back to 2.7.0 and force reinstall the correct pkgs from there:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstallSteve
-
I have 2 remote systems that I simultaneously did the same exact thing to and now stuck in the same boat. Since I am connected remotely to both firewalls performing a clean install and restoring is not an option.
When you say to "switch the update repo back to 2.7.0" are you talking about in the System>Update>System Update and choosing the "Previous Stable Release (2.7.0)" in the Branch selection?
-
Yes, set it back to 2.7.0 there and see if it can force update at least the pkg package.
-
I changed it to 2.7.0 and then ran the following command from a putty shell session:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
and then
pkg-static upgrade -f
I was a bit afraid to reboot the firewall since this is a remote system. So I changed the repo back to 2.7.1 after running the above commands and was able to install the upgrade to 2.7.1.
In the process of rebooting now. Fingers crossed it comes back up.
-
System came back up and had to reinstall a couple of the packages from the Installed Packages page before those particular package services would start properly. But all appears to be OK.
Won't make that mistake again to update packages before updating to the latest pfSense version.
-
On the second system I had to also run the following command since i was getting an error about "no active remote repositories configured"
ln /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf /usr/local/etc/pkg/repos/pfSense.conf
I had changed and saved a couple times between the 2.7.0 and 2.7.1 repo and only running the above command allowed me to continue with the above steps.
-
Nice result. Going forward the upgrade system should prevent this happening.
-
@Kidder-0
I had a bit worse result. I was still running 23_05 and tried to upgrade pfBlockerNG and the result was an unbootable router. Grrrr..., I had a memstick image of 2.7.0 on my harddrive, no internet access to pull 2.7.1 so install 2.7.0 is what I had to do and upgrade from there. Fun, fun! Oh well, I needed to update to 2.7.1 anyway with the change in licensing terms... but not a fun way to start the morning. -
@datanet said in Upgraded Package before Upgrading to 2.7.1 - System screwed!:
I changed it to 2.7.0 and then ran the following command from a putty shell session:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
and then
pkg-static upgrade -f
I was a bit afraid to reboot the firewall since this is a remote system. So I changed the repo back to 2.7.1 after running the above commands and was able to install the upgrade to 2.7.1.
In the process of rebooting now. Fingers crossed it comes back up.
Hi Everyone,
I just wanted to let everyone know this worked PERFECTLY. Followed the exact same steps above, but once I did the
pkg-static upgrade -f
I went back to the gui and reset the upgrade version to 2.7.1. Did a refresh on the main page and then went back to update .... hit confirm and the system updated NO PROBLEM.
Came right back up after reboot and life is good.
Always awesome when you have people help you solve problems like this ...Thanks @stephenw10 and @datanet
Cheers,
C -
@Robert42 I've also been hit with the same boot issue you describe
-
C CyclonePF referenced this topic on
-
K Kidder 0 referenced this topic on
