IBM ServeRAID, Справочник пользователя

Страница: 176 / 226

This procedure involves the following steps:
1. Capturing the ServeRAID logs
2. Isolating and removing the failed physical drive
3. Checking the hardware connections
4. Setting defunct drives to the online state
5. Accessing the critical logical drives
6. Finishing the procedure
Capturing the ServeRAID logs
Complete the following steps to capture the ServeRAID logs:
1. Run DUMPLOG.BAT to capture the ServeRAID logs. Do one of the following:
v If the operating system is located on the failed logical drive, complete the
following steps:
a. Copy the DUMPLOG.BAT and CLEARLOG.BAT files to the root of the
ServeRAID diskette.
b. Start the server from the ServeRAID command-line diskette.
c. At the prompt, type the following:
DUMPLOG filename controller
where filename is the name of the text file and controller is the
ServeRAID controller number (1-12)
v If the operating system is accessible, complete the following tasks:
a. Copy or extract the DUMPLOG utility appropriate for your operating
system to a local directory or folder.
b. Run the DUMPLOG command appropriate for the operating system and
save the output to a text file.
2. Send the logs to your IBM service representative for root-cause analysis. The
logs provide the best evidence for determining the cause of the failure.
Isolating and removing the failed physical drive
To use ServeRAID Manager to determine the order in which drives were marked
defunct, complete the following steps:
1. Start ServeRAID Manager in startable-CD mode.
2. In the ServeRAID Manager tree, right-click Local system .
3. Click Save printable configuration and event logs ; then, press Enter. A
window opens, listing the name and location of the log file.
4. Click OK .
5. Open the log file in a text editor. The ServeRAID defunct drive event log lists all
physical drives marked defunct; the most recent failure is shown at the bottom
of the list.
6. Review the list to determine which physical drive failed first. If you cannot
determine which drive failed first, go to step 7 on page 162 of “Accessing the
critical logical drives.
″
Notes:
a. The ServeRAID defunct drive event log might contain entries from earlier
incidents of defunct drives. Review the list of defunct drives carefully, and
use the date and time stamps to identify the first drives associated with
this
incident.
160
IBM ServeRAID: User’s Reference, Version 5.10