do you face any issues, like hanging VM guests, SCSI disks errors in the VM guest eventlog or high latencies? If not, I suggest to update the drivers (update to 6.0U1 with a HP customized image) and check if the error occurs again.
The issue existed before I installed any guests. I watched it for a few days (with no guests) and the event error appeared periodically.
I then installed a guest as a test, and the guest does hang for a second when the event occurs.
When it first occurred I thought it was related to a bad disc in the newly built array I put together. I replaced the disk, the array rebuilt, and there are no other bad disks right now. Yet the error continues.
I guess if there are no other options I will look to do the 6.0update1 which was just recently released as soon as I can.
try to update to 6.0U1. Make sure that you use a HP customized ISO. If the error isn't resolved with this update, you should open a support case. This isn't a normal behaviour.
Do you have a spare drive configured? I have seen this problem on HP servers with P410i controller when a spare drive is configured. Try removing the spare drive and see if that cures the problem.
The November 6.0 U1 HP image contains the hpsa driver 220.127.116.11.
So as already said before, U1 should improve this.
Ok, I must be on the simple side here, but check the cable from the controller to the disk backplane. Also check the battery on the controller
I have just updated to 6.0 update1 (build 3073146) using the HP image so we'll see how it goes. I will update this thread.
It looks promising because before this I noticed that my Performance Chart for Disk had non-stop activity on it, even though I had no guest VMs running. Now I only see minimum activity on the Disk chart. Interesting.
Yes, I do have a spare drive configured in the Raid5 config of the p410i. If the update above doesn't solve the issue, my next action will be to remove the spare as some have suggested.
I completed the upgrade to 6.0update1 at around 6:15pm tonight.
I'm checking vSphere event log now and I still see the error appearing at 7:20pm, 8:20pm, 9:35pm, 10:50pm, 11:50pm, 1:26am, 2:26am.
I get the "Lost access to volume" and then immediately get "Successfully restored access to volume" within the same second.
It appears to happen every hour (but sometimes a little more than an hour). This leads me to believe it's related to some kind of heartbeat for the storage array.
The VMware knowledge base is down right now so I can't search anything on this topic, but if I highlight the event and click the "Ask VMware" button it tries to search for an article related to esx.problem.vmfs.heartbeat.timedout
Since I only have VMware Essentials license I can't seem to open a support ticket with them.
I haven't had a chance to remove the Spare Drive in the raid to try that approach yet.
I did find this KB about the vmfs heartbeat in ESXi 6.0, so I just gave this a try to disable it: Enabling or disabling VAAI ATS heartbeat (2113956)
We'll see what happens I guess....
See my post below - talk about horrible issues. Try the latest build see if like the iSCSI issues we are seeing those "APIs" also mysteriously fix your issues, too. Or, that the driver has been updated.
Did you ever resolve this? I have ESXI 6 build 3247720 with RAID 10 and one spare on a new dell R730 and every time I start a vm on the server the entire server looses the local volume and then one minute later it reconnects and everything starts to work properly.
I haven't tried updating the firmware on the dell server yet.
I have not tried it, but the best option at this point seems to be to remove the hot spare from the raid config.
See this thread:
ok, I will try that on my dell box. It is so odd....I can make it happen every time I restart my Windows 7 or Windows 8 VDIs.
I am also going to update the firmware and see if that fixes it.
Doesn't happen when I restart the server vdis...only the desktops. If I move the desktops to my synology NAS it works fine and the host never looses the LOCAL storage.
can you see any events in vmkernel similar to following?
ATS Miscompare detected beween test and set HB images at offset XXX on vol YYY
Please find an article on heatbeat issue with the error message mentioned in this thread. Though the article is related to IBM its worth read.
If you find this or any other answer useful please mark the answer as correct or helpful.