
Disk Failure Notification Messages from Diagnostics
If you have Event Monitoring Service (EMS) hardware monitors installed on your system, and you
enabled the disk monitor disk_em, a failing disk can trigger an event to the (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 example is
part of an error 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 on the docs.hp.com website.
LVM Command Errors
Sometimes LVM commands, such as vgdisplay, return an error suggesting that a disk has problems.
For example:
# vgdisplay –v | more
…
--- Physical volumes ---
PV Name /dev/dsk/c0t3d0
PV Status unavailable
Total PE 1023
Free PE 173
…
The physical volume status of unavailable indicates that LVM is having problems with the disk. You
can get the same status information from pvdisplay.
The next two examples are warnings from vgdisplay and vgchange indicating that LVM has no
contact with a disk:
Comentarios a estos manuales