| Title: | Ask the Storage Architecture Group |
| Notice: | Check out our web page at http://www-starch.shr.dec.com |
| Moderator: | SSAG::TERZA N |
| Created: | Wed Oct 15 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6756 |
| Total number of notes: | 25276 |
I have a PCI based SWXCR (KZPSC-XA) on which a RAID 1 conf. is set.
An extra disk is being configured as Hot Spare. (all disks are
RZ29B-VW)
D-Unix ver.4.0a is being installed.
My problem is that if i manually remove a disk after i push it back
i cant change its state and is labelled as failed without mine
being able to change it.
The Hot Spare acts as it is suppose to(automatically being put
on the Raid and rebuilted).
SWXCRMGR seems unable to change the state of the disk.
Any suggestions out there?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6479.1 | hot spare functionality | SUBSYS::TURCOTTE | fun stuff | Mon Mar 24 1997 14:34 | 14 |
When you physically remove a member of a redundant RAID set, the hot spare should kick in to replace the removed drive, and an automatic rebuild should be invoked. After the rebuild is complete, if you insert a physical drive into the same slot as the drive you removed (same size), the "new" drive should kick in to become the new hot spare. If you try to force the re-inserted drive to become a hot spare during the rebuild, you will find that it remains in the FLD state. You might try toggling the "refresh" button on the GUI SWXCRMGR window, if it remains in the FLD state. | |||||