System information
Using the RAID GUI
2-35
To stop the DST of a hard disk, select it and click Stop. A confirmation prompt displays. Click Confirm to end the DST.
2.7.12 Array roaming
Array roaming will be activated when hard disks are moved from one slot to another or from one controller to a new
controller. This ensures that the new controller can be working at all times. You can determine the way of array roaming
through the Auto Array Roaming Control (See 2.7.16 Miscellaneous on page 2-37).
When the Auto Array Roaming Control option is enabled, the configuration of the disks can be identified and restored and
uncompleted tasks are automatically resumed.
Some hard disk configurations may cause conflicts when moved to a new controller. You are allowed to view group
information, including the virtual disk and hard disk states, from the Array Roaming page.
To import the foreign/conflict disks, click the Import button and specify the following options.
2.7.13 Array recovery
With the Array Recovery Utility (ARU), you can recover the disk groups, logical disks, and volumes. To perform
recovery, you must fully understand the partition state of each logical disk.
A partition of a logical disk can be one of the following states: OPTIMAL, FAULTY, , REBUILD, or UNTRUST. Each state
is described as below:
• OPTIMAL: The partition is working and the data is valid.
• FAULTY: The partition is lost (the member disk is removed or faulty) and it results in a faulty logical disk. The data
on the faulty partition will be still in sync with data on other partitions. The data on the faulty partition can be used
after recovery.
• BANISH: The partition is lost (the member disk is removed or faulty) and it results in a degraded logical disk. The
data on the banish partition will be out of sync with data on other partitions. The data on the banish partition can’t
be used after recovery.
• REBUILD: The member disk of the partition has been added to the logical disk, and the partition is rebuilding the
data.
• UNTRUST: The member disk of the partition has been added to the logical disk, but the data on the partition cannot
be trusted. It can become trusted if the logical disk can rebuild the data on the partition.
Note
1. Hard disks must support DST.
2. Hard disks must not be executing DST.
3. For ATA disks, the SMART must be turned on.
4. For ATA disks, if SMART is turned off during DST execution, DST will be aborted.
5. During DST execution, accessing the hard disks may lead to performance degradation.
6. For scheduling DST, the disk must be either unused, a global spare, a local spare, or a JBOD.
7. (For redundant-controller system only) The DST may not continue after failover and the
following error messages may pop up (see 5.3 Redundant Controller on page 5-11 for more
detailed information on failover):
• The self-test was interrupted by the host with a hardware or software reset.
• Self-test fail due to unknown error.
Users can simply re-launch the DST process when encountering the above conditions. Please
note that some disks may continue the DST process without any problems.
Note
At the top of the page, you can select the group id and the group type (JBOD disk, disk group, or
volume) for the information to be displayed. Each group type will have different columns on this
page.
Target ID Select an ID (which may be a JBOD ID, disk group ID, or volume ID) to be used
after import.
Members Select the foreign/conflict hard disks to be imported and restored the
configurations. Use the arrow buttons to move the hard disks from the Available
Members list to the Selected Members list.
Force to import
abnormal group
Check this option to allow the import of incomplete disk groups. Without this option,
only normal disk groups and volumes can be restored.