Copyright 2015
Raid Pitfaill2
Pitfalls of Raid Server System

Lost of data could always be avoided if all things are done right with correct understanding.

1. RAID server is not a backup solution. It is only there to increase disk storage capacity,  improve system performance and add some fail-safe redundancy for some RAID level, which is never full-proof.

2. Rebuilding RAID is not a data recovery solution. It has a lot of negative implication if not done right, it will result  in blotched or mottled state. Recovery is near impossible in such  state.

3. Stop your rescue attempt if you have 1 failed disk in raid 0, more than 1 failed disk in RAID 5 and more than 2 failed disks in in RAID 6. It is unlikely that you can continue without fixing the damaged disk. If you are not able to access data normally, do not attempt a rebuild.

4. Do not swap drives in different slots in an attempt to bring back the lost volume. Some controllers may be forgiving and allow you to do this but most will not. It  will introduce more problems and may kick off a false rebuild. Remove only one drive at a time from the slot before labelling it.  This will avoid mixing  up the drive sequence.

5. If you need to restore data from the failed RAID volume, do not return the faulty disks to the supplier for warranty swap. The faulty disks contain part of your valuable data to make complete  recovery possible.

6. There are situations after disk failures, the server is in semi-accessible state. You could see some files but some are lost. The system may prompt you to do a chkdsk. Do not continue as this is another infamous data killer.
Raid Pitfall1
Adroit Data Recovery Centre Logo