How to Downgrade or Rollback your failed ESXi 6 upgrade to previous Version

-
I hope this time most of the VMware administrators  will be busy with upgrading their infrastructure to vSphere 6. There are some rare situations in which your ESXi upgrade to 6.0 may fail due to some old firmware or drivers or may be whatever reasons. Most of the administrators will be aware  about rolling back vCenter or VM upgrade by reverting it to previous snapshot. Most of them may be unaware about the rolling back your ESXi upgrade. This post explains you the procedure to roll back your ESXi 6.0 upgrade to previous version i.e ESXi 5.5.

Procedure to Downgrade or Rollback your ESXi 6.0 Upgrade:

After the ESXi upgrade is failed or Hung, reboot your ESXi host. Durig ESXi host boot up, hit  Shift+R
Recovery mode will display the ESXi build version which you were upgrading from. If you want to roll back to the previous version, hit Y to go back to the previous version of ESXi. In my case , I was upgrading my ESXi host from ESXI 5.5 to ESXi 6.0. So I am hitting Y to rollback to previous version ie. ESXi 5.5.
Thats it. Your ESXi server will boot with the previous version of the ESXi i.e ESXi 5.5. This is a permanent and you will not able to boot to ESXi 6.0 until your next successful upgrade. I hope this is informative for you. Thanks for Reading!!!.  Be Social and share it in social media, if you feel worth sharing it.

Comments

Post a Comment

Popular posts from this blog

esxi-host-shows-disconnected-vmware

-
Symptom: The host and VMs in a vcenter server appears to be disconnected. Issue: The host and its corresponding vms could appear as disconnected due to issue with any of the following services. vpxa - a service which runs in the esxi host. This service communicates with vcenter server. hostd - core service which runs in the esxi host vpxd - a service which runs in the vcenter server which communicates with the vpxa Resolution: 1. Try to ping the ESXi host. This ensures that the host is reachable 2. Ensure you can login to the VMs remotely. This ensures that VMs in the host are working fine. 3. Try to login to the ESXi host using vsphere client. This ensures that the hostd services are running perfectly. If this step fails, restart the hostd service using putty. 4. If the above three steps worked fine for you, the issue would be with the vpxa or vpxd service. In that case, first try to restart the vpxa service in the host and if that didnot resol
Read more

ESXi : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down

-
We had an issue suddenly getting an alert : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected portgroups:"vMotion", "Management Network". So as a troubleshooting Select the ESXi host effected Click on Configuration, Select Networking, Click on vSwitch0 Properties,Click on Network adapters Select on vmnic0, Click on remove, Click on Close Again Select Networking, Click on vSwitch0 Properties,Click on Network adapters, Click on Add, Select the vmnic0, Click on Next, Click on Next, Click on Finish Now Click on Ports tab of vSwitch Properties, Select on vMotion, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select on vmnic0, Click on Move Down to Standby Adapters, Click on OK Now Click on Ports tab of vSwitch Properties, Select on Management Network, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select o
Read more

Virtual machines appear as invalid or orphaned in vCenter Server

-
Symptoms Virtual Machines show as invalid or orphaned in vCenter Server Virtual Machines show as invalid or orphaned after a VMware High Availability (VMware HA) host failure occurs Virtual Machines show as invalid or orphaned after an ESX host comes out of maintenance mode Virtual Machines show as invalid or orphaned after a failed DRS migration Virtual Machines show as invalid or orphaned after a storage failure Virtual Machines show as invalid or orphaned after the connection is lost between the vCenter Server and the host where the virtual machine resides You see one or more of these errors when trying to start a virtual machine: Could not power VM, no swap file, failed to power on VM. VMControl error -11: No such virtual machine. A general system error occurred. The system returned on error. Communication with the virtual machine may have been interrupted In   C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log   file, you see entries similar to: [11916 error
Read more