The logs tell the story of which datastore and path(s) failed.
[esx.problem.storage.redundancy.degraded] Path redundancy to storage device naa.60060160841039008b428b7a1d38e411 degraded. Path vmhba2:C0:T0:L1 is down. Affected datastores: "CT_LUN1_3TB".
it goes on to rattle off more entries.
So your CT_LUN1_3TB lost connectivity to the storage array. The NAA number can be used on the storage array side to uniquely identify which LUN on the array correlates to CT_LUN1_3TB.
Hi,
Is it FC,NFS, ISCSI or local storage.
Is it FC,NFS, ISCSI or local storage.
All the datastore are available on Esxi host ?.
Is it possible to upload vmkernel.log and vobd.log covering the Time stamp.
Follow the below respective kb's and troubleshoot
Troubleshooting connectivity issues to an NFS datastore on ESX and ...
https://kb.vmware.com/kb/1003967
Troubleshooting fibre channel storage connectivity (1003680 ...
https://kb.vmware.com/kb/1003680
Troubleshooting ESXi/ESX connectivity to iSCSI arrays using software ...
https://kb.vmware.com/kb/1003952
The logs tell the story of which datastore and path(s) failed.
[esx.problem.storage.redundancy.degraded] Path redundancy to storage device naa.60060160841039008b428b7a1d38e411 degraded. Path vmhba2:C0:T0:L1 is down. Affected datastores: "CT_LUN1_3TB".
it goes on to rattle off more entries.
So your CT_LUN1_3TB lost connectivity to the storage array. The NAA number can be used on the storage array side to uniquely identify which LUN on the array correlates to CT_LUN1_3TB.
Thanks for that. Suppose it only lost one path. Just find it strange that this information isn't available within the client and you have to dig through the logs.
Glad to help.
The information should be available under the hosts "events" section. However depending on how long ago the event occurred it may have rolled off from the view.
Also if you have your alarms configured for storage you will get an email alert with all the information (datastore, path, host ect..) as soon as it happens.