2.3.5 Upgrade risk management
-
The hardware in question is an Intel D2500CC Atom processor with Intel NICs. This is a big jump to 2.6.0 and I wanted to have a backup plan as recommended in case the hardware didn't quite support it. I have kept some old images, but of course 2.3.5 isn't one of them. I'd appreciate if someone could connect me with that image. Hopefully I won't have to use it. I read the upgrade guide and it's enough to make me nervous.
-
@driver8 said in 2.3.5 Upgrade risk management:
The hardware in question is an Intel D2500CC Atom processor with Intel NICs. This is a big jump to 2.6.0 and I wanted to have a backup plan as recommended in case the hardware didn't quite support it. I have kept some old images, but of course 2.3.5 isn't one of them. I'd appreciate if someone could connect me with that image. Hopefully I won't have to use it. I read the upgrade guide and it's enough to make me nervous.
I wouldn't trust anyone with 2.3.5 off the internet... Assuming your device has an SSD or HDD you could image them using DD on another machine and then install 2.6 and apply your config and see if it works and if it doesn't restore the image.
Or get another SSD/HDD and use that. That is what I would do if it was possible.
-
2.3.5 might be a 32bit install as well. If so it will need to be reinstalled, you cannot upgrade that to a 64bit version.
Steve
-
@stephenw10
You may be right. The previous install filename was pfSense-CE-2.3.2-RELEASE-i386.iso, which followed by over the air updates to 2.3.5. There was some argument at the time about whether the Atom D2500 could support the 64 bit CE version. Someone back then said it could, but the Intel supported OS matrix says only 32 bit Win7 could be supported. Looking for modern posts on this, all I could find was some issue with VGA but there was a work-around. Maybe the key question is whether 2.6.0 can even run on this processor now. -
It's a 64bit CPU I would certainly expect it run 2.6.
Try booting the 2.6 memstick installer, it will be pretty obvious if it can't run 64bit for some reason.
-
@stephenw10
Results: Reinstallation of 2.6.0 on this hardware went smoothly with packages removed beforehand. Restore of prior config from 2.3.5 - no problems detected so far. Backup imaging of the drive was a pain though, took 6 hours with an old version of Clonezilla. Thank you for your inputs.
