Skip to main content
NetApp Knowledge Base

Which EMS messages indicate the occurrence of bad data?

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Answer

  • Bad data occurrence refers to events indicating data corruption or loss (such as file corruption, disk label inconsistencies, RAID or WAFL errors). 
  • The following EMS messages are representative indicators of such events:
    • Checksum/WAFL related (data corruption):
      • raid.cksum.wc.blkErr
        • Indicates a checksum error due to WAFL context mismatch (data integrity inconsistency detected in WAFL block).
        • Severity: NOTICE
        • Recommended action: Restore the corrupted file from snapshot or backup media.
        • Command to check event catalog:event catalog show -message-name raid.cksum.wc.blkErr
      • wafl.inconsistent
        • Indicates WAFL file system inconsistency error (potential file system corruption detected).
        • Severity: ERROR
        • Recommended action: Contact NetApp support.
        • Command to check event catalog:event catalog show -message-name wafl.inconsistent.* -instance
    • RAID/Disk label related (metadata corruption or loss):
      • raid.config.disk.bad.label
        • Indicates an unassigned disk has label inconsistency (missing or unexpected label data detected).
        • Severity: NOTICE
        • Recommended action: Automatic recovery is performed by ONTAP.
        • Command to check event catalog:event catalog show -message-name raid.config.disk.bad.label
      • raid.config.filesystem.disk.bad.label
        • Indicates a file system disk has label inconsistency (missing or unexpected label data detected).
        • Severity: NOTICE
        • Recommended action: Automatic recovery is performed by ONTAP.
        • Command to check event catalog:event catalog show -message-name raid.config.filesystem.disk.bad.label
    • Note:
      • These EMS messages can be monitored to proactively detect and respond to events indicating bad data occurrence.
      • Severity and recommended actions may vary depending on the specific message and ONTAP version.
      • For detailed message descriptions and corrective actions, use the ONTAP CLI command event catalog show -message-name <message_name>.

Additional Information

additionalInformation_text
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.