Chapter 14 IA: Booting a System (Tasks)

This chapter describes the procedures for booting an IA based system.

For information on the procedures associated with booting an IA system, see IA: Booting a System (Task Map).

For overview information about the boot process, see Chapter 10, Shutting Down and Booting a System (Overview).

For step-by-step instructions on booting a SPARC based system, see Chapter 13, SPARC: Booting a System (Tasks).

IA: Booting a System (Task Map)

IA: Booting the Solaris Device Configuration Assistant

The Device Configuration Assistant (Solaris Intel Platform Edition) is a program that enables you to perform various hardware configuration and booting tasks. You can access the Solaris Device Configuration Assistant from either of the following:

• Solaris boot diskette

• Solaris Installation CD

In the procedures in this chapter, you might be requested to insert the Solaris Device Configuration Assistant boot diskette to boot the Configuration Assistant. If your system's BIOS supports booting from the CD, you can, instead, insert the Solaris installation CD to boot the Configuration Assistant.

IA: How to Boot the Solaris Device Configuration Assistant

1. Insert the Solaris Device Configuration Boot Diskette or the Solaris Installation CD in the appropriate drive.

2. If the system displays the Type any key to continue 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.

   The first menu of the Configuration Assistant is displayed after a few minutes.

IA: Booting a System

The following procedures use the reset button to restart the system. If your system does not have a reset button, use the power switch to restart the system. You might be able to press the Ctrl-Alt-Del keys to interrupt system operation, depending upon the state of the system.

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

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

1. If the system displays the Type any key to continue 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.

   The Current Boot Parameters menu is displayed after a few minutes.

2. Type b to boot the system to run level 3. Press Enter.

   If you do not make a selection within five seconds, the system is automatically booted to run level 3.

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—Booting a System to Run Level 3 (Multiuser Level)

Type any key to continue
           .
           .
           .
                     <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: 
Type    b [file-name] [boot-flags] <ENTER>      to boot with options
or      i <ENTER>                               to enter boot interpreter
or      <ENTER>                                 to boot with defaults

                  <<< timeout in 5 seconds >>>

Select (b)oot or (i)nterpreter: b
             .
             .
             .
venus console login:

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

Use this procedure to boot a system (that is currently at run level 0) to run level S.

1. If the system displays the Type any key to continue 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.

   The Current Boot Parameters menu is displayed after a few minutes.

2. Type b -s to boot the system to run level S. Press Enter.

   If you do not make a selection within five seconds, the system is automatically booted to run level 3.

3. Type the superuser password, if prompted.

4. Verify that the system is at run level S by using the who -r command.

   # who -r . run-level S Jul 19 14:37 S 0 3

5. Perform the maintenance task that required the run level change to S.

6. Press Control-D to bring the system back to run level 3.

IA: Example—Booting a System to Run Level S (Single-User Level)

Type any key to continue
            .
            .
            .
 
                     <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: 
Type    b [file-name] [boot-flags] <ENTER>      to boot with options
or      i <ENTER>                               to enter boot interpreter
or      <ENTER>                                 to boot with defaults
 
 
                     <<< timeout in 5 seconds >>>

Select (b)oot or (i)nterpreter: b -s
              .
              .
              .
INIT: SINGLE USER MODE

Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance):  xxx
Entering System Maintenance Mode
              .
              .
              .
# who -r
   .       run-level S  Jul 19 14:37     S      0  3
(Perform some maintenance task)
# Press Control-D

IA: How to Boot a System Interactively

Use this procedure to boot a system and you need to specify an alternate kernel or /etc/system file.

1. If the system displays the Type any key to continue 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.

   The Primary Boot Subsystem menu is displayed after a few minutes.

2. Select the Solaris partition (if not marked as active) from the list and press Enter.

   If you do not make a selection within five seconds, the active boot partition is selected automatically.

   The Current Boot Parameters menu is displayed after a few minutes.

3. Type b -a to boot the system interactively. Press Enter.

   If you do not make a selection within five seconds, the system is automatically booted to run level 3.

4. Answer the system prompts as described in the following table.

   System Prompt	Action
   Enter default directory for modules: [/platform/i86pc/kernel /kernel /usr/kernel]:	Provide an alternate path for the modules directory and press Enter. Or, press Enter to use the default modules directory path.
   Name of system file [etc/system]:	Provide the name of an alternate system file and press Enter. Or, press Enter to use the default /etc/system file. Type/dev/null if your /etc/system file has been damaged.
   root filesystem type [ufs]:	Press Enter to use the default root (/) file system. Type: UFS for local disk booting, or NFS for network booting.
   Enter physical name of root device [physical_device_name]:	Provide an alternate device name and press Enter. Or, press Enter to use the default physical name of the root device bootpath.

IA: Example—Booting a System Interactively

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

Type any key to continue
            .
            .
            .
 
                     <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: 
Type    b [file-name] [boot-flags] <ENTER>      to boot with options
or      i  <ENTER>                              to enter boot interpreter
or      <ENTER>                                 to boot with defaults
 
 
                     <<< timeout in 5 seconds >>>>
