Skip to main content
NetApp Knowledge Base

Duplicate aggregate in nodeshell not in clustershell

  1. Last updated
  2. Save as PDF
Views:
215
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9

Issue

  • The nodeshell is reporting a failed aggregate that is a duplicate of an existing healthy aggregate on the system.
  • This incorrect aggregate has the same name as the correct aggregate with (1) appended to it. The incorrect aggregate shows as failed and consists of one disk and possibly additional orphan disks that were not assimilated.

Example:

Aggregate n01_aggr1(1) (failed, mixed_raid_type, partial, hybrid_enabled) (block checksums)
  Plex /n01_aggr1(1)/plex0 (offline, failed, inactive)
    RAID group /n01_aggr1(1)/plex0/rg5 (partial, block checksums, raid_dp)

      RAID Disk	Device  	HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------	------  	------------- ---- ---- ---- ----- --------------    --------------
      dparity	FAILED  		N/A                        1695466/ -
      parity	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data    	3b.12.17	3b    12  17  SA:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      data	FAILED  		N/A                        1695466/ -
      Raid group is missing 13 disks.
    Plex is missing 11 RAID groups.

  Unassimilated n01_aggr1(1) disks

      RAID Disk	Device  	HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------	------  	------------- ---- ---- ---- ----- --------------    --------------
      orphaned	3b.12.9 	3b    12  9   SA:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 
      orphaned	3b.13.1 	3b    13  1   SA:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
  • Vreport also shows a discrepancy.

Example:

Object type    aggregate
Object    n01_aggr1(xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
Node Name: NODE-01
Aggregate UUID: <xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx>
Aggregate State: failed
Aggregate Raid Status: mixed_raid_type, partial, hybrid_enabled
Aggregate HA Policy: sfo
Is Aggregate Root: false
Is Composite Aggregate: false
Reason for difference    Present in WAFL Only

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.