For example, this could occur in the event of a power loss to any of the components in the SCSI ServeRAID subsystem. Software and Physical Replacement: When the ServeRAID adapter communicates with the hardfile and receives an unexpected response, the adapter will mark the drive defunct in order to avoid any potential data loss. No rebuild, synchronization, or logical-drive migration operation is in process.Note: If you physically replace the drive and the new drive does not appear in the Physical Drives branch of the Main Tree, you must scan for new or removed Ready drives. If no hot-spare or standby hot-spare drives are available, the rebuild operation will start the moment you replace the defective drive.The smallest drive that meets this requirement enters the Rebuild state. When multiple hot-spare drives are available, the ServeRAID adapter/controller searches for a hot-spare drive of the appropriate size.A hot-spare or standby hot-spare drive with a capacity equal to or greater than the capacity of the defunct drive is available the moment the drive fails.The physical drive that failed is part of a RAID level-1 or RAID level-5 logical drive.The ServeRAID adapter/controller will rebuild a defunct drive automatically when all of the following conditions exist: The ServeRAID adapter/controller adds a hot-spare or a standby hot-spare drive to the array and changes its state from Hot-Spare or Standby Hot-Spare to Rebuilding.Īutomatically Rebuilding the Defunct Drive.When you physically replace a defunct drive in a critical logical drive, the ServeRAID adapter/controller rebuilds the data on the new physical drive before it changes the logical drive state back to Okay. You physically replace a defunct drive that is part of the critical logical drive.General Information about the Rebuild OperationĪ physical hard disk drive can enter the rebuild state if: If you backed up your data before the drive failed, you can restore the data to the new drive. If you use the Administration and Monitoring Utility to initiate the rebuild operation, you can unblock the blocked RAID level-0 drive when the rebuild operation completes.ĭata in a logical drive with RAID level-0 is lost during the rebuild operation.You must unblock any RAID level-0 logical drives at the end of the rebuild operation.If the hard disk drive being rebuilt is part of a RAID level-0 logical drive, the RAID level-0 logical drive is blocked. The replacement hard disk drive must have a capacity equal to or greater than the failed drive. But remember, the logical drive might contain damaged data.īefore you rebuild a drive, review the following guidelines and general information. After the Rebuild operation completes, you can unblock the RAID level-0 logical drives, and access them once again. To prevent data integrity problems, the ServeRAID adapters and controllers set the RAID level-0 logical drives to Blocked during a Rebuild operation. The ServeRAID adapters and controllers can reconstruct RAID level-1 and RAID level-5 logical drives, but they cannot reconstruct data stored in RAID level-0 logical drives. When a hard disk drive goes defunct (DDD), a Rebuild operation is required to reconstruct the data for the device in its respective disk array. The following information applies only to drives that are part of the same arrayĭrive Replacement (Rebuilding a Defunct Drive) When HSP is Not Present at Time of Failure.Recovery From ServeRAID Adapter Failure.Using and Understanding the ServeRAID Administration Log.Drive Replacement (Rebuilding a Defunct Drive).Procedures for recovering from DDD scenarios include: Information in this section is for use with all ServeRAID adapters listed in this HMM. ServeRAID - Recovery Procedures for DDD Drives
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |