SOLVED: Upgrading from 2.2 RC
-
@lewis wouldn't it be better to troubleshoot or bring to netgate attention that current 2.6 doesn't install so can be worked out why vs installing a RC version from what like late 2014 or like Jan 2015? Where did you even get 2.2RC install media?
I am with @heper here - why would current not install, what sort of errors were you seeing?
I would suggest install 2.6, and if it fails post up specific on your hardware, and the errors your seeing..
I don't even believe 2.3 is available, 2.2 sure shouldn't be - what would be the upgrade path from such an old version even if was latest 2.2 line which was 2.2.6.. When the previous versions are no longer available, pretty sure netgates policy is to remove old versions.. The current supported lines are really the only ones available..
-
Hmm, the OP makes it sound like they tried current versions and and could not get that to install.
Some time last year I tested upgrading from 2.1.5 and was able to get to 2.6. Eventually. But it's pretty tortuous.
There are a few places you need to refresh the update page several times and/or switch the update repo back and forth to allow it to 'see' the next step. I would not recommend it!What update branches does it show as available?
Steve
-
I tried updating my first post but the site would not let me. I've been here a while now, obviously not a spammer so why still limited?
Anyways, it's an old supermicro server in a remote equipment room. There's no physical access to it and all I have is IP KVM to work with it. It needs to be converted to a pfsense firewall.
Does that device pass basic diagnostics (memtest or builtin )
Is this a new device or a very old one?
Is the bios up to date?
Uefi or legacy? Did you try to switch between?No idea, the BIOS is locked and from remote, I can't get into it.
@lewis wouldn't it be better to troubleshoot or bring to netgate attention
that current 2.6 doesn't install so can be worked out why vs installing a RC >version from what like late 2014 or like Jan 2015? Where did you even get >2.2RC install media?There would be nothing useful to provide.
I started with the newest all the way back to 1.2.3, every single one of them gave me the same/similar 'error 19'. I did everything possible to try to mount/boot the installer but never could.
Then I tried a livecd 2.2 and miraculously, that finally installed so since then I've been trying to find a newer livecd but they are removed from this site.
I am with @heper here - why would current not install, what sort of errors >were you seeing?
Every one that I tried did a similar thing.
I tried usb and virtual CD and all of them gave me a similar error. I looked online trying countless things people suggested and nothing worked.
I don't even believe 2.3 is available, 2.2 sure shouldn't be - what
would be the upgrade path from such an old versionThat wasn't the goal :). As I said, I tried from new to old trying to find a way. Once I was able to get this old version on, I thought maybe there might be an upgrade path.
The current supported lines are really the only ones available..
Since livecd worked, that's what I've been trying to find but have yet to find any newer ones.
As for where I found them, old CD's I've made over the years, converted to ISO to try.
So really the question is, where can I get some livecd versions that still have an upgrade path.
BTW, the fact that the installer may not work is not an indicator that the hardware is useless. I've gone through this countless times where I fought and fought to get pfsense installed and the machine became a useful firewalll, some still running to this day on old hardware and doing very well.
-
Installing remote via IPMI on SM hardware has always been a PITA. I assume you cannot try to install from a USB attached to it physically?
-
I just found this note on the net.
https://livecdlist.com/pfsense/ While the pfSense project continues, it is no longer available in LiveCD form after version 2.2.6. LiveCDs images were dropped in version 2.3 according to https://doc.pfsense.org/index.php?title=2.3_New_Features_and_Changes#Security.2FErrataWhy??? Why is netgate doing that? So much useful old hardware out there that can be used as firewalls.
-
@stephenw10 I did get to try USB but it was the same, error 19.
-
With that same CAM error? That just looks like a bad USB stick. Or possibly a bad port.
Retiring the live CD should not have restricted the hardware that can be installed to. It's only the quirkiness of the SM that gets in the way here.
What hardware is it exactly?
-
@stephenw10 said in Upgrading from 2.2 RC:
With that same CAM error? That just looks like a bad USB stick. Or possibly a bad port.
Retiring the live CD should not have restricted the hardware that can be installed to. It's only the quirkiness of the SM that gets in the way here.
What hardware is it exactly?
I don't know the exact model since I can't get into the BIOS and the KVM doesn't show that info.
CPU however is E3-1230v2 (3.3Ghz Quad Core + HT).
Standard enterprise blade in a chassis but that's all the info I can get.
I could try again using a newer version and post as I go if anyone is willing to stick with this. Maybe it can help netgate or maybe it's wasted time to them.This was the first version I started with; pfSense-CE-2.6.0-RELEASE-amd64.iso
-
Using the ISO via IPMI introduces a bunch of potential issues there.
If you can I would first try the 2.6 vga memstick image on a local USB stick. If that fails to boot the error output would be more useful.If it stops ate the mountroot> prompt what devices are shown hen you enter
?.Steve
-
@stephenw10 The problem is that there is no way to scroll back using the IP KVM so I'm limited to trying to catch what ever I can by eye in a fraction of the second to the end where I can take a screen shot.
Is there a version you'd like me to try specifically? Can you share the URL and I'll see if I can get a usb image done.
I have a much better chance of getting an iso virtually mounted than getting a usb stick prepped.
-
@lewis said in Upgrading from 2.2 RC:
Why??? Why is netgate doing that?
When hardware no longer meets standard as well as mitigate known risk and security vulnerability, it's unreasonable to expect continuation...it's not just Netgate, Apple, Microsoft, Linux, FreeBSD, Cisco, Sonicwall, Mikrotik, you name it. A common practice is the moment you buy hardware is the moment you start saving for the day it becomes obsolete, three years for business, five years for home/office/lab.
-
@nollipfsense I don't agree and in fact, I think it's irresponsible.
If you search the net, you'll come across many asking why they can no longer use some old hardware.
I've gotten pfsense running current versions on tons of old hardware that works just fine. That said, I also have it running on new hardware too.
As human beings, we need to stop junking so much stuff and try to re-use as much as possible.
-
I have this mounted now;
pfSense-CE-2.6.0-RELEASE-amd64.iso -
@lewis said in Upgrading from 2.2 RC:
use some old hardware.
You didn't define...is it 10yrs, 20yrs, 30yrs, 50yrs? Things change for continuous improvement whether you agree or not. Maybe create your own entire hardware that will last 100yrs is the solution for you.
-
This post is deleted! -
@nollipfsense said in Upgrading from 2.2 RC:
@lewis said in Upgrading from 2.2 RC:
use some old hardware.
You didn't define...is it 10yrs, 20yrs, 30yrs, 50yrs? Things change for continuous improvement whether you agree or not. Maybe create your own entire hardware that will last 100yrs is the solution for you.
I mentioned I don't have any way of knowing. My guess, 7-10 years old.
I do agree with improvement, I use both new and old but like to re-purpose old for as long as possible.In some cases, people are trying to survive with little money so have to use really old hardware as they cannot afford new hardware.
-
This post is deleted! -
As I mentioned, I still have the 2.6.0 mounted now.
Should I give it a try and share what ever I can? -
@lewis I would if Steve is still around - he is the guru when it comes to stuff like getting pfsense installed on hardware.
-
This post is deleted!
