Upgrade path to 2.4 alpha from 2.3.2 release?
-
I cloned a working vm of 2.3.2 release and want to try upgrading to 2.4alpha with it. However, when I enable developer branch, it's only upgrading to 2.3.3.
What is the recommended upgrade method to get to 2.4? Or is the recommendation to start fresh and reconfigure by hand?
You can always backup config from 2.3.2/2.3.3 and import it on a brand new 2.4 install :)
-
We don't yet have a working upgrade process that can cross into 2.4 yet, there are some limitations of the upgrade procedure and pkg that are making it challenging. We're almost there, though.
Easiest and quickest way at the moment is to backup, wipe and reload, then restore. If you have enough RAM you'll want to do that anyhow so you get ZFS!
-
Do you get a choice of filesystems during install or is ZFS just installed by default?
-
Yes, you can choose the type of filesystem.
We don't have any concrete guidelines yet but you won't want to use ZFS if you have low amounts of RAM
-
Would the 4GB that comes on the 2440 be sufficient?
-
That should be fine (depending on the size of your disk and other things using RAM)
-
Ok. I've had a number of units experience corruption after power failures and subsequently refuse to boot without a pave/reinstall (similar to #6340. So I'm looking for something more reliable to save on truck rolls—hopefully ZFS will be the ticket.
While I'm on the subject of that corruption- I captured some debug output after the last time this happened (last week) which was from a 2.3.2 unit. Is that worth sending in anywhere, or is this a known problem / no more info needed?
-
I assume one or two truck rolls would pay off a UPS.
-
To be honest most of the time the problem is other people messing around with my equipment. A security vendor will come in to install a DVR and he will "need to move the power cables around to make room" or some other such nonsense and I will find he has unplugged our stuff. This happens more often than you would think. Yes a UPS is nice to have and does help in certain situations, but the human factor is always there ready to destroy even the best laid plans.
-
To be honest most of the time the problem is other people messing around with my equipment.
Hard wire and silicone. ;D
-
Ok. I've had a number of units experience corruption after power failures and subsequently refuse to boot without a pave/reinstall (similar to #6340. So I'm looking for something more reliable to save on truck rolls—hopefully ZFS will be the ticket.
While I'm on the subject of that corruption- I captured some debug output after the last time this happened (last week) which was from a 2.3.2 unit. Is that worth sending in anywhere, or is this a known problem / no more info needed?
redmine.pfsense.org open a bug, attach files. Thank you!
-
Will do. Does it matter if 2.3.2_1 has been released since then? I don't think any changes were made with regard to filesystem…..
-
no, it won't.
-
Have had those crash output files sitting on my laptop for a month and I got tired of seeing them staring back at me so I finally opened a redmine. Not sure they are relevant anymore now that we are a bit closer to ZFS + 2.4. But FWIW, https://redmine.pfsense.org/issues/6891
-
Thank you.
-
Curious if an upgrade path is in place yet? :)
-
Set it to upgrade to 2.3.3, then upgrade, then set it to upgrade to 2.4, then upgrade
-
Thanks Jim!
:)
-
While 2.4 isn't alpha anymore, the following posts might help people upgrading from 2.3.X to 2.4.X:
https://forum.pfsense.org/index.php?topic=140169.0
