Skip to main content
NetApp Knowledge Base

E-Series "Isolation of drive causing redundancy mismatch" - AutoSupport Message

  1. Last updated
    May 19, 2025
  2. Save as PDF
Views:
5,228
Visibility:
Public
Votes:
2
Category:
disk-drives
Specialty:
esg
Last Updated:
5/19/2025, 1:44:46 AM

​ ​

Applies to

  • NetApp E-Series
  • Dynamic Disk Pools (DDP)
  • RAID6 Volume Groups (VG)

Event Summary

The controller detected a data parity mismatch and isolated the mismatch to a single drive.

Validate

If the CRITICAL event of Isolation of drive causing redundancy mismatch or Data/parity mismatch on volume gets reported by ASUP, it is required to execute this procedure.

Resolution

  1. From the Support > Events section in SANtricity System Manager, identify the most recent Media scan operation (Event ID 2022) before the isolation event was logged.
  2. If this is a isolation event against a single drive perform the steps immediately after this step. If against multiple proceed to step 3. 
  3. Check the volume that is being scanned, ensure it has completed the scan on that volume. 
  4. Media scan (scrub) started - Volume_1
  5. Media scan (scrub) completed - Volume_1
  6. Verify once the scan completes if the isolation events were logged against a single or multiple drives. 
    1. If the events were logged against a single drive, then the drive must be failed and replaced. When failing the drive, you must leave the Copy Content Before Fail box unchecked. Please engage NetApp Technical Technical Support to issue a drive replacement.
    2. If the events were logged against multiple drives, then proceed to next step.
  7. Follow the steps described in the following articles as applicable to check and repair the data/parity mismatch if this is across multiple drives or volumes:
    1. Using CLI on systems running pre-11.80 OS: How to check/repair volume parity errors on E-Series arrays running pre-11.80 OS
    2. Using API on systems running 11.80 or newer OS: How to check/repair volume parity errors on E-Series arrays running 11.80 or newer OS via API
    3. Using CLI on systems running 11.80 or newer OS: How to check/repair volume parity errors via CLI on E-Series arrays running 11.80 or newer
  8.  If additional volumes exist in the volume group or disk pool, then the scan/repair is recommended to those volumes as well.
  9. After the scan/repair is completed, and only if the isolation of drive causing redundancy mismatch identified a unique (singular) drive, the fail and replace the drive. When failing the drive leave the Copy Content Before Fail box unchecked.

Additional Information

 

 

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.