Skip to main content
NetApp Knowledgebase

After scheduled or unscheduled restart of a controller all volumes failed

Views:
95
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

 

  • E-Series

Issue

 

  • Troubleshooting SANtricity System Manager Support Center then restart controller volumes fail
  • After running through recovery steps system does not start reconstruction
    • Volumes / LUN's degraded but hosts can not access
  • Massive amount of unreadable sectors reported filling up log when recovery attempted
  • Controller goes into lockdown
Example E-Series errors:
E-Series Notification from volumex (Volume failure) CRITICAL
Failure Entry 1: DISK_POOL_DRIVE_FAILURE-Recovery Failure Type Code: 443
Failure Entry 2: FAILED_VOLUME-Recovery Failure Type Code: 17
Failure Entry 3: DISK_POOL_CAPACITY_DEPLETED-Recovery Failure Type Code: 437
Failure Entry 4: SAS_PORT_FAILED-Recovery Failure Type Code: 113
Failure Entry 5: OFFLINE_CTL-Recovery Failure Type Code: 28
Failure Entry 6: DISK_POOL_RECONSTRUCTION_DRIVE_COUNT_BELOW_THRESHOLD-Recovery Failure Type Code: 424
E-Series Notification (Overflow in unreadable sector database) CRITICAL
 
Example of VMware errors:
[root@esxserverxyz-ESXi-Mgmt:~] dmesg | grep "I/O error"
cpu13:2099356)HBX: 1034: 'datastorexyz': HB at offset 0987654 - Setting pulse failed: I/O error:
cpu13:2099356)HBX: 1034: 'datastorexyz': HB at offset 0987654 - Setting pulse failed: I/O error:

 

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support