My Oracle Support Banner

Solaris Volume Manager (SVM) How To Fix Metadevice(s) is in Needs Maintenance state Resolution Path (Doc ID 1503894.1)

Last updated on AUGUST 28, 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 10 9/10 U9 to 10 9/10 U9 [Release 10.0]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on x86-64 (64-bit)

Purpose

This document is a resolution path for trouble shooting and resolving Solaris Volume Manger (SVM) metadevices that are reported as being in "Needs maintenance" state. There are multiple types of metadevice layout and each of these requires a slightly different approach to ensure minimal risk of data loss. This document will give examples of most of the possible metadevice layouts and recommend steps to follow to recover the devices back to an "Okay" state. This document does not cover the actual processes involved in the disk/LUN replacement so this will need to be done according to the documentation for the storage array being used.

The procedure first checks to ensure that the "Needs Maintenance" state is valid and checks to configuration so as to allow the correct procedure to be followed.

Some terms used in the document are:

local = not in a metaset

did device = Solaris Cluster device used in place of physical disk name

 

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
 1: Determine OS version
 2: Determine run level of Solaris
 3: Check svc and process states to ensure mdmonitor is running and metasync startup script has been called.
 4: Determine if running Solaris Cluster or not.
 5: Determine if problem metadevice are local or within a metaset
 6: Determine the date/time the device last changed state.
 7: Check messages for possible causes
 8: The difference between the states "Maintenance" and "Last Erred"
 9: If running Solaris Cluster resolve did device to physical device.
 10: Recovery steps for a "Maintenace" state on a mirrored local metadevice without/with Solaris Cluster.
 11: Working with metasets
 12:Recovery procedure for a mirror with both submirrors in "Needs Maintenace" state
 13: Examples of possible configurations and how to recover them.
 14: Hotspares.
 15: Soft Partitions
References

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