JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Booting and Shutting Down Oracle Solaris on SPARC Platforms     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  Booting and Shutting Down a SPARC Based System (Overview)

2.  Booting a SPARC Based System to a Specified State (Tasks)

Booting a SPARC Based System to a Specified State (Task Map)

Booting a SPARC Based System to a Specified State

Determining a System's Current Run Level

Booting a SPARC Based System to a Multiuser State (Run Level 3)

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

Booting a SPARC Based System to a Single-User State (Run Level S)

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

Booting a SPARC Based System Interactively

How to Boot a System Interactively

3.  Shutting Down a System (Tasks)

4.  Rebooting a SPARC Based System (Tasks)

5.  Booting a SPARC Based System From the Network (Tasks)

6.  Modifying Boot Parameters on a SPARC Based System (Tasks)

7.  Creating, Administering, and Booting From ZFS Boot Environments on SPARC Platforms (Tasks)

8.  Keeping a SPARC Based System Bootable (Tasks)

9.  Troubleshooting Booting a SPARC Based System (Tasks)

Index

Booting a SPARC Based System to a Specified State

The following procedures describe how to boot a SPARC based system to a specified state, also called run level booting, from the ok PROM prompt. These procedures assume that the system has been cleanly shut down, unless stated otherwise.

Determining a System's Current Run Level

To determine the current run level on a running system, use the who -r command.

Example 2-1 Determining a System's Run Level

The output of the who -r command displays information about a system's current run level, as well as previous run levels.

$ who -r
 .    run-level 3  Dec 13 10:10  3  0 S
$
Output of who -r command
Description
run-level 3
Identifies the current run level
Dec 13 10:10
Identifies the date of last run level change
3
Also identifies the current run level
0
Identifies the number of times the system has been at this run level since the last reboot
S
Identifies the previous run level

Booting a SPARC Based System to a Multiuser State (Run Level 3)

If a system is turned off, turning it on starts the multiuser boot sequence.

Use the who -r command to verify that the system is brought to the specified run level. See Determining a System's Current Run Level.

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

Use this procedure to boot a SPARC based system that is currently at run level 0 to run level 3.

  1. Bring the system to the ok PROM prompt.
  2. Boot the system to run level 3.
    ok boot

    The automatic boot procedure displays a series of startup messages and brings the system to run level 3. For more information, see the boot(1M) man page.

  3. Verify that the system has booted to run level 3.

    The login prompt is displayed when the boot process has finished successfully.

    hostname console login:

Example 2-2 Booting a System to a Multiuser State (Run Level 3)

The following example shows the messages from booting a system to run level 3.

ok boot
Probing system devices
Probing memory
ChassisSerialNumber FN62030249
Probing I/O buses

.
.
.
.
OpenBoot 4.30.4.a, 8192 MB memory installed, Serial #51944031.
Ethernet address 0:3:ba:18:9a:5f, Host ID: 83189a5f.
Rebooting with command: boot
Boot device: /pci@1c,600000/scsi@2/disk@0,0:a  File and args:
SunOS Release 5.11 Version fips_checksum_nightly 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
DEBUG enabled
misc/forthdebug (455673 bytes) loaded
Hardware watchdog enabled
Hostname: portia-123
NIS domain name is solaris.us.oracle.com

portia-123 console login: NIS domain name is solaris.us.oracle.com

Booting a SPARC Based System to a Single-User State (Run Level S)

Booting a system to a single-user state is used for system maintenance, such as backing up a file system or troubleshooting other system issues.

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

  1. Bring the system to the ok PROM prompt.
  2. Boot the system to run level S.
    ok boot -s
  3. Type the root password when the following message is displayed:
    SINGLE USER MODE
    
    Root password for system maintenance (control-d to bypass): xxxxxx
  4. Verify that the system is at run level S.
    # who -r
  5. Perform the maintenance task that required the change to run level S.
  6. After you complete the system maintenance task, type Control-D to bring the system to the multiuser state.

Example 2-3 SPARC: Booting a System to a Single-User State (Run Level S)

