1.2.3 - > 2.0-RC2 x64 upgrade feedback. A few issues.
-
I took the plunge and upgraded 1.2.3 to 2.0RC2 using the firmware auto upgrade feature. Two observations:
- my RRD databases were not upgraded properly and had to be cleared prior to trying the upgrade again. I reverted back to my 1.2.3 snapshot, cleared /var/db/rrd and did the upgrade from the webconsole again.
- when upgrading 1.2.3 (32-bit) to 2.0RC2 (64-bit) it appears the killall line/process that is supposed to reboot the machine after an upgrade is missing a "(" somewhere, it threw back an error message (I didn't capture it), however I had to manually force a reboot. My Xen VM running pfSense was pegged at 100%. When it came up, did a fsck and all seems to be well thus far. Running it at this time and haven't notice any additional significant issues.
-
Upgrading cross-ARCH hasn't ever really been supported. And crossing ARCHes will cause the RRD data to be invalidated. In some cases this does work, but it has some quirks.
If you went to 2.0 i386 you probably wouldn't have had any issues.
The reboot process probably had an issue because at that point the "reboot" binary is 64-bit and the OS is 32-bit so it will freak out in various unpredictable ways.
-
Agreed that cross platform upgrades are tricky. However to the best of my knowledge 1.2.3 was only available in a 32bit edition. If the later is true, why even offer the option.. 64-bit clean installs only..
You're correct. 1.2.3 to 2.0 32-bit went without incident.
-
Well the 64-bit updates are really meant for people who installed from 64-bit ISOs… we just don't have any code in the upgrade that checks (and can't add any to 1.2.3... that boat has sailed) the architecture of the new update file to prevent foot-shooting.
It may very well work for some people... so it's one of those "Try at your own risk" / "Here be dragons" areas.
