Unable to power VM on after ESX upgarde

[arturka]

Hi

I have a problem with power on one of my VM's after hosts upgrade. Hosts were upgraded from ESX 3.5 U5 to 4.0.3 .

Here there an error message from VM

Power On virtual machine ermwp10 Cannot open the disk
'/vmfs/volumes/4da2fa13-2a-bb836a-495a-00237da9896a/ermwp10/ermwp10.vmdk' or one of the snapshot disks it depends on. Reason: The file specified is not a virtual disk.

There were no snapshots at all on that VM, vmdk and flat files are exists

Unregister and register back VM doesn't help, I think it might be a problem with vmdk file descriptor but I don't know how to play with it.

Below vmdk descriptor OS disk

# Disk DescriptorFile
version=1
CID=2b091f55
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 104857600 VMFS "ermwp10_1-flat.vmdk"

# The Disk Data Base
#DDB

ddb.toolsVersion = "7302"
ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "6527"
ddb.uuid = "60 00 C2 94 0b 5b 9c 5e-a8 4c 19 94 4f 67 87 9e"
ddb.virtualHWVersion = "4"

Below vmdk descriptor DATA disk

# Disk DescriptorFile
version=1
CID=2b091f55
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 104857600 VMFS "ermwp10_1-flat.vmdk"

# The Disk Data Base
#DDB

ddb.toolsVersion = "7302"
ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "6527"
ddb.uuid = "60 00 C2 94 0b 5b 9c 5e-a8 4c 19 94 4f 67 87 9e"
ddb.virtualHWVersion = "4"

Thanks in advance for any help

Artur

[a_p_]

I really hope it's just a copy&paste issue that both virtual disks use the same flat file

Anyway, please attach the vmware.log file from the VM's folder to be able to find out what causes the issue.

André

[arturka]

Hi

Sorry for late response

I really hope it's just a copy&paste issue that both virtual disks use the same flat file

Upps, my mistake, of course both disks uses different flat files

here is the story

I've moved VM to ESX 3.5 ( one left in a farm) and VM started without problems however I cannot clone it, sMotion it, cannot do nothing what is related with disk. I tryied to make an image from OS drive (clonezilla  and GParted) but tools says that partition table is corrupted or broken. From what I can see, VMDK size is 10GB but on OS level is visible only 9.5 GB (this same size is shown in Gparted and clonezilla). here you have a printscreen from datastore view

disk is THICK

Any ideas ?

P.S

vmkfstools didn't help as well, clone and copy stops at 92% with error

Cheers
Artur

Please, don't forget the awarding points for "helpful" and/or "correct" answers.

[Rubeck]

Recreating the descriptor file dosn't help either?

http://kb.vmware.com/kb/1002511

/Rubeck

[a_p_]

If you can confirm that the physical size if the flat.vmdk is 9,601,810,432 bytes (ls -lisa) then try to:

• backup the current ermwp10.vmdk descriptor file
• modify the size in the original descriptor file as shown below
• clone the virtual disk using vmkfstools -i ermwp10.vmdk ermwp10-clone.vmdk (just to see whether this works)
• take a snapshot
• power on the VM

To be honest, I have no idea why there is a difference in the sizes, so carefully check everything if the VM powers up before using it in production again!

André

# Disk DescriptorFile
version=1
CID=bd86e6ed
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 18753536 VMFS "ermwp10-flat.vmdk"

# The Disk Data Base
#DDB

ddb.toolsVersion = "7302"
ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "1167"
ddb.virtualHWVersion = "4"

[arturka]

Well,

it works

I recreated disk descriptor and VM's powered on on vSphere without problems. But I did that yesterday already (recreated vmdk descriptor) and it didn't worked, so WTH. Anyway, thanks a lot for your help guys.

Cheers
Artur

Please, don't forget the awarding points for "helpful" and/or "correct" answers.

[Rubeck · Accepted solution]

Happy to hear you've made it work... Just one of those things, I guess :smileyconfused:

/Rubeck

[arturka]

Happy to hear you've made it work... Just one of those things, I guess :smileyconfused:

Yea, most probably, but now I can build my schedule for VMworld without any obstacles

Cheers
Artur

Please, don't forget the awarding points for "helpful" and/or "correct" answers.