Last updated on OCTOBER 06, 2016
Applies to:Solaris Operating System - Version 10 11/06 U3 to 10 11/06 U3 [Release 10.0]
Sun Solaris Volume Manager (SVM) - Version 11.10.0 to 11.11 [Release 11.0]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (32-bit)
The problem described in this article can have multiple symptoms and errors. One of these issues described in this article can occur right after disk replacement, or when disk was not correctly replaced in the past. When this problem happens there will be a mismatch of Solaris Volume Manager (SVM) disk Device ID (DevID) is in the metadb that causes various errors and meta command failures.
In below example, the DevID in metastat output for disk c1t1d0 does not match the DevID in /etc/lvm/mddb.cf and /kernel/drv/md.conf despite metadevadm -u command was done. Beware that depending on your server the name of the disk can also be a WWN disk name like "c0t5000C5004382FDCFd0s0".
You will need to enter maintenance mode and delete the metadbs on the disk that got the metadevadm error.
The following document has the metadb commands to run.
<Document 1010270.1> Solaris Volume Manager (SVM) Recovering From Insufficient Metadevice State Database Replicas
The following can lead to this issue:
1) patching the system with recommended patch cluster so it is now at a patch level that is now vulnerable to the bug described in this article.
2) incomplete or incorrect disk replacement
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