Go to main content

Booting and Shutting Down Oracle® Solaris 11.3 Systems

Exit Print View

Updated: October 2017

What's New in Booting and Shutting Down a System

In this release, the bootadm command has been expanded to secure the GRUB menu. You can now allow only specific users or users with a specific password to view, edit, or boot from the GRUB menu. See Administering the GRUB Configuration by Using the bootadm Command for more information.

On systems that can boot using firmware-inaccessible storage devices, such as an iSCSI device accessed using IP over Infiniband (IPoIB), the Oracle Solaris boot process has the following enhancements:

  • Can access boot archives in a boot pool on firmware-accessible devices. The boot archive includes the set of files needed to boot the Oracle Solaris kernel for the boot environment (BE) with which that boot dataset is associated. The boot pool includes boot loader data files and recovery data. Each dataset in the boot pool is linked to a BE. See Managing Systems with Boot Pools for more information.

  • Allows the root pool to reside on a firmware-inaccessible storage device that is not accessible from OpenBoot. When you create a root pool, a boot pool is automatically created on OpenBoot-accessible devices. See Changes to the Boot Process for more information.

  • Can boot from a fallback image stored on the service processor (SP) if no devices in the boot pool are accessible from OpenBoot. The fallback image is available on any domain that has access to a service processor and its associated rKVMS services. See Booting From a Fallback Image for more information.