System Administration Guide, Volume I

Booting a SPARC System

Table 8-1 describes the boot scenarios covered in this chapter.

Table 8-1 SPARC: Boot Type Descriptions


Booting the System ...	Is Usually Done ...	See ...
To run level 3 (multiuser state with NFS resources shared)	After halting the system or performing some system hardware maintenance task. This is the default boot level where all resources are available and users can log into the system.	"Example--Booting a System to Run Level 3 (Multiuser State)"
To run level S (single-user state)	After performing some system maintenance task such as backing up a file system. At this level only local file systems are mounted and users cannot log into the system.	"SPARC: Example--Booting a System to Run Level S (Single-User State)"
Interactively	After making temporary changes to a system file or the kernel for testing purposes. This type of boot allows you to recover easily if there are problems with the system file or kernel by supplying an alternative pathname to these files when prompted. Use the default settings for the other system prompts.	"SPARC: Example--Booting a System Interactively"
From local CD-ROM or the network for recovery purposes	To repair an important system file that is preventing the system from booting successfully. This type of boot is also used for installing (or upgrading) a new release of the operating system.	"SPARC: Example--Booting a System for Recovery Purposes"
Using `kadb`	To troubleshoot system problems by running the kernel debugger.	"SPARC: Example--Booting the System Using the Kernel Debugger (`kadb`)"

If a system is turned off, turning it on starts the multiuser boot sequence. The following procedures show how to boot to different run levels from the ok PROM prompt.

Use the who -r command to verify that the system is brought to the specified run level.

See Chapter 6, Run Levels and Boot Files (Tasks) for a description of run levels.

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

Boot to run level 3 by using the boot(1M) command.
ok boot
The automatic boot procedure displays a series of startup messages, and brings the system to run level 3.

Verify the system boots to run level 3.

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

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

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

