Cannot upgrade from 2.1.4 to 2.2.2
-
Probably because it did not reboot. Reboot it manually and re-apply the update manually once again.
Not sure I understand. Reboot BEFORE upgrading, or after? Also, what's the right way to reboot?
-
https://redmine.pfsense.org/issues/4653
-
Probably because it did not reboot. Reboot it manually and re-apply the update manually once again.
Not sure I understand. Reboot BEFORE upgrading, or after? Also, what's the right way to reboot?
Afterwards.
Only then pfSense boots from the NEW kernel.
The right way to do it, is:
Login into GUI. Goto the menu Diagnostics: Reboot System and hit the Yes button.
Or, login using SSH and type the command 'reboot'. -
So I invoked auto upgrade. Here's what happened.
Auto Update Download Status
–--------------------------------------------------
Current Version : 2.1.4-RELEASE
Latest Version : 2.2.2-RELEASE
File size : 71699610
Downloaded : 71699610
Percent : 100%
pfSense download complete.
pfSense is now upgrading.
The firewall will reboot once the operation is completed.
This is where things get very confusing. Nothing happens on the screen at all at this point. After waiting for 5 minutes, I rebooted manually (Diagnostics/Reboot). After doing all of that, there's NO upgrade to be had. Back to square 1.
2.1.4-RELEASE (i386)
built on Fri Jun 20 17:06:12 EDT 2014
FreeBSD 8.3-RELEASE-p16Update available. Click Here to view update.
Any other ideas?
-
Then I went thru the manual upgrade process, which actually auto-rebooted. Same result:
2.1.4-RELEASE (i386)
built on Fri Jun 20 17:06:12 EDT 2014
FreeBSD 8.3-RELEASE-p16Update available. Click Here to view update.
-
The not rebooting post-upgrade issue doesn't apply to nano versions. What does the upgrade log under Diag>nanobsd show?
-
NanoBSD firmware upgrade log attached…please advise on how I might be able to get this working!
[NanoBSD Firmware upgrade.txt](/public/imported_attachments/1/NanoBSD Firmware upgrade.txt)
-
The key part there is "fdisk: invalid fdisk partition table found". That's something that has happened on occasion for unknown reasons. It appears to be an issue with the CF card itself, but in many cases rewriting the card fixes it (probably because it remaps something in the process of rewriting it). Pulling the img off of an affected card, and writing it out to another card or even back to the same card, fixes the issue which seems to indicate there isn't actually anything wrong in software. Unfortunately you'll need to pull the card and rewrite it. Can rewrite it with 2.2.2, then restore your 2.1.4 config backup.
-
@cmb:
Pulling the img off of an affected card, and writing it out to another card or even back to the same card, fixes the issue which seems to indicate there isn't actually anything wrong in software. Unfortunately you'll need to pull the card and rewrite it. Can rewrite it with 2.2.2, then restore your 2.1.4 config backup.
Thanks for the update. How would I do this?
-
https://doc.pfsense.org/index.php/Writing_Disk_Images
