Probably can't see the text in the image so I'll type out some of it. Not sure why I can't paste it in here.
Failed to start the virtual machine
Cannot open the disk '/vmfs/volumes/54945749-..../AMDIN2vm.vmdk' or one of the snapshot disks it depends on
Failed to lock the file
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/54d56373-.../ADMIN2vm_vmdk' or one of the snapshot disks it depnds on.
The file specified is not a virtual disk
When the virtual server stated to fail, I thought if I rebooted it I could get what I needed. I know the reason it was failing was because the c: drive was just about completely full. I had configured it for 75 GB but I see the file is at 78 GB. I also discovered that I could not log in to the vSphere Client for this esxi server with my AD account. I could log in using the IP of the esxi server and root password. I ended up rebooting the esxi server. and then found out I could not start the vm server. I could now log in with my AD account though.
I had 2 hard drives, the OS - 2012 R2 was the C: and it was on the datastore drive. the D: drive was on the storage drive. It had plenty of space left.
I tried mounting the D: drive to a new vm as a second drive but I got a similar message that it was not a vm drive. When I browsed to it's location, even though it had the same vmdk extension, it would not see it.
Not sure how catastrophic this problem is, a little worried since I built another vm on the same esxi box. Box was new last summer
running esxi 5.5 on sd card as a standalone
Would be great if I can get both drives running but right now, I would be extremely appreciative to get the second drive open on either a new or different server folder (same name in both places) had aADMIN2vm_1-flat.vmdk FILE WHICH IS 209 GB but was configured for 200 and another file AMDIN2vm_1.vmdk which is only .51KB
