Customer has replaced a failed drive, but when they check the RAID status the new drive is not listed in the status command output and the overall RAID status does not show the array "rebuilding ".
AppResponse appliance fails to recognize replacement drive and therefore fails to rebuild
Categories:
Solution Number:
S25809
Last Modified:
2016-12-14
Issue
Solution
The RAID controller has marked that " Px" drive as failed and removed it from the RAID array.
For some reason the drive bay status was not reset to "empty and ready" by the RAID controller when the failed drive was removed.
A graceful "warm" reboot of the appliance initiated by using the
reboot command may resolve the issue and cause the RAID controller to recognize the newly replaced hard drive. - First, remove the new drive, then issue the reboot command from the cli (or WebUI).
cli> reboot - Replace the new drive back into its drive bay once the appliance has completed the reboot cycle and the appliance is collecting traffic.
If the warm boot procedure does not work and the newly replaced drive is still not recognized by the RAID controller then the next step is a cold boot of the appliance to drain any residual memory stored on the RAID controller card.
Below are the recommended steps to perform a cold boot of the appliance:
cli> halt
- Gracefully shut down the appliance by issuing the shutdown command from the CLI:
cli> halt - Press and hold down the power button until the appliance is fully shut down.
- Unplug all power cables connected to the appliance
Wait - for at least three minutes to allow the capacitors to drain - Reconnect the power cables and power up the appliance
Environment
Disk IO RAID
Related Bugs
Attachments
Related Files
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case