100% Failure: Remote Update (thru vpn) 2.0.3 => 2.1 RELEASE
-
I must say that this update just don't work on nanobsd (1g) to version 2.1-RELEASE (i386).
I did five (5) updates thru vpn connection. I have done dublicate slices on every Alix nanobsd (1g) boards before I run the update. Not a single update recovered it's connection or got online. I have dual access to remote pfSense's (ssh and vpn tunnel) If tunnel fails I still should have ssh, but not this time. Must say that this is not working and DO NOT UPDATE remotely - buy a car and drive to site!. You will loose contact of your device !
All regular pfsense installations on Vmware updates from 2.0.3 => 2.1 worked remotely!
What's the problem? Must be something general if all my devices "fucked up" it's update.
==> All of these updates has gone to "factory" defaults and all old configurations has been totally lost. Whats the problem here? This should not go like this - or should it?
-
I have done lots of successful Alix 2D13 updates remotely across a functioning OpenVPN link, although all the recent ones have been from 2.1-BETAn to 2.1-RELEASE, since I was using 2.1-BETAn for some time, and I use the 2G image. The system reboots and OpenVPN re-establishes.
There is no need to do "duplicate slice" before upgrading. The upgrade will write the new version on the slice you are not currently using, then switch boot slices and reboot. Perhaps you are duplicating slices, switching the boot slice, then not rebooting - or some unusual sequence that then causes the upgrade to not write to the expected place?
If it comes up in factory defaults, then that implies config.xml has got lost, corrupted or??? That is on a separate CF partition, separate to the 2 boot slices/partitions.