Upgrade to 2.1.4 breaks serial console
I have upgraded 3 OPNsense Quad Core Gen1 rack edition from pfSense 2.1.3 to 2.1.4 through console menu option 13) Upgrade from console:
Enter the URL to the .tgz or .img.gz update file. Type 'auto' to use https://updates.pfsense.org/_updaters/amd64/latest-nanobsd-4g.img.gz > auto
Even though we were never running the vga version on these Gen1 appliances, and even though the upgrade URL seems correct, it was installing the vga version.
After next boot, we would then find the following "auto" URL:
Enter the URL to the .tgz or .img.gz update file. Type 'auto' to use https://updates.pfsense.org/_updaters/amd64/latest-nanobsd-vga-4g.img.gz
Note the "vga" in latest-nanobsd**-vga**-4g.img.gz
This broke our serial console. The only way to get it back working was to modify /etc/ttys as follows:
--- /etc/ttys.OLD +++ /etc/ttys @@ -30,7 +30,7 @@ # # If console is marked "insecure", then init will ask for the root password # when going to single-user mode. -console none unknown off secure +console "/usr/libexec/getty Pc" cons25 on secure # ttyv0 "/usr/libexec/getty Pc" cons25 on secure # Virtual terminals
Any way of getting again the non-vga edition installed? And can you tell me please why this upgrade broke the serial console, even though I checked the "Enables the first serial port with 9600/8/N/1 by default, or another speed selectable below" option?
Best regards, Philip
I had the same happen.
Checking the enable console worked but it ignores the baud rate and is stuck at 9600.
If you are running nanobsd images then this is a known issue: The nanobsd, e.g. non-VGA, image files on the update server under https://updates.pfsense.org/_updaters/ are wrong. They are identical with the VGA versions.
You can either use "Upgrade from console" when in an SSH session or the "Manual Update" from the webGUI to get the right update image. You can find some more details in this thread: https://forum.pfsense.org/index.php?topic=78713.0.
Yes, just installed the nano update over the vga one. Now I get boot messages but no console.
Thanks for the fix.