Sun Microsystems Ultra 5, Service Manual

Page: 142 / 258

7-14 Sun Ultra 5 Service Manual • February 2000
7.2.4.5 Recovery Procedure for Broken Database Replicas
The high-level recovery steps are as follows:
■
Delete the broken database replica and reboot.
■
Repair or replace the problem hard drive.
■
Add back the database replica.
Detailed instructions for the broken database recovery are as follows:
1. After you see the error messages described in the previous section, type your root
password to enter system maintenance mode at the following prompt:
The following message then displays:
Entering System Maintenance Mode
2. Type the
metadb
command as follows to look at the databases to determine which
database replica is broken.
In the example shown above, the system can no longer detect the state database
replica on slice
/dev/dsk/c1t2d0s3
, which is part of the failed disk. The
metadb
command flags the replicas on this slice as having a problem with the master blocks.
3. Delete the database replica on the bad disk using the
-d
option of the
metadb
command as follows. Using the example, you would type:
At this point, the root (/) file system is read-only. You can ignore any
mddb.cf
error
messages that are displayed.
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): <root password>
# usr/opt/SUNWmd/metadb -i
flags first blk block count
a p l 1050 1034 /dev/dsk/c0t3d0s3
M p unknown unknown /dev/dsk/c1t2d0s3
# usr/opt/SUNWmd/metadb -d -f /dev/dsk/c1t2d0s3
metadb: demo:/etc/opt/SUNWmd/mddb.cf.new: Read-only file system