I've had simliar issues with previous updates.  Now I always update the system using ssh with option 13 and it never fails there.

Sure enough, it's working now. Thanks!

@Gertjan: https://www.netgate.com/docs/sg-2220/connect-to-console.html You''re using a PC ? A COM port is present and you use it when starting Putty ? edit : Putty as a COM (serial or RS232) client won't help you much to clarify the situation. As per instructions,, Putty connects to a COM port (created by the driver that comes along with the Serial-to-USB cable - check that this COM port was created when the drivers was installed AND the cable is connected ) and will 'open' this port ans show on screen everything that's comes in. Bit rater, stop bits and other parity stuff becomes important, using the wrong settings on both sides of the COM port will produce rubbish at best, nothing at worst. From what I understand reading the doc "SG-2220", the BIOS will init his COM port with known settings : the settings on the PC COM port should match exactly. That's about it. Thanks Gertjan.  I found that while I couldn't access the console, I can see system logs as the PfSense is booting up. There appears to have been a different issue as well though - so I'm not sure how the whole solution got messed up this badly since I configured it initially.  Since I can access the boot menu, I tried to boot into single user mode to reset the password like that.  However, the mount command gave an error indicating that I need to run fsck.  I tried it using journaling first, which completed successfully but resulted in a kernel panic after I ran /etc/rc.initial.password.  That was yesterday.  This morning I gave it another shot without journaling, which worked.  I'm finally able to access the web interface again, but still no console if I connect after it booted.  It's weird.  It sounds like the plug has been pulled on it a couple of times though, resulting in a hard shutdown. Thanks again for your help, much appreciated!

There is no new logo in UI, only on login page, overall UI is the same as 2.3 You should ask your questions about 2.4 in appropriate forum https://forum.pfsense.org/index.php?board=69.0

2GB disk, partitioned by the original install - 1GB UFS and 1GB swap. I've got it going now by creating a new VM and restoring from a backup - only thing missing was the OpenVPN client export, but that was easy to fix  :)

My upgrade from 2.3.4 went fine too. I'm running pfsense on VMWare 6.5.

@Blade1: …  I give a private IP for the LAN interface, e.g. 11.0.0.1, which can be pinged from pfsense. However, 11.0.0.1 is private ??

Sorry, newbie mistake. My status dashboard indicates install of the amd64 version and shows 4 CPUs: 1 package(s) x 4 core(s).

Hey biggsy I checked and no errors at the moment. But I did revert back to using the realtek as the WAN and the HP as LAN due to performance issues. So right now I'm only using one of the two dual ports and things are working well again.  So I'm not using the HP nic for WAN and LAN. When I get a chance I'll try re-configuring the interfaces to use only the HP dual nic for LAN and WAN and then checking STATUS > INTERFACES again. Thanks

@potentialcustomer: do I simply plug it in, plug in my destination USB key,  boot off the installer and then install to the destination key? Yes. You could gmirror across two USB drives. Or even ZFS across them in 2.4Beta if you wanted. Running from USB is not recommended though. Fine for a test as you said though. Nano is not particularly limited in 2.3.X. It will probably do all you need to test out pfSense. Steve

I cannot say for curtain but I suspect that during the upgrade the settings of wan somehow got messed up. In the WAN settings of the GUI I did not see anything odd. So I reset the pfs, exported the default settings which are ok for me. Compared them with the xml export of the troubled config and just replaced the WAN part of the default export file with my export file which was quite different. Now all my wan problems are solved without having to reconfigure everything from scratch. Cheers

@beremonavabi: I'm assuming by "update all client devices with the latest version of OpenVPN," that means (in my case) the OpenVPN for Android app I installed on my Android phones.  Since the phones automatically updated that and the "What's New" for the app says it fixed CVE-2017-7508, CVE-2017-7520, CVE-2017-7521, and CVE-2017-7522, I again assume I don't have to do anything with the phone app. Correct. @beremonavabi: But, do I have to re-export the profiles from pfSense (I originally exported the Inline Configurations for Android and pointed OpenVPN for Android on the phones at them)? No, the settings are the same it's the client itself that needed an update. Only Windows users who wanted to install the latest version using the export package needed to export anything again.

Thank you all, Finally made it Thanks for all your help along with the following posts https://forum.pfsense.org/index.php?topic=130307.msg718833#msg718833 https://www.hexhound.com/how-to-flash-pfsense-2-1-to-a-watchguard-firebox-x750e-x550e-ssl-500/ Thanks Alex

As mentioned above. It is always best practice to backup your config before updating! Now all that aside. You said "not booting" what is it displaying during the boot cycle? Can you connect directly to a display interface and see what it is doing via a monitor? I saw another post by you that included a screenshot. Is that what is being shown once device has booted? Right away I see WAN is not configured anymore but LAN is active. In that state you should be able to access GUI locally. However, if that is not working, have you tried to reset the interfaces or reassign them? Reset the modem to reobtain a WAN? I'm also a little confused on why you would need to spend another $100 dollars for a stock image? Couldn't you just redownload PFSense directly from PFSense website and reinstall using a USB thumb drive for free? or is there something I'm missing here? Does this unit require some vendor drivers etc….? If you are talking about reobtaining backup image from PFSense Gold, well its only $100, they is very cheap compared to other services out there in the real world. However, couldn't you just do a factory reset on your unit? Have you tried a factory reset within PFSense GUI or via the physical button on the device? We need a little more information in order to properly help.

What exact error are you seeing? The two threads you posted in have slightly different messages listed. What harddrives are you using? What raid controller? Steve

Then i should install 2nd NIC because I dont have VLAN capable switch  :D Thanks for response. :)

Apparently pfSense just doesn't like some drives. Took out the Kingston and put in a LiteOn, and it loaded just fine. That Kingston worked fine when this was my media PC. shrug

Having the same problem. Trying to install from USB on a Shuttle DS68U with a Skylake family CPU (Celeron 3855U). Tried several USB stick but it's always the same… SLOW. 2.3.4 Release BTW

ticket filed https://redmine.pfsense.org/issues/7697 Thanks for the help and the fix.