Unsolved
This post is more than 5 years old
2 Intern
•
5.7K Posts
2
12357
February 6th, 2014 03:00
Lost access to volume.... successfully restored access to volume.....
A customer of mine is seeing a lot of these errors on ESX 4.1 as well as ESX 5.1. Some hosts are running on 4Gb FC, others on 8Gb FC. The hosts are connected to several VNXs and can't be related to a single VNX.
Does anyone have any ideas of what this can be? Thus far EMC as well as VMware have no clue what causes this.
No Events found!
Conor
341 Posts
0
February 6th, 2014 03:00
These are datastore timeouts, where the datastore heartbeat has not responded withing the timeout period.
Are you seeing any PowerPath or NMP messages relating to path failures in the vmkernel.log?
Any SCSI errors in the vmkernel.log?
Any device latency warnings?
Other performance issues being reported from the VNX?
Care to post up any errors from that log (with customer's permission)
RRR
2 Intern
•
5.7K Posts
0
February 6th, 2014 08:00
I'll ask for them first thing tomorrow morning! Thanks for the help.
manuel2016
1 Message
0
September 23rd, 2015 08:00
Hi Guys, were you able to find a solution for this?
PedalHarder
465 Posts
0
September 27th, 2015 16:00
If you are getting these messages, check the error counters on the switch ports (and fabric interconnects if a blade chassis is involved) and also the device and adapter stats in ESX with commands:
localcli storage core device stats get
localcli storage core adapter get
If you are seeing error counters incrementing, you are very likely to have a physical connectivity issue.
RRR
2 Intern
•
5.7K Posts
0
September 28th, 2015 22:00
And that's the thing: we don't see that. All error counters on switch ports are zero (0). As far as we can see on the SAN and on the storage side there's no buggy connections. Also we don't see anything in the storage processor's logs about hosts loosing connections. So my conclusion is that it has to be something on the server side. And it's not bound to a specific ESX version as well: I've been seeing these kind of errors since 10 years or so and no matter what upgrade, and what version is running, ESX servers have always displayed errors like this. I'm very interested in seeing a solution for this as the VMware dudes are loosing their minds over this as well.
priyesh88
5 Posts
0
July 16th, 2017 14:00
hi,
were you able to a solution for this?
RRR
2 Intern
•
5.7K Posts
0
July 19th, 2017 23:00
Unfortunately not. We've been seeing this for years already. Since then we've replaced servers (1U models, blades, you name it), SAN switches (Cisco 9124/34, 9222i, 9148, 9148S, 9250i, 9396) and even the storage arrays (Clariion, VNX, Unity) and of course several firmware upgrades on all equipment. Where the errors come from, we never found out (and it's still going on too!!).
So if somebody has these errors too, please join the conversation!!
kisitu
1 Rookie
•
4 Posts
0
November 15th, 2024 14:20
Hello Team,
this is 2024, am facing this error any one with a probable solution?