Alix2D13 upgrade from 1.2.3 to 2.0-Release failing
ck42 last edited by
I've tried upgrading from the GUI and CLI. This is the 2G nanobsd upgrade image
At least in the CLI, I can see the whole process proceed normally until it gets to the part where it's actually updating.
1) Update from a URL 2) Update from a local file Q) Quit Please select an option to continue: 1 Enter the URL to the .tgz update file: > http://files.chi.pfsense.org/mirror/updates/pfSense-2.0-RELEASE-2g-i386-nanobsd-upgrade.img.gz Fetching file size... File size: 68229808 Fetching file... looking up files.chi.pfsense.org connecting to files.chi.pfsense.org:80 requesting http://files.chi.pfsense.org/mirror/updates/pfSense-2.0-RELEASE-2g-i386-nanobsd-upgrade.img.gz remote size / mtime: 68229808 / 1316225048 /root/firmware.tgz 100% of 65 MB 1759 kBps 00m00s Fetching MD5... looking up files.chi.pfsense.org connecting to files.chi.pfsense.org:80 requesting http://files.chi.pfsense.org/mirror/updates/pfSense-2.0-RELEASE-2g-i386-nanobsd-upgrade.img.gz.md5 remote size / mtime: 92 / 1316225048 /root/firmware.tgz.md5 100% of 92 B 58 kBps URL MD5: 96672e01257370aaf60159f2dbc91fbb Downloaded file MD5: 96672e01257370aaf60159f2dbc91fbb MD5 checksum matches. NanoBSD upgrade file detected... One moment please... Invoking firmware upgrade...
It's been doing this for about 20 minutes now.
I originally had problems when trying to upgrade to the 2.0-RC3 build…so I figured I'd just wait until the final release and then try it again. Looks like the same type issue as before.
Any way to troubleshoot this?
ck42 last edited by
Okay, here's a clue.
/etc/rc.firmware pfSenseNanoBSDupgrade /root/pfSense-2.0-RELEASE-2g-i386-nanobsd-upgrade.img.gz Broadcast Message from email@example.com (no tty) at 12:37 EST... NanoBSD Firmware upgrade in progress... Broadcast Message from firstname.lastname@example.org (no tty) at 12:37 EST... Installing /root/pfSense-2.0-RELEASE-2g-i386-nanobsd-upgrade.img.gz. kern.geom.debugflags: 16 -> 16 Something went wrong when trying to update the fstab entry. Aborting upgrade.
What exactly does the part "kern.geom.debugflags: 16 -> 16" mean?
Also, tested and verified that fstab is setup correct and that I could successfully make modifications to it using vi.