Volume Mgr Raid 0:- Need maintaince.

[sunny1504]

# metastat d0

d0: Mirror
Submirror 0: d32
State: Needs maintenance
Submirror 1: d33
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4149600 blocks

d32: Submirror of d0
State: Needs maintenance
Invoke: metareplace d0 c1t0d0s0 <new device>
Size: 4149600 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Last Erred

d33: Submirror of d0
State: Needs maintenance
Invoke: after replacing "Maintenance" components:
metareplace d0 c1t1d0s0 <new device>
Size: 4149600 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Maintenance


Tried
# metareplace -e d0 /dev/dsk/c1t0d0s0
But the above command doesnot do anything the resync starts and then just stops.

Any Suggestions ......

Thanks
D'Souza

 

[sunny1504]

Please Ignore the above message, below is the complete information.

http://www.tek-tips.com/viewthread.cfm?qid=1144795&page=5

In the above mentioned thread it was said ,that we should always start with "last erred" device but sun says to start with “Maintenance” first, please refer to the below mentioned link.

http://docs.sun.com/app/docs/doc/816-4518/6mannldk8?a=view

The problem started after my colleague pulled the second drive from v210 while the system was running(I probably think the blue LED light was still not lit on, while pulling out the hard drive).

After the above steps I copied the VTOC on the new second disk and then used metareplace -e to sync both the disk.
Root and /var had completely sync but /export/home just went on till 60%, next day the system gave me last erred and maintainence error as mentioned below.

This both hard drive contains root filesystem.
Should I try to first do format/analyze/read on the second harddisk.

d2: Mirror
Submirror 0: d25
State: Needs maintenance
Submirror 1: d26
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 259691520 blocks (123 GB)

d25: Submirror of d2
State: Needs maintenance
Invoke: after replacing "Maintenance" components:
metareplace d2 c1t0d0s7 <new device>
Size: 259691520 blocks (123 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s7 0 No Last Erred Yes


d26: Submirror of d2
State: Needs maintenance
Invoke: metareplace d2 c1t1d0s7 <new device>
Size: 259691520 blocks (123 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s7 0 No Maintenance Yes


Device Relocation Information:
Device Reloc Device ID
c1t0d0 Yes id1,sd@SSEAGATE_ST314670LSUN146G35426ZE6____________3KS26ZE6
c1t1d0 Yes id1,sd@SSEAGATE_ST314670LSUN146G34424907____________3KS24907

 

[sunny1504]

I have tried the below mentioned step but after a while it stop synching and gives me the same error.
metareplace -e d2 c1t1d0s7

Will the below mentioned steps work without any data loss.

http://www.tek-tips.com/viewthread.cfm?qid=1144795&page=5

________________________________________________________
If metareplace does not work you can run (if you have a md.tab)
metadetach -f dmirrordsubmirror1
metadetach -f dmirrordsubmirror2
metaclear -f dmirror
metaclear -f dsubmirror1
metaclear -f dsubmirror2
metainit dsubmirror1
metainit dsubmirror2
metainit dmirror
metattach dmirror dsubmirror2
________________________________________________________

 

[daFranze]

this is exactly what I would suggest, forced detach and recreate the md

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage

 

[sunny1504]

DaFranze,

metadetach -f d2 c1t1d0s7
metadetach -f d2 c1t0d0s7
metaclear -f d2
metaclear -f c1t1d0s7
metaclear -f c1t0d0s7

metainit d25 1 1 c1t0d0s7
metainit d26 1 1 c1t1d0s7
metainit d2 -m d25
metattach d2 d26


With the above steps wont there be any corruption of data?

 

[daFranze]

the meta... commands above will NOT destroy any data. the data may be already corrupt (now). If you are lucky you can recover all data without loss. BTW: Did you mount the ufs with "logging" flag? I recommend to do this with any ufs (OS must be 5.7 or higher to have "logging" flag afaik)

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage

 

[daFranze]

ups: it's in your examples

metadetach -f d2 c1t1d0s7
metadetach -f d2 c1t0d0s7
metaclear -f d2
metaclear -f d25
metaclear -f d26

#d25 should be the device which is now "last erred"
metainit d2 -m d25

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage

 

[daFranze]

sorry, another typo

metadetach -f d2 d25
and
metadetach -f d2 d26

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage