Skip to main content
NetApp Knowledge Base

What does "Isolation of drive causing redundancy mismatch" mean?

  1. Last updated
  2. Save as PDF
Views:
2,267
Visibility:
Public
Votes:
1
Category:
disk-drives
Specialty:
esg
Last Updated:

​ ​ ​  

Applies to

E-Series

Answer

  • Isolation of drive causing redundancy mismatch is MEL event type 2046.
  • Isolation of drive causing redundancy mismatch is a data parity mismatch for which the controller firmware can isolate the mismatch to a single drive.
    • This is only possible for RAID 6 volume groups and Dynamic Disk Pools.
  • Typically if a drive has been isolated it can be replaced, however, we do want to perform troubleshooting first. For additional troubleshooting steps, check out the E-Series Isolation of drive causing redundancy mismatch - AutoSupport Message article.
    • In case the defined troubleshooting steps are not followed, then data integrity may be propagated to user data blocks that were previously intact.

Additional Information

N/A

 

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.