Really big problem to go to 2.2.2 from 2.2.1
-
Dear Guys
Yesterday after this tragic error I had to be quick in decision, because here we have many workstations and all were stoped! So I quickly re-installed pfSense 2.2.1 and restored the backup, so everything is working again. So today I decided to upgrade to 2.2.2 again and the error happened again…. so, now i've disabled the serial port on the pfSense setup and the system boot normally. Thank you all. Here the image of the error, the letters write very slowly!
Cheers
-
If the boot menu is fast, press option 3 to go to a loader prompt, then type
unset boot_serial boot -
Hi Jimp,
Yes nice tip! also to fix the problem I commented lines in /boot/loader.conf
##boot_serial="YES"
##comconsole_speed="9600"Cheers, thank you !!!
-
This issue can be also mitigated by connecting a compatible serial console to match the speed:
-
Same problems here, disabling serial fixed for me. Dell Vostro 230.
-
Yet another day of me be glad I am not using equipment with serial console… (-:
-
Every box we ship has a serial console and near as we can tell from the testing, they're all fine, though we enable the serial console and force it on, since the serial console is the only console on most of these units.
Problem seems to be if specific to certain hardware combinations and only those that both have a hardware serial port and also have it disabled.
-
I had a serial port enabled, with a GPS connected to provide PPS for NTP, and it did impact me. I disabled the serial interface to get it to boot, but without it, my NTP lost the ability to sync with the GPS.
-
For those on 2.2.2 who have managed to get booted, try applying this fix:
https://github.com/pfsense/pfsense/commit/eee053fe10fe2857f7a6921f893d66a86f090b92 -
For those on 2.2.2 who have managed to get booted, try applying this fix:
https://git.pfmechanics.com/pfsense/pfsense/commit/eee053fe10fe2857f7a6921f893d66a86f090b92That (presumably internal) URL is unreachable.
-
-
Same problem here.
HA Setup with 2 different mainboards, on both systems I had to disable the serial console in the bios to boot the systems.
-
Just wanted to report that I got the same problem. Luckily I'd read this post before upgrading so I connected my normally headless box to a screen before upgrading. When I saw the slow character-by-character boot I rebooted, entered bios and disabled the com port. Booted normally and upgraded my packages and all seems well now.
-
For those on 2.2.2 who have managed to get booted, try applying this fix:
https://github.com/pfsense/pfsense/commit/eee053fe10fe2857f7a6921f893d66a86f090b92I was finally able to replicate this on an old VIA CV700A and confirmed the above patch worked.
If you apply the patch and then re-save the settings on System > Advanced, Admin Access tab then you can reboot safely with the COM port enabled.
-
Yet another day of me be glad I am not using equipment with serial console… (-:
Actually if you have the serial console enabled, the problem won't occur. It's only where it's disabled that this can happen, on some minority of hardware.
-
I added the workaround(s) to the upgrade guide – https://doc.pfsense.org/index.php/Upgrade_Guide#pfSense_2.2.2_Upgrade_Notes
-
I had a serial port enabled, with a GPS connected to provide PPS for NTP, and it did impact me. I disabled the serial interface to get it to boot, but without it, my NTP lost the ability to sync with the GPS.
+1 here
-
I had a serial port enabled, with a GPS connected to provide PPS for NTP, and it did impact me. I disabled the serial interface to get it to boot, but without it, my NTP lost the ability to sync with the GPS.
+1 here
Apply the workaround from my last post and then you can re-enable your serial port.
-
-
Its like EVERYBODY :D
No. It's like everyone with unused serial port that doesn't KISS.
I'd say actively going into the BIOS to disable hardware (keeping in mind physical access to the machine means it's already compromised) is the exact opposite of keeping it simple.
