Skip to main content
NetApp Knowledge Base

Initial setup shows inactive and failed aggregates

Views:
26
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
HW
Last Updated:
4/14/2025, 1:39:30 PM

Applies to

  • AFF-A150
  • ONTAP 9

Issue

  • During initial setup, the sysconfig -r command shows aggregates that are offline and not serving data.

node-01:

Aggregate aggr0 (failed, raid_dp, partial, fast zeroed) (block checksums)

  Plex /aggr0/plex0 (offline, failed, inactive)

    RAID group /aggr0/plex0/rg0 (partial, block checksums)

      RAID Disk       Device    HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

      ---------     ------  ------------- ---- ---- ---- ----- --------------    --------------

      dparity    FAILED          N/A                        13698/ -

      parity      FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data        0a.01.0P3      0a    1   0   SA:B   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.1P3      0a    1   1   SA:B   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.2P3      0a    1   2   SA:B   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.3P3      0a    1   3   SA:B   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      Raid group is missing 12 disks.

node-02:

Aggregate aggr0 (failed, raid_dp, partial, fast zeroed) (block checksums)

  Plex /aggr0/plex0 (offline, failed, inactive)

    RAID group /aggr0/plex0/rg0 (partial, block checksums)

      RAID Disk       Device    HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

      ---------     ------  ------------- ---- ---- ---- ----- --------------    --------------

      dparity    FAILED          N/A                        13698/ -

      parity      FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data FAILED          N/A                        13698/ -

      data        0a.01.18P3    0a    1   18  SA:A   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.19P3    0a    1   19  SA:A   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.20P3    0a    1   20  SA:A   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      data        0a.01.21P3    0a    1   21  SA:A   0   SSD   N/A 13698/28053504    13706/28069888 (fast zeroed)

      Raid group is missing 12 disks.

  • EMS log show messages such as raid.assim.rg.missingChildraid.assim.mirror.noChild, and raid.assim.tree.multipleRootVols.

[?]  Sun Aug 04 14:52:08 +0900 [node-01: config_thread: raid.assim.rg.missingChild:debug]: Aggregate aggr0, rgobj_verify: RAID object 0 has only 4 valid children, expected 16.
[?]  Sun Aug 04 14:52:08 +0900 [node-01: config_thread: raid.assim.plex.missingChild:debug]: Aggregate aggr0, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline
[?]  Sun Aug 04 14:52:08 +0900 [node-01: config_thread: raid.assim.mirror.noChild:debug]: Aggregate aggr0, mirrorobj_verify: No operable plexes found.
[?]  Sun Aug 04 14:52:08 +0900 [node-01: config_thread: raid.assim.tree.multipleRootVols:EMERGENCY]: Volume aggr0 and volume aggr0_tbnetappC0_01 both claim to be the root volume.
[?]  Sun Aug 04 14:52:08 +0900 [node-01: config_thread: raid.assim.tree.restrict:debug]: Restricting aggregate aggr0 due to root volume conflict.
[?]  Sun Aug 04 14:56:32 +0900 [node-01: config_thread: raid.assim.rg.missingChild:debug]: Aggregate aggr0, rgobj_verify: RAID object 0 has only 4 valid children, expected 16.
[?]  Sun Aug 04 14:56:32 +0900 [node-01: config_thread: raid.assim.plex.missingChild:debug]: Aggregate aggr0, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline
[?]  Sun Aug 04 14:56:32 +0900 [node-01: config_thread: raid.assim.mirror.noChild:debug]: Aggregate aggr0, mirrorobj_verify: No operable plexes found.
[?]  Sun Aug 04 14:56:32 +0900 [node-01: config_thread: raid.assim.tree.multipleRootVols:EMERGENCY]: Volume aggr0 and volume aggr0_tbnetappC0_01 both claim to be the root volume.
[?]  Sun Aug 04 14:56:41 +0900 [node-01: config_thread: raid.assim.tree.restrict:debug]: Restricting aggregate aggr0 due to root volume conflict.
[?]  Sun Aug 04 14:59:47 +0900 [node-01: config_thread: raid.assim.rg.missingChild:debug]: Aggregate aggr0, rgobj_verify: RAID object 0 has only 4 valid children, expected 16.
[?]  Sun Aug 04 14:59:47 +0900 [node-01: config_thread: raid.assim.plex.missingChild:debug]: Aggregate aggr0, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline
[?]  Sun Aug 04 14:59:47 +0900 [node-01: config_thread: raid.assim.mirror.noChild:debug]: Aggregate aggr0, mirrorobj_verify: No operable plexes found.
[?]  Sun Aug 04 14:59:47 +0900 [node-01: config_thread: raid.assim.tree.multipleRootVols:EMERGENCY]: Volume aggr0_tbnetappC0_01 and volume aggr0 both claim to be the root volume.
[?]  Sun Aug 04 14:59:47 +0900 [node-01: config_thread: raid.assim.tree.restrict:debug]: Restricting aggregate aggr0 due to root volume conflict.


[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.rg.missingChild:debug]: Aggregate local:aggr0, rgobj_verify: RAID object 0 has only 4 valid children, expected 16.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.plex.missingChild:debug]: Aggregate local:aggr0, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.mirror.noChild:debug]: Aggregate local:aggr0, mirrorobj_verify: No operable plexes found.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.rg.missingChild:debug]: Aggregate partner:aggr0, rgobj_verify: RAID object 0 has only 4 valid children, expected 16.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.plex.missingChild:debug]: Aggregate partner:aggr0, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.mirror.noChild:debug]: Aggregate partner:aggr0, mirrorobj_verify: No operable plexes found.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.tree.restrict:debug]: Restricting aggregate local:aggr0 due to root volume conflict.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.tree.multipleRootVols:EMERGENCY]: Volume aggr0 and volume aggr0_tbnetappC0_02 both claim to be the partner root volume.
[?]  Sun Aug 04 15:01:15 +0900 [node-02: config_thread: raid.assim.tree.restrict:debug]: Restricting aggregate partner:aggr0 due to root volume conflict.

 

 

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.