Upgrade 2.3.1-p1 -> p5 "failed" but at the end successful
-
Hi,
after upgrade the pfSense GUI show "firmware installation failed!", but the system reboot and running under -p5.
Was the same problem from 2.3.1 -> -p1.Version 2.3.1-RELEASE-p5 (amd64) built on Thu Jun 16 12:53:15 CDT 2016 FreeBSD 10.3-RELEASE-p3 The system is on the latest version. Platform nanobsd (4g) NanoBSD Boot Slice pfsense0 / da0s1(rw)
Maybe only a wrong return value?
-
At times with nanobsd, pkg seems to have issues with its status output, which makes the GUI think it's failed, but it's actually working fine it's just its status reporting that has an issue. So your upgrade was fine. The pkg issue's one we're looking to track down.
-
Yes, I have noticed this also. I will be at a nanoBSD Alix on Monday that did this last time, so this time I will try and capture as much info as possible (which means the problem probably won;t happen).
As Chris says, the upgrade continues in the background and some time later the system reboots into the other upgraded partition successfully. -
The update of my ALIX pfSense box (i386) works fine.
Maybe only amd64 affected? -
@slu:
The update of my ALIX pfSense box (i386) works fine.
Maybe only amd64 affected?It's not architecture-specific, just rarely happens with either. There have been at least a couple reports of it happening on an ALIX.
-
Mine worked fine from 2.3.1 p1 to p5 on an Alix that previously had been doing the thing where it would quickly scroll some text in the upgrade text box, say it failed, but then go on doing the upgrade in the background.
So I am not sure what the difference was this time.
-
I've seen this multiple time upgrading NANO on APU boards.
I also often get a successful upgrade message but the system never comes back up.
Power cycling has always brought it backup again to a successful p5
(to summarize - the upgrades are working… sometime with failed sometimes OK - but often dont re-boot without power cycling (NANO & full install - all APU)