Solaris Cluster Unable to Start a Resource Group due to Device Group in Maintenance State (Doc ID 1007678.1)

Last updated on DECEMBER 15, 2016

Applies to:

Solaris Cluster - Version 3.0 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)

Symptoms

A Solaris Cluster resource group fails to start.

Example for Solaris Cluster 3.2 and higher:

# clresourcegroup switch -n node1 nfs-rg
clresourcegroup:  (C748634) Resource group nfs-rg failed to start on chosen node and might fail over to other node(s)

You can also use the 'clrg' shorthand command for the 'clresourcegroup' command.


Example for Sun Cluster 3.0 and 3.1:

# scswitch -z -g nfs-rg -h node1
scswitch: Resource group nfs-rg failed to start on chosen node and may fail over to other node(s)

 

And the system log file, /var/adm/messages, reports that the SUNW.HAStoragePlus resource in this resource group has a global device service, 'nfs-dg' in this case, that is in the maintenance state.

Dec 23 14:49:02 testnode SC[zone1,SUNW.HAStoragePlus:9,ffs-rg,ffs-hasp,hastorageplus_prenet_start]: [ID 579208 daemon.error] Global service nfs-dg associated with path /ha/nfs-dg is found to be in maintenance state.

For Sun Cluster 3.0 and earlier, the logged message will almost be the same, as shown in the example below.

Jan  4 15:45:31 node1 SC[SUNW.HAStoragePlus,nfs-rg,nfs-hastp-rs,hastorageplus_prenet_start_private]: Global service nfs-dg associated with path /ha/nfs-dg is found to be in the maintenance state.

 

Cause

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