If the system is not booted from a firmware-inaccessible storage device, all BEs are bootable. However, when booting from an iSCSI boot device using IPoIB, for example on a SPARC M7 series server, it is possible that the dataset associated with a BE has been evicted from the boot pool. In this case the BE is no longer bootable. You can use the steps below to restore the dataset and make the BE bootable.
In this example, BE1 includes a ! in the list of flags, which means that BE1 is not bootable. Note that the N flag indicates that BE3 is booted now, and the R flag indicates that BE3 will be used during the next reboot.
# beadm list BE Flags Mountpoint Space Policy Created -- ----- ---------- ----- ------ ------- BE1 !- - 6.13M static 2014-10-09 17:21 BE2 - - 52.86M static 2015-01-03 16:22 BE3 NR / 313.1M static 2015-02-04 17:36
This command sets the BE to be active on reboot, and configures the boot pool dataset for booting.
# beadm activate BE1
In this example, BE1 is now bootable because the ! is missing from the list of flags for that BE.
# beadm list BE Flags Mountpoint Space Policy Created -- ----- ---------- ----- ------ ------- BE1 R - 6.13M static 2014-10-09 17:21 BE2 - - 52.86M noevict 2015-01-03 16:22 BE3 N / 313.1M static 2015-02-04 17:36
If you do not want to boot from BE1 the next time the OS reboots, reset the active BE.
# beadm activate BE3 # beadm list BE Flags Mountpoint Space Policy Created -- ----- ---------- ----- ------ ------- BE1 - - 6.13M static 2014-10-09 17:21 BE2 - - 52.86M noevict 2015-01-03 16:22 BE3 NR / 313.1M static 2015-02-04 17:36