Select (b)oot or (i)nterpreter: b -a
Enter default directory for modules [/platform/i86pc/kernel /kernel 
/usr/kernel]: Press Enter
Name of system file [etc/system]:Press Enter
SunOS Release 5.9 Version Generic 32-bit
Copyright (c) 1983-2002 by Sun Microsystems, Inc.
root filesystem type [ufs]: Press Enter
Enter physical name of root device
[/pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a]: Press Enter
configuring IPv4 interfaces: dnet0.
Hostname: venus
(fsck messages)
The system is coming up.  Please wait
(More messages)
venus console login:

IA: How to Boot a System From the Network

Any system can boot from the network if there is a boot server available. You might want to boot a standalone system from the network temporarily if the system cannot boot from the local disk.

If the system is capable of a PXE network boot, you might want to boot the system directly from the network without using either the Configuration Assistant boot diskette or the installation CD.

The menu, Set Network Configuration Strategy, on the Configuration Assistant's Boot Tasks Menu, enables you to select the appropriate boot strategy.

1. Determine whether you want to boot from the network by using the RARP/bootparams method or the DHCP method.

   There are two network configuration strategies to choose from, RARP (Reverse Address Resolution Protocol) or DHCP (Dynamic Host Configuration Protocol). The default network boot strategy is set to RARP. You can use either strategy depending on whether a RARP boot server or a DHCP boot server is available on your network.

   The PXE network boot is available only with DHCP.

2. Insert the Configuration Assistant boot diskette or the installation CD that you wish to boot from.

   Or, use the system or network adapter BIOS configuration program to enable the PXE network boot.

3. If the system displays the Type any key to continue 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.

   The Solaris Device Configuration Assistant screen is displayed.

4. Press the F2 key (F2_Continue) to scan for devices.

   Device identification is performed and the Identified Devices screen is displayed.

5. Press the F2 key (F2_Continue) to load drivers.

   Bootable drivers are loaded.

   The Boot Solaris menu is displayed.

6. Press the F4 key (F4_Boot Tasks).

7. Select Set Network Configuration Strategy and press the F2 key (F2_Continue).

8. Select either RARP or DHCP and press the F2 key (F2_Continue).

   A screen that confirms your new network boot strategy appears.

   Your network boot strategy selection is saved as the default network boot method for the next time this diskette is used for booting.

9. Press F3_Back to return to the Boot Solaris menu.

10. Select NET as the boot device. Then, press F2_Continue to boot the network device.

    The Solaris boot option screen is displayed.

IA: How to Stop a System for Recovery Purposes

If possible, stop the system by using one of the following commands:

• If the system is running, become superuser and type init 0 to stop the system. After the Type any key to continue prompt appears, press any key to reboot the system.

• If the system is running, become superuser and type init 6 to reboot the system.

If the system doesn't respond to any input from the mouse or keyboard, press the reset key, if it exists, to reboot the system. Or, you can use the power switch to reboot the system.

IA: How to Boot a System for Recovery Purposes

Follow these steps to boot the system to repair a critical system resource. The example shows you how to boot from a Solaris Installation CD or from the network, mount the root (/) file system on the disk, and repair the /etc/passwd file.

Substitute the device name of the file system to be repaired for the devicename variable in the following procedure. If you need help with identifying a system's device names, refer to Chapter 29, Accessing Devices (Overview).

1. Stop the system first by using the system stop key sequence.

   Use the stop sequence for your system if you don't know the root password or if you can't log in to the system. For more information, see IA: How to Stop a System for Recovery Purposes.

2. Boot from the Solaris installation CD (or from the network) to single-user mode.

   1. Insert the Configuration Assistant boot diskette or the installation CD that you wish to boot from.

   2. If the system displays the Type any key to continue 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.

      The Solaris Device Configuration Assistant screen is displayed.

   3. Press the F2 key (F2_Continue).

      Device identification is performed and the Identified Devices screen is displayed.

   4. Press the F2 key (F2_Continue).

      Bootable drivers are loaded.

      The Boot Solaris menu is displayed.

   5. Select the CD-ROM drive or network device. Then press the F2 key (F2_Continue).

      The Current Boot Parameters menu is displayed.

   6. Type b -s at the prompt. Press Enter.

      After a few minutes, the single-user mode # prompt is displayed.

3. Mount the root (/) file system that contains the invalid passwd file.

   # mount /dev/dsk/devicename /a

4. Change to the newly mounted etc directory.

   # cd /a/etc

5. Make the necessary change to the file by using an editor.

   # vi filename

6. Change to the root (/) directory.

   # cd /

7. Unmount the /a directory.

   # umount /a

8. Reboot the system.

   # init 6

9. 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:

IA: Example—Booting a System for Recovery Purposes

The following example shows how to repair the /etc/passwd file after booting from a local CD-ROM.

Type any key to continue

SunOS Secondary Boot version 3.00


Solaris Intel Platform Edition Booting System

Running Configuration Assistant...
Autobooting from Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a

If the system hardware has changed, or to boot from a different
device, interrupt the autoboot process by pressing ESC.

