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.

Good to see the 2.2.3 snapshots just appeared after I made my post above. On the front page at http://snapshots.pfsense.org/ you could now s/2.2.2/2.2.3/

luck is my baddy today :) thx again. solved it

IMHO the CARP interfaces/IPs should be used for what they've been designed. Agree. It was just an upgrade issue - in 2.1.5 worked, in 2.2.2 without tuning - not. In any case I would not qualify this as an error in pfSense :)

i can confirm that solved it, probably it should be set as default in the config

@clusty: I got this working only with Putty under windoze as a serial console. All others I've tried […] give me garbaged output Coming from a Windows world myself I know what you're saying. Been there, … There's puTTY for OS X which works reasonably well (but needs X11). Currently I use ZOC in OS X which works great. I also have a Win7 VM where I use Tera Term frequently.