Users Guide
Failure message to indicate that the enclosure has lost a communication path to the controller, indicating that the enclosure is no longer in
redundant path mode.
Related link
Path Health
Clearing The Connectors Redundant Path View
Clearing The Redundant Path View
Consider a case where you reboot your system and Storage Management, displays the logical connector with a path failure message. It is
possible that you may have intentionally unplugged the second connector. In this case, the path failure message is not relevant. There could
be a fault in the connected cable or the cable may not be connected properly to the controller. In both cases, Storage Management displays
that the system was in redundant path conguration before reboot and is no longer in this conguration. If you are sure you, do not want
the redundant path mode, clear the existing redundant path view using Clear Redundant Path View provided in the Changing The
Controller Properties controller task. Selecting this option clears the redundant path view and the connectors are represented on the user
interface as Connector 0 and Connector 1.
Related link
Setting The Redundant Path Conguration
Logical Connector Properties And Tasks
Setting The Patrol Read Mode
NOTE
: This task is not supported on PERC hardware controllers running in HBA mode.
Does my controller support this feature? See Supported Features.
Patrol read identies disk errors in order to avoid disk failures and data loss or corruption. The Set Patrol Read task is applicable only for
disks used as virtual disks or hot spares.
The Set Patrol Read task runs in the background and corrects, when possible. When the Set Patrol Read mode is set to Auto, patrol read
is initiated when the controller is idle for a period of time and when no other background tasks are active. In this scenario, the patrol read
enhances the system performance as disk errors can be identied and corrected when there is not input/output activity on the disk.
The controller adjusts the amount of system resources dedicated for patrol read based on the amount of controller activity that is
competing with the Patrol Read task. When the controller activity is high, fewer system resources are dedicated to the patrol read task.
Patrol Read does not run on a physical disk in the following circumstances:
• The physical disk is not included in a virtual disk or is assigned as a hot spare.
• The physical disk is included in a virtual disk that is currently undergoing one of the following:
• Rebuild
• Reconguration or reconstruction
• Background initialization
• Check consistency
In addition, the Patrol Read suspends during heavy I/O activity and resumes when the I/O is nished.
Related link
Starting And Stopping Patrol Read
74
Controllers