topic Re: Single-Node Cluster damage in ONTAP Discussions

Single-Node Cluster damage

FLISCHEIDBRACHT — Wed, 04 Jun 2025 11:21:34 GMT

Hi,

my Cluster don't start up.

***********************
** SYSTEM MESSAGES **
***********************

Internal error: Cannot open corrupt replicated database. Automatic recovery
attempt has failed or is disabled. Check the event logs for details. This node
is not fully operational.

vifmgr Database seem to be broken.

Is the any option to repair ist?

When i change to 7-Mode shell on the Node i can see all data-volumes are ok.

The Cluster is a Single-Node System. Another options is to reinstall the Cluster and bring back the volumes later.

When i start cluster setup and configure it, after finih the error will be the same.

Any ideas?

Running Ontap 9.6P5

Re: Single-Node Cluster damage

SpindleNinja — Thu, 23 Jan 2020 14:22:57 GMT

try this:

halt the node to get to the LOADERA>

run: "unsetenv bootarg.init.boot_recovery"

and then "boot_ontap"

Re: Single-Node Cluster damage

FLISCHEIDBRACHT — Thu, 23 Jan 2020 14:35:24 GMT

LOADER-A> unsetenv bootarg.init.boot_recovery
Could not delete environment variable 'bootarg.init.boot_recovery': Environment variable not found
Environment variable not found (errcode=-9)

i have read in a other forum that this option is not longer supportet in 9.6

Re: Single-Node Cluster damage

SpindleNinja — Thu, 23 Jan 2020 14:42:59 GMT

huh TodayILearned...

let me do some additional looking.

Re: Single-Node Cluster damage

SpindleNinja — Thu, 23 Jan 2020 20:23:37 GMT

Nothing else I can find, and i've checked with a few others. I'd open a case asap if you haven't already.

Re: Single-Node Cluster damage

FLISCHEIDBRACHT — Fri, 24 Jan 2020 05:12:36 GMT

Thanks for your Support.

Re: Single-Node Cluster damage

shuklas — Wed, 05 Feb 2020 01:57:50 GMT

Not sure if this is fixed or not, In 9.6 we have a command to verify and fix this from cluster shell

system configuration recovery node mroot-state show << This will show the state of RDB

based on the output you can use the clear command to fix that .

Re: Single-Node Cluster damage

SpindleNinja — Wed, 05 Feb 2020 04:18:58 GMT

What's the clear command? I don't see it in the command

labcluster::*> system configuration recovery node mroot-state ?
show *Show mroot recovery state

Re: Single-Node Cluster damage

shuklas — Wed, 05 Feb 2020 04:23:14 GMT

::> system configuration recovery node mroot-state clear -recovery-state

Options for recovery-state are 'all|wafl|rdb'

The command will only available when there is an issue .

Re: Single-Node Cluster damage

SpindleNinja — Wed, 05 Feb 2020 04:28:56 GMT

Cool, thank you for the info.

Re: Single-Node Cluster damage

Randy_Lin — Sat, 20 Feb 2021 02:56:18 GMT

Thank you , shuklas 🙂

I tried these steps and the problem is solved.

::> set -priv diag

::*> system configuration recovery node mroot-state clear -recovery-state rdb

::*> reboot

Re: Single-Node Cluster damage

vipingupta — Thu, 25 Feb 2021 07:41:53 GMT

very useful command

issue resolved with below command

set -priv diag

system configuration recovery node mroot-state show
system configuration recovery node mroot-state clear all

Thanks