Checking for hard disk drive failures

To check the hard disk drives from problems:

1. If you are not logged in, log in as root.
2. At the command prompt, enter metadb

   The system displays information about each hard disk drive.

   The following example shows the results of the metadb command for a system with hard disk drive problems.

   flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s4
a p luo 1050 1034 /dev/dsk/c1t0d0s4
a p luo 2084 1034 /dev/dsk/c1t0d0s4
a p luo 3118 1034 /dev/dsk/c1t0d0s4
a p luo 4152 1034 /dev/dsk/c1t0d0s4
a p luo 5186 1034 /dev/dsk/c1t0d0s4
a p luo 6220 1034 /dev/dsk/c1t0d0s4
a p luo 7254 1034 /dev/dsk/c1t0d0s4
W p l 16 1034 /dev/dsk/c1t1d0s4
W p l 1050 1034 /dev/dsk/c1t1d0s4
W p l 2084 1034 /dev/dsk/c1t1d0s4
W p l 3118 1034 /dev/dsk/c1t1d0s4
W p l 4152 1034 /dev/dsk/c1t1d0s4
W p l 5186 1034 /dev/dsk/c1t1d0s4
W p l 6220 1034 /dev/dsk/c1t1d0s4
W p l 7254 1034 /dev/dsk/c1t1d0s4

Where:

o = Replica active prior to last mddb configuration change
u = Replica is up to date
l = Locator for this replica was read successfully
c = Replica's location was in /etc/lvm/mddb.cf
p = Replica's location was patched in kernel
m = Replica is master, this is replica selected as input
W = Replica has device write errors
a = Replica is active, commits are occurring to this replica
M = Replica had problem with master blocks
D = Replica had problem with data blocks
F = Replica had format problems
S = Replica is too small to hold current data base
R = Replica had device read errors

The Ws in the first column indicate that there is a problem writing to partitions on the secondary disk (c1t1d0s4).

If you want to check for additional disk status information, you can run the metastat command.

If you detect problems with the hard disk drive, you must remove the failed drive and replace it with a good one. For more information, see Removing a failed hard disk drive.

© 2006 Avaya Inc. All Rights Reserved.