Press ESCape to interrupt autoboot in 5 seconds.
      .
      .
      .
Boot Solaris

Select one of the identified devices to boot the Solaris kernel and
choose Continue.

To perform optional features, such as modifying the autoboot and property
settings, choose Boot Tasks.

An asterisk (*) indicates the current default boot device.

> To make a selection use the arrow keys, and press Enter to mark it [X].

[ ]  NET : DEC 21142/21143 Fast Ethernet
on Board PCI at Dev 3                                                
[ ]  DISK: (*) Target 0, QUANTUM  FIREBALL1280A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 1:ST5660A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 0:Maxtor 9 0680D4
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[X]  CD  : Target 1:TOSHIBA  CD-ROM XM-5602B  1546
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1

F2_Continue   F3_Back   F4_Boot Tasks   F6_Help
      .
      .
      .
               <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: kernel/unix -r

Select the type of installation you want to perform:

1 Solaris Interactive
2 Custom JumpStart
3 Solaris Web Start
 
Enter the number of your choice followed by <ENTER> the key.

If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.

Select type of installation:  b -s
      .
      .
      .
# mount /dev/dsk/c0t0d0s0 /a
      .
      .
      .
# cd /a/etc
# vi passwd
(Remove invalid entry)
# cd /
# umount /a
# init 6

IA: Example—Booting a System if You Forgot Root Password

The following example shows how to recover when you forget the root password by booting from the network. This example assumes that the boot server is already available. Be sure to apply a new root password after the system has rebooted.

Type any key to continue

SunOS Secondary Boot version 3.00


Solaris Intel Platform Edition Booting System

Running Configuration Assistant...
Autobooting from Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a

If the system hardware has changed, or to boot from a different
device, interrupt the autoboot process by pressing ESC.

Press ESCape to interrupt autoboot in 5 seconds.
      .
      .
      .
Boot Solaris

Select one of the identified devices to boot the Solaris kernel and
choose Continue.

To perform optional features, such as modifying the autoboot and property
settings, choose Boot Tasks.

An asterisk (*) indicates the current default boot device.

> To make a selection use the arrow keys, and press Enter to mark it [X].

[X]  NET : DEC 21142/21143 Fast Ethernet
on Board PCI at Dev 3                                                
[ ]  DISK: (*) Target 0, QUANTUM  FIREBALL1280A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 1:ST5660A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 0:Maxtor 9 0680D4
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  CD  : Target 1:TOSHIBA  CD-ROM XM-5602B  1546
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1

F2_Continue   F3_Back   F4_Boot Tasks   F6_Help
      .
      .
      .
               <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: kernel/unix -r

Select the type of installation you want to perform:

1 Solaris Interactive
2 Custom JumpStart
3 Solaris Web Start

Enter the number of your choice followed by <ENTER> the key.

If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.

Select type of installation:  b -s
      .
      .
      .
# mount /dev/dsk/c0t0d0s0 /a
      .
      .
      .
# cd /a/etc
# vi shadow
(Remove root's encrypted password string)
# cd /
# umount /a
# init 6

IA: How to Boot a System With the Kernel Debugger (kadb)

1. If the system displays the Type any key to continue 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.

2. Type b kadb to boot the kernel debugger. Press Enter.

   If you do not make a selection within five seconds, the system is automatically booted to run level 3.

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:

4. Verify that you can access the kernel debugger by pressing F1-A.

   The kadb[0]: prompt is displayed when you enter the kernel debugger.

Example—Booting a System With the Kernel Debugger (kadb)

Type any key to continue
        .
        .
        .
            <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args:
Type    b [file-name] [boot-flags] <ENTER>     to boot with options
or      i <ENTER>                              to enter boot interpreter
or      <ENTER>                                to boot with defaults

            <<< timeout in 5 seconds >>>

Select (b)oot or (i)nterpreter: b kadb
        .
        .
        .
naboo console login: (Enter login and password)
(Press F1-A to verify that you can access the kernel debugger)

IA: Forcing a Crash Dump and Rebooting the System

Forcing a crash dump and rebooting the system is sometimes necessary for troubleshooting purposes. The savecore feature is enabled by default.

For more information on system crash dumps, see “Managing System Crash Information (Tasks)” in System Administration Guide: Advanced Administration.

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

The system must be booted with the kernel debugger option, kadb, to get to the kadb[0]: prompt and to enable you to force the crash dump.

You must be in text mode to enter the kernel debugger (kadb). So, first exit any window system.

1. Press F1–A.

   kadb[0]:

   The kadb[0]: prompt is displayed.

2. Type the following commands at the kadb[0]: prompt.

   Press <F1-a> kadb[0]: vfs_syncall/W ffffffff kadb[0]: 0>eip kadb[0]: :c kadb[0]: :c kadb[0]: :c

   After you type the first :c , the system panics, so you need to type :c again. The system panics again, so type :c a third time to force the crash dump and reboot the system.

   After the crash dump is written to disk, the system continues to reboot.

3. Verify that the system has rebooted by logging in at the console login prompt.