Successful WebUI in-place upgrade from 2.6.0 to 2.7.0 (What I did)
-
Here are my steps:
- Read the Release Notes and specific upgrade instructions. Read the Upgrade Guide in the pfSense documentation.
- Make a pre-upgrade config.xml backup via Diagnostics -> Backup & Restore.
- Reboot (just for fun).
- Take a screenshot of all Installed Packages. (Or otherwise copy and paste/make note of what's installed.)
- Manually uninstall all packages, one-by-one.
- Upgrade to 2.7.0 via WebUI. It took about 5-7 minutes total, including reboot.
- Log in and note the version is now 2.7.0. Note that none of the package-specific widgets show up on the Dashboard.
- Manually install all packages, one-by-one from the screenshot/notes.
- Reboot (just for fun).
- Make a post-upgrade backup of the config.xml.
-
I did a similar process with my update to 2.7.0.
I did make a post on here to verify my plan before doing it as I really didn't want to muck it up. LOL
But over all, it went way better and easier than I expected.
I've only been poking round this new version for a little bit but, some of the new stuff is pretty interesting.
My favorite so far is the new online status indicator in the "Status / DHCP Leases." Pretty cool and way easier to see what or if things are online or not in my network.I've found this new version uses about 2% more ram and took up .6GB more of hard drive space but, even with the extra usage my system is fine with the 8GB ram and 214GB hard drive that I have installed. And actually, I just checked and the RAM usage went down to 1% over what it was (2.6.0 was running 4% RAM usage and now 2.7.0 has claimed 5%. Down from 6%).
Even the 2.0GB of used hard drive is only 1% of the available.
CPU usage and temps seem the same as with old version too so, over all I'm happy! -
@Finger79 said in Successful WebUI in-place upgrade from 2.6.0 to 2.7.0 (What I did):
Here are my steps:
Read the Release Notes and specific upgrade instructions. Read the Upgrade Guide in the pfSense documentation.
Make a pre-upgrade config.xml backup via Diagnostics -> Backup & Restore.
Reboot (just for fun).
Take a screenshot of all Installed Packages. (Or otherwise copy and paste/make note of what's installed.)
Manually uninstall all packages, one-by-one.
Upgrade to 2.7.0 via WebUI. It took about 5-7 minutes total, including reboot.
Log in and note the version is now 2.7.0. Note that none of the package-specific widgets show up on the Dashboard.
Manually install all packages, one-by-one from the screenshot/notes.
Reboot (just for fun).
Make a post-upgrade backup of the config.xml.I did the same thing and result seems fine till now. Anyway, I skipped step 9 of yours. :D
Cheer.
-
@Kilted1 said in Successful WebUI in-place upgrade from 2.6.0 to 2.7.0 (What I did):
I just checked and the RAM usage went down to 1% over what it was (2.6.0 was running 4% RAM usage and now 2.7.0 has claimed 5%. Down from 6%).
Even the 2.0GB of used hard drive is only 1% of the available.
CPU usage and temps seem the same as with old version too so, over all I'm happy!I got similar result as you, when running v2.6.0, RAM gone up to 21%-23% and after upgraded to 2.7.0, RAM dropped to only 10% of usage.
Cool.
-
@Finger79 Yah, I did much of what you list here but mine won’t boot up. It’s on VMware. I rolled back to the pre-upgrade snapshot. I get a fatal error in the VMware.log file for the v2.7. Fresh install of version 2.7 gives the same error. ESXi 5.1 - it might be time to upgrade. I guess FreeBSD 14 doesn’t like that VMware version…
-
@binyamincohen said in Successful WebUI in-place upgrade from 2.6.0 to 2.7.0 (What I did):
@Finger79 Yah, I did much of what you list here but mine won’t boot up. It’s on VMware. I rolled back to the pre-upgrade snapshot. I get a fatal error in the VMware.log file for the v2.7. Fresh install of version 2.7 gives the same error. ESXi 5.1 - it might be time to upgrade. I guess FreeBSD 14 doesn’t like that VMware version…
Oh wow, how old is ESXi 5.1? I believe 8.0a is out. I'm not an ESXi guru but it might be worth making a separate thread. (Or upgrade :P )
-
Thanks guys,.. After 275+days of flawless uptime, ( not a single reboot! Since last upgrade ), Followed these simple instructions,... with all the reboots and some config-backups...
And 'Voilà' ,.. normal service has been restored, 'Rock on'....
Many thanks.. -
@Finger79 -tyvm
I followed your steps to the letter and everything is green approx. 15-20 minutes later
I backed everything up as you outlined
uninstalled all extra packages
did not reboot
did the upgrade
after the reboot I reinstalled all the packages
did not reboot
I imported the backup.xml
PC rebooted on it's own
after the reboot it had a big yellow warning about installing packages in the background on the dashboard page
All I did was start the three missing services and a force reload of all in pfblockerng
then I did a refresh on the dashboard page and all is running and green
everyone in the house had a momentary disconnect and that was it - they do not even know the FW was upgraded, like it should be :-) = Happy!!Pretty much a flawless upgrade
crossing fingers nothing rears it's ugly head although my setup is basic as belowwan
lansub1
lansub2
no vlan or vpn
with the following packagesarpwatch
backup
mailreport
mtr-nox11
notes
pfblockerng-devel -
@1OF1000Quadrillion For future reference. No need to restore after an upgrade. ;)
-
I will try your step tomorrow. I don't have too much packages (a total of three) but I have a tons of rules.
If I do a configuration backup will I be able to restore it on the new 2.7x (I'm planning to do a clear install)?
-
@CC88 Backup files can be restored to a later version.
https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html
