tinajoe7
asked on
VMWare Server 2.0 virtual machine won't start
I am having an urgent issue with a virtual machine that won't start, that runs our ERP system. We were running out of disk space, and I added a data store, but then the virtual machine stopped with a message that there was insufficient disk space. I tried deleting the last snapshot to save space, and I tried moving some older files to a different drive, but then I got this error: . So I moved the old files back, but still get the message. Maybe it thinks there is a snapshot that is missing, but I don't know how to bypass this.
I attached the configuration file. Also, in the web interface for VMWare Server, it says "Hard Disk 2 (SCSI 0:1) Hard Disk not valid". But I can see all the files in the Virtual Machine Directory that it thinks are missing.
Help!!
thanks
Christina
terminal.emprod.lan.vmx.txt
Capture.PNG
I attached the configuration file. Also, in the web interface for VMWare Server, it says "Hard Disk 2 (SCSI 0:1) Hard Disk not valid". But I can see all the files in the Virtual Machine Directory that it thinks are missing.
Help!!
thanks
Christina
terminal.emprod.lan.vmx.txt
Capture.PNG
ASKER
I attached the log file, and screentshots of the web admin console and the virtual machine directory. What else would be helpful? Any help is greatly appreciated!
Thanks
Christina
vmware.log
Screentshot-1.docx
Screentshot-2.docx
Thanks
Christina
vmware.log
Screentshot-1.docx
Screentshot-2.docx
It looks like you have a virtual machine with 3 virtual disks, which has snapshots.
and it's possible that the last snapshot has got corrupted.
and it's possible that the last snapshot has got corrupted.
ASKER
So how can I "bypass" this snapshot, if that's possible, or load the virtual machine without it?
ASKER
Sorry, I guess I'm in panic mode, and didn't see the rest of your original comment. Here are my answers...
did you just delete the snapshot file in the file system ? - if you did you have corrupted your virtual disks, snapshots should not just be deleted and discarded on the file system. No, I removed it via the web admin interface.
do you have this file ? Yes, the file is there
terminal.emprod.lan-000004 .vmdk
did you just delete the snapshot file in the file system ? - if you did you have corrupted your virtual disks, snapshots should not just be deleted and discarded on the file system. No, I removed it via the web admin interface.
do you have this file ? Yes, the file is there
terminal.emprod.lan-000004
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi again James, not sure if you are still awake, but quick question: can the new virtual disks be on a different datastore/volume from the original virtual machine?
Not too sure who James is, Maybe James Bond!
but yes final post before bed!
Yes, the new disks can be on a different datastore, just specify the correct path to the destination vmdk.
off now.
but yes final post before bed!
Hi again James, not sure if you are still awake, but quick question: can the new virtual disks be on a different datastore/volume from the original virtual machine?
Yes, the new disks can be on a different datastore, just specify the correct path to the destination vmdk.
off now.
ASKER
Sorry--Andrew!
I tried executing the first command with the following syntax:
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-000004. vmdk" -t 2 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-.vmdk"
I got the following error: "Failed to convert disk: The called function cannot be performed on partial chains. Please open the parent virtual disk (0x500003e83)
I tried executing the first command with the following syntax:
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l
I got the following error: "Failed to convert disk: The called function cannot be performed on partial chains. Please open the parent virtual disk (0x500003e83)
As I wrote, if the snapshot is corrupted it will fail, and you'll need to discard that snapshot, and move onto the next good snapshot.
number 3! - terminal.emprod.lan\termin al.emprod. lan-000003 .vmdk
e.g.
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-000003. vmdk" -t 2 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-.vmdk"
number 3! - terminal.emprod.lan\termin
e.g.
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l
ASKER
When you say discard that snapshot, do you mean remove it from the virtual machine directory? And would I remove all the files associated with it, i..e. with -000004 in the file name?
just leave all files "as is".
re-run the command, but use the next snapshot available.
this will create a new disk, based on hopefully working and correct files.
re-run the command, but use the next snapshot available.
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.lan\termina l.emprod.l an-000003. vmdk" -t 2 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-.vmdk"
this will create a new disk, based on hopefully working and correct files.
ASKER
Oh boy. I tried the command with the -000003 and -000002 snapshots, and got the same error. Is it really possible they are all corrupted?
this is odd, but possibly they are corrupted.
can you try a different disk ?
can you try a different disk ?
ASKER
Sorry, what do mean by a different disk?
ASKER
Sorry, I guess you mean SCSI disk 1. I just tried that command with all three snapshots and got the same result.
As to SCSI disk 2, we aren't using that one, it was something I was testing to create more space on the virtual machine. I later removed that disk from the virtual machine. When I tried that one, I got a file not found error.
As to SCSI disk 2, we aren't using that one, it was something I was testing to create more space on the virtual machine. I later removed that disk from the virtual machine. When I tried that one, I got a file not found error.
try it on the other disks remaining disks, 1 and 2.
you have three!
vmware-vdiskmanager -r terminal.emprod.lan-000004 .vmdk -t 2 terminal.emprod.lan-.vmdk [scsi disk 0]
vmware-vdiskmanager -r terminal.emprod.lan_2-0000 04.vmdk -t 2 terminal.emprod.lan1.vmdk [scsi disk 1]
vmware-vdiskmanager -r terminal2.emprod.lan-00000 2.vmdk -t 2 terminal2.emprod.lan2.vmdk [scsi disk 2]
you have three!
vmware-vdiskmanager -r terminal.emprod.lan-000004
vmware-vdiskmanager -r terminal.emprod.lan_2-0000
vmware-vdiskmanager -r terminal2.emprod.lan-00000
ASKER
I think our posts might have crossed in the night, so I thought I'd repost my comment below, in case you didn't see it...
Sorry, I guess you mean SCSI disk 1. I just tried that command with all three snapshots and got the same result.
As to SCSI disk 2, we aren't using that one, it was something I was testing to create more space on the virtual machine. I later removed that disk from the virtual machine. When I tried that one, I got a file not found error.
Sorry, I guess you mean SCSI disk 1. I just tried that command with all three snapshots and got the same result.
As to SCSI disk 2, we aren't using that one, it was something I was testing to create more space on the virtual machine. I later removed that disk from the virtual machine. When I tried that one, I got a file not found error.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, I ran the two commands below, replacing the -000004 in the file names with both -000003 and -000002 (as below), and got the same error both times. Is there possibly some explanation other than corruption?
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-000002. vmdk" -t 2 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-.vmdk" [scsi disk 0]
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l an\termina l.emprod.l an_2-00000 2.vmdk" -t 2 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an1.vmdk" [scsi disk 1]
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l
vmware-vdiskmanager.exe -r "d:\virtual machines\terminal.emprod.l
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So it's basically the same command but with -t 0 instead of -t 2? I ran the command below
vmware-vdiskmanager -r "d:\virtual machines\terminal.emprod.l an\termina l.emprod.l an-000004. vmdk" -t 0 "H:\virtual machines\terminal.emprod.l an\termina l.emprod.l an.vmdk"
And got this error:
Failed to convert disk: The called function cannot be performed on partial chains.
Please open the parent virtual disk (0x500003e83).
I tried again replacing 4 with 2 and 3, and got the same error.
vmware-vdiskmanager -r "d:\virtual machines\terminal.emprod.l
And got this error:
Failed to convert disk: The called function cannot be performed on partial chains.
Please open the parent virtual disk (0x500003e83).
I tried again replacing 4 with 2 and 3, and got the same error.
Yes that's correct
Something is wrong with the snapshots
You could as a last resort either restore your backup
Or discard the last snapshot and try starting the VM
Something is wrong with the snapshots
You could as a last resort either restore your backup
Or discard the last snapshot and try starting the VM
ASKER
I don't have a backup (I know, I'm an idiot), so that's out. When you say discard the last snapshot, what is the correct way to go about that?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, I tried modifying the vmx file to point to 00003 and 00002, and got the same error I was getting yesterday.
"Power On Virtual Machine" failed to complete
DetailsVMware Server cannot find the virtual disk "terminal.emprod.lan_2.vmd k". Please verify the path is valid and try again. Cannot open the disk 'D:\Virtual Machines\terminal.emprod.l an\termina l.emprod.l an_2-00000 2.vmdk' or one of the snapshot disks it depends on. Reason: The system cannot find the file specified.
One more thing: in the VMWare console it shows this in the hardware section:
Hard Disk 2 (SCSI 0:1)
Hard disk not valid
Is this just because the files are corrupted?
"Power On Virtual Machine" failed to complete
DetailsVMware Server cannot find the virtual disk "terminal.emprod.lan_2.vmd
One more thing: in the VMWare console it shows this in the hardware section:
Hard Disk 2 (SCSI 0:1)
Hard disk not valid
Is this just because the files are corrupted?
just link to the file, without the -000002.vmdk.
remove all these references from the vmx.
remove all these references from the vmx.
ASKER
Sorry to be so slow, but is this what you mean (I changed the rows in bold)?
numvcpus = "2"
floppy0.present = "TRUE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
parallel0.present = "TRUE"
parallel0.fileType = "device"
parallel0.fileName = "auto-detect"
parallel0.autodetect = "TRUE"
serial0.present = "TRUE"
serial0.fileType = "device"
serial0.fileName = "auto-detect"
serial0.autodetect = "TRUE"
serial1.present = "TRUE"
serial1.fileType = "device"
serial1.fileName = "auto-detect"
serial1.autodetect = "TRUE"
usb.present = "TRUE"
ethernet0.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "bridged"
ethernet0.startConnected = "TRUE"
ide0:0.present = "TRUE"
ide0:0.autodetect = "TRUE"
ide0:0.filename = "auto detect"
ide0:0.deviceType = "cdrom-raw"
scsi0.present = "TRUE"
scsi0.virtualDev = "buslogic"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "terminal.emprod.lan.vmdk"
mks.enable3d = "TRUE"
vmci0.present = "TRUE"
buslogic.noDriver = "FALSE"
ehci.present = "TRUE"
annotation = ""
pciBridge0.present = "TRUE"
tools.upgrade.policy = "useGlobal"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
extendedConfigFile = "terminal.emprod.lan.vmxf"
virtualHW.productCompatibi lity = "hosted"
ethernet0.generatedAddress = "00:0c:29:8f:43:71"
uuid.location = "56 4d f0 0c a7 78 3a fc-64 69 ae f2 de 8f 43 71"
uuid.bios = "56 4d f0 0c a7 78 3a fc-64 69 ae f2 de 8f 43 71"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "67108864"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
vmci0.pciSlotNumber = "35"
usb:0.present = "TRUE"
usb:1.present = "TRUE"
ethernet0.generatedAddress Offset = "0"
vmci0.id = "-561036431"
tools.remindInstall = "FALSE"
usb:1.deviceType = "hub"
usb:0.deviceType = "mouse"
parallel0.startConnected = "FALSE"
floppy0.startConnected = "FALSE"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "terminal.emprod.lan_2.vmd k"
scsi0:1.writeThrough = "TRUE"
scsi0:1.redo = ""
ide0:0.startConnected = "TRUE"
tools.syncTime = "FALSE"
checkpoint.vmState = ""
scsi0:2.fileName = "terminal2.emprod.lan-0000 02.vmdk"
scsi0:2.mode = "persistent"
scsi0:2.present = "FALSE"
scsi0:2.redo = ""
numvcpus = "2"
floppy0.present = "TRUE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
parallel0.present = "TRUE"
parallel0.fileType = "device"
parallel0.fileName = "auto-detect"
parallel0.autodetect = "TRUE"
serial0.present = "TRUE"
serial0.fileType = "device"
serial0.fileName = "auto-detect"
serial0.autodetect = "TRUE"
serial1.present = "TRUE"
serial1.fileType = "device"
serial1.fileName = "auto-detect"
serial1.autodetect = "TRUE"
usb.present = "TRUE"
ethernet0.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "bridged"
ethernet0.startConnected = "TRUE"
ide0:0.present = "TRUE"
ide0:0.autodetect = "TRUE"
ide0:0.filename = "auto detect"
ide0:0.deviceType = "cdrom-raw"
scsi0.present = "TRUE"
scsi0.virtualDev = "buslogic"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "terminal.emprod.lan.vmdk"
mks.enable3d = "TRUE"
vmci0.present = "TRUE"
buslogic.noDriver = "FALSE"
ehci.present = "TRUE"
annotation = ""
pciBridge0.present = "TRUE"
tools.upgrade.policy = "useGlobal"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
extendedConfigFile = "terminal.emprod.lan.vmxf"
virtualHW.productCompatibi
ethernet0.generatedAddress
uuid.location = "56 4d f0 0c a7 78 3a fc-64 69 ae f2 de 8f 43 71"
uuid.bios = "56 4d f0 0c a7 78 3a fc-64 69 ae f2 de 8f 43 71"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "67108864"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
vmci0.pciSlotNumber = "35"
usb:0.present = "TRUE"
usb:1.present = "TRUE"
ethernet0.generatedAddress
vmci0.id = "-561036431"
tools.remindInstall = "FALSE"
usb:1.deviceType = "hub"
usb:0.deviceType = "mouse"
parallel0.startConnected = "FALSE"
floppy0.startConnected = "FALSE"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "terminal.emprod.lan_2.vmd
scsi0:1.writeThrough = "TRUE"
scsi0:1.redo = ""
ide0:0.startConnected = "TRUE"
tools.syncTime = "FALSE"
checkpoint.vmState = ""
scsi0:2.fileName = "terminal2.emprod.lan-0000
scsi0:2.mode = "persistent"
scsi0:2.present = "FALSE"
scsi0:2.redo = ""
correct
ASKER
Thanks so much for your help!
Most definitely caused by a snapshot, which the virtual machine has been running on, and when the space on the datastore fills up, and there is no space, the snapshot virtual machine cannot write and the VM fails, and stops.
When this happens there is a risk, of snapshot corruption and disk failure.
Can you screenshot the files which you have available.
But I've also read.....
did you just delete the snapshot file in the file system ? - if you did you have corrupted your virtual disks, snapshots should not just be deleted and discarded on the file system.
they need to be managed and handled correctly ?
can you please confirm, how did did this ?
do you have this file ?
terminal.emprod.lan-000004