ok boot
Resetting ...
SPARCstation 10 (1 X 390Z50), Keyboard Present
ROM Rev. 2.14, 32 MB memory installed, Serial #number.
Ethernet address #number, Host ID: number.

Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0  
File and args: 
SunOS Release 5.7 Version generic [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1998, Sun Microsystems, Inc.
configuring network interfaces: le0.
Hostname: venus
The system is coming up.  Please wait.
add net default: gateway 129.152.75.248
NIS domainname is solar.com
starting rpc services: rpcbind keyserv ypbind done.
Setting netmask of le0 to 255.255.255.0
Setting default interface for multicast: add net 224.0.0.0: gateway venus
syslog service starting.
Print services started.
volume management starting.
The system is ready.

venus console login:

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

Boot the system to run level S by using the boot -s command.
ok boot -s

Enter the superuser password when the following message is displayed.

INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
 
(or give root password for system maintenance):  xxx

Use the who -r command to verify that the system is at run level S.
# who -r . run-level 3 Jun 10 15:27 3 0

To bring the system up to multiuser state after the system maintenance task is performed, press Control-d.

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

The following example displays a system booted to run level S.

ok boot -s
.
.
.
SunOS Release 5.7 Version [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1998, Sun Microsystems, Inc.
configuring network interfaces: le0.
Hostname: mars
INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): xxx
Sun Microsystems Inc.   SunOS 5.7 August 1998
# who -r
  .       run-level S  Jun 10 15:34     S      0  ?
(Perform some maintenance task)
# Press <Control-d>

SPARC: How to Boot a System Interactively

Boot the system interactively by using the boot -a command.
ok boot -a

Answer the system prompts as described in Table 8-2.

Table 8-2 SPARC: Interactive Boot Procedure Steps


If the System Displays ...	Do the Following ...
`Enter filename [kernel/unix]:`	Provide the name of another kernel to use for booting. Or, press Return to use the default kernel (/platform/`uname -m`/kernel/unix).
Name of default directory for modules [/platform/`uname -m`/kernel /kernel /usr/kernel]:	Provide an alternate path for the modules directory and press Return. Or, press Return to use the default modules directory path.
`Name of system file [/etc/system]:`	Provide the name of an alternate system file and press Return. Enter `/dev/null` as the file if your `/etc/system` file has been damaged. Or, press Return to use the default `/etc/system` file.
`root filesystem type [ufs]:`	Press Return to use the default root file system type: UFS for local disk booting or NFS for diskless clients.
`Enter physical name of root device` [`physical_device_name`]:	Provide an alternate device name and press Return. Or, press Return to use the default physical name of the root device.

If you are not prompted to answer the questions in Table 8-2, verify that you entered the boot -a command correctly.

SPARC: Example--Booting a System Interactively

In the following example, the default choices shown in square brackets [] are accepted.

ok boot -a
.
.
.
Resetting ...
Rebooting with command: -a                                           
Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0 
File and args: -a
Enter filename [kernel/unix]: Return
Enter default directory for modules
[/platform/SUNW,SPARCstation-10/kernel /platform/sun4m/kernel /kernel /usr/kernel]:
Return
SunOS Release 5.7 Version generic [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1998, Sun Microsystems, Inc.
Name of system file [etc/system]:  Return
root filesystem type [ufs]: Return
Enter physical name of root device
[/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000
/sd@3,0:a]: Return
configuring network interfaces: le0.
Hostname: earth
The system is coming up.  Please wait.
.
.
.
The system is ready.
earth console login:

SPARC: How to Boot a System for Recovery Purposes

This procedure is needed when an important file, such as /etc/passwd, has an invalid entry and is causing the boot process to fail.

If you need help identifying a system's device names, refer to Chapter 20, Accessing Devices (Overview).

Follow the instructions below depending on whether you are booting from the Solaris installation CD or the network.

If You Are Booting From ...	Then ...
Solaris installation CD	1. Insert the Solaris installation CD into the CD caddy. 2. Insert the CD caddy into the CD-ROM drive. 3. Boot from the installation CD in single-user mode: `ok` `boot cdrom -s`
The network and an installation server or remote CD drive are available	Use the following command: `ok` `boot net -s`

If You Are Booting From ...

Then ...

Solaris installation CD

1. Insert the Solaris installation CD into the CD caddy.

2. Insert the CD caddy into the CD-ROM drive.

3. Boot from the installation CD in single-user mode:

ok boot cdrom -s

The network and an installation server or remote CD drive are available

Use the following command:

ok boot net -s

Mount the file system that has the file with an invalid entry.
# mount /dev/dsk/device-name /a

Change to the newly mounted directory.
# cd /a/directory

Set the terminal type.
# TERM=sun # export TERM

Remove the invalid entry from the file using an editor.
# vi filename

Change to the root (/) directory.
# cd /

Unmount the /a directory.
# umount /a

Reboot the system.
# init 6

Verify the system boots to run level 3.

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

SPARC: Example--Booting a System for Recovery Purposes

The following example shows how to repair an important system file (in this case, /etc/passwd) after booting from a local CD-ROM.

ok boot cdrom -s
# mount /dev/dsk/c0t3d0s0 /a
# cd /a/etc
# TERM=sun
# export TERM
# vi passwd
(Remove invalid entry)
# cd /
# umount /a
# init 6

SPARC: How to Stop the System for Recovery Purposes

The specific stop key sequence depends on your keyboard type. For example, you can press Stop-a or L1-a. On terminals, press the Break key.

Type the abort key sequence for your system.

The monitor displays the ok PROM prompt.
ok

Use the sync command to synchronize the disks.
ok sync

When you see the syncing file systems... message, press the abort key sequence for your system again.

Type the appropriate boot(1M) command to start the boot process.

Verify the system is booted to the specified run level.

# who -r
 .       run-level 3  May  2 07:39     3      0  S

SPARC: Example--Stopping the System for Recovery Purposes

Press <Stop-a>
ok sync
syncing file systems...
Press <Stop-a>
ok boot

SPARC: Forcing a Crash Dump and Rebooting the System

Saving crash dumps of the operating system is sometimes necessary for troubleshooting purposes. The savecore feature and how it is set up is described in "Managing System Crash Information" in System Administration Guide, Volume II. This section only describes how to reboot the system when the savecore feature is enabled.

SPARC: How to Force a Crash Dump and Reboot the System

Type the stop key sequence for your system. The specific stop key sequence depends on your keyboard type. For example, you can press Stop-a or L1-a. On terminals, press the Break key.

The monitor displays the ok PROM prompt.

Use the sync command at the ok prompt to synchronize the disk and write the crash dump.
> n ok sync
After the crash dump is written to disk, the system will continue to reboot.

Verify the system boots to run level 3.

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

SPARC: Example--Forcing a Crash Dump and Rebooting the System

Press <Stop-a>
ok sync

SPARC: How to Boot the System Using the Kernel Debugger (`kadb`)

Type the stop key sequence for your system. The specific stop key sequence depends on your keyboard type. For example, you can press Stop-A or L1-A. On terminals, press the Break key.

The monitor displays the ok PROM prompt.

Use the sync command at the ok prompt to synchronize the disk and write the crash dump.
> n ok sync

When you see the syncing file systems... message, press the abort key sequence for your system again.

Boot the system using the kernel debugger.
ok boot kadb

Identify kadb booting messages to verify the system is booted using the kernel debugger.

Rebooting with command: kadb
Boot device: /iommu/sbus/espdma@4,800000/esp@4,8800000/sd@3,0
.
.
.

SPARC: Example--Booting the System Using the Kernel Debugger (`kadb`)

Press <Stop-a>
ok sync
syncing file systems...
Press <Stop-a>
ok boot kadb