Upgrade to 2.4 killed my SG-2220
-
Yes, the problem with not able to install packages is biting me with an erroneous 2.3.x installation, too. Not being able to recover those is a real showstopper atm!
-
Yup, it's points to a direction of only running pfSense virtualized.
Blows up … roll back ... no problems. Wait for bug fixes.
If this was a customer 500 miles away, and I remote upgraded, I would be in trouble now.I just really fancy pfSense hardware, high quality.
-
Same issue here.. Ran the upgrade from the GUI on my SG-2220
Trying to rebuild from the USB stick right now on site.
Can someone tell me which image I should be using?
-
Use the Netgate ADI labeled memstick.
-
-
Take a backup of the config before you upgrade so you are not trying to restore a config from a LATER version on an older version. That is not and has never been supported.
-
Hi again
After much fumbling, I'm back to 2.3.4
Now I get this message in promt
[2.3.4-RELEASE][root@pfSense-Konge.localdomain]/root: pfSense-upgrade -4
Shared object "libssl.so.8" not found, required by "pkg"
Shared object "libssl.so.8" not found, required by "pkg"
ERROR: It was not possible to identify which pfSense kernel is installedNow, what's that all about?
-
It got my SG-2440 too.
Did an usb install and everything is back up now.
Don't forget to install the Netgate_Coreboot_Upgrade
-
Thanks oppland
But part of the problem is, that in the package section I got this message:
Unable to retrieve package information.
It simply won't tell anything, search anything,- but is connected to the internet, it really want to test me :)
-
Reporting in…
My standalone SG2440 upgrade failed, too. The GUI said upgrade failed and the box became unresponsive. After digging up a console cable and driver, I bounced it to see a bunch of PHP library errors. I was up and running in a little less than an hour, after burning a stick with the latest release.
I've got a bunch of other boxen to upgrade. How do I tell what broke? I've got the uprade_log.txt, but nothing's obvious so far.
