Bug #3571
closed
Upgrade from 2.1-RELEASE to 2.1.1-RELEASE on NanoBSD/4G/amd64 results in system still being at 2.1-RELEASE
Added by Daniel Becker about 10 years ago.
Updated about 10 years ago.
Description
I've gone through the update wizard in the web interface twice now on my NanoBSD/4G/amd64 system, and I keep ending up with 2.1-RELEASE after the reboot. The download completes, the machine reboots, packages get reinstalled, everything; and yet, after all is said and done, the machine is still at 2.1-RELEASE and showing "update available".
Also, for some reason, there appear to be two sets of identically named copies of the hash files for the NanoBSD images, one with time stamp 15-Sep-2013 and one with timestamp 04-Apr-2014.
Comparing to the listing in http://updates.pfsense.org/_updaters/ (without amd64), I noticed another oddity: The amd64 subdirectory has files of the form "latest-nanobsd-[size]", without an extension, with a 04-Apr-2014 time stamp. These files are at the exact same position in the listing where the .img.gz files are in the i386 directory. Looks like something went wrong with the upload?!
that's my bad, fixing it right now.
- Status changed from New to Feedback
I'm going through and testing now to fully confirm, but should be ok. If you can also confirm that'd be appreciated.
"The image file is corrupt. Update cannot continue"
FWIW, doing a command line upgrade (with ".img.gz" removed from the default URL) seems to have worked fine. It did just skip the hash check step, though, without any user input.
- Status changed from Feedback to Resolved
I cannot use the auto updater via the web GUI or the CLI. I am still at 2.1 upon reboot.
It's not a general issue currently, please post on the forum for assistance.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Doktor Notor 
Updated by 
Updated by