Weekend? This takes about 10 minutes, reinstall and restore the configuration backup.

Turned out to be pretty simple.  IPCop hosts table extracts easily into a comma delimited format and that can be converted into the XML of the XML layout of the backup file, that can then be restored. (I don't know how to format code on this board, so forgive me..) Simple batch job to do the conversion, then paste the output in between the appropriate sections of the backup file, then restore. I think the biggest issue here is that I couldn't find anything on this because I couldn't figure out appropriate keywords for searches. I know someone else has had this issue before and already solved it… #!/bin/ksh -x INFILE=$1 OUTFILE=$2 for LINE in cat $INFILE do IP=echo $LINE | cut -f1 -d, HOST=echo $LINE | cut -f2 -d, DOMAIN=echo $LINE | cut -f3 -d, print "\t<hosts>" >> $OUTFILE print "\t\t<host>$HOST</host>" >> $OUTFILE print "\t\t<domain>$DOMAIN</domain>" >> $OUTFILE print "\t\t<ip>$IP</ip>" >>$OUTFILE print "\t\t<descr>" >> $OUTFILE print "\t\t<aliases>" >> $OUTFILE print "\t</aliases></descr></hosts>" >> $OUTFILE done

Downgraded to 2.2.1 and no sync as well, Will downgrade to 2.2 and test

I'd just like to give an update to my problem as I've finally able to install 2.2 onto my system. I had tinkered with the SCSI drives, cables, assortment of system tunables, boot loader configs, etc but nothing helped. I was able to reinstall 2.1.5 just fine, but somehow when it comes to 2.2 the system would get stuck at that dreaded "bsdlabel" command. Then one fine morning when the system booted up with the 2.2. Install CD, I noticed something odd with how 2.2 reported the transfer rates of the two SCSI disks attached to the Adaptec controller. It reported the SCSI disks as having a transfer rate of about 11MB/s. I can't remember how it was reported under 2.1.5, but I have a SCSI-2 disk there, which should give me a transfer rate of 20MB/s. But I also knew pfSense loaded the correct disk driver (ahc) for it. And so, I went to the SCSI BIOS and had a look at what I could change so that pfSense 'detects' the appropriate transfer rate. Under the Adaptec SCSI BIOS, the "Initiate Wide Negotiation" was set at a default of "Yes" and at the default transfer rate of 40MB/s. I disabled the setting by selecting "No" and with that the maximum default transfer rate went down to 20MB/s (the 40MB/s option was no longer there). With the above setting in the SCSI BIOS, the installation was no longer stuck at bsdlabel (in fact, the command just did it's thing within a second as it should) and I was able to complete the installation of 2.2 and restored the config. Hope this help someone with a similar setup and issue.

No idea what the problem was. I reinstalled 2.2.1 and restored a config backup so now I'm back to square one. I think I'll refrain from upgrading to 2.2.2 for a bit.

Hello again, Well, a big THANK YOU for the replies. Disabled serial port 1 and 2 in BIOS and have rebooted a few times from both slice one and slice two. The only thing now is to re-do all the settings but that's a trade off I'm happy to pay. Thanks again. Marked as resolved.

I finally got around to trying this today. It booted and ran 2.1.5 just fine, and I had it auto-update to 2.2.2.  Upon rebooting, it had the same ATA problem and didn't boot. Back to the CF card with M0n0wall for now…

They will hang onto the existing state. Did you make sure the checkbox under advanced, misc 'State Killing on Gateway Failure' is unchecked? Also make sure the provider is allowing the phones to register from the WAN2 IP.

https://forum.pfsense.org/index.php?topic=88031.0 https://forum.pfsense.org/index.php?topic=87813.msg483500#msg483500 This should really be in the upgrade notes…

cmb, seems that NanoBSD images are affected too: https://forum.pfsense.org/index.php?topic=93010.0 Can you please update these too with the appropriate change?

Do a full install, not nano.

Yeah, that was my first thought but that's been fixed since 21st Apr so if you only updated yesterday you should not be running into that. Odd. Steve

More information please. What hardware are you running? NIC types especially? Are you able to access the primary after rebooting it? It goes back to being the backup after a few hours again? Steve

It only asks you if you want to configure DHCP on LAN if you use menu option 2 to re-assign the IP addresses after pfSense is already setup. At the initial interface assign screen on first boot it does not. Edit: Hmm, I was sure about this until just now…  ;) Steve

Just another data point.  pfsense nanobsd 4GB vga v2.2.2.  Adding hint.agp.0.disabled=1 as a boot option worked for me as well to get my Intel Pro/1000 and Realtek Onboard NIC to be recognized in pfsense.  I also agree that this fix may (depending on frequency and scale) need to be added to the https://doc.pfsense.org/index.php/Boot_Troubleshooting section on the wiki. Neither my Intel Pro/1000 (em0) nor Realtek 8111E (re0) were available as WAN/LAN NICs in pfsense but the FreeBSD boot process showed unable to attach the device for both of them: em0: Setup of Shared code failed device_attach: em0 attach returned 6 My hardware is as follows: Intel Desktop Board D525MW (running latest BIOS, 0132) http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-d525mw.html?wapkw=d525mw Intel Atom D525 http://ark.intel.com/products/49490/Intel-Atom-Processor-D525-1M-Cache-1_80-GHz Standard 4GB USB key - booting from USB running pfsense nanobsd 4GB vga v2.2.2

MySQL can enable is there, but  I need MySQLi, I'm trying to see what else I need, maybe some libraries but not much debug info I have, if some else  have something to add I will appreciated. Thanks Gertjan.