Disk subsystem troubleshooting

ii

Disk subsystem troubleshooting

Contents
Disk subsystem troubleshooting . . . . 1

iii

iv

Disk subsystem troubleshooting

Disk subsystem troubleshooting

You can troubleshoot problems with the Information Archive disk subsystem by analyzing related symptoms. Since most problems have multiple symptoms, various symptoms are grouped by a similar cause.
Table 1. Disk subsystem troubleshooting table Symptoms The appliance exhibits all or many of the following symptoms: v Lights on disk drive modules (DDMs) are amber instead of green. Actions 1. Gather additional details from the notifications or call-home report. 2. Access the IBM Systems Director and gather additional information about the hardware status of the disk subsystem components. Use the IBM Systems Director Troubleshooting and Support Guide if necessary.

v The customer received an SNMP or e-mail notification or a call-home report was sent, if those 3. Access the RSM for Storage interface and gather features are used. additional information about the status of the v A warning or critical error is disk subsystem components. displayed for the disk subsystem 4. If the DDM indicator lights are displayed as component in the Health Monitor amber rather than green, follow the instructions page. in Replacing a failed DDM. v The disk subsystem iastorageX displays an error in the IBM Systems Director. v An alert is opened for one of the disk subsystems in the RSM for Storage interface. The appliance exhibits all or many of the following symptoms: v Customer jobs on a cluster fail. v The customer received an SNMP or e-mail notification or a call-home report was sent, if those features are used. v A warning or critical error is displayed for the disk subsystem component in the Health Monitor page. v A warning or critical error is displayed on the iBMC-related entry for the disk subsystem component in the IBM Systems Director. v A warning or critical error is displayed on the operating systems entry for the disk subsystem component in IBM Systems Director.

1. Gather additional details from the notifications or call-home report. 2. Access the IBM Systems Director and gather additional information about the hardware status of the disk subsystem components. Use the IBM Systems Director Troubleshooting and Support Guide if necessary. 3. Use the troubleshooting information in the disk subsystem (DS4000) publications listed in Related publications to determine if the problem is due to the failure of both disk controllers in one disk controller drawer. If so, follow the instructions in Repairing both disk controllers within a disk controller drawer.

Table 1. Disk subsystem troubleshooting table (continued) Symptoms The appliance exhibits all or many of the following symptoms: v Loss of access to data. v The customer received an SNMP or e-mail notification or a call-home report was sent, if those features are used. v A warning or critical error is displayed for the disk subsystem component in the Health Monitor page. v A warning or critical error is displayed on the iBMC-related entry for the disk subsystem component in the IBM Systems Director. v A warning or critical error is displayed on the operating systems entry for the disk subsystem component in IBM Systems Director. The appliance exhibits all or many of the following symptoms: v Degraded performance. v The customer received an SNMP or e-mail notification or a call-home report was sent, if those features are used. v A warning or critical error is displayed for the disk subsystem component in the Health Monitor page. v The disk subsystem iastorageX displays an error in the IBM Systems Director. v An alert is opened for one of the disk subsystems in the RSM for Storage interface. 1. Gather additional details from the notifications or call-home report. 2. Access the IBM Systems Director and gather additional information about the hardware status of the disk subsystem components. Use the IBM Systems Director Troubleshooting and Support Guide if necessary. 3. Access the RSM for Storage interface and gather additional information about the status of the disk subsystem components. 4. If the customer jobs are continuing but are experiencing degraded performance, the problem might be due to one of the following problems: v Failure of one or two DDMs. Refer to Replacing a failed DDM. v Loss of one controller. Refer to Replacing a disk controller. v Failure of a component in a disk controller. Refer to Replacing a disk controller component. v Loss of one ESM in an expansion drawer. Refer to Replacing one ESM within a disk expansion drawer. v Failure of an ESM component. Refer to Replacing a disk expansion drawer ESM component. Actions 1. Gather additional details from the notifications or call-home report. 2. Access the IBM Systems Director and gather additional information about the hardware status of the disk subsystem components. Use the IBM Systems Director Troubleshooting and Support Guide if necessary. 3. If you cannot access data contained on LUNs in an expansion drawer, use the troubleshooting information in the disk subsystem (DS4000) publications listed in Related publications to determine if the problem is due to the failure of both Environmental Service Modules (ESMs) within the expansion drawer. If so, follow the instructions in Repairing both ESMs in an expansion drawer.

