VMware Cloud Community
max70
Contributor
Contributor

Virtual machines don't boot for strange vmdk lock

Hi all,

i have a 3.5 esxi server with 12 VM. Last night the machine was turned off by a power failure and now only 2 of my VM are booting.

The other machines don't boot complaining they cannot open vmdk, file. I attach part of the log of one of my machines:

I tried all suggestions i found googling internet but none of them worked. I can't find any process locking vmdk files on esxi. A reboot of the server did not solve the problem.

Has anyone some suggestions?

Thanks in advance

....

Oct 30 08:08:53.700: vmx| Mapped mainmem as pageable

Oct 30 08:08:53.700: vmx| MStat: Creating Stat vm.uptime

Oct 30 08:08:53.700: vmx| MStat: Creating Stat vm.suspendTime

Oct 30 08:08:53.700: vmx| MStat: Creating Stat vm.powerOnTimeStamp

Oct 30 08:08:53.705: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 30 08:08:53.710: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk' persistent R[(null)]

Oct 30 08:08:53.747: vmx| DISKLIB-VMFS : "/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2-flat.vmdk" : failed to open (327689): AIOMgr_Open failed. Type 3

Oct 30 08:08:53.748: vmx| DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode

Oct 30 08:08:53.748: vmx| DISKLIB-LINK : "/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk" : failed to open (Input/output error).

Oct 30 08:08:53.748: vmx| DISKLIB-CHAIN : "/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk" : failed to open (Input/output error).

Oct 30 08:08:53.748: vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk' with flags 0xa (Input/output error).

Oct 30 08:08:53.748: vmx| DISK: Cannot open disk "/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk": Input/output error (327689).

Oct 30 08:08:53.748: vmx| Msg_Post: Error

Oct 30 08:08:53.748: vmx| http://msg.disk.noBackEnd Cannot open the disk '/vmfs/volumes/489ce6a5-2b89324d-6079-00151780605d/fenice2/fenice2.vmdk' or one of the snapshot disks it depends on.

Oct 30 08:08:53.748: vmx| http://msg.disk.configureDiskError Reason: Input/output error.----


Oct 30 08:08:53.754: vmx| Module DiskEarly power on failed.

Oct 30 08:08:53.754: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

Oct 30 08:08:53.755: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Oct 30 08:08:54.854: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Oct 30 08:08:54.854: vmx| VMX idle exit

Oct 30 08:08:54.857: vmx| Flushing VMX VMDB connections

Oct 30 08:08:54.857: vmx| IPC_exit: disconnecting all threads

Oct 30 08:08:54.857: vmx| VMX exit (0).

Oct 30 08:08:54.857: vmx| AIOMGR-S : stat o=1 r=0 w=0 i=0 br=0 bw=0

Oct 30 08:08:54.857: vmx| VMX has left the building: 0.

Tags (3)
Reply
0 Kudos
2 Replies
Dave_Mishchenko
Immortal
Immortal

VMX has left the building: 0.

It appears that the VM has gone on vacation :).

For one of the VMs, could you post a list of files for the folder and the entire latest vmwareX.log file?

Reply
0 Kudos
max70
Contributor
Contributor

I opened a support call with vmware and found that the raid5 array

was broken, there was a logical read error in the first 30Mb of the

disk. I had to re-install esxi server and restore virtual machines.

Now server is up and running. Hope will not happen again...

Reply
0 Kudos