Upgrade from 2.1 to 2.1.1
-
Hello all.
I tried upgrading my one router, which is a Alix based one. Used the auto upgrade. it downloaded the upgrade, installed it, rebooted, installed the packages. Once it finished up, it still shows on 2.1 and an upgrade is available.
Stumped, I tried the upgrade on another router I'm using which is a Supermicro Atom based 1U. It did the exact same thing as described above.
Both are running NanoBSD 4G. Only thing different is the Alix is not running the VGA firmware, while the Supermicro Atom 1U is.
Any ideas? Thanks for any pointers.
-
Hm, strange. I have just finished an Alix upgrade from 2.1.1-PRERELEASE to 2.1.1-RELEASE. This went fine though my upgrade path is slightly different.
A shot in the dark: You could try to switch the boot slice on the NanoBSD systems - at least on your Alix - and see, if it carries the old version as well. If not, your slices boot preferences could have been disturbed. But this is just a vage assumption and I could not give any reason for it.
I have upgraded now a lot of times and have seen thing that my run into a wrong direction but your experiences are new to me.
Regards,
Peter -
Thanks Pvoigt.
I tried that on both routers and still no-go. Looking at the directory listing for the update files, many, including mine are still dated 2013.
I'm guessing not all of the update files have been uploaded yet?
-
OK, both slides still show version 2.1.
Is it possible that your download of the upgrade files was incomplete? Did you carefully watch what was going on? To give you a rough estimation of the time needed on my Alix from starting the upgrade procedure to automatically reboot after the upgrade: It takes up to 15 minutes with my 16.000 kbit/s DSL internet connection. Is your upgrade time comparable?
Alternatively you could start the upgrade from the console menu.
And if all goes wrong: Reflash your compact flash card of your Alix with a full 2.1.1 image.
Regards,
Peter -
Running into the exact same problem, also with NanoBSD/4G. I went through the upgrade process twice now, and both times I ended up with 2.1-RELEASE again. Nothing in either the web interface or the console indicates any issues with the transfer, and the box thinks it's upgrading (it's reinstalling all packages after the reboot, too), but at the end of the day I'm back to where I left off.
An upgrade on another system that uses an embedded install worked just fine.
-
https://redmine.pfsense.org/issues/3571
-
Definitely looks like there's something funny going on with the NanoBSD file links at http://updates.pfsense.org/_updaters/amd64/. There are also two copies of all the NanoBSD-related hash files, one set with Sep-2013 time stamps and one with Apr-2014 ones…
-
Definitely looks like there's something funny going on with the NanoBSD file links at http://updates.pfsense.org/_updaters/amd64/. There are also two copies of all the NanoBSD-related hash files, one set with Sep-2013 time stamps and one with Apr-2014 ones…
It looks like someone changed the filename format:
latest-nanobsd-vga-1g.img.gz <- 2.1 - 15-Sep-2013 13:46
latest-nanobsd_vga-1g.img.gz <- 2.1.1 - 04-Apr-2014 00:32