Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 1 results
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/When_recovering_failed_volumes_an_unexpected_controller_reboot_might_occur
      Controller A rebooted While Controller A rebooting, Controller B lost connection to all drives. Drives and volumes have failed. vdmRecoverAllRAIDVols was run on Controller B to recover the failed volu...Controller A rebooted While Controller A rebooting, Controller B lost connection to all drives. Drives and volumes have failed. vdmRecoverAllRAIDVols was run on Controller B to recover the failed volumes. While vdmRecoverAllRAIDVols was still running, between the time after volumes were degraded and before the recovery was completed, controller B rebooted due to transaction timeout. Controller B's reboot is stuck at recoverRAIDVolumes while handling interrupted Writes (IW) entries in NVSRAM.