2.3.3.1> 2.3.4 OK; but now unable to check for updates / wrong OS
-
Unfortunately I don't have a config backup - and concerned that if I take a current one it may be corrupted in some way - caused by whatever is affecting the ability to upgrade / view packages.
I am happy to spend the time to follow the upgrade path - if I can only resolve the current issue.
What puzzles me is that the upgrade to 2.3.4-Release-p1 seems to go perfectly - I am struggling to understand what went wrong and how to overcome it.
Any thoughts on how to overcome the issue and start an upgrade to to 2.4?
Thanks
-
@hackinate Plug a USB into one of the ports and copy it off?
Just have to copy the entire /conf/ directory to a flash drive, or offload using SCP.
One of the (30) backups statistically should be OK. If you don't have a good backup, though, upgrading like this isn't going to solve that problem. -
I am, as most would have guessed, inexperienced.
Originally the PC Engines APU2 came preconfigured with pfSense.Ideally I would like to follow the upgrade path:
-
Should I simply set IGNORE_OSVERSION=yes and run pkg-static update -f
-
Is there some other way to force an update to version 2.4 ?
-
I have a conf backup - If I cannot upgrade - is there a simple way to do a fresh install of version 2.4?
Thanks
-
-
@hackinate said in 2.3.3.1> 2.3.4 OK; but now unable to check for updates / wrong OS:
is there a simple way to do a fresh install of version 2.4?
No not really, 2.4 isn't even available for download any more.. Just do a clean install of 2.6
-
Thanks - unfortunately that leaves the question of how to do a fresh install of 2.6?
(And will I be able to reload the current config into the newer version?)
Thanks
-
-
Thanks - understand the process, but don't have a serial cable.
Still hoping that someone will be able to suggest a way to force an upgrade - as everything else is working well.
Tempted to go ahead and try the ignore_osversion=yes
Has anyone run this previously - with a similar issue?Thanks
-
@hackinate Null Modem cables can be picked up relatively inexpensively and you never know when you'll need it again in the future (I have one I purchased for my ATI Geode ALIX 2D3 [remember those?!] appliance in 2009 and I've used it multiple times a year since with various devices, typically old switches and ASICs).
$20-30 here in the US, YMMV elsewhere, though.
-
Appreciate the help - I will look to buy a suitable cable.
In the meantime I am still hoping that someone may be able to suggest how I can overcome the upgrade issue - would much prefer following that route.
It seems as though the last upgrade (to 2.3.4) added some files that should belong to 2.4.x - which include the OS upgrade. If I was able to remove them it seems likley I could then upgrade normally.
Any help appreciated.
-
@hackinate where are you finding that you should do something with ignore_osversion?
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html
But until you can install clean, I wouldn't mess with an update of such an old version - if its working.. I would wait til you have the cable, that way if something goes wrong you can recover.
-
The response to trying to update pkg:
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries:
pkg-static: Newer FreeBSD version for package pfSense-pkg-RRD_Summary:
To ignore this error set IGNORE_OSVERSION=yesWill wait until I have cable, but hoping there is a way to remove the offending files and do a regular update.
