The main aim to perform the testing of RAID is to know the capability and the performance of a RAID drives, a lot of experiments is carried out when the RAID was booted with a drive missing and mirrored drive and powered back up. The testing was done after Disk 1 was removed, the only indicator that was got a lack of activity on the front-panel LED that was associated with the drive. The RAID testing is of various types such as digging on the system log where you could see some information about the missing disk and the powered down, inserted the missing drive and booted back up.

The system log contains a message indicating that the volume was being rebuilt. After leaving another 20 minutes, log entry starts to rebuild, but again, there was alert to this. After powering down, removing the drive and re-powering, we found to see that the system was booted normally. Another test was performed after Disk 1 has been removed and the drive number was set wrong, at least I got some sort of indication of disk failure.

The secondary disk and the primary drive starts to trigger and rebuild process. The RAID 1 has the capability to do the works, but needs work on the user interface. At the beginning and at end of any disk test there is a need to rebuild drive problems reflected in a status screen. If the removal and reinstallation of the secondary drive went ok, by moving right the primary drive which resulted in a plug a monitor. The monitor can be thought of as the box was in an endless reboot cycle of standard PC BIOS initialization, trying to find the OS, failing and rebooting. It wasn't until I plugged in a USB keyboard, and selected an option telling the box to boot off the mirrored copy, that the 200d once again booted normally.

The other tests such as the problems of units need if the extra memory and CPU speed would translate into faster file system performance. The following tests can be performed against a file system to validate the read and write performance of various RAID configurations. The test on a disk storage system, results in a embedded hardware RAID interface. The operating system which was used is a professional which is probably modern type of inexpensive based storage servers. The testing of RAID results in maintaining the file system to be reformatted.

The RAID testing could be used to see whether all the information are present. And whether some of the disks are missing and the powered down are inserted which can cause the missing drive to get booted and can be used for the back up. The testing of RAID is necessary to determine whether the systems are of capability to do the works on the user interface. At the beginning and at end of any disk test there is a need to rebuild drive problems reflected in a status screen.

Data Recovery Software - RAID Recovery

More Information
RAID 0
RAID 1
RAID 1+0
RAID 5
Adaptive RAID
Different RAID Levels
RAID Configuration
RAID Advantages
RAID Reliability Issues
Bad RAID Parity
RAID Concept
RAID Controller
Software Vs Hardware RAID
Quantum DX30 Drives
IBM Servers RAID
IDE RAID Controllers
Fibre Channel
RAID SATA Data Loss
SCSI Interface
Hot Swapping
Storage Controllers
Western Digital RAID Drives
Technical Factors RAID
NAS Servers
Storage Area Network

Related Information
USB Storage Devices
SCSI Tape Drives
Online Data Backup
Project Management
Workflow Software