We use cookies on this website. To find out more about cookies and how they are used on this website, see our Privacy Policy.
By clicking ‘Continue’, you hereby agree with our use of cookies.

Knowledge Base

How to Deal with Drive Failure Causing Controller Shutdown?

Last modified date: Thu, 24 Oct 2024 15:57:43 GMT+8

Symptom:

Drive failure results in the Controller shutting down. Typically, you will first see drive failure events followed by a Controller shutdown event. Below is an example:

  • Error 0x21081282 Enclosure Slot: 40 Drive failed. (reported by slot A)
  • Error 0x22081682 Enclosure Slot: 40 Drive error detected (reported by slot A)
  • Critical Error 0x32011102 Controller A shutdown due to an unexpected condition. (reported by slot B)
Diagnosis:

When a drive fails, the Input/Output (IO) operations directed to that drive become stuck. This IO congestion can cause significant delays or timeouts in the system. The firmware of the storage system attempts to handle the stuck IO operations, but conflicts within the firmware can lead to the Controller shutting down to prevent further issues.

Solution:
  • Replace the Failed Drive:
    Identify and replace the drive in the enclosure slot where the failure is reported.
  • Reinsert the Failed Controller:
    1. Remove the failed Controller from the system.
    2. Wait until all LEDs on the Controller are off.
    3. Reinsert the Controller into the system.
  • Contact Technical Support:
    1. Reach out to technical support to obtain the firmware fix needed to address the issue.
    2. Contact technical support at: Infortrend Support

Following these steps should resolve the issue of drive failure causing the Controller to shut down.

Was this article helpful?Yes | No

Thank you for your feedback!

Do you have any other feedback for this article?

{{ vm.showErrorMessage }}