Upgrade from 2.4.3 to 2.4.3_1 reported successful but machine didn't reboot
After the usual "upgrade successful" message from the GUI, I waited around 5 minutes before attempting to log back into the admin page but it was not responding.
Taking a look at the monitor connected to the firewall I see the following (image):
Any thoughts on what I should do next? I don't really want to force a reboot when the last message on the screen is "Updating CPU Microcode…" :(
I'm using the AMD 64bit version of pfSense by the way.
- ASUS CM1745 CP machine
- AMD Virgo CPU
- 8GB RAM
- 250GB SATA drive
- Bios 5007 x64 2012/8/27
I've never had any issues with pfSense upgrades and have been good at not skipping releases.
Also, I tried connecting a USB keyboard to the machine but the caps lock LED doesn't come on.
I did backup the configuration before the upgrade per usual worst case, but I really don't have time to setup a new usb stick with the latest release, format the drives, etc. to restore at the moment.
If the caps lock key doesn't respond it looks to be really hard locked. You probably don't have any choice but to reboot.
The CPU microcode is updated every boot, it's not in the process if flashing the CPU or something that should not be interrupted.
Re-installing and restoring the config is a relatively quick process and will get you back up again. Especially if you use PFI / ECL to load the config during the install:
Thanks for your reply.
I'm going to try and shut it down and restart and see if I end up stuck at the same place.
In the meantime I've already downloaded pfSense-CE-memstick-2.4.3-RELEASE-amd64.img.gz and am writing it to a USB stick as a type in case I need to go down the re-install route.
I now remember the PFI/ECL feature so it shouldn't be too painful to restore back to the last backup I made earlier today before the upgrade.
Unfortunately upon reboot, it wasn't able to load pfSense, but it was detected as an option.
I was eventually able to restore my system to 2.4.3-Release with my previous configuration intact.
Now what to do about the pending 2.4.3_1 update…
Gertjan last edited by
Now you have secured your "can go back in a snap", try a complete fresh install.