Skip to main content
NetApp Knowledge Base

fatal disk error in RAID group with no parity disk

  1. Last updated
  2. Save as PDF
Views:
116
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Cloud Volume ONTAP 9
  • Azure

Issue

  • Node_2 in a HA pair rebooting everyday around same time.

Fri Apr 21 00:13:45 +0000 [Node-02: config_thread: sk.panic:alert]: Panic String: aggr aggr0_xxxxxxxxxxx_02: raid volfsm, fatal disk error in RAID group with no parity disk..  Raid type - raid0 Group name plex0/rg0 state NORMAL. 1 disk failed in the group. Disk 0d.0 S/N [xxxxxxxxxxcontainer01RootBlob-Z] UID [xxxxxxxxxxcontainer01RootBlob-Z] error: fatal disk error. in SK process config_thread on release 9.9.1P12 (C)

Fri Apr 21 00:13:36 +0000 [Node-02: cf_main: cf.fsm.takeoverByPartnerDisabled:error]: Failover monitor: takeover of Node-02 by xxxxxxxxxx-01 disabled (HA interconnect error. Verify that the partner node is running and that the HA interconnect cabling is correct, if applicable. For further assistance, contact technical support)

 

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.