Corrupt lock detected.....

[TCP]

Hi All.

I get the following error when trying to access a one of my VM's console in VI Inventory - "Virtual machine config file does not exist".

In vmkernel I find many errors messages like:

vmkernel: 15:13:16:42.169 cpu3:1091)<6>Debug scsi underrun

vmkernel: 15:13:16:10.703 cpu3:1041)WARNING: FS3: 5507: FS 479885c6-516e1dc6-4c5b-00145ec2c8ec may be damaged. Corrupt lock detected: [type c2c2c3c2 offset 14033993530586874562 v 14033993530586874562, hb offset 14033993530586874562

vmkernel: gen 14033993530586874562

Any ideas?

Thanks.

[mikepodoherty]

Is the VM on the same storage as the Vms you can access or different storage - I've seen a similar error when we lost connection to the SAN - we had problems accessing one VM that we were restarting after patching and then we eventually lost communications to all the VMs. Had to represent the servers to the SAN and that fixed the problem.

You can also check in the datastore to verify that the config file still exists.

[TCP]

This VM works properly, I can access to VM through RDP, but can't access through VI Console.

Than i try to check files on the Datastore I recieve message:

# ls

ls: reading directory .: Invalid argument

#

[TCP]

I have find one more error message in vmkwarning:

svr vmkernel: 14:18:44:48.033 cpu3:1043)WARNING: SCSI: 119: Failing I/O due to too many reservation conflicts

svr vmkernel: 14:18:44:48.033 cpu3:1043)WARNING: FS3: 4785: Reservation error: SCSI reservation conflict

svr vmkernel: 14:18:44:48.033 cpu3:1043)WARNING: FS3: 4979: Reclaiming timed out heartbeat http://HB state abcdef02 offset 3528192 gen 161 stamp 1277081888490 uuid 48a7f9d6-b121fc3e-75ba-001a64760040 jrnl <FB 10197> drv 4.31 failed: SCSI reservation conflict

[petedr]

It good be that the scsi reservations issues you are seeing may be the cause of the problem. Any logging or issues on your SAN side.

[Texiwill]

Hello,

I would backup the VM data using traditional backup means.

THe main issue is that the mount point looks to have gone away on your ESX server, this is never a good thing. Which means the files that the VM is using have also gone away.

I would check presentation, zoning, and possibly reboot the ESX host. The LUN itself may also be corrupt.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization