Gateway E-842R, User Manual

Page: 114 / 164

APPENDIX A: Troubleshooting and Support www.gateway.com
108
Inadvertently pulled
the incorrect drive
from the enclosure
and the array is
dead. Possible incorrect drive
identification and removal. Removing a working drive member
by mistake instead of the failed
drive can cause the array to fail. In
most cases. you can simply re-insert
the drive that was incorrectly
removed and the array returns to
the same state it was in prior to
removing the drive.
For RAID 5/50 arrays , a drive failure
puts the array in a critical state. If a
hot spare is available, the array
should go into a rebuild mode. If
you inadvertently remove one of
the known-good drives that is in
the process of rebuilding, the
rebuild operation stops. After you
re-insert the incorrectly removed
drive, the array returns to the
critical state and the rebuild
process starts again. If you did not
have a hot spare assigned, the array
is in a critical state. If you
inadvertently remove a
known-good drive instead of the
failed drive, the array changes to a
failed array state. Re-inserting the
inadvertently removed drive puts
the array back into a critical state.
Replacing the failed drive causes
the array to begin a rebuild
operation, provided you assign it as
a hot spare, or if the
Auto Hot
Spare option was enabled. the
rebuild begins automatically when
the new replacement drive is
installed.
For RAID 0 arrays , if you
inadvertently remove a known
good drive, the array is dead. After
you re-insert the incorrectly
removed drive, the array returns to
its working state.
For RAID 1/10 arrays , if you
inadvertently remove a
known-good drive, the array fails.
After you re-insert the incorrectly
removed drive, the array returns to
its previous state. If the array was
critical, you can then replace the
known-failed drive with a working
drive and assign it as a hot spare,
then the array begins rebuilding.
Note: For all arrays, removing a
drive as described above causes all
current processing I/O from the
controller to stop. Any I/O in
progress may be lost or cause a
corrupt file.Make sure that you
verify all data stored during this
type of incidence to ensure data
reliability.
Symptom Reason Solution