SOLVED: Console upgrades - never actually upgrade?
-
Wanting to upgrade an old 2.0 RC1 upward to starting with 2.0 release.
I have this installed on an old HP DL360 which has drives and 4GB memory. Used the ISO version of course.
Plenty of space on the drives.I've read that the memstick upgrade version is the one to be used with drives. Just pick your architecture.
I went with;
http://files.nyi.pfsense.org/mirror/downloads/old/pfSense-memstick-2.0-RELEASE-i386.img.gzWeird;
WARNING! ACHTUNG! DANGER!
This image is not digitally signed.yet, it's coming from a pfsense.org site
Anyhow, it went through it's upgrade process but… when I logged back in...
*** Welcome to pfSense 2.0-RC1-pfSense (i386) on pf5 ***Same old version as it was before?
Ok, then decided to try;
http://files.nyi.pfsense.org/mirror/downloads/old/pfSense-memstick-2.0.1-RELEASE-i386.img.gzSame problem.
Looking on the net but not coming up with how to actually upgrade yet.
If anyone could help, you could save me hours of frustrations :)Thanks.
UPDATE: Found the following URL and was able to upgrade.
http://mirror.myip.be/pub/pfsense/updates/old/Did so incrementally and all went fine.
-
Any particular reason you don't just update via the GUI?
-
Yes, the reason for the upgrade is mainly because WebConfigurator simply disappeared yesterday. No obvious reason, it simply won't come up. I restarted the service and the router and it never comes up.
I posted about that and was pretty much told that I should upgrade since I'm still running 2.0 RC1 :).
So, that's where I'm at.
-
You don't upgrade with the memstick, that's not an update file. You also don't want to upgrade to 2.0. Use https://nyifiles.pfsense.org/mirror/updates/pfSense-CE-Full-Update-2.3-RELEASE-i386.tgz
-
From what I've read, it's safer to upgrade incrementally. I tried upgrading a long time ago and it broke this configuration so wanted to do it smaller steps at a time since I'd forgotten about this router.
-
@cmb:
You don't upgrade with the memstick, that's not an update file. You also don't want to upgrade to 2.0. Use https://nyifiles.pfsense.org/mirror/updates/pfSense-CE-Full-Update-2.3-RELEASE-i386.tgz
I don't see any incremental upgrades of -CE-Full-Update- in the link you sent me and I've yet to find those. Might you have a lead on that since you knew about these?
-
Does anyone know for sure if it is safe to upgrade all the way to current release starting from 2.0 RC?
-
Does anyone know for sure if it is safe to upgrade all the way to current release starting from 2.0 RC?
Well since one of the devs linked you to the file you need to upgrade directly to 2.3 I would assume that's the way you should do it.
Make a backup of your config prior to upgrading if you're that worried about it.
-
Yes, you should upgrade direct to 2.3. Incrementally upgrading in between isn't going to help anything. If anything, it might cause problems you wouldn't otherwise have, as a since-fixed config upgrade issue in some previous old version wouldn't be encountered in that case. I can't think of any such examples off the top of my head, but that's like 15 releases behind current at this point.
-
I upgraded only to 2.0 release because I got an error and it would no longer boot.
Fetching file…
looking up mirror.myip.be
connecting to mirror.myip.be:80
requesting http://mirror.myip.be/pub/pfsense/updates/old/pfSense-Full-Update-2.2-RELEASE-i386.tgz
remote size / mtime: 81951329 / 1422058754
/root/firmware.tgz 100% of 78 MB 1634 kBps 00m00sFetching MD5...
looking up mirror.myip.be
connecting to mirror.myip.be:80
requesting http://mirror.myip.be/pub/pfsense/updates/old/pfSense-Full-Update-2.2-RELEASE-i386.tgz.md5
remote size / mtime: 82 / 1422058744
/root/firmware.tgz.md5 100% of 82 B 260 kBps
URL MD5: 0fbb3d11d82426ddace32c699067a937Downloaded file MD5: 0fbb3d11d82426ddace32c699067a937
MD5 checksum matches.
One moment please...
Broadcast Message from root@pf5.mydomain.com
(no tty) at 7:33 MST...Firmware upgrade in progress...
...Done. Rebooting...
*** Welcome to pfSense 2.2-RELEASE-pfSense (i386) on pf5 ***
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82LAN (lan) -> bge0 ->
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82
Warning: in_array() expects parameter 2 to be array, null given in /etc/inc/interfaces.inc on line 82WAN (wan) -> bge1 -> sockstat: struct xtcpcb size mismatch
sockstat: struct xinpcb size mismatch -
I cannot find out why this happened so am stuck at 2.0. Can anyone shed some light on what is happening and how I can safely upgrade all the way to current.
-
The errors at the end of that output are not a problem. They're old scripts trying to run new PHP, and also from a mismatched kernel/world – it should have been fine after a reboot. We'd need to see what it does after the reboot to help further. And as others have mentioned, stop trying to update to an interim release. If you want to stop at 2.2.x, use 2.2.6-RELEASE and not 2.2-RELEASE. We have fixed numerous upgrade bugs over the years and you're sidestepping that process by trying to upgrade to a release that potentially has known issues for zero benefit.
-
Well, I'm not trying to sidestep anything honestly and that's why I've asked for help in these forums because I don't have the knowledge that others configuring these things have :).
When the device would no longer boot, I didn't have much choice but to revert because it's a live network. I can't recall 100% but I think it locked up with the last message being usb related. Not 100% sure and didn't have time to spend on it.
Now, since I'm running 2.0 release, you figure I could simply go to 2.3 release and be fine now?
-
You may want to wait for 2.3.1 to drop in a few days rather than going to 2.3 right this moment, but yes, generally speaking it's best to go right to the most recent version.
You could also back up your config and simply install the new version fresh and restore the config rather than upgrading in-place if you're worried about that.
-
I wasn't sure if a backup from an old version would work but since you mention it does, then yes, that sounds like a plan.
I'll wait to see the new version then go ahead and upgrade or rebuild if upgrading didn't work.Thanks very much.
