SOLVED: Upgrading from 2.2 RC
-
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! -
I keep getting errors like 'forbidden' and not being allowed to share an image or links that are completely about this thread.
I found this here but am not sure about the validity.
http://mirror.transip.net/pfsense/downloads/
-
@lewis said in Upgrading from 2.2 RC:
I mentioned I don't have any way of knowing. My guess, 7-10 years old.
Use Google or your favorite search engine; however, if it's 7 - 10yrs, I can tell you that the hardware in my signature was made in 2013 and is able to run pfSense 2.6 or plus no problem. Of course, I upgraded the hard drive to SSD and 32GB RAM. My latest pfSense private cloud implementation is a Dell Precision 3630MT made in 2018.
-
All of this is silly. If one doesn't have physical access to the device, one has no business loading anything on it.
I get saving money. I get using old hardware. Of course old hardware will work.
None of this matters though ... if it isn't the current firewall ... well eventually somebody needs to move wires around. Loading it remotely via kvm is neat...but you need to get access eventually. Best arrange physical access now. Dedicate a couple days to it. ...assuming we're volunteering somehow... as literally any time spent on site, and indeed your efforts thus far...should have far out-spent the cost of simply buying the right piece of hardware.
Still...need to get physical access eventually...might as well do it now.
-
What is the price of two USB sticks as today?
I got two of them, theSanDisk 64GB Ultra USB Flash Drive USB 3.0
and the
SanDisk 64GB Ultra USB Flash Drive USB 2.0
each for 9 € over amazon.de. You can send them
by postal express mail to the point where your pfSense
is standing and it will be arriving in one or two days else where, pending on the given distance. As today it would be not the problem that someone is stitching it in and
call you by phone.You should follow the tip from @stephenw10 and try out the vga image. There are three images out for installation.
DVD ISO
pfSense-CE-2.6.0-RELEASE-amd64.iso.gzUSB (serial console)
pfSense-CE-memstick-serial-2.6.0-RELEASE-amd64.img.gzUSB (vga console)
pfSense-CE-memstick-2.6.0-RELEASE-amd64.img.gzI would try out to save the config backup and then
installing it new (fresh install) with 2.6 and play back
the config. -
The fact you are able to try booting an ISO remotely tells me you're using the SM IPMI. Is that true?
Booting from that has given problems in the past especially if the IPMI version on the unit is old.
My recommendation is to use the 2.6 memstick-vga image written to a USB drive local to the firewall. That's by far the most likely option to work.
Steve
-
@stephenw10 said in Upgrading from 2.2 RC:
Booting from that has given problems in the past especially if the IPMI version on the unit is old.
I'd assume that's the problem. I have an older box running around with an SM-IPMI and I never got remote ISO mounting running in the first place as it always broke half way through. So no, these aren't the most reliant and OP should really get a USB stick to the box and just run it from there!
@lewis said in Upgrading from 2.2 RC:
Why??? Why is netgate doing that? So much useful old hardware out there that can be used as firewalls.
I don't even understand your "why"? That note only said that the old live-iso is deprecated and vanished. But the normal ISO is still around and working just fine. Why get the panties in a knot over a stone-old live-CD ISO? Don't get it. As of those comments about so many hardware out there - yeah there is. So? Check if it's 64bit and the HW works with the current version, take your USB memstick with a 2.6 memstick image on it and bring them online! No one's deprecating old boxes besides those stone old 32bit only boxes or the one with bad MoBos that only ran in 32bit mode. Nothing to cry over.
Cheers
-
Panties in a knot? LOL. Talk about a childish statement. Please, take your drama to someone else's post.
The box is not 32bit, I shared the CPU info and what little info I have :).Several of the things pointed out in the last few posts were already covered earlier. If they were not, simply ask for clarity and I'll be happy to respond.
I would try out to save the config backup and then
installing it new (fresh install) with 2.6 and play back
the config.There is no config to save. This is an install issue. 2.6.0 was tried, as were several others all the way down to 1.2.3 out of curiosity at that point. 1.2.3 actually installed.
Not sure that anyone said usb sticks being too expensive. Usb sticks were tried. Someone mentioned using cheap sticks might cause a problem. The exact same problem shows up using virtual cdrom as well.
When you are remote to something, you have little choice but to count on what the folks who are physically there can do for you. My challenge is just trying to find a way to install pfsense onto an older server that for all intents and purposes should work.
I've been able to install pfsense on countless servers, old and new. Some fought me the entire time while some were just finicky but I've always had them physically. This is not the case so I have to work with that I've got.
BTW, the BIOS was fully upgraded yesterday and the problem remains.
The usb image also doesn't work. I might try one more time and share an image. I took several images but I lost track of which were what at this stage. I was using each at the time to try and remember what the installer was showing for errors. Happy to share those if anyone's interested. -
You see the same error booting the 2.6 USB image from a local USB drive?
What devices are shown when you enter
?at the mountroot> prompt?
