I'm getting the following messages for one of the 4 hard drives connected to a VM
Lost access to volume
1) due to connectivity issues. Recovery attempt
is in progress and outcome will be reported
4/21/2010 1:16:16 PM
and then not even a second later:
Successfully restored access to volume 4bcce772-
following connectivity issues.
4/21/2010 1:16:16 PM
This message will continue on and off throughout the day. Eventually it says Lost access and never restores access. When this happens that VM completely freezes and I cannot do anything with it (have to reboot ESXi at this point)
The hard drive in question is 1 of 3 hard drives connected to the VM for a storage pool (4th VM HDD is from datastore as system disk). Its always the same hard drive and the other 2 storage drives don't have an issue.
Is the hard drive going bad? HD test came up clean on that drive.
I'm at a complete loss why this one hard drive is continously having these issues. I tried to look at the hostd logs, but I'm having a hard time deciphering them (time seems to be off compared to whats showin in vShpere).
Did a search, but nothing came up in regards to my specific issue.
ESXi v4.0.0 Build 244038
AMD Phenom 9850 BE
GB MB: BA-MA-770-UDR3
8GB DDR2 800
From the Logs it looks like it has problem with HA (Heartbeat) , You try the below solution or Remove the LUNs from heartbeat.
Please Mark the reply correct or Helpful.
This event indicates that the ESX host's connectivity to the volume (for which this event was generated) degraded due to the inability of the host to renew its heartbeat for period of approximately 16 seconds (the VMFS lock breaking lease timeout). After the periodic heartbeat renewal fails, VMFS declares that the heartbeat to the volume has timed out and suspends all I/O activity on the device until connectivity is restored or the device is declared inoperable.
Heartbeat Interval = 3 Seconds
If an ESX host has mounted a volume san-lun-100 from device naa.60060160b4111600826120bae2e3dd11:1 and loses connectivity (due to a cable pull, disk array failure, and so on) to the device for a period exceeding 16 seconds, the following error message appears:
Lost access to volume 496befed-1c79c817-6beb-001ec9b60619 (san-lun-100) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
All I/O, metadata operations to the specific volume from COS, user interface (vSphere Client), or virtual machines are internally queued and retried for some duration of time. If the volume or storage device connectivity is not restored within that duration of time, such I/O operations fail. This might have an impact on already running virtual machines as well as any new power on operations by virtual machines.
To resolve this issue:
To resolve this issue using the service console: