An error occurred while consolidating disks Error ESXI 6.5
I am trying to consolidate a very large virtual disk of 28tb. I am using the thick client to consolidate the disk because I can not find a way to do it in the web client. The snapshot is 3tb and there is 3.6tb free on the datastore. What are my options to fix the "Vitural machine disks consolidation is needed" error?
Thanks
Here is the message I get "an error occurred while consolidating disks: msg.disklib.NOSPACE." Please see attached photo.
Capture.JPG
Thanks
Here is the message I get "an error occurred while consolidating disks: msg.disklib.NOSPACE." Please see attached photo.
Capture.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It may not have worked!
Although the snapshots may have gone from snapshot manager, this could be a red herring, and they may remain.
CHECK the Virtual DIsk, is not still writing to a snapshot disk, it looks to me it's just created another one, e.g. 00004.vmdk.
Because the parent VMDK is locked, because it's attached to another VM!
This machine is not backed up by another backup product ?
Although the snapshots may have gone from snapshot manager, this could be a red herring, and they may remain.
CHECK the Virtual DIsk, is not still writing to a snapshot disk, it looks to me it's just created another one, e.g. 00004.vmdk.
Because the parent VMDK is locked, because it's attached to another VM!
This machine is not backed up by another backup product ?
ASKER
I checked and it is now writing to 00004.vmdk. There is no other VM attached to this VMDK.
Okay, so something has a lock on the Parent VMDK. without free-up the parent, you will NOT be able to consolidate.
How is this VM backed up ?
How is this VM backed up ?
ASKER
This VM is not backed up at all because of it's size.
ASKER
It is mainly used as a DR site.
Well the quick method, if you are sure no other VM has the parent disk attached to it.
is to restart the host, otherwise you will need to find out which process has a lock on the Parent VMDK
which is long, and sometimes does not real the process, resulting in a restart anyway.
is to restart the host, otherwise you will need to find out which process has a lock on the Parent VMDK
which is long, and sometimes does not real the process, resulting in a restart anyway.
obviously when running out of disk space you go to the shop and buy new disks.
If you dont clean all snapshots (salmon or herring) they eventually grow to another vmdk in size.
If you dont clean all snapshots (salmon or herring) they eventually grow to another vmdk in size.
ASKER
Is it better to have the VM off while consolidating it?
if the VM is OFF, it will NOT use any storage space, and be faster.
but you will not be able to use the VM.
BUT, if you've not worked out why this parent VMDK has a lock on it, you will not be able to merge/consolidate.
but you will not be able to use the VM.
BUT, if you've not worked out why this parent VMDK has a lock on it, you will not be able to merge/consolidate.
ASKER
I ended up moving a lot of VM's off the data store to make room for the Consolidation to run. It seems to be running now.
Be patient, and monitor in the future.
ASKER