Hi,
I have recently bought a brand new HP ProLiant ML110 (G5) for my VMware environment at home - which is going great so far
I have successfully migrated 2 windows server 2008 virtual machines from my old Vmware Server 2 (running on ubuntu server 64-bit) by just copying the virtual hard disks across and creating new virtual machines with those disks on the new box. I have a third 2008 VM which is having some issues though. When you try to boot up the virtual machine the vSphere client displays the following message:
"Cannot open the disk '/vmfs/volumes/blah.../File Server/os/FileServer.vmdk' or one of the snapshot disks it depends on. Reason: Broken pipe."
This disk was working perfectly fine just this morning on the old box, so I am unsure as to why it has failed. Below is the contents of the .vmdk file - I cannot see anything obviously wrong with it at the moment, but I have not been on the virtualisation bandwagon for very long, and am far from an expert in it
encoding="UTF-8"
CID=540e3393
parentCID=ffffffff
createType="twoGbMaxExtentSparse"
RW 4192256 SPARSE "File Server-s002.vmdk"
RW 4192256 SPARSE "File Server-s003.vmdk"
RW 4192256 SPARSE "File Server-s004.vmdk"
RW 4192256 SPARSE "File Server-s005.vmdk"
RW 4192256 SPARSE "File Server-s006.vmdk"
RW 4192256 SPARSE "File Server-s007.vmdk"
RW 4192256 SPARSE "File Server-s008.vmdk"
RW 4192256 SPARSE "File Server-s009.vmdk"
RW 4192256 SPARSE "File Server-s010.vmdk"
RW 4192256 SPARSE "File Server-s011.vmdk"
RW 4192256 SPARSE "File Server-s012.vmdk"
RW 24576 SPARSE "File Server-s013.vmdk"
ddb.virtualHWVersion = "7"
ddb.uuid = "60 00 C2 90 58 26 ac 7e-55 a7 bf ee d1 05 08 ff"
ddb.geometry.cylinders = "3133"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
ddb.toolsVersion = "7397"
I have attached the file aswell because this forum converts the number signs to actual numbers!
Any advice on this situation would be great,
Thanks - Aaron Trout
I have recently bought a brand new HP ProLiant ML110 (G5) for my VMware environment at home - which is going great so far
I have successfully migrated 2 windows server 2008 virtual machines from my old Vmware Server 2 (running on ubuntu server 64-bit) by just copying the virtual hard disks across and creating new virtual machines with those disks on the new box. I have a third 2008 VM which is having some issues though. When you try to boot up the virtual machine the vSphere client displays the following message:
"Cannot open the disk '/vmfs/volumes/blah.../File Server/os/FileServer.vmdk' or one of the snapshot disks it depends on. Reason: Broken pipe."
This disk was working perfectly fine just this morning on the old box, so I am unsure as to why it has failed. Below is the contents of the .vmdk file - I cannot see anything obviously wrong with it at the moment, but I have not been on the virtualisation bandwagon for very long, and am far from an expert in it
- Disk DescriptorFile
encoding="UTF-8"
CID=540e3393
parentCID=ffffffff
createType="twoGbMaxExtentSparse"
- Extent description
RW 4192256 SPARSE "File Server-s002.vmdk"
RW 4192256 SPARSE "File Server-s003.vmdk"
RW 4192256 SPARSE "File Server-s004.vmdk"
RW 4192256 SPARSE "File Server-s005.vmdk"
RW 4192256 SPARSE "File Server-s006.vmdk"
RW 4192256 SPARSE "File Server-s007.vmdk"
RW 4192256 SPARSE "File Server-s008.vmdk"
RW 4192256 SPARSE "File Server-s009.vmdk"
RW 4192256 SPARSE "File Server-s010.vmdk"
RW 4192256 SPARSE "File Server-s011.vmdk"
RW 4192256 SPARSE "File Server-s012.vmdk"
RW 24576 SPARSE "File Server-s013.vmdk"
- The Disk Data Base
ddb.virtualHWVersion = "7"
ddb.uuid = "60 00 C2 90 58 26 ac 7e-55 a7 bf ee d1 05 08 ff"
ddb.geometry.cylinders = "3133"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
ddb.toolsVersion = "7397"
I have attached the file aswell because this forum converts the number signs to actual numbers!
Any advice on this situation would be great,
Thanks - Aaron Trout
Attachments:
- File Server.vmdk (940 bytes)
Tags:
esx4i,
error,
vmdk,
broken_pipe