Users Guide

CAUTION: Resetting a conguration permanently destroys all data on all virtual disks attached to the controller. If the

system or boot partition resides on these virtual disks, it is destroyed.

NOTE: Resetting the controller conguration does not remove a foreign conguration. To remove a foreign conguration,

select Clear Foreign Conguration task.

NOTE: This task is not supported on PERC hardware controllers running in HBA mode.

Related links

Reset The Controller Conguration

To Locate Reset Conguration In Storage Management

Changing The Controller Properties

Reset The Controller Conguration

To reset the controller conguration:

1. Review the virtual disks that are destroyed by resetting the controller conguration. Make backups as necessary. Click Blink at

the bottom of the page to blink the physical disks included in the virtual disks.

2. Click Reset Conguration when you are ready to erase all information on the controller.

To exit without resetting the controller conguration, click Go Back to Previous Page.

To Locate Reset Conguration In Storage Management

1. In the Server Administrator window, under the system tree, expand Storage to display the controller objects.

2. Select a controller object.

3. Click Information/Conguration.

4. Select Reset Conguration from the Available Tasks drop-down menu.

5. Click Execute.

You can also locate this task from the Change Controller Properties drop-down menu.

Exporting The Controller Log File

Does my controller support this feature? See Supported Features.

The Export Log task exports the controller log to a text le. This log provides detailed information on the controller activities and can

be useful for troubleshooting.

On a system running Microsoft Windows, the log le is exported to the windows or winnt directory. On a system running Linux, the

log le is exported to the /var/log directory.

Depending on the controller, the log le name is afa_<mmdd>.log or lsi_<mmdd>.log, where <mmdd> is the month and date.

NOTE: In the VMware ESXi environment, only one log le is created (lsiexport.log). If the le exists, exporting the log le

overwrites the existing log le.

NOTE: Controllers without cache cannot store logs and export log les.