<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Migrate-root time outand error on -resume in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466602#M45355</link>
    <description>&lt;P&gt;I have an interesting one. We're migrating our root aggr0 due to shelves being retired.&lt;/P&gt;&lt;P&gt;I followed this KB: &amp;nbsp;How_to_non-disruptively_migrate_a_nodes_root_volume_aggregate_onto_new_disks_in_ONTAP_9&lt;/P&gt;&lt;P&gt;I'm on 9.1.16p4 so following the 9.2 and above directions. I followed the progress of the aggr being backed up etc. and it was going through restore when it timed out at 600sec.&lt;/P&gt;&lt;P&gt;"Timeout the operation “copy_root_volume_contents_iterator:: create_imp()” took longer than 600 seconds to complete [from mgwd on node {ha partner} (VSID: -3)"&amp;nbsp;&lt;BR /&gt;so after a call to Netapp today an engineer agreed to use the resume command. "&lt;SPAN class=""&gt;&lt;CODE&gt;&lt;FONT color="#000000"&gt;::*&amp;gt; system node migrate-root -node node1 -resume true"&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;That immediately failed&lt;/FONT&gt;&amp;nbsp;&lt;FONT color="#000000"&gt;"Complete: Internal error. Failed to online the aggregate "n03_aggr0". Reason: Aggregate "n03_aggr0" is already online. [1]&lt;/FONT&gt;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN class=""&gt;&lt;CODE&gt;The netapp engineer (yes engineer) and myself are stumped.&amp;nbsp;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN class=""&gt;&lt;CODE&gt;&lt;FONT color="#000000"&gt;Further documentation (not specific error) said it needs to be repaired in diag mode and to contact netapp.&lt;/FONT&gt;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Apr 2026 13:23:34 GMT</pubDate>
    <dc:creator>Linuxed</dc:creator>
    <dc:date>2026-04-02T13:23:34Z</dc:date>
    <item>
      <title>Migrate-root time outand error on -resume</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466602#M45355</link>
      <description>&lt;P&gt;I have an interesting one. We're migrating our root aggr0 due to shelves being retired.&lt;/P&gt;&lt;P&gt;I followed this KB: &amp;nbsp;How_to_non-disruptively_migrate_a_nodes_root_volume_aggregate_onto_new_disks_in_ONTAP_9&lt;/P&gt;&lt;P&gt;I'm on 9.1.16p4 so following the 9.2 and above directions. I followed the progress of the aggr being backed up etc. and it was going through restore when it timed out at 600sec.&lt;/P&gt;&lt;P&gt;"Timeout the operation “copy_root_volume_contents_iterator:: create_imp()” took longer than 600 seconds to complete [from mgwd on node {ha partner} (VSID: -3)"&amp;nbsp;&lt;BR /&gt;so after a call to Netapp today an engineer agreed to use the resume command. "&lt;SPAN class=""&gt;&lt;CODE&gt;&lt;FONT color="#000000"&gt;::*&amp;gt; system node migrate-root -node node1 -resume true"&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;That immediately failed&lt;/FONT&gt;&amp;nbsp;&lt;FONT color="#000000"&gt;"Complete: Internal error. Failed to online the aggregate "n03_aggr0". Reason: Aggregate "n03_aggr0" is already online. [1]&lt;/FONT&gt;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN class=""&gt;&lt;CODE&gt;The netapp engineer (yes engineer) and myself are stumped.&amp;nbsp;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;SPAN class=""&gt;&lt;CODE&gt;&lt;FONT color="#000000"&gt;Further documentation (not specific error) said it needs to be repaired in diag mode and to contact netapp.&lt;/FONT&gt;&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Apr 2026 13:23:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466602#M45355</guid>
      <dc:creator>Linuxed</dc:creator>
      <dc:date>2026-04-02T13:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate-root time outand error on -resume</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466605#M45356</link>
      <description>&lt;P&gt;xperience says to open a case fdr this. It could be any number of issues include "too much data" to copy or performance on the node....some odd things. Could be your ONTAP version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please open a support ticket to dig into this to resolve&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Apr 2026 15:13:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466605#M45356</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2026-04-02T15:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate-root time outand error on -resume</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466615#M45357</link>
      <description>&lt;P&gt;So it is possible (given the time) the system configuration backup may have caused the failure. In any case we had to go into diag remove the old root and point the dis, and diskroot to the new volume. renamed the root aggr &amp;amp;vol. (much more detail) and eventually failed it back.&lt;BR /&gt;My advice is look at the config backup schedules before you start your migration to avoid this headache.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 14:25:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Migrate-root-time-outand-error-on-resume/m-p/466615#M45357</guid>
      <dc:creator>Linuxed</dc:creator>
      <dc:date>2026-04-03T14:25:13Z</dc:date>
    </item>
  </channel>
</rss>

