Solaris Cluster 3.x with VxVM Failed to Boot "fsck failed with no device", Volumes DISABLED and Diskgroup Deported, "Degraded" Device group (Doc ID 1009205.1)

Last updated on APRIL 12, 2017

Applies to:

Solaris Cluster - Version 3.0 to 3.3 U2 [Release 3.0 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

Solaris Cluster 3.x with Veritas Volume Manager (VxVM) node failed to join cluster after reboot.

It went into single user mode and reported that fsck had failed, and that the fsck command must be run on the file system manually.

When fsck was run against the volumes, the volumes appeared not to exist and the diskgroup was not imported.

The diskgroups were then imported manually and all volumes were ENABLED, but fsck reported a "no device" error.

Then, it DISABLED all the volumes in the diskgroup and deported the diskgroup.

Changes

Possible improper disk replacement in a Sun Cluster environment

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