2.6.0 upgrade

maverickws

Hi guys,

I just updated my router from 2.5.2 to 2.6.0. I got this error in the end (although it installed and rebooted just fine, and everything seems to be working) just wanted to clear my conscience that all is fine:

The process will require 98 MiB more space.
[1/1] Upgrading pfSense-kernel-pfSense from 2.5.2 to 2.6.0...
[1/1] Extracting pfSense-kernel-pfSense-2.6.0: .......... done
===> Keeping a copy of current kernel in /boot/kernel.old
cp: /boot/kernel/.pkgtemp.fuse.ko.ox3k1rCgBBJ1: No such file or directory
cp: /boot/kernel/.pkgtemp.if_igb.ko.VMPAsvyHGZ0s: No such file or directory
cp: /boot/kernel/.pkgtemp.if_ixlv.ko.7BFrq7yKIZrq: No such file or directory
cp: /boot/kernel/.pkgtemp.if_tap.ko.5cbdorCoyp5A: No such file or directory
cp: /boot/kernel/.pkgtemp.if_tun.ko.dkEVE8AYlbHC: No such file or directory
pkg-static: DEINSTALL script failed
>>> Removing unnecessary packages... done.
System is going to be upgraded.  Rebooting in 10 seconds.
Success

Thanks!

rpsmith

@maverickws -- From what I recall, a Netgate official post said to ignore any error messages that come up during the upgrade process if after it reboots everything appears normal.

Roy...

jimp

That is a bug in the old kernel deinstall script. It's fixed on current versions so it won't happen in future upgrades. Since it was a bug in a file already on your firewall there wasn't a viable way to fix it there, but it's harmless log spam at this point.

PeteRage

I saw the same error message. However my pfsense Netgate 1100+ did not come up.

After waiting 15 minutes, I power cycled it, at which point it did come back up.

Glad I was not trying a remote upgrade. Let me know if there is any info from logs that would be helpful.

SteveITS

@peterage said in 2.6.0 upgrade:

After waiting 15 minutes, I power cycled it,

That might not be long enough. I have updated several 2100s which are a similar CPU and if I uninstall major packages first it usually takes around 10 minutes or so to boot up when upgrading. 3100s are not much faster. My rule of thumb is to not even start to think about worrying until the 15 minute mark.

PeteRage

@steveits That is good information to have. Sounds like I got lucky then on the power cycle not bricking it…