11.4
Recovering from a Disk Drive Failure
This section explains how to recover when a disk drive or SSD fails:
• If the array was protected by a hot spare, see
Failed Disk Drive Protected by a Hot Spare disk drives
failure recoverywith hot spare
• If the array was not protected by a hot spare, see
Failed Disk Drive Not Protected by a Hot Spare disk
drives failure recoverywithout hot sparefailed disk drives without hot spare
.
• If there is a disk drive failure in more than one array simultaneously, see
Simultaneously disk drives failure recoverymultiple arraysfailed disk drives multiple arrays
• If it is a RAID 0 array, see
Disk Drive Failure in a RAID 0 Array disk drives failure recoveryRAID 0
arraysfailed disk drives RAID 0 arrays
.
• If multiple disk drives fail within the same array, see
Multiple Failures in the Same Array disk drives
failure recoverymultiple disk drivesfailed disk drives multiple disk drives
.
• If the drive is part of the maxCache Device, see
Failed SSD in maxCache DevicemaxCache Solid State
Note: maxView Storage Manager uses the term logical drives or logical devices when
referring to arrays (see
Terminology Used in this Guideterminology
).
11.4.1
Failed Disk Drive Protected by a Hot Spare
When an array is protected by a hot spare, if a disk drive in that array fails the hot spare is automatically
incorporated into the array and takes over for the failed drive.
To recover from the failure:
1. Remove and replace the failed disk drive.
2. If copyback is not enabled—In maxView Storage Manager, remove the ‘hot spare’ designation from the
original hot spare (the disk drive that was built into the array). Then, designate a new hot spare to
protect the arrays on that controller.
If copyback is enabled—Data is automatically moved back to its original location once the controller
detects that the failed drive has been replaced. No action is required.
11.4.2
Failed Disk Drive Not Protected by a Hot Spare
When an array is not protected by a hot spare, if a disk drive in that array fails, remove and replace the
failed disk drive. The controller detects the new disk drive and begins to rebuild the array.
If the controller fails to rebuild the array, check that the cables, disk drives, and controllers are properly
installed and connected. Make sure that the new disk drive is equal or greater in size than the failed disk
drive. Then, if necessary, use maxView Storage Manager to rebuild the array. For instructions, refer to the
maxView Storage Manager User’s Guide or the online Help.
11.4.3
Failure in Multiple Arrays Simultaneously
If there's a disk drive failure in more than one array at the same time (one failure per array), and the arrays
have hot spares protecting them, the controller rebuilds the arrays with these limitations:
• A hot spare must be of equal or greater size than the failed disk drive it's replacing.
• Failed disk drives are replaced with hot spares in the order in which they failed. (The array that includes
the disk drive that failed first is rebuilt first, assuming an appropriate hot spare is available—see bullet
above.)
If there are more disk drive failures than hot spares, see
Failed Disk Drive Not Protected by a Hot Spare disk
drives failure recoverywithout hot sparefailed disk drives without hot spare
If copyback is enabled, data is moved back to its original location once the controller detects that the failed
drive has been replaced.
42
Microsemi Proprietary and Confidential. Installation and User's Guide Revision 5
Solving Problems