User's Manual
l "SMART Thermal Shutdown"
l "Set Temperature Probe Values"
Rescan to Update Storage Configuration Changes
The Rescan task scans the storage attached to the controller's connectors (channels or ports) to verify the currently connected devices or to recognize devices
that have been added to or removed from the connectors. When you do a rescan on a controller object, all storage attached to the controller is rescanned.
Performing a rescan causes the controller to recognize changes in the storage configuration, such as adding or removing physical disks from a virtual disk or
changing a RAID level.
You may want to rescan in the following situations:
l To see new disks attached to the controller.
l To make the operating system recognize a virtual disk.
l To make Storage Management display a new virtual disk.
l After expanding a virtual disk, you may need to rescan the controller so that the virtual disk can use the additional disk space.
l To update the status of an offline disk.
l To display updated information in a clustered configuration after a failover of cluster resources.
Related Information:
l "I/O and Reboot Requirements for Detecting Physical Disk Status Changes"
l "Time Delay in Displaying Configuration Changes"
Time Delay in Displaying Configuration Changes
When you change the storage configuration, Storage Management quickly generates SNMP traps in response to the configuration changes. The Storage
Management MIB (Management Information Base) is also updated to reflect storage configuration changes. However, it may take up to five minutes to update
the MIB with the most recent storage configuration. For this reason, there is a time delay of up to five minutes between the receipt of an SNMP trap and the
ability to identify the configuration changes by querying the Storage Management MIB. This time delay is particularly notable when creating a new virtual disk
or performing an unmirror or split mirror on a RAID 1-concatenated virtual disk. You can minimize this time delay by performing a controller rescan. See "Rescan
Controller" for more information.
I/O and Reboot Requirements for Detecting Physical Disk Status Changes
This section applies to PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch
controllers
Because of hardware restrictions, the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers will not detect a physical
disk status change until I/O is attempted or the system is rebooted.
If the controller has an open communication path to the disk, then performing an I/O operation on the controller updates the disk status. For example, when
an unconfigured disk is removed, the controller may not detect the change until a manual rescan is done or other I/O operations are attempted. Likewise,
displaying a status change of a virtual disk or one of its member physical disks may require that you do an I/O operation on the controller on which the virtual
disk resides.
If, however, the controller has lost the communication path, then rebooting the system is required to update the disk status. Communication loss is evident if
the operating system generates I/O errors when you attempt to access data, even though Storage Management displays the disk status as healthy. Once the
communication path is restored, reboot the system to update the disk status. If the communication path is not restored, then Storage Management does not
display the storage objects after the reboot.
Related Information:
l "Rescan to Update Storage Configuration Changes"
Back to Contents Page
NOTE: For SCSI controller-based systems, if you want to rescan all controllers, perform a "Global Rescan." If you want to rescan only the components
attached to a particular controller, perform a "Rescan Controller."
NOTE: Clicking the Refresh button in the right pane refreshes only the right pane. To view the new physical disk in the left pane tree view, click the
system name displayed at the top of the left pane, or select View --> Refresh from the browser's menu bar.