VM disk cannot be resized- Failed to extend the disk

-
Issue:-
-With the vSphere Client, if you edit a VM's settings and then select one of its virtual
disks, the option to resize the disk is greyed out.
-When trying to extend the disk using vmkftools for resizing, you will receive the below
error:
Failed to extend the disk. Failed to lock the file.
-When you extend the disk using vsphere client, the change is not getting reflected.

Root cause:-
The VM will be having a snapshot. Because when a snaphot is taken the actual VMDK file
will be locked and the changes will be written to a new delta file. Due to this reason, the
actual VMDK file could not be resized.
Another possible reason: If the disk is IDE, the change may not get reflected. The
resolution step for this issue is mentioned here

Resolution:-
Remove the snapshot file and then try to resize.

Comments

Post a Comment

Popular posts from this blog

Designing and Configuring an Enterprise Cloud Solution

-
Image
We have already discussed the architecture of a vRealize Automation environment in previous post. Many topics, including the physical, conceptual and logical design have been covered. These design documents helped us to set up a vRealize Automation environment. However, in order to proceed with the configuration of vRealize Automation, we again need to shift our focus towards the design aspects of implementing a vRealize Automation platform. This chapter will help you to understand these fundamental design concepts. In the following, we will focus on the different components as well as on security aspects. For the most part, this chapter deals with describing the building blocks within a vRealize Automation environment. Afterwards, it will end up with discussing a couple of further design aspects. This chapter will only focus on design issues. The implementation itself will be described in the following chapters. 6.1 vRealize Automation Layers Traditionally, one of the key requ...
Read more

"Host IPMI system event log status" alarm in vCenter Server

-
To resolve this issue, ensure that the NTP settings are correct on the ESXi host, clear the IPMI System Event log file, and reset the sensors.   To clear the IPMI System Event log file and reset the sensors: Open vCenter Server using the vSphere Client. In the vCenter Server Inventory, select the ESXi/ESX host. Click the  Hardware Status  tab. Click  System Event log  under View. Click  Reset Event   Log . The red alert is removed from the System Event log. Click  Reset Sensors  to reset the host sensors. Starting with ESXi 5.1 U2, 5,5 P01 and later, you can use the  localcli  command line to clear the IPMI SEL logs. To clear the IPMI SEL logs in ESXi 5.1 and later: Connect to the ESXi host through SSH.  Run this command: localcli hardware ipmi sel clear If you find an incorrect date and if you are unable to reset the logs: In ESX - Restart the management agents and  sfcbd...
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