Skip to main content
NetApp Knowledge Base

Removing stale (foreign aggregates) from ONTAP - Resolution guide

Last Updated:

Applies to

  • ONTAP 9
  • Foreign aggregate
    • raid.assim.tree.foreign
  • Stale aggregate
  • Orphaned aggregate


If disks are introduced into a node and those disks came from another system and were not properly unowned and zeroed, the disks will report owned by the node they came from and will be inaccessible by the current node.

  • This occurs when a RAID tree object contains an ownership identifier that is different from the local system.
    • In this case, the aggregate is declared "foreign" and is marked offline.
    • A volume may not display at the cluster level but is displayed at the node level.
How to verify
  1. Run the following command to identify the node with the aggregate flagged as foreign.
    The relevant aggregate will have the label foreign.
    ::> node run -node * sysconfig -r

Aggregate aggr0 (offline, raid_dp, foreign, degraded) (block checksums)
  Plex /aggr0/plex0 (online, normal, active, pool0)
    RAID group /aggr0/plex0/rg0 (double degraded, block checksums)


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.
Scan to view the article on your device