PANIC after dirty shutdown: NVRAM contents are invalid... The system cannot boot with the message
Applies to
- ONTAP
- FAS
Issue
- A dirty shutdown occurred and the node cannot boot.
-
When accessed from the BMC CLI, the status of
Loaderprompt, even ifboot_ontapfromLoadersystem occurred PANIC and cannot be restarted.
PANIC : NVRAM contents are invalid...
version: 9.8P6: Tue Aug 3 12:23:18 EDT 2021
conf : x86_64.optimize
cpuid = 0
KDB: stack backtrace:
vpanic() at vpanic+0x70d/frame 0xfffff7005c84fbf0
panic() at panic+0x43/frame 0xfffff7005c84fc50
sk_panic() at sk_panic+0x63/frame 0xfffff7005c84fcb0
boot_nv_jettison() at boot_nv_jettison+0xbb/frame 0xfffff7005c84fce0
boot_from_disk() at boot_from_disk+0x1df1/frame 0xfffff7005c850250
boot_manager() at boot_manager+0x1b7/frame 0xfffff7005c850280
rc_main() at rc_main+0x7f/frame 0xfffff7005c8502e0
fork_exit() at fork_exit+0xc7/frame 0xfffff7005c850330
fork_trampoline_sk() at fork_trampoline_sk+0xe/frame 0xfffff7005c850330
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Uptime: 2m50s
ahcich2: AHCI reset done: devices=00000001
PANIC: NVRAM contents are invalid... in SK process rc on release 9.8P6 (C) on Sat Jan 7 01:05:13 GMT 2023
version: 9.8P6: Tue Aug 3 12:23:18 EDT 2021
compile flags: x86_64.optimize
-
Check the
bootarg.init.boot_recovery, results see the number "8".
LOADER-B> printenv bootarg.init.boot_recovery
Variable Name Value
-------------------- --------------------------------------------------
bootarg.init.boot_recovery 8
- Even if you delete the bad flag with the following command, the system still cannot be started.
LOADER-B> priv set advanced
LOADER-B*> unsetenv bootarg.init.boot_recovery
LOADER-B*> saveenv
LOADER-B*> boot_ontap