Skip to main content
NetApp Knowledge Base

When recovering failed volumes an unexpected controller reboot might occur

  1. Last updated
  2. Save as PDF
Views:
48
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • SANtricity OS version prior to 11.80.1
  • Unreadable Sectors (URS)

Issue

Events leading to the failure:

  1. Controller A rebooted
  2. While Controller A rebooting, Controller B lost connection to all drives. Drives and volumes have failed.
  3. vdmRecoverAllRAIDVols was run on Controller B to recover the failed volumes.
  4. 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.
  5. Controller B's reboot is stuck at recoverRAIDVolumes while handling interrupted Writes (IW) entries in NVSRAM.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.