9 Posts
0
11560
ESXi datastore timeouts
hi all
on my Dell t410 running Esxi 6.7 i keep getting datastore timeouts for one of my Dell disks. I have moved slots still same issue. Also i have changed the timeout settings on Esxi. after a reboot it runs for few days and then i get sam error.
ScsiDeviceIO: 10347: READ CAPACITY on device "naa.690b11c01b61e80023ce5687082d3046" from Plugin "NMP" failed. I/O error
2019-01-17T13:14:25.118Z cpu10:2099236)WARNING: ScsiDeviceIO: 10347: READ CAPACITY on device "naa.690b11c01b61e80023ce5687082d3046" from Plugin "NMP" failed. I/O error
)ScsiDevice: 9827: Operation attach device not supported on device:naa.690b11c01b61e80023ce5687082d3046 in state:All Paths Down Timeout
Dell-DylanJ
4 Operator
4 Operator
•
2.9K Posts
0
January 17th, 2019 09:00
It may be the case that the drive is faulty, I would just recommend checking these things before jumping to that conclusion, in case there is something else happening.
Dell-DylanJ
4 Operator
4 Operator
•
2.9K Posts
0
January 17th, 2019 07:00
Hello,
How is the storage set up? Is this drive internal storage or external? Is it a member of a virtual disk, or is it being passed straight through to ESXi? What PERC is controlling the storage?
If you can acquire a PERC log, it may be helpful because it may yield some information on why the drive is getting an IO error. You can also run "esxcli hardware ipmi sel list > SEL.txt" to export the server's hardware log to see if the system is logging any hardware issues relating to storage.
zx10rsilver
9 Posts
0
January 17th, 2019 08:00
zx10rsilver
9 Posts
0
January 17th, 2019 09:00
ok will take a look, just was curious as i have 5 disks and this seems to be the only one with a problem
Dell-DylanJ
4 Operator
4 Operator
•
2.9K Posts
0
January 17th, 2019 09:00
If you're talking about the on-board PERC, that should be the S300. That controller is only meant for use with Windows operating systems. You could look at going into BIOS and turning RAID mode off and setting it to AHCI. If it is set to RAID mode, that would activate the software PERC, and that may be part of the problem.
As for the SEL, the only other way to get that would be either by accessing the iDRAC, or by booting to the live support image and launching OpenManage there. The S300 doesn't maintain a storage log, unfortunately.
I would recommend confirming that you are in AHCI mode, confirming the SEL is clear, and running the diagnostics on the server from the Lifecycle controller.