2.3.4-RELEASE-p1 => 2.4.0 "system update failed" please help!
-
With that all being said will my config backup work on a fresh install to a 64bit system when the config was based from x86 i386?
Be sure it will be running well and working and if not, I mean if something goes wrong for you, you may be also
able to reinstall the older verison and play it back there, if needed. -
Ok, I will make sure I have an older copy just in case I have to revert back. My config is rather extensive. Thanks for the feedback guys.
-
I'm getting no where with updating. I believe I have 64bit hardware– but I still get "System Update Failed".
I'm on version:
2.3.4-RELEASE-p1 (amd64)
built on Fri Jul 14 14:52:43 CDT 2017
FreeBSD 10.3-RELEASE-p19My hardware is:
Platform pfSense
CPU Type Intel(R) Xeon(R) CPU X3470 @ 2.93GHz
Current: 2933 MHz, Max: 2934 MHz
8 CPUs: 1 package(s) x 4 core(s) x 2 SMT threads
8GB RAMAny ideas? I'm using hardware I bought online, and from my research this CPU is 64bit
-
I'm getting no where with updating. I believe I have 64bit hardware– but I still get "System Update Failed".
Was this over the webgui or over a memstick image on an USB pen drive? And when USB pen drive what image
you were using for this update?CPU Type Intel(R) Xeon(R) CPU X3470 @ 2.93GHz
It is a real 64Bit CPU!
Any ideas? I'm using hardware I bought online, and from my research this CPU is 64bit
If you will be able to get the amd64 memstick serial image to download, I woudl do so and then you might be
preparing an USB pen drive for the upgrade. Save your config backup image and then do a fresh and full install.
Play back the config backup and see what is going on. -
Just reinstall… You can spend forever on this.
-
Just reinstall… You can spend forever on this.
Is there a quick way to re-install via the web gui? I have my box mounted in a peculiar spot and getting a monitor, keyboard and mouse would be a huge pain.
Thanks
-
I thought you already had a huge pain? Sorry. I have no easy answer.
-
I got the dreaded “System update failed!” message back when I tried upgrading one of my pfSense 2.3.4 boxes to 2.4.0, and I got it again today when I tried upgrading another 2.3.4 box to 2.4.2. I'm really surprised it still has this problem in 2.4.2, and even more surprised that none of the pfSense upgrade documentation mentions this problem.
Here's what I had to do both times: SSH into your pfSense machine and run the following three commands as root:
pkg-static install -f pkg
mv /usr/local/etc/pkg.conf /usr/local/etc/pkg.conf.old
pfSense-upgrade -dDetail:
When you run “pkg-static install -f pkg” you’ll see the following:
Updating pfSense-core repository catalogue…
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):Installed packages to be REINSTALLED:
pkg-1.10.1_1 [pfSense]Number of packages to be reinstalled: 1
After you select “y” and it upgrades the “pkg” package it will tell you the following:
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
Instead, I renamed it to pkg.conf.old, just in case.
After you run “pfSense-upgrade -d” to complete the upgrade it will automatically reboot. The reboot will take longer than normal because it will continue upgrading packages after it boots. Eventually, though, the Web interface will load again and you'll see the new Web GUI design.
Hope that helps.
–Dan -
Thanks, this helped me get upgraded.
-
@fluidmindorg Thanks Mate, that worked. It was a very slow process though.
-
I was very hopeful this would fix me, but it did not. Same issue trying to go from 2.3.4 to current. Doing this actually made the issue slightly worse in that before I could at least check for updates and now I cannot. Sounds like I might be stuck with a config backup/fresh install/config restore situation now unless someone has a better suggestion.
