Solaris Volume Manager (SVM) How to Recover/Restore from "Insufficient metadevice database replicas located" (Doc ID 1010270.1)

Last updated on JULY 12, 2017

Applies to:

Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Solstice DiskSuite Software - Version 4.2.1 to 4.2.1 [Release 4.0]
Solaris Operating System - Version 10 8/07 U4 to 10 8/07 U4 [Release 10.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on x86-64 (64-bit)

Goal

During the boot process, Solaris Volume Manager (SVM) probes for available state database replicas. If SVM does not find "enough" available replicas, one will see the following messages:

   ok boot
.......
.......
Hostname: demo
metainit: demo: stale databases
Insufficient metadevice database replicas located.
Use metadb to delete databases which are broken.
Ignore any "Read-only file system" error messages.
Reboot the system when finished to reload the metadevice
database.  After reboot, repair any broken database
replicas which were deleted.
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance):<root-password>
Entering System Maintenance Mode

The issue occur when the partition which include the local metadb/replica is gone.
For example:

 

This document provides solution to recover from hitting the problem of getting "Insufficient metadevice database replicas."

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms