https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USB

If you see two drives, the system must contain an mSATA SSD along with the default eMMC drive. Did you add an mSATA disk yourself? Normally when we ship a system with mSATA, the eMMC remains blank. You only need to worry about upgrading the version on the disk that firewall boots and runs from. The other disk wouldn't be used.

Yes, now is a good time to learn how to connect something to the console.

I'd just like to thank you guys for your input. I've managed to get it working near perfect and I've been learning the ins and outs. I have a small issue with putting it behind a Server 2012 with Active Directory as the DNS doesn't want to play nice. I made a root hints only and that wasn't working so I just made a forward only zone and I'm able to see it but can't connect a client PC at the moment. I'll keep chugging away. Thank you again, I truly appreciate it.

Gravedigging this to note that it seems that PFSense 2.4 will be the release that is based on FreeBSD11, meaning it should finally be able to install to/boot from NVMe storage at that point.

I did a restore of the config.xml on the new VM not on the old. I backuped the config.xml via scp and did a full install and restored. It's the new VM that failed. It was the config.xml itself that was problematic. Something got wrong at the upgrade.

https://doc.pfsense.org/index.php/Multi-WAN is good and current information. Read that, try it, then ask if you are stuck.

Because you had a rip in the space time continuum? ;) your clock on your device was OFF would be my guess..

Can you ping them if you select LAN as source there? If so the NAT is working fine and you probably have a firewall rule missing somewhere. If you;re using policy routing to send packets to a gateway grouyp you will need a firewall rule above that to bypass it to reach the modem interfaces. Steve

Thanks for the update.  :) Steve

Yeah, I learned the hard way: Panic-ville. Hair on fire. Naked running through the campus. All that.  :D IBOX-501(N10a) Intel J1900 Quad Core 2.0Ghz 1SO-DIMM, support 1333/1066Mhz, DDR3L(1.3V low power), 4GB AMIBIOS 32MBit 4IntelWG82583 10/100/1000M Lan 32GB SSD Pretty much like this one: https://www.amazon.com/Firewall-Micro-Appliance-Gigabit-Barebone/dp/B01GIVQI3M/ The hardest lessons learned are the hardest to forget

You could probably write the install image to a SATA hard drive and boot from that. Then install to mSATA. Or if you can boot anything at all (some Linux distro from ISO) you can boot that then download the installer image and DD it to the on-board eMMC. Then boot from that an install to mSATA. Steve

The libcurl.so.4 should be reinstalled by curl as indicated by pkg its installed as a part of that: pkg which /usr/local/lib/libcurl.so.4 When i rename that file curl complains with the same error as you have, when i reinstall curl with previous command it works again.. For my test anyhow.. Not sure what else to try, maybe reinstall 'everything'?: pkg-static unlock pfSense-kernel-pfSense pkg-static upgrade -f

I installed a proxy with squid, squidguard and sarg. But blacklist management is not for everyone and reports are bad.