During some housekeeping I stupidly renamed a VM's virtual disk in the datastore browser in vSphere Client and it now shows as type: File. This now means the VM won't start. Any suggestions on how I can re-associate the file as a virtual disk.
I can SSH into the server if needs be.
Thanks in advance for any help with getting this sorted out.
Znook
Have you looked at this? Fits this description pretty well - VMware KB: Powering on the virtual machine fails with the error: The file specified is not a virtual...
Are you getting a specific error message when you attempt to start the VM?
Did you remove the extension .vmdk ? If yes, just add the extension .vmdk again.
If possible, post the screenshot of files of datastore or a output of a "ls -l" from the SSH.
As per as know we can not rename VMDK from VI client. Rename option should be grayed out.
Can you let us know what exactly you did? Also plz do provide details that "Richardson" has requested.
@blabarbera The VM once started stops with, "The file is not a virtual disk' error. Just to clarify it should be the 100GB C drive of the Windows VM.
@Richardson Porto I would have to assume the extension changed when I renamed the disk (right-click) in the vSphere datastore browser, though that really should not have happened.
If I use rename again in the datastore browser to add the extension back it does appears to show the file as now having a vmdk extension (see photo below) but the Type still shows as File. Even if I go in via SSH and do the same (to remove any possibility it's a datastore browser renaming issue) it still shows as Type: File 😞
For what it's worth in the VM's Properties window it shows the entry for "Hard disk 1" as having a provisioned size of 0. I don't want to change it to 100GB just in case it then irreversibly damages the file (it's too big to do a back-up of to try this out). I feel it's something simple that needs setting to tell vSphere it's a virtual disk but I'm flummoxed on what it is.
Anyway thanks for the input guys, much appreciated.
Have you looked at this? Fits this description pretty well - VMware KB: Powering on the virtual machine fails with the error: The file specified is not a virtual...
Whoa, that does sound like the issue I'm having. Thanks @blabarbera! Unfortunately it will have to wait till later before I can get the chance to peruse those docs and give any suggestion/s a try. My best, Znook.
Only just spotted @vickvision2020's reply - apologies. In the image I posted if I right-click 'Windows 7.vmdk' in the Name column the option to rename is available.