Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 189307

Cannot power on VM.

$
0
0

Hi All,

 

Recently I always encounter the issue that one or several VMs cannot be powered on after deployment. In the VMWare.log it will contains the following error message:

 

VMWare.log

Aug 12 13:49:41.175: vmx| DISKLIB-DSCPTR: Opened [0]: "021966-Win2K8R2SP1_80G_Clean-0-0-scsi-flat.vmdk" (0xe)

Aug 12 13:49:41.175: vmx| DISKLIB-LINK  : Opened '/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21966/021966-Win2K8R2SP1_80G_Clean-0-0-scsi.vmdk' (0xe): vmfs, 167772160 sectors / 80 GB.

Aug 12 13:49:41.186: vmx| DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 13, numSubChains = 1

Aug 12 13:49:41.419: vmx| DISKLIB-CHAINESX : ChainESXOpenSubChainNode: can't create deltadisk node 27a85124-030515-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk failed with error Not a directory

Aug 12 13:49:41.419: vmx| DISKLIB-CHAIN : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30515/030515-Win2K8R2SP1_80G_Clean-0-0-scsi.vmdk" : failed to open (Not a directory).

Aug 12 13:49:41.420: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30515/030515-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.421: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30207/030207-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.422: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30121/030121-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.423: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/24403/024403-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.425: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/23713/023713-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.426: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/22102/022102-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.427: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/22075/022075-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/22050/022050-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21998/021998-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21979/021979-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21978/021978-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21973/021973-Win2K8R2SP1_80G_Clean-0-0-scsi-delta.vmdk" : closed.

Aug 12 13:49:41.428: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/21966/021966-Win2K8R2SP1_80G_Clean-0-0-scsi-flat.vmdk" : closed.

Aug 12 13:49:41.429: vmx| DISKLIB-LIB   : Failed to open '/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30515/030515-Win2K8R2SP1_80G_Clean-0-0-scsi.vmdk' with flags 0xa (Not a directory).

Aug 12 13:49:41.429: vmx| DISK: Cannot open disk "/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30515/030515-Win2K8R2SP1_80G_Clean-0-0-scsi.vmdk": Not a directory (1310729).

Aug 12 13:49:41.429: vmx| Msg_Post: Error

Aug 12 13:49:41.429: vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4f2b7294-6a77fd3f-f49a-0024e82e2501/saaslm/30515/030515-Win2K8R2SP1_80G_Clean-0-0-scsi.vmdk' or one of the snapshot disks it depends on.

Aug 12 13:49:41.429: vmx| [msg.disk.configureDiskError] Reason: Not a directory.----------------------------------------

Aug 12 13:49:41.467: vmx| Module DiskEarly power on failed.

Aug 12 13:49:41.467: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

 

VCenter 4.0.0, 208111.

 

I searched here and did not found any similar issue with the error "Not a directory", dose anyone have some ideas about this? Thanks in advance.

 

Travis


Viewing all articles
Browse latest Browse all 189307

Trending Articles