Simplest way is to use the 2.2.3 installation CD or USB stick. Download the image you need from here: https://www.pfsense.org/download/ The installation process will do all the reformatting for you.

Restored 2.2.1 last evening: been running for 17 hours now; all problems gone again.

@Dadoo: Update: the message in the Version box (on the dashboard) has gone away (even though we haven't changed anything), but now it's taking a very long time (maybe 30 seconds) to get past the login screen, after entering the password. I've checked DNS, to make sure it's working. What else might cause such a long delay? I also discovered, this morning, that we lost a couple of rules. We just needed to re-enter them, but I'm not sure why the update would have deleted them, in the first place. Did you get any notices at the top of your screen?  If you did, chances are it may have said something like "reverting to backup configuration" or something, which is why you lost your rules.  This, assuming you got that notice.

Thanks for the confirmation that this is by design and not a bug. I just wasn't expecting it.

Fixed, thanks.

Great, Many thanks

There isn't enough information here to go by. Is this a full install or NanoBSD? Or is it running live from CD/Memstick? If it is a full install you can edit /etc/fstab to change where it is looking for the root slice, but from the text in the error I'm not certain that's what is happening.

@Mr.: Something must have changed; It just rolled back 2.2.3 to 2.2.1: it did automatically reboot. https://redmine.pfsense.org/issues/4107

This ZFS noise is completely safe to ignore… ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behaviour

Thanks, JIMP, for answering my question clearly and completely. I didn't even think of looking for a "support" e-mail address, as there has always been a lot of great answers in the forums.  I also felt that the answers might be helpful to others who want to support pfSense by migrating from something home-built to a box purchased from pfSense.  I'll be sure and e-mail future questions to the support e-mail address. Now I can put the new SG-2440 into service. Thanks again, Frank

@derringer66: Do I use the standard 64-bit firmware update URL or do I wait for an update on https://firmware.netgate.com/auto-update/ADI/amd64? You should wait for the official factory image to show up there and/or on the portal site that you can see once you login. These and other questions should always come in to customersupport@pfsense.org – we don't always monitor the forum closely for customer requests such as these and to ensure that you receive a timely and appropriate response, it is best to use the official support channels. Basic questions like this do not count as support incidents, so there isn't any worry about expending any support time on such things.

MCA: CPU 0 UNCOR PCC BUSLG Source ERR Other panic: Unrecoverable machine check exception Not good. https://en.wikipedia.org/wiki/Machine-check_exception Overheating or bad CPU.

does this list help? http://www.hobit.co.uk/settings.pdf or http://www.bestrouter.co.uk/articles/uk-isp-adsl-settings finally http://www.onesourcecommunications.co.uk/uk-dsl-service-providers-setting-list/

ok, got it.  It isn't clear, but after going to Dowloads and clicking "Show me the mirrors" in the text paragraph at the bottom, it took me to the file list. Thanks for the help everyone. 70tas

[Solved] –> See: https://forum.pfsense.org/index.php?topic=95837.0 Had to remove the sync-option from /etc/fstab

I ran into a similar situation when I was trying to save the config file directly with the web interface based file editor. Also got the same when I tried to replace the file manually on the file system with another one, uploaded with SFTP. It looks like there's a process "watching" this file when it's being modified from outside, and instead accepting the modifications, it deletes it and it tries to restore something from a backup. The problem is, that: if the backup doesn't contain a valid file, the result will be an empty file the user doesn't have a chance to override this behaviour. It may be very well that somebody wants to do this on purpose, and fighting against the system is not something pleasant to do.

you can ping the wan address from the lan side with the default rules. Not sure what a proxy service has to do with icmp? Sounds like to me he put a gateway on the "lan" which I just am blown away at how many times that comes up..  And yup will break it pretty bad..