My Oracle Support Banner

Solaris Volume Manager (SVM) How to Troubleshoot and Fix Mirroring Issues Resolution Path (Doc ID 1503608.1)

Last updated on OCTOBER 09, 2019

Applies to:

Solstice DiskSuite Software - Version 4.2 to 4.2.1 [Release 4.0]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Solaris Operating System - Version 9 GA to 9 GA [Release 9.0]
Oracle Solaris on x86 (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)

Purpose

This document is a Resolution Path. It provides steps to troubleshoot and fix SVM Solaris Volume Manager Metadevice(s) mirroring issues.

This document address the following issues :

I - one submirror in "Needs maintenance", other submirror in "Okay" states

II - one submirror in "Needs maintenance", other submirror in "Last Erred" state

III - one submirror in "Resyncing", the other in "Last Erred"

IV - all submirrors in "Needs maintenance"

V - Recover the mirror by deleting and recreating it with the exact same layout

 

To keep the command line simple in this document all examples are refer to local metadevices. If using metadevice in a metaset, then certainly you need to use the command with the -s option and the setname.

If you using soft partitions then also refer to
<Document 1494494.1> How to Troubleshoot and Repair SVM Soft Partitions (Softpartitions) Resolution Path

This Document does not address boot issues with mirrored metadevices, please refer to:
<Document 1489871.1> Solaris Volume Manger, SVM mirrored root disk server system/node can not boot. Troubleshooting. Resolution Path

 

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 I - Recovery procedure for a SVM mirror with one submirror in "Needs maintenance" state and one submirror in "Okay" state
 II - Recovery procedure for a SVM mirror with one submirror in "Needs maintenance" state and one submirror in "Last Erred" state:
 III - Recovery procedure for a SVM mirror with One sub-mirror in “Resyncing”, the other in “Last Erred" state 
 IV - Recovery procedure for a SVM mirror with all submirrors in "Needs maintenance" state
 V - Recover the mirror by deleting and recreating it with the exact same layout
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.