You are on page 1of 3

How to remove a foreign aggregate (made out of orphaned disks) in

ONTAP

https://kb.netapp.com/onprem/ontap/hardware/How_to_remove_a_foreign_aggregate_made_out_of_or…
Updated: Tue, 16 Apr 2024 12:08:56 GMT

Applies to
• ONTAP 9
• Foreign aggregate

Description

Check Active IQ if this impacts your systems

'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 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
• Aggregate will report failed and foreign under the aggr status command and EMS may report RAID
assimilation failures during reboot/takeover. Example:

aggr0(1) failed raid_dp, aggr diskroot, raidtype=raid_dp,


raidsize=24,
foreign raid_lost_write=on,
resyncsnaptime=5,

[?] Fri Jul 16 06:01:45 CDT [cluster1-01: config_thread:


raid.assim.rg.missingChild:debug]: Aggregate partner_foreign:aggr0,
rgobj_verify: RAID object 0 has only 5 valid children, expected 10.
[?] Fri Jul 16 06:01:45 CDT [cluster1-01: config_thread:
raid.assim.plex.missingChild:debug]: Aggregate partner_foreign:aggr0,
plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is
being taken offline
[?] Fri Jul 16 06:01:45 CDT [cluster1-01: config_thread:
raid.assim.mirror.noChild:debug]: Aggregate partner_foreign:aggr0,
mirrorobj_verify: No operable plexes found.
[?] Fri Jul 16 06:01:45 CDT [cluster1-01: cf_takeover:
raid.fm.takeoverFail:alert]: RAID takeover failed: Partner label
processing failed.

• Event logs can also report raid.assim.tree.multipleRootVols

Procedure
1. Run the following command to identify the node with the aggregate flagged as foreign.

::> system node run -node * -command sysconfig -r

The relevant aggregate will have the label foreign.

2. Based on the above output, run the following clustershell commands, referencing the node that has the
foreign aggregate.

::> set -privilege advanced


::*> storage aggregate remove-stale-record -nodename [node_name]
-aggregate [foreign aggregate name]

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
This will remove all foreign aggregates and return the drives as unzeroed spares.

Additional Information
• RAIDTREE ASSIMILATION FAILED - AutoSupport message
• If the above steps fail, review KB Cannot remove foreign aggregates

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3

You might also like