Last updated on APRIL 20, 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 SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
In Solaris Cluster 3.0 to 3.3 software, a problem might occur where all filesystems are available when booted outside of a cluster but when booted into cluster the filesystem(s) fail to mount or be accessed producing the error "No such device or address".
This error occurs even though the device group is shown as Online in scstat, and the disk is available through format and the volume manager software.
This can occur when creating a filesystem with newfs, or when accessing a filesystem or using fsck.
No errors are present in the /var/adm/messages file or in the dcs_dbg debug buffer.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms