George_Yu
Contributor
Contributor

vDISK missing, can't delete it on VM Edit Settings...

Jump to solution

one vDisk( not C drive) missing, can't delete it on VM Edit Settings... and can' boot it, get error message below:

Capture.PNG

How can I delete it and let the VM boot.

thank,

0 Kudos
1 Solution

Accepted Solutions
vGuy
Expert
Expert

vmx only has a reference to virtual disk 1...there is no reference to VD 2 & 3.

can you unregister the VM --> restart the management services --> re-register the VM and see if it works.

Alternately you may perhaps create a new vmx:

--> unregister the VM --> create new VM --> select "Use existing Virtual Disk" instead of create new disk --> point to the virtual disk 1 --> and follow the wizard.

View solution in original post

0 Kudos
6 Replies
vGuy
Expert
Expert

Does the vmdk file exist on the Datastore. Have you already tried rescanning the Storage.

If the vmdk file does not exist, you will need to unregister the VM -> Login to the ESX/i host -> edit .vmx file to remove the SCSI entries corresponding to the virtual disk (scsi entries can be identified from edit settings). Although ensure to take a backup of the .vmx file.

George_Yu
Contributor
Contributor

After the VM was removed from inventory. I only can see the.vmx file by Datastorage Browser, can't edit it.

Do you mean I need to login host, use Vi to edit it?

If yes. where it is?

thanks,

0 Kudos
sparrowangelste
Virtuoso
Virtuoso

if tyou are having problems changing the vm's setting's you might have to restart the management services on the host, or even reboot it (less likely).

--------------------- Sparrowangelstechnology : Vmware lover http://sparrowangelstechnology.blogspot.com
0 Kudos
vGuy
Expert
Expert

George Yu wrote:

Do you mean I need to login host, use Vi to edit it?

If yes. where it is?

Yes, login to the host via CLI --> cd to the /vmfs/volumes/<Datastore>/<VM Name>/ --> vi <VM_name.vmx> --> remove the entries corresponding to SCSI device ID of the problem virtual disk --> then re-register the VM.

(SCSI device ID can be identified from the VM edit settings).

George_Yu
Contributor
Contributor

vGuy,

I did like you said. Then I can't fine the entry of the lost hard drive in .vmx. Please see the vmx file below:

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "8"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

hpet0.present = "TRUE"

nvram = "Win2003.nvram"

virtualHW.productCompatibility = "hosted"

powerType.powerOff = "soft"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "soft"

displayName = "SCCM2007"

extendedConfigFile = "Win2003.vmxf"

scsi0.present = "TRUE"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "2048"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Win2003.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

ide1:0.present = "TRUE"

ide1:0.fileName = ""

ide1:0.deviceType = "atapi-cdrom"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "vmxnet"

ethernet0.features = "15"

ethernet0.dvs.switchId = ""

ethernet0.dvs.portId = ""

ethernet0.dvs.portgroupId = ""

- Win2003.vmx 1/102 0%

Edit Setting... on the VM, can see 3 hard disks, the second hard drive is lost as the storage iSCI1 was erroneously deleted.

1.png

Now, the third also is a problem. First, it apeared automaticly after registered the VM. I didn't creasted it before. And it can't be removed like the second hard disk, neither revised the size:

2135917-2.png

0 Kudos
vGuy
Expert
Expert

vmx only has a reference to virtual disk 1...there is no reference to VD 2 & 3.

can you unregister the VM --> restart the management services --> re-register the VM and see if it works.

Alternately you may perhaps create a new vmx:

--> unregister the VM --> create new VM --> select "Use existing Virtual Disk" instead of create new disk --> point to the virtual disk 1 --> and follow the wizard.

0 Kudos