The following example shows the messages from booting a system to run level S.

ok boot -s
SC Alert: Host System has Reset
Enter #. to return to ALOM.
cpu Device: pci
Device: ebus
/ebus@800: serial
Device: pci
/pci@780: Device 0 Nothing there
/pci@7c0: Device 0 pci
/pci@7c0/pci@0: Device 4 network network
/pci@7c0/pci@0: Device 8 pci
/pci@7c0/pci@0/pci@8: Device 1 network network
/pci@7c0/pci@0/pci@8: Device 2 scsi tape disk

Sun Fire(TM) T1000, No Keyboard
Copyright 2008 ...  All rights reserved.
OpenBoot 4.30.0.build_12***PROTOTYPE BUILD***, 2000 MB memory available,
Serial #69312178.
Ethernet address 0:14:4f:21:9e:b2, Host ID: 84219eb2.

Boot device: /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0:a  File and args:
zfs-file-system
Loading: /platform/SUNW,Sun-Fire-T1000/boot_archive
ramdisk-root hsfs-file-system
Loading: /platform/SUNW,Sun-Fire-T1000/kernel/sparcv9/unix
SunOS Release 5.11 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.30.0.build_12***PROTOTYPE BUILD***, 2000 MB memory available,
Serial #69312178.
Ethernet address 0:14:4f:21:9e:b2, Host ID: 84219eb2.



Boot device: /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0:a  File and args:
zfs-file-system
Loading: /platform/SUNW,Sun-Fire-T1000/boot_archive
ramdisk-root hsfs-file-system
Loading: /platform/SUNW,Sun-Fire-T1000/kernel/sparcv9/unix
SunOS Release 5.11  64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
os-io Hostname: t1000


t1000 console login:

Booting a SPARC Based System Interactively

Booting a system interactively is useful if you need to specify an alternate kernel or the /etc/system file during the boot process. Use the following procedure to boot a system interactively.

How to Boot a System Interactively

To specify an alternate /etc/system file when booting a SPARC based system that has only one boot environment, you can boot the system interactively by using the boot -a command. Alternatively, you can resolve a problem with the /etc/system file by creating and booting an alternative boot environment. See Booting From a ZFS Boot Environment on SPARC Platforms.

  1. Make backup copies of the /etc/system and boot/solaris/filelist.ramdisk files. For example:
    # cp /etc/system /etc/system.bak
    # cp /boot/solaris/filelist.ramdisk /boot/solaris/filelist.ramdisk.orig
  2. Add the etc/system.bak file name to the /boot/solaris/filelist.ramdisk file.
    # echo "etc/system.bak" >> /boot/solaris/filelist.ramdisk
  3. Update the boot archive.
    # bootadm update-archive -v
  4. Bring the system to the ok PROM prompt.
  5. Boot the system interactively.
    ok boot -a
  6. Respond to the system prompts as follows:
    1. Specify an alternate system file, then press Return. For example:
      Name of system file [etc/system]: /etc/system.bak
    2. Specify the root file system, then press Return.
    3. When prompted, specify the physical name of the root device, then press Return.

    Pressing Return without providing any information accepts the system defaults.

  7. If you are not prompted by the system for information, verify that you typed the boot -a command correctly.

Example 2-4 Booting a System Interactively

In the following example, the default choices (shown in square brackets []) are accepted. For instructions and an example of booting an alternate file system by using the boot -a command, see How to Boot a System Interactively.

ok boot -a
Boot device: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a  File and args: -a
Name of system file [/etc/system]:
SunOS Release 5.11 Version ... 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Retire store [/etc/devices/retire_store] (/dev/null to bypass):
root filesystem type [zfs]:
Enter physical name of root device
[/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a]:
Hostname: system1
Mar 11 17:15:20 svc.startd[9]: svc:/system/filesystem/local:default: \
 Method "/lib/svc/method/fs-local" failed with exit status 95.
system1 console login: NIS domain name is solaris.us.oracle.com
NIS domain name is solaris.us.oracle.com

system1 console login: