Skip to main content
NetApp Knowledge Base

NS224 DISK REDUNDANCY FAILED ERROR after disk replacement with no missing drives

  1. Last updated
  2. Save as PDF
Views:
99
Visibility:
Public
Votes:
0
Category:
disk-shelves
Specialty:
hw
Last Updated:

Applies to

  • NS224 shelf running fw. 2.10
  • Disk replacement after failure

Issue

  • Disk failed and replaced
  • After disk replacement, AutoSupport send messages with:
[...: dsa_disc: callhome.dsk.redun.fault:debug]: Call home for DISK REDUNDANCY FAILED
  • NSM100 module issue reported but cleared
[node_name-01: mgwd: callhome.hm.alert.major:debug]: Call home for Health Monitor process schm: NoPathFromSwitchToNSM_Alert[1.1:A].
 
Alert ID           NoPathFromSwitchToNSM_Alert
Description        Storage shelf 1.1 module A is not connected to storage switches.
Corrective Actions Connect shelf 1.1 module A to two storage switches, following the guide applicable to your shelf.
Possible Effect    Access to shelf 1.1 can be lost with a single shelf module failure.
 
[node_name-01: schmd: hm.alert.cleared:debug]: Alert Id = NoPathFromSwitchToNSM_Alert , Alerting Resource = 1.2:A cleared by monitor system-connect
  • System storage transition from Quad-Path to Mixed-Path HA
[node_name-01: shelf.config.tomixedha:notice]: System has transitioned to a mixture of single, multi-path or quad-path storage configurations.

[node_name-02: shelf.config.tomixedha:notice]: System has transitioned to a mixture of single, multi-path or quad-path storage configurations.

  • Replaced disk is not reporting the paths/connections through the other NSM100 module.
    • Discovered paths
node_name-02:e4b.01.1.5
node_name-02:e4a.01.0.5
node_name-01:e4b.01.1.5
node_name-01:e4a.01.0.5
    • Missing paths:
node_name-01:e4a.01.2.5
node_name-01:e4b.01.3.5
node_name-02:e4b.01.3.5
node_name-02:e4a.01.2.5
  • No erros found in any shelf component, including disks.
  • The issue remains after the disk replacement / re-seat
  • The issue remains after the NSM100 A module re-seat
  • The issue remains after both NSM100 modules 'soft reboot'

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.