Disk subsystem troubleshooting

Table 1. Disk subsystem troubleshooting table (continued) Symptoms The appliance exhibits all or many of the following symptoms: Actions 1. Gather additional details from the notifications or call-home report.

v The customer received an SNMP 2. Access the IBM Systems Director and gather or e-mail notification or a additional information about the hardware status call-home report was sent, if those of the disk subsystem components. Use the IBM features are used. Systems Director Troubleshooting and Support Guide v A warning or critical error is if necessary. displayed for the disk subsystem 3. Access the RSM for Storage interface and gather component in the Health Monitor additional information about the status of the page. disk subsystem components. v The disk subsystem iastorageX displays an error in the IBM Systems Director. v An alert is opened for one of the disk subsystems in the RSM for Storage interface. 4. Review the troubleshooting information in the disk subsystem (DS4000) publications listed in Related publications to isolate the problem. The following scenarios might also relate to the problem: v Battery failure. Refer to Replacing a battery within a disk controller drawer. v Power supply and fan unit failure. Refer to Replacing a power supply and fan unit within a disk controller drawer or Replacing a power supply and fan unit within a disk expansion drawer. IBM Systems Director does not show Complete the following steps: the disk storage subsystems in its 1. Log on to the management console server with list of resources. the iaadmin user ID. 2. Enter the following command: sudo /opt/tivoli/tiam/bin/ia_setup_storage.sh 3. Log on to the IBM Systems Director Web interface with the iaadmin user ID. 4. From the navigation tree on the left, expand Inventory and click Advanced System Discovery. Select Default IA storage discovery and then click Run. 5. Select Run now and click OK. 6. Return to the 2231_IA3 group and wait for the disk subsystem (iastoragex) entries to be added to the table. Note: It might take a few minutes for the resource to display in the table. If it does not show up, check the All Systems group.

Disk subsystem troubleshooting

Table 1. Disk subsystem troubleshooting table (continued) Symptoms Any combination of the following symptoms occur: v Multiple errors indicate that the logical unit number (LUN)s/logical drives are not on their preferred path. Actions When a fibre-channel switch fails or loses power, LUNs on the disk storage subsystems can show errors indicating that they are not on their preferred path. This causes errors to be shown in the Information Archive administrative interface and in the RSM for Storage interface.

v The IBM Systems Director Web To correct this problem, use the following steps: interface shows warning or critical errors for the iastoragex nodes in Attention: You can receive I/O errors if the the Information Archive group. following procedure is not followed correctly. v Call-home notifications are 1. Verify that both fibre-channel switches are received for the disk storage operational. subsystems stating that logical 2. Stop all I/O on the affected storage subsystems. drives are not on their preferred 3. Suspend all the collections that are associated path and these errors show in the with affected storage subsystems. RSM for Storage interface. 4. At the keyboard video mouse console, log on to the management console server and open an xterm window. 5. In the xterm window, enter the following command: sudo /usr/bin/SMclient Note: If the Window Task Assistant opens, close it. 6. Click the affected disk storage subsystem to select it. 7. Click the Advanced menu and select Recovery Redistribute Logical Drives. 8. When prompted, click OK. Note: A progress bar shows as each logical drive is configured to its preferred path. 9. Repeat steps 5 to 8 for each affected disk storage subsystem. 10. After the preferred-path errors have been corrected on all affected disk storage subsystems, close the IBM System Storage DS Storage Manager interface. 11. Resume all collections that were suspended and begin I/O operations again. Any combination of the following symptoms occur: v A disk controller does not come online. v When you connect to the disk controller using a serial interface port, the controller status is reported as locked. 1. Connect to the disk controller using a serial port, as described in the IBM System Storage DS4200 Express Storage Subsystem Installation, User's and Maintenance Guide. 2. Log on with the shellUsr user ID and the password wy3oo&w4. 3. Use the command-line interface to issue the following command: lemClearLockdown.

Disk subsystem troubleshooting