Hello,
today one of my datastores went full and I got a message like this
'There is no more space for virtual disk xxxx.vmdk. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.'
Because I didn't want to have any issues with other VMs on the datastore and it's a VM that can be shut down without business impact, I clicked Cancel and the VM shut down. Then I saw that it runs on a snapshot, which I deleted and then set the second disk to independent because it's unnecessary to be snapshotted.
But now I can neither start the VM, consolidate or move it to another datastore. When starting, I get the following error
An error was received from the ESX host while powering on VM XX.
Failed to start the virtual machine.
Cannot open the disk '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000003.vmdk' or one of the snapshot disks it depends on.
Failed to lock the file
Module Disk power on failed.
Cannot open the disk '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000001.vmdk' or one of the snapshot disks it depends on.
Failed to lock the file
The vmdk files are existing though and there are NO lock files on the datastore.
After a few tries to boot it up I tried to create another snapshot and deleted it again, but then the error came up that disk consolidation is needed. This doesn't work either:
An error occurred while consolidating disks: msg.snapshot.error-DISKLOCKED.
I already read KB10051 about disk locks, but the owner IDs of the disks are only zeroes instead of an MAC-address.
[root@at0195:/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/AT1124] vmkfstools -D /vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/AT1124/XX-000003.vmdk
Lock [type 10c00001 offset 228986880 v 123, hb offset 4157440
gen 49, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2666079
num 0 gblnum 0 gblgen 0 gblbrk 0]
Addr <4, 529, 58>, gen 115, links 1, type reg, flags 0, uid 0, gid 0, mode 600
len 388, nb 0 tbz 0, cow 0, newSinceEpoch 0, zla 4305, bs 8192
I already tried restarting the management services on all my hosts all well as restarting the vCenter service.
I also cannot migrate the machine to a datastore with more free space. Host migration is working, but on datastore migration, I get the following
Error caused by file '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000001.vmdk'
Cloning the VM also doesn't work because of
Unable to access file'/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000003.vmdk' since it is locked
Does anybody have an idea what I can do? I sure do not have a backup of that damn server..