Simulator Discussions

Re: Root volume is damaged

SeanHatfield

Then you likely need to make some free space first.

 

Start by deleting aggregate snapshots and vol0 snapshots if any are present, then try it again.

 

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Root volume is damaged

Davidjai

Thank you so much Mr.hat, i got solution

 

Regards and Thanks

 

JAI

 

 

Re: Root volume is damaged

rsankuru

Hey, How did you resovle this


@Davidjai wrote:

Thank you so much Mr.hat, i got solution

 

Regards and Thanks

 

JAI

 

 


How did you resolve this issue ?

Re: Root volume is damaged

Davidjai

Am just simply followed the recovery procedure, and we used "unsetenv 

bootarg.init.boot_recovery". 

 

And i deleted volume which is damaged, in CLI mode

Re: Root volume is damaged

SupraJari

Hi, trying to recover with 9.3 simulator.

 

VLOADER> unsetenv bootarg.init.boot_recovery

no such file or directory

 

Also printenv does not show such option.

 

Has something changed in 9.3?

 

-Jari

Re: Root volume is damaged

SeanHatfield

Thats the response you get when you try to unset a variable that has not been set.  Maybe something changed, or maybe you are hitting a different scenario.  Whats the message you get after a normal boot?

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Root volume is damaged

Greg_Wilson

this option is no longer there in 9.5

 

any ideas how to recover cluster from a power outage

Re: Root volume is damaged

christian_ruppert

unsetenv bootarg.rdb_corrupt

Re: Root volume is damaged

haopengl

1.  Bring the node to the LODER prompt:

::*>halt -node <node>

2.  Check to see if the following bootargs have been set:

LOADER>printenv bootarg.init.boot_recovery
LOADER>printenv bootarg.rdb_corrupt

3.  IF either bootarg as been set to a value, un-set it and boot ONTAP

LOADER>unsetenv bootarg.init.boot_recovery
LOADER>unsetenv bootarg.rdb_corrupt
LOADER>bye

Re: Root volume is damaged

SeanHatfield

The simloader has no saveenv, so when you bye none of the changes will be saved.  Instead you have to boot, and let it proceed to at least the boot menu for changes from the loader prompt to be persistent.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
2021 NetApp Partner Experience Survey
PES Banner
All Community Forums
Public