21.05 update bricked my 5100
-
I did hold off with update considering how many issues there were but yesterday I decided to upgrade my 5100 from 2.4.5 to 21.05. Web interface reported success but after reboot no more DHCP assignment and statically assigning IP in the range that was distributed before does not help.
Below is the end part of the update log if of any use. I would be grateful if anyone could point me to a guide as to how to recover from this horror.Number of packages to be removed: 63 Number of packages to be installed: 75 Number of packages to be upgraded: 120 Number of packages to be reinstalled: 50 The process will require 61 MiB more space. >>> Downloading pkg... The following packages will be fetched: New packages to be FETCHED: pkg: 1.16.3 (7 MiB: 100.00% of the 7 MiB to download) Number of packages to be fetched: 1 The process will require 7 MiB more space. 7 MiB to be downloaded. Fetching pkg-1.16.3.txz: .......... done >>> Locking package pkg... done. >>> Upgrading pfSense-rc... Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-rc: 2.4.5_1 -> 21.05 [pfSense-core] Number of packages to be upgraded: 1 [1/1] Upgrading pfSense-rc from 2.4.5_1 to 21.05... [1/1] Extracting pfSense-rc-21.05: ........ done >>> Upgrading pfSense kernel... Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-kernel-pfSense: 2.4.5_1 -> 21.05 [pfSense-core] Number of packages to be upgraded: 1 The process will require 19 MiB more space. [1/1] Upgrading pfSense-kernel-pfSense from 2.4.5_1 to 21.05... [1/1] Extracting pfSense-kernel-pfSense-21.05: .......... done ===> Keeping a copy of current kernel in /boot/kernel.old >>> Scheduling package pfSense-pkg-Netgate_Coreboot_Upgrade for removal... >>> Removing unnecessary packages... done. System is going to be upgraded. Rebooting in 10 seconds. >>> Unlocking package pkg... done. Success -
@nomadmd I didn’t think you could update from 2.4.5 to 21.05. You would have had to do it in increments or install 21.05 as a new install. Assuming you have a backup (which you should always have before updating) you can submit support ticket for the 21.05 installation file, reinstall, restore, and go about your day. Really takes minimal amount of time to do and netgate has responded to my ticket quicker than the system can even send me the “we’ve received your ticket” confirmation email.
-
@gabacho4 said in 21.05 update bricked my 5100:
@nomadmd I didn’t think you could update from 2.4.5 to 21.05. You would have had to do it in increments or install 21.05 as a new install.
Web interface did not offer intermediate options. it was to stay on 2.4.5, update to 21.05 or 21.09 devel
-
@nomadmd said in 21.05 update bricked my 5100:
Web interface did not offer intermediate options.
Nor will it
no no no this is a big leap, first need to learn (forum) and always use the new Netgate image, before you take such a big step (update FreeBSD 11 - 12, etc)
don't worry, it will work
-
@gabacho4 said in 21.05 update bricked my 5100:
I didn’t think you could update from 2.4.5 to 21.05
It's fine skipping, I've done it many times including 2.4.5 to 21.05. There is a doc page for that.
@nomadmd Did you find the troubleshooting docs including the /conf/upgrade_log.latest.txt file?
There's no support plan needed to open a ticket to get the 21.05 installer file.
-
You should definitely be able to update from 2.4.5p1 to 21.05. I tested that personally numerous times on many hardware types.
The part of the upgrade log shown looks fine, nothing unexpected there. When you run the update it upgrades the minimum required to boot to the new kernel and then updates most of the packages after the reboot. You can see that is:
Number of packages to be removed: 63 Number of packages to be installed: 75 Number of packages to be upgraded: 120 Number of packages to be reinstalled: 50Of which one package is upgraded before the reboot.
To be clear the majority of the time required to upgrade is after the initial reboot.
I suspect what happened here is that is was still upgrading. If you have a lot of pfSense packages installed or a low bandwidth connection it can take while.
Running the upgrade from the console allows you to see the upgrade taking place so you know exactly when it's finished. It also gives you a lot more error output to work with if there is a problem.
Steve
-
It was indeed most likely incomplete update as when I logged into console there was a wall of PHP errors along with the option to ssh into it. I was able to recover the config.xml file onto USB drive.
Netgate support was quick in providing the link to firmware and instructions for recovery using USB booting option. Actually a good thing in the end because I was procrastinating moving the entire setup to the M.2 drive that I physically installed a year ago. Since the system had to be reinstalled anyway I installed it onto M.2 drive.
Thanks everyone for help
-
Just for anyone reading if you do connect to the console during an upgrade, or initiate it from there, you will see a bunch of php errors if the update includes a php version change. And 2.4.5 to 21.05 does.
But it should complete anyway, if you reach a prompt that isn't the normal console menu something has not completed correctly.Steve
