Successful upgrade to 2.2 still on 2.1.5
-
Trying to upgrade 2.1.5 i386 to 2.2 using manual firmware upload using pfSense-Full-Update-2.2-RELEASE-i386.tgz (I checked MD5 and SHA1, download OK).
Console shows "Firmware upgrade is complete. Rebooting in 10 seconds". No errors before that message. However, after the reboot I am still on 2.1.5 in the console and webinterface.Is there any upgrade log?
Thanks for any hint on this!
-
In the web gui under
Diagnostics: NanoBSD
you'll see view upgrade log at the bottom.
I'm having the same exact issue and i've narrowed it down to its upgrading a different boot slice than the one the firewall is booting up on. Switching the boot slice in the web gui has no affect. I've tried doing this on multiple firewalls with no luck. All are ALIX2.d.3
-
There is some difference here between the OP's post and jcpolo.
The OP is using Full-Update - so I hope that is on a full install.
jcpolo has a nanoBSD system with 2 boot slices - on that system the nanoBSD upgrade file to match the CF/SD card size must be used.
If something goes wrong unpacking the update to the other boot slice, or in any of the subsequent fsck, protection setting etc of the other boot slice, then the upgrade script is good and does not switch the boot slice. There should be something in the upgrade log to indicate what went wrong. Or the system ran out of real memory when do the unpacking… and there might be "Killed: out of swap space" indicating that the process/es doing the upgrade got killed by the OS.@srynoname: Are you on nanoBSD or full install?
-
@srynoname: Are you on nanoBSD or full install?
I am on the full install. Can't find a log in Diagnostics though ):
-
Try Diagnostics->Edit file or command line and look for /conf/upgrade_log.txt
On nanoBSD it is /cf/conf/upgrade_log.txt (and /conf points to /cf/conf also) -
thanks phil!
I attached the upgrade log, can anyone help me with this?
relevant matches for "error" from the log:
Line 141: tar: Error exit delayed from previous errors.
Line 141: tar: Error exit delayed from previous errors.
Line 793: bin/perror changed -
I ended up with a new install of 2.2 and importing config. Worked fine and was done in a few minutes.