JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: Common Tasks     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

About This Book

1.  Locating Information About Oracle Solaris Commands

2.  Managing User Accounts and Groups (Overview)

3.  Managing User Accounts and Groups (Tasks)

4.  Booting and Shutting Down an Oracle Solaris System

What's New in Booting and Shutting Down a System?

Support for Administratively Provided driver.conf Files

Bitmapped Console

Boot and Shutdown Progress Animation

Fast Reboot

x86: Removal of Support for 32-Bit Kernel

Booting and Shutting Down an Oracle Solaris System (Overview)

GRUB Based Booting

Management of Boot Services by the Service Management Facility

Booting a System to a Specified State (Task Map)

Booting a System to a Specified State (Run Level)

Determining a System's Current Run Level

SPARC: How to Boot a System to a Multiuser State (Run Level 3)

x86: How to Boot a System to a Single-User State (Run Level S)

Shutting Down a System (Task Map)

Shutting Down a System

How to Shut Down a System by Using the shutdown Command

Bringing a System to a Shutdown State (Run Level 0) by Using the init Command

How to Shut Down a System by Using the init Command

Booting a System From the Network

Accelerating the Reboot Process (Task Map)

Accelerating the Reboot Process

How to Initiate a Fast Reboot of a SPARC Based System

How to Initiate a Fast Reboot of an x86 Based System

Changing the Default Behavior of the Fast Reboot Feature

Initiating a Standard Reboot of a System That Has Fast Reboot Enabled

Booting From a ZFS Boot Environment (Task Map)

SPARC: Booting From a ZFS Boot Environment

SPARC: How to Display a List of Available Boot Environments During the Boot Sequence

SPARC: How to Boot From a ZFS Boot Environment or Root File System

Modifying Boot Parameters (Task Map)

Modifying Boot Parameters

SPARC: How to Determine the Default Boot Device

SPARC: How to Change the Default Boot Device by Using the Boot PROM

x86: How to Modify Boot Parameters by Using the eeprom Command

x86: How to Modify Boot Parameters at Boot Time

Adding a Linux Entry to the GRUB Menu After an Installation

Keeping a System Bootable (Task Map)

Keeping a System Bootable

Determining Whether the boot-archive SMF Service Is Running

How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive

x86: How to Clear a Failed Automatic Boot Archive Update by Using the auto-reboot-safe Property

Where to Find More Information About Booting and Shutting Down a System

5.  Working With Oracle Configuration Manager

6.  Managing Services (Overview)

7.  Managing Services (Tasks)

8.  Using the Fault Manager

9.  Managing System Information (Tasks)

10.  Managing System Processes (Tasks)

11.  Monitoring System Performance (Tasks)

12.  Managing Software Packages (Tasks)

13.  Managing Disk Use (Tasks)

14.  Scheduling System Tasks (Tasks)

15.  Setting Up and Administering Printers by Using CUPS (Tasks)

16.  Managing the System Console, Terminal Devices, and Power Services (Tasks)

17.  Managing System Crash Information (Tasks)

18.  Managing Core Files (Tasks)

19.  Troubleshooting System and Software Problems (Tasks)

20.  Troubleshooting Miscellaneous System and Software Problems (Tasks)

Index

Modifying Boot Parameters

On SPARC platforms, the boot PROM is used to boot a SPARC based system and to modify boot parameters. For example, you might want to reset the device from which to boot, change the default boot file or kernel, or run hardware diagnostics before bringing the system to a multiuser state.

For a complete list of PROM commands, see the monitor(1M) and eeprom(1M) man pages.

On x86 platforms, the primary methods for modifying boot parameters are as follows:

SPARC: How to Determine the Default Boot Device

  1. Bring the system to the ok PROM prompt.

    For more information, see How to Shut Down a System by Using the init Command.

  2. Determine the default boot device.
    ok printenv boot-device
    boot-device

    Identifies the parameter for setting the device from which to boot.

    For more information, see the printenv(1B) man page.

    The default boot-device is displayed in a format that is similar to the following:

    boot-device = /pci@1f,4000/scsi@3/disk@1,0:a

    If the boot-device parameter specifies a network boot device, the output is similar to the following:

    boot-device = /sbus@1f,0/SUNW,fas@e,8800000/sd@a,0:a \
    /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0:a disk net

SPARC: How to Change the Default Boot Device by Using the Boot PROM

