|
|
|
|
|
|
To check the hard disk drives from problems:
metadbThe 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
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 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.