Solaris Volume Manager (SVM) Diskset/Metaset troubleshooting Resolution Path. Solstice Disksuite disk set import Resolution Path (Doc ID 1501173.1)

Last updated on OCTOBER 10, 2022

Applies to:

Purpose

This document is a Resolution Path. It will guide you through step by step to troubleshoot SVM SDS diskset problems no clustering.

If this is Solaris Cluster please reference Cannot add a disk to diskset or Multi owner diskset in Sun Cluster/Solaris Cluster (Doc ID 1021063.1).  This document covers most issues with disksets within cluster.
If working in a clustered environment, root must be a member of Group 14. Alternatively, the /.rhosts file on each host must contain an entry for the other host names associated with the disk set.

 The following problems are addressed in this document:


Problems importing or taking ownership of a diskset after a hostname change.
Cannot import diskset.
Problems importing or taking ownership of a diskset.
Cannot take diskset.
Problems importing or taking ownership of a diskset from a clustered system to a non clustered system.

Problems adding disks to a diskset.
Cannot add disk to diskset.
Failing to create a diskset or meta device because /kernel/drv/md.conf file is not defined correctly or have
reached the maximum number of disksets or metadevices.

When running the command metaset on one node and no metasets are found.

How to change the hostname of a system with disksets.

Example Errors:

"tagged data detected, user intervention required"

"partial diskset detected"

"No such file or directory"

"no available set numbers"

# metaset -s ora-set  "no such set"

"metad client create: RPC: Rpcbind failure"

Troubleshooting Steps

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