Skip Navigation Links | |
Exit Print View | |
Booting and Shutting Down Oracle Solaris on SPARC Platforms Oracle Solaris 11 Information Library |
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)
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)
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.
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 $
|
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.
Use this procedure to boot a SPARC based system that is currently at run level 0 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.
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 system to a single-user state is used for system maintenance, such as backing up a file system or troubleshooting other system issues.
ok boot -s
SINGLE USER MODE Root password for system maintenance (control-d to bypass): xxxxxx
# who -r
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 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.
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.
# cp /etc/system /etc/system.bak # cp /boot/solaris/filelist.ramdisk /boot/solaris/filelist.ramdisk.orig
# echo "etc/system.bak" >> /boot/solaris/filelist.ramdisk
# bootadm update-archive -v
ok boot -a
Name of system file [etc/system]: /etc/system.bak
Pressing Return without providing any information accepts the system defaults.
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: