2.5 SG-3100 Upgrade Failure
-
Tried to upgrade my SG-3100 tonight since you guys have been crushing bugs, and are down to only a few. Ended in a flaming failure, and I'm pretty sure this is why.
[2/2] Upgrading pfSense-u-boot-sg3100 from 2.4.5_1 to 20181101...
[2/2] Extracting pfSense-u-boot-sg3100-20181101: ....... doneThat looks like firmware from 2018, probably not what 2.5 wants, and then this:
pkg-static: https://firmware.netgate.com/beta/packages/pfSense_factory-master_armv7-pfSense_factory-devel/All/pkg-1.15.10.txz: Non-
recoverable resolver failureI'm sure this was just an overlook, so just letting others know until its fixed.
-Thanks for the work you guys do
-
That u-boot is right. Unrelated to whatever else you hit, which sounds like a DNS issue.
-
The issue I was having then is after my SG-3100 takes time to download the new files, it reboots, and instead of installing 2.5, it just boots straight into 2.4.5, but now none of the interfaces are working. Each time it required me to reinstall 2.4.5P1 from a USB drive to make the unit function again.
-
Could you start over again with 2.4.5, then try the update from the serial console and record the entire output?
-
I spent some time reinstalling my 3100 last night, trying to figure out what the problem is. You were correct in a previous post, it was DNS related. When I'd upgrade, my DNS resolver would crash. I figured out this was being caused by having the Avahi package installed.
For some reason when this is installed the DNS Resolver crashes during the upgrade, causing my issue. I also verified this by uninstalling the package, doing the upgrade, and then when the upgrade was complete reinstall Avahi, and in less than 5 minutes DNS was broken again.
-
Any log messages from the Avahi package or the DNS Resolver that give you any clue about what is happening? Check the main system log as well as the DNS Resolver log.
-
I did not see any errors on the console other than the ones resulting from the resolver being broken during the upgrade. I can't pull anything from the GUI once this happens because I completely lose network connectivity. I'm not sure why this is happening because the console port still shows me the ports have IP addresses.
There are a bunch of errors during the upgrade even during a normal upgrade, but I think their a result of changes from BSD version upgrades you guys did because my 3100 has been stable for almost 12 hours now even with them during the upgrade.
If you interested in these non-fatal errors, I can do the upgrade from 2.4.5P1 tonight and fully log the output and send it to you.
-
Well I spoke too soon. I just completely lost network connectivity, and the console port froze up. Definitely something going on here.. I must have hit the 12 hour mark, if not its pretty close. Had been working good up until just now.