Before You Begin

You might need to identify the devices on the system before you can change the default boot device to some other device. For information about identifying devices on the system, see How to Identify Devices on a System in Booting and Shutting Down Oracle Solaris on SPARC Platforms.

  1. Bring the system to the ok PROM prompt.
    # init 0
  2. Change the value of the boot-device parameter.
    ok setenv boot-device device[n]
    device[n]

    Identifies the boot-device value, such as disk or network. The n can be specified as a disk number. Use one of the probe commands if you need help identifying the disk number.

  3. Verify that the default boot device has been changed.
    ok printenv boot-device
  4. Save the new boot-device value.
    ok reset-all

    The new boot-device value is written to the PROM.

Example 4-6 SPARC: Changing the Default Boot Device by Using the Boot PROM

In this example, the default boot device is set to disk.

# init 0
# 
INIT: New run level: 0
.
.
.
The system is down.
syncing file systems... done
Program terminated
ok setenv boot-device /pci@1f,4000/scsi@3/disk@1,0
boot-device =         /pci@1f,4000/scsi@3/disk@1,0
ok printenv boot-device
boot-device           /pci@1f,4000/scsi@3/disk@1,0
ok boot
Resetting ... 

screen not found.
Can't open input device.
Keyboard not present.  Using ttya for input and output.
.
.
.
Rebooting with command: boot disk1                                    
Boot device: /pci@1f,4000/scsi@3/disk@1,0  File and args:

In this example, the default boot device is set to the network.

# init 0
# 
INIT: New run level: 0
.
.
.
The system is down.
syncing file systems... done
Program terminated
ok setenv boot-device net
boot-device =         net
ok printenv boot-device
boot-device           net                    disk
ok reset
.
.
.
Boot device: net  File and args:

pluto console login:

See Also

For instructions on using the eeprom utility to change the default boot device on a SPARC based system, see How to Change the Default Boot Device by Using the eeprom Utility in Booting and Shutting Down Oracle Solaris on SPARC Platforms.

x86: How to Modify Boot Parameters by Using the eeprom Command

  1. Become the root role.
  2. Change the specified parameter.
    # eeprom parameter=new-value
  3. Verify that the new parameter has been set.
    # eeprom parameter

    The output should display the new eeprom value for the specified parameter.

Example 4-7 Setting the auto-boot Parameter by Using the eeprom Command

The following example shows how to set the auto-boot boot parameter to true.

# eeprom auto-boot?=true

When the eeprom command is run in user mode, any parameters that have a trailing question mark (?) need to be enclosed in double quotation marks to prevent the shell from interpreting the question mark. Preceding the question mark with an escape character (\) also prevents the shell from interpreting the question mark. For example:

# eeprom "auto-boot?"=true

x86: How to Modify Boot Parameters at Boot Time

When you modify the default kernel usage by editing the GRUB menu at boot time, the changes do not persist over a system reboot. The default boot parameters are restored the next time you boot the system.

For a detailed description of all of the boot parameters that you can specify at boot time, see Modifying Based Boot Parameters at Boot Time in Booting and Shutting Down Oracle Solaris on x86 Platforms.

  1. Reboot the system.

    When the boot sequence begins, the GRUB main menu is displayed.

  2. Use the arrow keys to select the boot entry to edit.
  3. Type e to access the GRUB edit menu.
  4. Select the kernel$ line in the menu.
  5. Type e to add boot arguments to the line.
  6. Type any additional boot arguments.
  7. Press Return to save your changes and return to the previous menu.

    Note - Pressing the Escape key returns you to the GRUB main menu without saving your changes.


  8. To boot the system, type b.

    Changes you make take effect when the system is booted.

Adding a Linux Entry to the GRUB Menu After an Installation

If you are setting up a boot environment in such a way that you install Linux on one partition first and Oracle Solaris on another partition afterwards, you will need to follow certain instructions to ensure that the GRUB menu information from the new installation does not erase the GRUB menu information from a previous installation. For instructions, see How to Add a Linux Entry to the GRUB Menu After Installing Oracle Solaris in Booting and Shutting Down Oracle Solaris on x86 Platforms.


Note - Some Linux distributions now run on GRUB2, for example, Ubuntu and Mint Linux. You cannot boot GRUB2 partitions on the version of GRUB that is included in Oracle Solaris 11. In these instances, an alternate workaround is suggested.