Loading ...
Loading ...
Loading ...
4848
NOTE:
When the Rebuild operation to a hot spare begins, the failed drive is often removed from
the virtual drive before management applications detect the failed drive. When this removal
occurs, the event logs show the drive rebuilding to the hot spare without showing the failed
drive. The formerly failed drive will be marked as ready after a Rebuild operation begins to
a hot spare. If a source drive fails during a rebuild to a hot spare, the Rebuild operation fails,
and the failed source drive is marked as oine. In addition, the rebuilding hot spare drive is
changed back to a hot spare. After a Rebuild operation fails because of a source drive failure,
the dedicated hot spare is still dedicated and assigned to the correct drive group, and the
global hot spare is still global.
An automatic drive Rebuild operation will not start if you replace a drive during a RAID-level
migration. The Rebuild operation must be started manually after the expansion or migration
procedure is complete. (RAID-level migration changes a virtual drive from one RAID level to
another.)
Loading ...
Loading ...
Loading ...