Hello,
We had a volume run out of space. One of the guests powered off and went orphaned. I removed from inventory and added it back in and now it is invalid. When I try to power it on it says the operation is now allowed in the current state. Any ideas?
Thanks!
Here's some log info:
Jun 24 18:06:00.276: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01-000001.vmdk" (flags 0xa, type vmfs).
Jun 24 18:06:00.302: vmx| DISKLIB-LIB : Content-ID check is now enabled.
Jun 24 18:06:00.304: vmx| DISK: Disk '/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01-000001.vmdk' has UUID '60 00 c2 99 6c d7 d4 b1-01 e8 1f 18 4d f2 17 55'
Jun 24 18:06:00.304: vmx| DISK: OPEN '/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01-000001.vmdk' Geo (5221/255/63) BIOS Geo (0/0/0)
Jun 24 18:06:00.317: vmx| DISK: OPEN scsi0:1 '/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01_1-000001.vmdk' persistent R[]
Jun 24 18:06:01.065: vmx| DISKLIB-VMFS : "/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01_1-000001-delta.vmdk" : open successful (10) size = 63284162560, hd = 289558248. Type 8
Jun 24 18:06:01.065: vmx| DISKLIB-DSCPTR: Opened [0]: "omabtnms01_1-000001-delta.vmdk" (0xa)
Jun 24 18:06:01.065: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01_1-000001.vmdk' (0xa): vmfsSparse, 513802240 sectors / 245 GB.
Jun 24 18:06:01.190: vmx| DISKLIB-VMFS : "/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01_1-flat.vmdk" : open successful (14) size = 263066746880, hd = 379506409. Type 3
Jun 24 18:06:01.190: vmx| DISKLIB-DSCPTR: Opened [0]: "omabtnms01_1-flat.vmdk" (0xe)
Jun 24 18:06:01.190: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4c86e04c-a5778dcd-80a3-001b21119cbc/omabtnms01/omabtnms01_1.vmdk' (0xe): vmfs, 513802240 sectors / 245 GB.
Jun 24 18:06:01.191: vmx| DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1
