metadevadm report invalid device relocation

Hi All ,

The syslogd reports the below error message in /var/adm/messages

May 4 08:26:02 ORADR metadevadm: [ID 209699 daemon.error] Invalid device relocation information detected in Solaris Volume Manager

May 4 08:26:02 ORADR metadevadm: [ID 912841 daemon.error] Please check the status of the following disk(s):

May 4 08:26:02 ORADR metadevadm: [ID 702911 daemon.error]c1t1d0

May 4 08:26:02 ORADR metadevadm: [ID 702911 daemon.error]c2t12d0

May 4 08:26:02 ORADR metadevadm: [ID 702911 daemon.error]c2t13d0

May 4 08:26:02 ORADR metadevadm: [ID 702911 daemon.error]c2t0d0

May 4 08:26:02 ORADR metadevadm: [ID 702911 daemon.error]c2t1d0

What does it mean and how can i resolvethis issue.

For your information, I have furnished the metastat outputfor your reference.

metastat output

=============

/var/adm#metastat

d30: Mirror

Submirror 0: d31

State: Okay

Submirror 1: d32

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 20972736 blocks (10 GB)

d31: Submirror of d30

State: Okay

Size: 20972736 blocks (10 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t0d0s4 0NoOkayYes

d32: Submirror of d30

State: Okay

Size: 20972736 blocks (10 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t1d0s4 0NoOkayYes

d20: Mirror

Submirror 0: d21

State: Okay

Submirror 1: d22

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 20972736 blocks (10 GB)

d21: Submirror of d20

State: Okay

Size: 20972736 blocks (10 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t0d0s3 0NoOkayYes

d22: Submirror of d20

State: Okay

Size: 20972736 blocks (10 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t1d0s3 0NoOkayYes

d10: Mirror

Submirror 0: d11

State: Okay

Submirror 1: d12

State: Okay

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 84511680 blocks (40 GB)

d11: Submirror of d10

State: Okay

Size: 84511680 blocks (40 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t0d0s0 0NoOkayYes

d12: Submirror of d10

State: Okay

Size: 84511680 blocks (40 GB)

Stripe 0:

DeviceStart Block DbaseState Reloc Hot Spare

c1t1d0s0 0NoOkayYes

d40: Concat/Stripe

Size: 286688448 blocks (136 GB)

Stripe 0:

DeviceStart Block DbaseReloc

c1t2d0s2 0NoYes

Stripe 1:

DeviceStart Block DbaseReloc

c1t3d0s210176NoYes

d65: Soft Partition

Device: d60

State: Okay

Size: 289406976 blocks (138 GB)

Extent Start Block Block count

0283115584289406912

1113875363264

d60: RAID

State: Okay

Interlace: 32 blocks

Size: 1146692736 blocks (546 GB)

Original device:

Size: 1146711680 blocks (546 GB)

DeviceStart Block DbaseState Reloc Hot Spare

c2t0d0s020682No OkayYes

c2t5d0s020682No OkayYes

c2t2d0s020682No OkayYes

c2t3d0s020682No OkayYes

c2t4d0s020682No OkayYes

d55: Soft Partition

Device: d53

State: Okay

Size: 545259520 blocks (260 GB)

Extent Start Block Block count

01024064545259520

d53: RAID

State: Okay

Interlace: 32 blocks

Size: 573336192 blocks (273 GB)

Original device:

Size: 573355840 blocks (273 GB)

DeviceStart Block DbaseState Reloc Hot Spare

c2t8d0s020682No OkayYes

c2t10d0s020682No OkayYes

c2t9d0s220682No OkayYes

d54: Soft Partition

Device: d53

State: Okay

Size: 1024000 blocks (500 MB)

Extent Start Block Block count

0321024000

d64: Soft Partition

Device: d60

State: Okay

Size: 283115520 blocks (135 GB)

Extent Start Block Block count

032283115520

d63: Soft Partition

Device: d60

State: Okay

Size: 283115520 blocks (135 GB)

Extent Start Block Block count

0855638080283115520

d62: Soft Partition

Device: d60

State: Okay

Size: 283115520 blocks (135 GB)

Extent Start Block Block count

0572522528283115520

Device Relocation Information:

DeviceReloc Device ID

c1t2d0Yesid1,sd@SSEAGATE_ST373307LSUN72G_3HZ9CYYV00007515MLC4

c1t3d0Yesid1,sd@SFUJITSU_MAT3073N_SUN72G_000520B05FKH_AAN0P5505FKH

c1t1d0Yesid1,sd@SSEAGATE_ST373207LSUN72G_0233P47T3KT3P47T

c1t0d0Yesid1,sd@SFUJITSU_MAP3735N_SUN72G_00Q0KG2D_

c2t0d0Yesid1,sd@SSEAGATE_ST314670LSUN146G4542Q6VK3KS2Q6VK

c2t5d0Yesid1,sd@SSEAGATE_ST314670LSUN146G4542SA5K3KS2SA5K

c2t2d0Yesid1,sd@SSEAGATE_ST314670LSUN146G4442QZD53KS2QZD5

c2t3d0Yesid1,sd@SSEAGATE_ST314670LSUN146G4242KS033KS2KS03

c2t4d0Yesid1,sd@SSEAGATE_ST314670LSUN146G2941WLSN3KS1WLSN

c2t8d0Yesid1,sd@SSEAGATE_ST314670LSUN146G4242C51J3KS2C51J

c2t10d0Yesid1,sd@w4849544143484920444b3332454a2d31344e4320202020203430363930313133

c2t9d0Yesid1,sd@SFUJITSU_MAT3147N_SUN146G000515C01A7A_AAC0P5401A7A

Regards,

R. Rajesh Kannan.

[5729 byte] By [grkrajesha] at [2007-11-27 3:23:05]
# 1
did you recently replaced disk in the system i think you might have to run metadevadm -u c1t6d0checkout man metadevadm
mtalhaa at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 2

Hi ,

I have updated the new device id in metadevice state database by using the following command for the device c1t1d0 and c2t0d0.

[b]metadevadm -u c1t1d0

metadevadm -u c2t0d0[/b]

But for the devices c2t12d0, c2t13d0, and c2t1d0, the metadevadm command returns nothing and also these devices are not showing in [b]metastat output[/b]

and also i have another problem the metadb -i shows the below output

#metadb -i

flagsfirst blkblock count

a m p luo16 8192/dev/dsk/c1t0d0s5

ap luo82088192/dev/dsk/c1t0d0s5

[b]Mp 16 unknown /dev/dsk/c1t1d0s5

Mp 8208unknown /dev/dsk/c1t1d0s5[/b]

In the above output the device c1t1d0s5 showing [i][b]unknow state[/b][/i]

How can i resolve this.

Regards,

R. Rajesh Kannan.

grkrajesha at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 3
i think device /dev/dsk/c1t1d0s5 i think may be replace or removed previously , can u see these disks in format command output Regards
mtalhaa at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 4
Hi ,I am able to view this disk in format command output 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1c,600000/scsi@2/sd@1,0 Regards,R. Rajesh Kannan.
grkrajesha at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 5

Is the box is in production ? M means in metadb -i the following

M - replica had problem with master blocks ,

may need to delete not working metadb replica and add it again

i assume someone replace the disk and forgot to add metadb on replace disks

Please read the Solaris volume manager documentation carefully before doing any changes on system

mtalhaa at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 6
Hi ,The Server is in production. I agree your point. Deleting and re-creating the metadb on ren level 3 casue any problem? please confirm.Regards,R. Rajesh Kannan.
grkrajesha at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 7
i think it will work in run level 3 , but i am not sure , if you test box , pull its secondary disk and reattach the mirror again and try to remove metadb in run -level 3 and add new metadbs Regards
mtalhaa at 2007-7-12 8:25:51 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...