topic Re: root vol missing and cannot be created in ONTAP Discussions

root vol missing and cannot be created

Baldur — Tue, 08 Jul 2025 07:26:42 GMT

Hello Netapp World,

I need you collective help regarding a Root Volume Recovery process.

We have a bit old FAS8200, 9.3P1 that was powered off for a while. Recently it was powered on but neither of the 2 nodes in the HA can boot.
After the replacement of node1, we had to fix a System ID and version missmatch and after a netboot, node 1 managed to boot normally.
node2 still remains down and as it seems with a missing root volume.
I have already tried a Netboot install (option 7 from boot menu) , tried restoring from backup (opt 6)
after the netboot install via an http server, the node informs at boot menu that "boot device has been changed, Normal Boot is prohibited"
Stuck at this situation as volume options during maintenance menu are not available - therefore i cannot create the root while the node is down and so far I have strictly avoided Option 4(wipe disk data/config).

I was wondering if i would be able to remove node2 from the cluster by breaking the ha and removing the ha interconnect.

then try a clean install on the node2 again. Yet, I am concerned about the data disks and causing another system ID and disk ownership missmatch.

Re: root vol missing and cannot be created

AlexDawson — Fri, 11 Jul 2025 02:33:04 GMT

Hi there!

Access Boot Menu: When prompted, you will see a menu with several options.
Select Option (6): Choose "(6) Update flash from backup config." This option will restore the system configuration from the last backup.
Confirm Update: If prompted to continue with the update, enter y to proceed.
Perform Failover Giveback: Once you see "Waiting For Giveback," execute the command storage failover giveback from the partner node to transfer the root aggregate back to the netbooted node.

If you have any problems, please let us know!

Re: root vol missing and cannot be created

Baldur — Fri, 11 Jul 2025 08:15:02 GMT

Thank you for the suggestion Alex,
I already have tried option 6 to the same result- it goes to Loader with same result "boot device changed , normal boot prohibited"