Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Administration: Basic Administration Oracle Solaris 10 1/13 Information Library |
1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
What's New in Booting an Oracle Solaris System?
Booting a SPARC Based System (Task Map)
SPARC: How to Boot a System to Run Level 3 (Multiuser Level)
SPARC: How to Boot a System to Run Level S (Single-User Level)
SPARC: How to Boot a System Interactively
SPARC: How to Boot a Kernel Other Than the Default Kernel
Booting From a Specified ZFS Root File System on a SPARC Based System
SPARC: How to List Available Bootable Datasets Within a ZFS Root Pool
SPARC: How to Boot From a Specified ZFS Root File System
Booting a SPARC Based System in Failsafe Mode
How to Boot a SPARC Based System in Failsafe Mode
Booting a SPARC Based System From the Network
SPARC: How to Boot a System From the Network
Booting an x86 Based System by Using GRUB (Task Map)
x86: How to Boot a System to Run Level 3 (Multiuser)
x86: How to Boot a System to Run Level S (Single-User Level)
x86: How to Boot a System Interactively
x86: Booting From a Specified ZFS Root File System on an x86 Based System
x86: How to Display a List of the Available ZFS Boot Environments
Booting an x86 Based System in Failsafe Mode
How to Boot an x86 Based System in Failsafe Mode
x86: How to Boot in Failsafe Mode to Forcibly Update a Corrupt Boot Archive
Booting an x86 Based System From the Network
x86: How to Perform a GRUB Based Boot From the Network
Accelerating the Reboot Process on the SPARC Platform (Task Map)
Initiating a Fast Reboot of a SPARC Based System
How to Initiate a Fast Reboot of a SPARC Based System
Performing a Standard Reboot of a SPARC Based System
Managing the Boot Configuration Service
Booting From an iSCSI Target Disk
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With Oracle Configuration Manager
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
To support booting an Oracle Solaris ZFS root file system on the x86 platform, a new GRUB keyword, $ZFS-BOOTFS, has been introduced. If a root device contains a ZFS pool, this keyword is assigned a value, which is then passed to the kernel with the -B option. This option identifies which dataset to boot. If you install or upgrade your system with an Oracle Solaris release that supports a ZFS boot loader, the GRUB menu.lst file, as well as the GRUB boot menu, contain this information by default.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
~# bootadm list-menu
# lustatus
Note that the lustatus command can also be used on SPARC based systems.
Note - If the following error is displayed when you run the lustatus command, it is an indication that a new installation was performed and that Solaris Live Upgrade was not used. Before any BEs can be acknowledged in the lustatus output, a new BE must be first created on the system.
# lustatus ERROR: No boot environments are configured on this system ERROR: cannot determine list of all boot environment names
For more information about using Solaris Live Upgrade to migrate a UFS root file system to a ZFS root file system, see Migrating to a ZFS Root File System or Updating a ZFS Root File System (Live Upgrade) in Oracle Solaris ZFS Administration Guide.
Example 12-12 Displaying a List of Available ZFS Bootable Datasets by Using the lustatus Command
In this example, the output of the lustatus command shows the status of three ZFS bootable datasets. The default boot environment is be1 and therefore cannot be deleted.
# lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ ---------- s10s_nbu6wos yes no no yes - zfs2BE yes yes yes no - zfsbe3 no no no yes - #
If the BE has been created and is bootable, a “yes” appears in the Is Complete column. If a BE has been created, but is not yet activated, a 'no” appears in this column. To activate a BE, use the luactivate command. Run the lustatus command afterwards to verify that the BE was successfully activated.
For more information see the lustatus(1M) and the luactivate(1M)man pages.
This procedure describes how to boot from a ZFS root file system on an x86 system that supports a ZFS boot loader.
Note that if you install or upgrade your system to an Oracle Solaris release that supports a ZFS boot loader, the GRUB menu entry contains the -B $ZFS-BOOTFS boot argument by default, so the system boots from ZFS without requiring any additional boot arguments.
# reboot
If the system displays the Press any key to reboot prompt, press any key to reboot the system.
You can also use the Reset button at this prompt. If the system is shut down, turn the system on with the power switch.
When the boot sequence begins, the GRUB main menu is displayed. If the default boot entry is a ZFS file system menu is similar to the following:
GNU GRUB version 0.95 (637K lower / 3144640K upper memory) +----------------------------------------------------------------+ | be1 | be1 failsafe | be3 | be3 failsafe | be2 | be2 failfafe +---------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.
If you do not choose an entry within 10 seconds, the system automatically boots to run level 3.
For more information about GRUB menu entries at boot time, seex86: How to Modify Boot Behavior by Editing the GRUB Menu at Boot Time.
Example 12-13 x86: Activating a New Boot Environment on an x86 Based System
This example shows the steps that are followed to activate a boot environment, be10, on a system. Note that the lustatus command is run first, to determine which BEs on the system are active and which BEs require activation.
# lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status ----------------------------------------------------------------- be1 yes yes yes no be10 yes no no yes # luactivate be10 System has findroot enabled GRUB Generating boot-sign, partition and slice information for PBE <be1> WARNING: The following file s have change on both the current boot environment <be1> zone <global> and the boot environment to be activitate <be10> /etc/zfs/zpool.cache INFORMATION: The files listed above are in conflict between the current boot environment <be1> zone <global> and the boot environment to be activated <be10>. These files will not be automatically synchronized from the current boot environment <be1> when boot environment <be10> is activated. Setting failsafe console to <ttyb> Generating boot-sign for ABE <be10> Generating partition and slice information for ABE <be10> Copied boot menu from top level dataset. Generating direct boot menu entries for PBE. Generating direct boot menu entries for ABE. Disabling splashimage Current GRUB menu default setting is not valid title Solaris bootenv rc No more bootadm entries. Deletion of bootadm entries is complete. GRUB menu default setting is unchanged Done eliding bootadm entries. ************************************************************** The target boot environment has been activated. It will be used when you reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You MUST USE either the init or the shutdown command when you reboot. If you do not use either init or shutdown, the system will not boot using the target BE. *************************************************************** ,,, # reboot May 30 09:52:32 pups reboot: initiated by root on /dev/console syncing file systems... done rebooting... CE SDRAM BIOS P/N GR-xlint.007-4.330 * BIOS Lan-Console 2.0 Copyright (C) 1999-2001 Intel Corporation . . . GNU GRUB version 0.95 (637K lower / 3144640K upper memory) +-------------------------------------------------------------------+ | be1 | be1 failsafe | be10 | be10 failsafe +------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. SunOS Release 5.10 Version Generic_144500-10 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Hostname: pups NIS domain name is sunsoft.eng.sun.com Reading ZFS config: done. Mounting ZFS filesystems: (8/8) pups console login: # lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status ----------------------------------------------------------------- be1 yes yes yes no be10 yes yes yes no #