Users Guide


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
