Cisco Model D-PCG1000 PowerKEY CAS Gateway Installation Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Chapter 1 Replace a Disk Drive on a Sun Fire V880 and V890 Server
32
4005697 Rev B
Remove a Hard Disk Drive (12-Disk Setup)
Finding a Meta Database
After examining the mirrored disk drives and determining that multiple portions of
a disk drive are inaccessible, you must remove the hard disk drive. Before you can
remove the drive, use the metadb utility to determine if the drive in question has a
metadevice.
Note: For more information about metadevice assignments, refer to the
After examining the mirrored disk drives and determining that multiple portions of
a disk drive are inaccessible, you must remove the hard disk drive. Before you can
remove the drive, use the metadb utility to determine if the drive in question has a
metadevice.
Note: For more information about metadevice assignments, refer to the
V880/V890
12-Disk Device Assignments (on page 46) table.
Complete these steps using the metadb utility to determine if a meta database is
located on the disk drive. If you have been following the procedures in this chapter
in order, you should still be logged in to an xterm window as root user.
1 Type the following command and press Enter to display the status of the disk
Complete these steps using the metadb utility to determine if a meta database is
located on the disk drive. If you have been following the procedures in this chapter
in order, you should still be logged in to an xterm window as root user.
1 Type the following command and press Enter to display the status of the disk
drive:
metadb -i
flags first blk block count
a m p luo 16 1034
/dev/dsk/c1t0d0s7
a p luo 16 1034
/dev/dsk/c1t1d0s7
a R p luo 16 1034
/dev/dsk/c1t2d0s7
a p luo 16 1034
/dev/dsk/c2t8d0s7
a p luo 16 1034
/dev/dsk/c2t9d0s7
a p luo 16 1034
/dev/dsk/c2t10d0s7
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