Skip to main content
NetApp Knowledge Base

How to force rediscovery for Volumes Not on Preferred Path on StorageGRID Appliance

  1. Last updated
  2. Save as PDF
Views:
905
Visibility:
Public
Votes:
0
Category:
e-series-santricity-storage-manager
Specialty:
esg
Last Updated:
  •  

Applies to

  • NetApp StorageGrid SG6060
  • NetApp StorageGrid SG57xx
  • NetApp StorageGrid SG56xx

Description

E-Series SANtricity reports Volumes not on preferred path. 

  • From affected node, run-host-command multipath -ll output shows secondary failback path failed :

| |- X:X:Y:Y sdbc 67:96 active ready running
| `- X:X:Y:Y sdbu 68:128 active ready running
`-+- policy='service-time 0' prio=0 status=enabled
|- #:#:#:# sds 65:32 failed faulty running
`- #:#:#:# sdak 66:64 failed faulty running

  • kern.logs :

localhost kernel: device-mapper: multipath: Failing path 65:32.
localhost kernel: device-mapper: multipath: Failing path 66:64.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.