I think that you might be able to get away with that, you'd have to check some other stuff out incase you make it worse I think.
You could check that the disks are all available with # prtvtoc /dev/rdsk/cXtNdNsN it would also maybe be worth looking at the output of # metastat -p if I run it on one of my machines I see;
I'd like to have at least that information to re-create the metadevices manually and rebuild from there.
It should be noted that this is a late Solaris 10 system;
Code:
e434069 on PROD SERVER # echo | format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000CCA07023D760d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris
/scsi_vhci/disk@g5000cca07023d760
1. c0t5000CCA07025DA5Cd0 <SUN600G cyl 64986 alt 2 hd 27 sec 668>
/scsi_vhci/disk@g5000cca07025da5c
2. c0t5000CCA07040B1F8d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris
/scsi_vhci/disk@g5000cca07040b1f8
3. c0t5000CCA0704093E4d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris
/scsi_vhci/disk@g5000cca0704093e4
4. c0t600507680C80827800000000000004A0d0 <IBM-2145-0000-3.00TB>
/scsi_vhci/ssd@g600507680c80827800000000000004a0
5. c0t600507680C80827800000000000004A1d0 <IBM-2145-0000 cyl 38398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000004a1
6. c0t600507680C80827800000000000004A2d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c80827800000000000004a2
7. c0t600507680C80827800000000000000ADd0 <IBM-2145-0000 cyl 32766 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000000ad
8. c0t600507680C80827800000000000000AEd0 <IBM-2145-0000 cyl 32766 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000000ae
9. c0t600507680C80827800000000000000AFd0 <IBM-2145-0000 cyl 38398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000000af
10. c0t600507680C80827800000000000004AFd0 <IBM-2145-0000 cyl 10238 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c80827800000000000004af
11. c0t600507680C80827800000000000000B0d0 <IBM-2145-0000 cyl 32766 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000000b0
12. c0t600507680C80827800000000000000B1d0 <IBM-2145-0000 cyl 32766 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000000b1
13. c0t600507680C808278000000000000029Bd0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c808278000000000000029b
14. c0t600507680C808278000000000000010Bd0 <IBM-2145-0000 cyl 12798 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c808278000000000000010b
15. c0t600507680C80827800000000000001CFd0 <IBM-2145-0000 cyl 15358 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c80827800000000000001cf
16. c0t600507680C808278000000000000010Cd0 <IBM-2145-0000 cyl 38398 alt 2 hd 128 sec 256>
/scsi_vhci/ssd@g600507680c808278000000000000010c
17. c0t600507680C808278000000000000029Cd0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c808278000000000000029c
18. c0t600507680C80827800000000000001DAd0 <IBM-2145-0000-2.00TB>
/scsi_vhci/ssd@g600507680c80827800000000000001da
19. c0t600507680C80827800000000000001DBd0 <IBM-2145-0000 cyl 6398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000001db
20. c0t600507680C80827800000000000001DCd0 <IBM-2145-0000 cyl 46078 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000001dc
21. c0t600507680C80827800000000000001DDd0 <IBM-2145-0000 cyl 26878 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000001dd
22. c0t600507680C80827800000000000001DEd0 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c80827800000000000001de
23. c0t600507680C80827800000000000001DFd0 <IBM-2145-0000 cyl 46078 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000001df
24. c0t600507680C808278000000000000010Dd0 <IBM-2145-0000 cyl 7678 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c808278000000000000010d
25. c0t600507680C80827800000000000001E4d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c80827800000000000001e4
26. c0t600507680C80827800000000000001E5d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c80827800000000000001e5
27. c0t600507680C80827800000000000004ECd0 <IBM-2145-0000 cyl 38398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000004ec
28. c0t600507680C80827800000000000004EEd0 <IBM-2145-0000 cyl 63998 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c80827800000000000004ee
29. c0t600507680C808278000000000000024Ed0 <IBM-2145-0000 cyl 57109 alt 2 hd 255 sec 252>
/scsi_vhci/ssd@g600507680c808278000000000000024e
30. c0t600507680C808278000000000000024Fd0 <IBM-2145-0000 cyl 6398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c808278000000000000024f
31. c0t600507680C808278000000000000049Fd0 <IBM-2145-0000 cyl 19198 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c808278000000000000049f
32. c0t600507680C8082780000000000000245d0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000245
33. c0t600507680C8082780000000000000250d0 <IBM-2145-0000 cyl 65278 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000250
34. c0t600507680C8082780000000000000421d0 <IBM-2145-0000 cyl 6398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000421
35. c0t600507680C8082780000000000000423d0 <IBM-2145-0000 cyl 13822 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000423
36. c0t600507680C8082780000000000000420d0 <IBM-2145-0000 cyl 34558 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000420
37. c0t600507680C8082780000000000000424d0 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c8082780000000000000424
38. c0t600507680C8082780000000000000134d0 <IBM-2145-0000 cyl 8190 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c8082780000000000000134
39. c0t600507680C8082780000000000000422d0 <IBM-2145-0000 cyl 42238 alt 2 hd 128 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000422
40. c0t600507680C8082780000000000000132d0 <IBM-2145-0000 cyl 18558 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000132
41. c0t600507680C8082780000000000000514d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c8082780000000000000514
42. c0t600507680C8082780000000000000515d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c8082780000000000000515
43. c0t600507680C8082780000000000000133d0 <IBM-2145-0000 cyl 6142 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g600507680c8082780000000000000133
44. c0t600507680C8082780000000000000561d0 <IBM-2145-0000 cyl 6398 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000561
45. c0t600507680C8082780000000000000247d0 <IBM-2145-0000 cyl 4478 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000247
46. c0t600507680C8082780000000000000251d0 <IBM-2145-0000 cyl 35198 alt 2 hd 128 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000251
47. c0t600507680C8082780000000000000252d0 <IBM-2145-0000 cyl 5118 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000252
48. c0t600507680C8082780000000000000253d0 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000253
49. c0t600507680C8082780000000000000246d0 <IBM-2145-0000 cyl 40318 alt 2 hd 128 sec 256>
/scsi_vhci/ssd@g600507680c8082780000000000000246
50. c0t600507680C8082780000000000000516d0 <IBM-2145-0000 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600507680c8082780000000000000516
Specify disk (enter its number): Specify disk (enter its number):
e434069 on PROD SERVER #
If you don't have the underlying stuff to hand, you have a problem when you try to reinstate - that's why I suggested the metarecover. It may be that the state databases have to be cleared down and the whole metadb recreated.
Regards
Gull04
These 2 Users Gave Thanks to gull04 For This Post:
Running Solaris 9 with SVM. I'm not that familiar with it, but metastat output gives "needs maintenance" message on 2 of the mirrors. There are no errors in /var/adm/messages. What do I need to do to fix this error? Thanks. (14 Replies)
hi all,
can someone pls pass on your suggestion?
Firs thing I am testing a script which checks for the pattern 'Needs Maintenance' from metastat output and prints some messages in the screen. So i need to simulate an error in mirrored disk for metastat to give this message 'Needs Maintenance'.... (3 Replies)
Hi people,
I have on problem when execute the command METASTAT...
d60: Soft Partition
Device: d10
State: Errored
Size: 12582912 blocks (6.0 GB)
Someone help me?
Thank you very much (4 Replies)
Hi All,
Sorry to post a problem for my first post but I'm in a bit of a pickle at the minute!
I have an Ultra45 connected to a Storedge 3100 series, 2 internal, 2 external disks with a db application running on the external disks.
Now everything is working fine and we've had no downtime or... (4 Replies)
Can any one of you suggest me the method to get apache server in online from maintenance mode. I tried in the following way, but couldn't get that service to online.
bash-3.00# svcs -a | grep apache
legacy_run 9:51:55 lrc:/etc/rc3_d/S50apache
offline 9:51:22... (3 Replies)
Dear,
Required an script such that :
If metastat |grep Needs , results in some output then this command to be executed for the same :
opcmsg object=metastat a=OS msg_grp=OpC severity=critical msg_text="Need maintenance for the system $line"
With regards,
Mjoshi (3 Replies)
Hi
I need to export a directory named /sybase from my solaris machine via NFS. The svcs command shows the state as disabled. Please let me know how to export the directory.
Once the directory is exported from the solaris machine it has to be mounted locally in an aix machine. Can some one... (2 Replies)
Hi,
I'm new to Solaris. I have an issue with ssh service. When I restart the service it exits with an exit status of 0
$svcadm restart svc:/network/ssh:default
$echo $?
0
$
However, the service goes into maintenance mode after restart. I'm able to connect even though the service is in... (3 Replies)