Unable to activate Solaris Boot Environment (BE) property 'bootfs': '/dev/dsk/' failed to open. No such device or address

Problem

Solaris 11 users may not be able to activate Solaris Boot Environments (BE) due to an interoperability issue between Solaris and Veritas Volume Manager 8.0 and higher.

 

Error Message

In this instance, the BE name is called 11.4.60.151.2
 

# beadm activate 11.4.60.151.2
Activating BE 11.4.60.151.2 failed.
property 'bootfs': '/dev/dsk/emc0_05fds0' failed to open. No such device or address. All disk labeling/system requirements for booting are not satisfied.
Please see logfile /var/share/beadm/beadm.21755.20231122_111714.xxxxx.log for additional details

Note: The beadm list command can be run to list the Solaris Boot Environment names.

Cause

The issue is identified as a defect in Veritas Volume Manager 8.0 and higher.

Solution

The Product Engineering Team currently plans to address this issue by way of a patch or hotfix for InfoScale 8.0.2 and higher.

Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.
There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time.  

InfoScale 8.0 users may be required to install Private VxVM hotfix, vm-sol11_sparc-HotFix-8.0.0.2801 or higher due to known defects when enabling/disabling dmp_native_support. 
 

Volume Manager 8.0.0.2801 addresses the issue - Please refer to Veritas Technical Support for the fix.
 

NOTE: To resolve related Solaris ZFS panics,  leaving the system unbootable after enabling dmp native support in solaris 11.4 sparc,  Veritas recommends applying the above Veritas Private hotfix for VxVM:
 

NOTICE: zfs_parse_bootfs: error 48
Cannot mount root on rpool/487 fstype zfs
panic[cpu0]/thread=20012000: vfs_mountroot: cannot mount root
Warning - stack not written to the dumpbuf
genunix:vfs_mountroot+494 ()
genunix:main+224 ()