Hyper-V Upgrade from 2.2.6 to 2.3 RC fails.
-
Decided to go ahead and try the upgrade, thankfully Hyper-V snapshots make recovering from this kind of thing trivial but I've tried three times now and each time I get to the point where it says the firmware update is completed, it reboots and then attempts to boot and eventually fails with:
Trying to mount root from ufs:/dev/ada0s1a [rw]... mountroot: waiting for device /dev/ada0s1a ... Mounting from ufs:/dev/ada0s1a failed with error 19.What's up? The install has been working perfectly for ages… any ideas?
-
Happens to me in plenty of updates not only 2.2.6 to 2.3 RC but between 2.3 beta upgrades. Ended up for Backup -> Reinstall -> Restore, process.
-
2.3 won't have any issues restoring from a 2.2.6 backup config?
It's not a big deal just to try it, just don't want to waste time creating a new VM and configuring it and trying to manage the changeover between the virtual switch assignments and stuff just to end up having to reconfigure it all from scratch again if there is some simple solution to working around this after-upgrade boot problem (I've never personally encountered it before when upgrading).
–> It seems creating a new VM and installing and then restoring the old config has gone OK, at least on the surface.
-
2.3 won't have any issues restoring from a 2.2.6 backup config?
In this world we never know.
Don't remember if i do any restore from 2.2.x because i do some backup time to time and keep the last. Eventually may i have restore from a 2.2 version to 2.3. Never have a big problem doing restore. Maybe if you have Ram disks and do a backup then with RAM Disk off and restore, you cold have some stuff not working. I tell this because my monitoring(rrd_data) dose't work after upgrade, simples as that and i believe could be because i restore a version that was in a RAM disk before to a new nom RAM Disk setup. Disabling Graphing Reset Graphing data and Enable Graphing could solve the problem but of course without the old data.
-
There is an option for the Primary Console at the bottom of the Advanced -> Admin Access page. Switch it to VGA and your input does get redirected to the Monitor instead of the Serial Console. Happens when you restore config from a Serial Installation.
-
There is an option for the Primary Console at the bottom of the Advanced -> Admin Access page. Switch it to VGA and your input does get redirected to the Monitor instead of the Serial Console. Happens when you restore config from a Serial Installation.
"Mounting from ufs:/dev/ada0s1a failed with error 19" seems more a media problem itself than a VGA or Serial, happens to me often time and i don't fail choosing version so many time if any. I could be wrong, easily.
-
There is an option for the Primary Console at the bottom of the Advanced -> Admin Access page. Switch it to VGA and your input does get redirected to the Monitor instead of the Serial Console. Happens when you restore config from a Serial Installation.
Definitely not that… but anyway, upgrade failed every time for me but backup config... create new VM, new install on new VM, then restore config worked for me.
