Cannot boot after upgrading to pfsense 2.2.6
-
After upgrading my virtual machine (on an ESXi host) from 2.2.5 to 2.2.6, I get the message in the attached screenshot. What can I do to solve this?
-
i think it would be best to start from scratch and restore a backup of config.xml afterwards.
-
What can I do to solve this?
Actual you should follow @hepers instructions, but for a future run you should make a copy of your existing
VM file and try it at first out with this file, if it fails you will be able to wipe it away! And might be able also
working with the original VM file! -
I understand. What I did was to boot off of the Live CD, tried rescuing the current config.xml, did an on-top quick/easy install, was able to logon to the web console, salvaged a config.xml that is before the upgrade process, reinstalled from scratch with 2.2.6, and then restored with the salvaged config.xml. Everything is working great now! And yes, I'll take a snapshot of this VM right away!
-
what version of esxi? Why are you managing it with workstation?
Why would you not take a snapshot of your vm before you do an upgrade??? It really is 2 seconds to take the snap… Run it through the upgrade -- if good you can delete the snap, if bad click your back to before the upgrade... This is one of the best reasons to run pfsense in a vm in the first place...
-
what version of esxi? Why are you managing it with workstation?
Why would you not take a snapshot of your vm before you do an upgrade??? It really is 2 seconds to take the snap… Run it through the upgrade -- if good you can delete the snap, if bad click your back to before the upgrade... This is one of the best reasons to run pfsense in a vm in the first place...
ESXi 6.0. I sometimes manage it with workstation or vcenter, either way as long as the VM's are already created (preferably with vcenter of course) there wouldn't be any disadvantage to doing that. Connecting to the ESXi host with workstation is just like RDP'ing to the VM's themselves.
It's because I forgot as this is just a test environment. I know how easy it is to create one.
-
Lesson learned I guess, test or production, change to vm take a snap ;)
No I guess workstation is fine, was just curious… I just use the actual vclient, but I guess if you have workstation already installed and licensed that works too. Save the install of the vclient.
-
Lesson learned I guess, test or production, change to vm take a snap ;)
No I guess workstation is fine, was just curious… I just use the actual vclient, but I guess if you have workstation already installed and licensed that works too. Save the install of the vclient.
Learned my lesson, definitely :) I was actually surprised that after restoring the config.xml on a brand new installation of pfsense it automatically installed the necessary packages.
Oh ok. In newer versions of ESXi, it's actually best to use the vsphere web client as it will give you all the new features. The locally-installed vsphere client can only do so much especially if the hardware version of the VM is 12.0 already.
-
Usual cause of that is not having enough available disk space to complete the upgrade successfully.
