Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sun Netra 440 metareplace error 1

Status
Not open for further replies.

siddharth786

Technical User
May 18, 2011
6
I am using Sun Netra 440 and i see below error.

When i run metastat, i see 1 disk is in Need Maintenance state.

After that i run below command and getting I/O error

Please help me on this.

bash-2.03# metareplace -e d50 c1t0d0s0
metareplace: dacp10: /dev/dsk/c1t0d0s0: I/O error




bash-2.03# metastat
d50: Mirror
Submirror 0: d51
State: Needs maintenance
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 33560448 blocks

d51: Submirror of d50
State: Needs maintenance
Invoke: metareplace d50 c1t0d0s0 <new device>
Size: 33560448 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Maintenance




May 18 14:48:04 dacp10 disk not responding to selection
May 18 14:48:09 dacp10 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
May 18 14:48:09 dacp10 disk not responding to selection
May 18 14:48:15 dacp10 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
May 18 14:48:15 dacp10 disk not responding to selection
 
Hi Sid, as the 'Invoke' states, you need to specify a new device (disk) to replace the failed one. Do you have a replacement you could swap it out with? If so, this would be assigned a new device name and you can use that to invoke metareplace. You might need to format it to match the original first though.

The internet - allowing those who don't know what they're talking about to have their say.
 
Am I to assume you replaced the drive? Or were you just trying to run metareplace -e d50 c1t0d0s0 without having replaced the drive? The errors are showing the drive as unavailable so looks to be bad drive


What does format show for c1t0d0s0?

also provide dumpadm output, metadb -i,metastat -p


Is this the OS drive? c1t0d0s0 usually is.


metareplace -e d50 (device) is correct when replacing with itself. you can try to use the same drive without replaceing(usually fails) or after disk replacement.


 
I have not replaced the drive, i just run the metareplace command.

Below is the output of all the command. It looks like the disk has gone bad and i need to replace the DISK.

How I can identify which one is OS DISK?

bash-2.03# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
0. c1t0d0 <drive not available: formatting>
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@1,0
Specify disk (enter its number): 0



bash-2.03# metadb -i
flags first blk block count
Wm p l 16 1034 /dev/dsk/c1t0d0s3
W p l 16 1034 /dev/dsk/c1t0d0s4
a p luo 16 1034 /dev/dsk/c1t1d0s3
a p luo 16 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
bash-2.03#
bash-2.03# metastat -p
d50 -m d51 d52 1
d51 1 1 c1t0d0s0
d52 1 1 c1t1d0s0
d60 -m d61 d62 1
d61 1 1 c1t0d0s1
d62 1 1 c1t1d0s1
d70 -m d71 d72 1
d71 1 1 c1t0d0s5
d72 1 1 c1t1d0s5
d80 -m d81 d82 1
d81 1 1 c1t0d0s6
d82 1 1 c1t1d0s6
bash-2.03#


bash-2.03# dumpadm >> /tmp/adm.txt
bash-2.03# vi /tmp/adm.txt
"/tmp/adm.txt" 4 lines, 145 characters
Dump content: kernel pages
Dump device: /dev/dsk/c1t0d0s1 (dedicated)
Savecore directory: /var/crash/dacp10
Savecore enabled: yes
 
So your drive 0 and 1 are mirrored together from what I see. Most likely you boot drive was c1t0d0(dead at this point) but since it is mirrored it really up and running off c1t1d0 at this point.
Your dump device is pointing to c1t0d0s1 which needs to be changed run dumpadm -d /dev/md/dsk/d60 which is the mirror (should not point to individual drive. You also have to change this do to the fact you are about to replace drive c1t0d0.

Then run dumpadm again to confirm the change.

Then delete the metastat database replicas on c1t0d0s3 and c1t0d0s4. run metadb -d c1t0d0s3 c1t0d0s4. Then run metadb -i to confirm they are gone.

look at this link to remove bad drive(turns on blue led for drive identification purposes, then install the replacement and run commands for the os to recognize it.
Then follow this link to complete the metastat portion which includes the repartition of the replacement drive to match c1t1d0 partition table(this has you copy the partition table from the remaining good drive to the recently replaced drive. Then reinstall the bootblock to the new drive, rebuild your state database replicas, and run metareplace -e d50 c1t0d0s0, then metareplace -e d60 c1t0d0s1 and so on until you ran that command for each portion of the mirror...see link
chris
 
Chris - some good stuff in those links, have a star!

The internet - allowing those who don't know what they're talking about to have their say.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top