Collecting Drive Data; Diagnosing A Controller - IBM System Storage DS3000 Programming Manual

Table 11-2. Support Data for the Storage Subsystem (continued)
Type of Data
Recovery profile
Unreadable sectors
State capture data
Storage subsystem

Collecting Drive Data

To gather information about all of the disk drives in a storage subsystem, use the save allDrives
command. This command collects sense data and saves the data to a file. The sense data consists of
statistical information that is maintained by each of the disk drives in the storage subsystem.

Diagnosing a Controller

The diagnose controller command provides these tests that help you make sure that a controller is
functioning correctly:
v The read test
v The write test
v The data-loopback test
The read test initiates a read command as it would be sent over an I/O data path. The read test compares
data with a known, specific data pattern, and the read test checks for data integrity and errors. If the read
command is unsuccessful or the data compared is not correct, the controller is considered to be in error
and is placed offline.
The write test initiates a write command as it would be sent over an I/O data path to the diagnostics
region on a specified disk drive. This diagnostics region is then read and compared to a specific data
pattern. If the write fails or the data compared is not correct, the controller is considered to be in error,
and it is failed and placed offline.
Run the data-loopback test only on controllers that have connections between the controller and the disk
drives. The test passes data through each controller disk drive-side channel, the minihub, out onto the
loop, and back again. Enough data is transferred to determine error conditions on the channel. If the test
fails on any channel, this status is saved so that it can be returned if all of the other tests pass.
For best results, run all three tests after you first install the storage subsystem and any time that you that
have made changes to the storage subsystem or the components that are connected to the storage
subsystem (such as hubs, switches, and host adapters).
Description and File Name
A detailed description of the latest recovery profile
record and historical data.
recoveryProfile.csv
A detailed list of all of the unreadable sectors that
have been logged to the storage subsystem.
badBlocksData.txt
A detailed description of the current state of the
storage subsystem.
stateCaptureData.dmp
A detailed listing of the hardware components and the
software components that comprise the storage
subsystem configuration.
storageSubsystemConfiguration.cfg
Chapter 11. Maintaining a storage subsystem
11-9