Seagate ST34572WC Specifications download pdf (Page 7)

2. Recognizing a Failing Disk

The guidelines in the previous section will not prevent disk failure on your system. Assuming you follow all the

recommendations, how can you tell when a disk has failed? This section explains how to look for signs that one of

your disks is having problems, and how to determine which disk it is.

I/O Errors in the System Log

Often an error message in the system log file is your first indication of a disk problem. In

/var/adm/syslog/syslog.log, you might see the following error:

SCSI: Request Timeout -- lbolt: 329741615, dev: 1f022000

To map this error message to a specific disk, look under the /dev directory for a device file with a device number

that matches the printed value. More specifically, search for a file whose minor number matches the lower six

digits of the number following dev:. The device number in this example is 1f022000; its lower six digits are

022000, so search for that value using the following command:

# ll /dev/*dsk | grep 022000

brw-r----- 1 bin sys 31 0x022000 Sep 22 2002 c2t2d0

crw-r----- 1 bin sys 188 0x022000 Sep 25 2002 c2t2d0

This gives you a device file to use for further investigation.

Disk Failure Notification Messages from Diagnostics

If you have EMS hardware monitors installed on your system, and you enabled the disk monitor disk_em, a

failing disk can trigger an event to the Event Monitoring Service (EMS). Depending on how you configured EMS,

you might get an email message, information in /var/adm/syslog/syslog.log, or messages in another log

file. EMS error messages identify a hardware problem, what caused it, and what must be done to correct it. The

following is part of an example message:

Event Time..........: Tue Oct 26 14:06:00 2004

Severity............: CRITICAL

Monitor.............: disk_em

Event #.............: 18

System..............: myhost

Summary:

Disk at hardware path 0/2/1/0.2.0 : Drive is not responding.

Description of Error:

The hardware did not respond to the request by the driver. The I/O request

was not completed.

Probable Cause / Recommended Action:

The I/O request that the monitor made to this device failed because the

device timed-out. Check cables, power supply, ensure the drive is powered

ON, and if needed contact your HP support representative to check the

drive.

For more information on EMS, see the

diagnostics section of http://docs.hp.com.

1 2 3 4 5 6 7 8 9 10 11 12 ... 35 36

No comments

Seagate ST34572WC Specifications Page 7