Upgrading from 2.0.3 to 2.1.4 and adding a second disk
-
I have a 2.0.3 box with a single harddrive.
I would like to upgrade to 2.1.4 and add a second harddrive for a mirror.Q1 - Can I create the mirror before or after the upgrade, or do I need to re-install from scratch?
Q2 - Also, if I upgrade, would there be any default settings in 2.1.4 that will be overwritten by my current config that may have been of benefit to me?
Q3 – If I choose to re-install from scratch, is there a way to export my current config in a human readable (not XML) format?
-
1. Don't know, never tried.
2. Not that I'm aware of. Any new settings will not be overwritten by using an older config. Of course if you've made any changes to defaults yourself they will be overwritten.
3. All of the pfSense config is already stored in a single, human readable, xml file. /conf/config.xml. You can easily export it using Diagnostics: Bakcup: in the webgui. You can also restore your config from there.
Steve
-
Q1 - Can I create the mirror before or after the upgrade, or do I need to re-install from scratch?
Though technically possible it results in an invalid mirror since the gmirror metadata would be written in the last few sectors of the active disk partition, partially corrupting the disk. Though usually harmless, it's not recommended. Reinstalling from CD is best, as the gmirror option is built into the installer.
Q2 - Also, if I upgrade, would there be any default settings in 2.1.4 that will be overwritten by my current config that may have been of benefit to me?
Lots of changes between 2.0.x and 2.1.x, including some default option changes, you'll have to review the release notes of all the releases between what you have now and the current release. There are some (e.g. Allow IPv6, Prefer old IPsec SA, Disable Login Autocomplete, state killing on gateway failure) which changed and you may or may not want them.
Q3 – If I choose to re-install from scratch, is there a way to export my current config in a human readable (not XML) format?
XML is the only way to export. Diagnostics > Backup/Restore.
It's about as "human readable" as you can get though. It's not encoded or obscured like some others do. -
Hmm, not quite sure what I was thinking when I replied earlier. One coffee too many perhaps!
Clearly I misread the question anyway so thanks Jim for correcting that. :)Steve
-
Thanks for the awesome answers.
I ended up re-installing from scratch with a mirror, and everything is working great so far.Not sure if this is the right place for a feature request, but…
A way to export the current config in a more readable format would be awesome for documentation purposes. -
It's unlikely to be a priority for the devs but what sort of format do you suggest?
I guess someone could write a script that converted the config file fairly easily.Steve
-
Maybe a nice TXT or PDF report with a section for each service.
For example, the DHCP section would list the config settings and any reservations.
The Firewall section, would list all the rules. So on and so forth.