Stuck during upgrade
-
@markgca If it's still "fetching" and hasn't started installing, I think I'd
- open a free ticket with Netgate and get a 21.05.2 and/or 22.01 firmware image (I'm assuming if you're on 21.05 you have Netgate hardware, and you have Internet to post this)
- restart the router
- try again
I've had a few updates over the years get stuck but way early in the process, like it doesn't even get started, and a reboot seems to get it back on track. To be clear this is on a very low percentage of routers+upgrades.
After the upgrade I usually allow 10-15 minutes before starting to worry about the router booting up. It can take a while depending on CPU and storage speed.
Netgate's upgrade docs suggest removing packages before upgrade and reinstalling.
-
After the upgrade I usually allow 10-15 minutes before starting to worry about the router booting up. It can take a while depending on CPU and storage speed.
I'd wait longer than 15 minutes; for me this particular update (I did mine last night) took longer than previous ones. But I left it for probably 25 minutes and it came back as it was supposed to.
The only time I've had an issue is when I panicked and restarted it. Since then I just leave it and it works.
-
@nguser6947 What hardware do you have? My 10-15 estimate was based mostly on 2100s and 3100s. The release notes do say for 22.01/2.6 and later the updates "will forcefully reinstall all operating system packages and add-on packages to ensure a consistent state and package set. This may increase the time the upgrade will take to download and install."
-
@steveits SG-1100
-
@nguser6947 What does the console show you?
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.html
-
@rcoleman-netgate I'm not the person with the issue... I was just recommending people wait a good while before concluding that their update had failed. My recent update went fine.
-
@nguser6947 Just for another reference point I updated my home 2100 last night. I uninstalled Snort and pfBlocker (left apcupsd, a bit lazy) and the upgrade took about 10 minutes. Then I reinstalled those two packages.
But yes overall it's easy to panic after 5-10 minutes when the counter says 90 seconds. :) I wish it said something like "this might take 5-15 minutes just wait, I'll check every 30 seconds."
-
@steveits i ended up restarting this; it went to the same place and stuck there again. so i left it overnight. after a couple hours it said it timed out, so now i have the ability to update it again.
i will be doing that this weekend so i have time to recover if anything goes wrong (and i have the firmware images in my hand)
thanks for the help.
mark
-
So the windup if anyone cares at this point (this is on a 7100-1u for what its worth)
after it reset itself, i figured i would try again. i had read that some people thought one or more of the packages was causing the issue during update.
so i removed several packages i wasnt using on a daily basis - the ones i was using like snort i left alone. i removed: cron, iperf, openvpn client export, and netgate firmware upgrade.
then i started the update again; single window, single browser, etc so that nothing could get in its way.it took about 30 minutes maybe total, and everything came up properly and worked well EXCEPT the OpenVPN gateways.
they stayed off line for hours, and only came back up when i restarted the service (there were two stuck, but i only needed to restart one of them for both to start working)then i reinstalled the firmware update utility (one of the ones i deleted) since i read there was a firmware update, first one since i got the appliance.
updated, then it rebooted, and another 20+ minutes to come back up. and again the gateways were down. another restart service and everything is fine.
not sure the gateway thing is new since the appliance never goes down, but it was consistent on this version. not a big deal, just something i noticed.
otherwise everything is perfect again.
-
@markgca What does the system log say about those OpenVPN gateways?
The 20 minute reboot indicates to me that it's hanging on something to do with interfaces.What have you found from plugging into the console port during a reboot cycle?