Solaris 10 5/09 Installation Guide: Network-Based Installations

Part IV Appendixes

This part provides reference information.

Appendix A Troubleshooting (Tasks)

This chapter contains a list of specific error messages and general problems you might encounter when installing Solaris 10 5/09 software. The chapter also explains how to fix the problems. Start by using this list of sections to determine where in the installation process the problem occurred.

Note –

When you see the phrase “bootable media,” this means the Solaris installation program and JumpStart installation method.

Problems With Setting Up Network Installations

Unknown client “host_name”

Cause:

The host_name argument in the add_install_client command is not a host in the naming service.

Solution:

Add the host host_name to the naming service and run the add_install_client command again.

Error: <system name> does not exist in the NIS ethers map

Add it, and rerun the add_install_client command

Description:

When you run the add_install_client command, the command fails with the above error.

Cause:

The client you are adding to the install server does not exist in the server's /etc/ethers file.

Solution:

Add the needed information to the /etc/ethers file on the install server and run the add_install_client command again.

Become superuser or assume an equivalent role.

On the client, find the ethers address.

# ifconfig -a grep ethers
ether 8:0:20:b3:39:1d

On the install server, open the /etc/ethers file in an editor. Add the address to the list.
On the client, run add_install_client again as in this example.
# ./add_install_client bluegill sun4u

Problems With Booting a System

Booting From Media, Error Messages

le0: No carrier - transceiver cable problem

Cause:

The system is not connected to the network.

Solution:

If this is a nonnetworked system, ignore this message. If this is a networked system, ensure that the Ethernet cabling is attached securely.

The file just loaded does not appear to be executable

Cause:

The system cannot find the proper media for booting.

Solution:

Verify that the system has been set up properly to install the Solaris 10 5/09 software from the network from an install server. The following are examples of checks you can make.

If you copied the images of the Solaris DVD or the Solaris Software CDs to the install server, ensure that you specified the correct platform group for the system when you set it up.
If you are using DVD or CD media, ensure that the Solaris DVD or Solaris Software - 1 CD is mounted and accessible on the install server.

boot: cannot open <filename> (SPARC based systems only)

Cause:

This error occurs when you override the location of the boot -file by explicitly setting it.

Note –

filename is a variable for the name of the file affected.

Solution:

Follow these instructions:

Reset the boot -file in the PROM to “ “ (blank).
Ensure that the diag-switch is set to off and to true.

Can't boot from file/device

Cause:

The installation media cannot find the bootable media.

Solution:

Ensure that the following conditions are met:

The DVD-ROM or CD-ROM drive is installed properly and turned on.
Solaris DVD or the Solaris Software - 1 CD is inserted into the drive.
The disc is free of damage or dirt.

WARNING: clock gained xxx days -- CHECK AND RESET DATE! (SPARC based systems only)

Description:

This is an informational message.

Solution:

Ignore the message and continue with the installation.

Not a UFS file system (x86 based systems only)

Cause:

When the current Solaris release was installed (either through the Solaris installation program or custom JumpStart), no boot disk was selected. You now must edit the BIOS to boot the system.

Solution:

Select the BIOS to boot. See your BIOS documentation for instructions.

Booting From Media, General Problems

The system does not boot.

Description:

When initially setting up a custom JumpStart server, you might encounter boot problems that do not return an error message. To verify information about the system and how the system is booting, run the boot command with the -v option. When you use the -v option, the boot command displays verbose debugging information about the screen.

Note –

If this flag is not given, the messages are still printed, but the output is directed to the system log file. For more information, see syslogd(1M).

Solution:

For SPARC based systems, at the ok prompt, type the following command.

ok boot net -v - install

Boot from DVD media fails on systems with Toshiba SD-M 1401 DVD-ROM

Description:

If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the system cannot boot from the Solaris DVD.

Solution:

Apply patch 111649–03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. The patch 111649–03 is available at sunsolve.sun.com.

The system hangs or panics when nonmemory PC cards are inserted. (x86 based systems only)

Cause:

Nonmemory PC cards cannot use the same memory resources that are used by other devices.

Solution:

To correct this problem, see the instructions for your PC card and check for the address range.

The system hangs before displaying the system prompt. (x86 based systems only)

Solution:

You have hardware that is not supported. Check your hardware manufacturer's documentation.

Booting From the Network, Error Messages

WARNING: getfile: RPC failed: error 5 (RPC Timed out).

Description:

This error occurs when you have two or more servers on a network responding to an install client's boot request. The install client connects to the wrong boot server, and the installation hangs. The following specific reasons might cause this error to occur:

Cause:

Reason 1:/etc/bootparams files might exist on different servers with an entry for this install client.

Solution:

Reason 1: Ensure that servers on the network do not have multiple /etc/bootparams entries for the install client. If they do have multiple entries, remove duplicate client entries in the /etc/bootparams file on all install servers and boot servers except the one you want the install client to use.

Cause:

Reason 2: Multiple /tftpboot or /rplboot directory entries might exist for this install client.

Solution:

Reason 2: Ensure that servers on the network do not have multiple /tftpboot or /rplboot directory entries for the install client. If they do have multiple entries, remove duplicate client entries from the /tftpboot or /rplboot directories on all install servers and boot servers except the one you want the install client to use.

Cause:

Reason 3: An install client entry might exist in the /etc/bootparams file on a server and an entry in another /etc/bootparams file that enables all systems to access the profile server. Such an entry resembles the following:

* install_config=profile_server:path

A line that resembles the previous entry in the NIS or NIS+ bootparams table can also cause this error.

Solution:

Reason 3: If a wildcard entry is in the naming service bootparams map or table (for example, * install_config=), delete it and add it to the /etc/bootparams file on the boot server.

No network boot server. Unable to install the system. See installation instructions. (SPARC based systems only)

Cause:

This error occurs on a system that you are attempting to install from the network. The system is not set up correctly.

Solution:

Ensure that you correctly set up the system to install from the network. See Adding Systems to Be Installed From the Network With a CD Image.

prom_panic: Could not mount file system (SPARC based systems only)

Cause:

This error occurs when you are installing Solaris from a network, but the boot software cannot locate the following:

Solaris DVD, either the DVD or a copy of the DVD image on the install server
Solaris Software - 1 CD image, either the Solaris Software - 1 CD or a copy of the CD image on the install server

Solution:

Ensure that the installation software is mounted and shared.

If you are installing Solaris from the install server's DVD-ROM or CD-ROM drive, ensure that the Solaris DVD or Solaris Software - 1 CD is inserted in the CD-ROM drive, is mounted, and is shared in the /etc/dfs/dfstab file.
If installing from a copy of the Solaris DVD image or Solaris Software - 1 CD image on the install server's disk, ensure that the directory path to the copy is shared in the /etc/dfs/dfstab file.

Timeout waiting for ARP/RARP packet...(SPARC based systems only)

Cause:

Reason 1: The client is trying to boot from the network, but it cannot find a system that knows about the client.

Solution:

Reason 1: Verify the system's host name is in the NIS or NIS+ naming service. Also, verify the bootparams search order in the boot server's /etc/nsswitch.conf file.

For example, the following line in the /etc/nsswitch.conf file indicates that JumpStart or the Solaris installation program first looks in the NIS maps for bootparams information. If the program does not find any information, the installer looks in the boot server's /etc/bootparams file.

bootparams: nis files

Cause:

Reason 2: The client's Ethernet address is not correct.

Solution:

Reason 2: Verify that the client's Ethernet address in the install server's /etc/ethers file is correct.

Cause:

Reason 3: In a custom JumpStart installation, the add_install_client command specifies the platform group that uses a specified server as an install server. If the wrong architecture value is used when using the add_install_client, this problem occurs. For example, the machine you want to install is a sun4u, but you used i86pc instead.

Solution:

Reason 3: Rerun add_install_client with the correct architecture value.

ip: joining multicasts failed on tr0 - will use link layer broadcasts for multicast (x86 based systems only)

Cause:

This error message is displayed when you boot a system with a token ring card. Ethernet multicast and token ring multicast do not work the same way. The driver returns this error message because an invalid multicast address was provided to it.

Solution:

Ignore this error message. If multicast does not work, IP uses layer broadcasts instead and does not cause the installation to fail.

Requesting Internet address for Ethernet_Address (x86 based systems only)

Cause:

The client is trying to boot from the network, but it cannot find a system that knows about the client.

Solution:

Verify the system's host name is listed in the naming service. If the system's host name is listed in the NIS or NIS+ naming service, and the system continues to print this error message, try rebooting.

RPC: Timed out No bootparams (whoami) server responding; still trying... (x86 based systems only)

Cause:

The client is trying to boot from the network, but it cannot find a system with an entry in the /etc/bootparams file on the install server.

Solution:

Use add_install_client on the install server. Using this command adds the proper entry in the /etc/bootparams file, enabling the client to boot from the network.

Still trying to find a RPL server... (x86 based systems only)

Cause:

The system is trying to boot from the network, but the server is not set up to boot this system.

Solution:

On the install server, execute add_install_client for the system to be installed. The add_install_client command sets up an /rplboot directory, which contains the necessary network boot program.

CLIENT MAC ADDR: FF FF FF FF FF FF (network installations with DHCP only)

Cause:

The DHCP server is not configured correctly. This error might occur if the options or macros are not correctly defined in the DHCP Manager software.

Solution:

In the DHCP Manager software, verify that the options and macros are correctly defined. Confirm that the Router option is defined, and that the value of the Router option is correct for the subnet you are using for the network installation.

Booting From the Network, General Problems

The system boots from the network, but from a system other than the specified install server.

Cause:

An /etc/bootparams and perhaps an /etc/ethers entry exist on another system for the client.

Solution:

On the name server, update the /etc/bootparams entry for the system that is being installed. The entry should conform to the following syntax:

install_system root=boot_server:path install=install_server:path

Also, ensure that only one bootparams entry is on the subnet for the install client.

The system does not boot from the network (network installations with DHCP only).

Cause:

The DHCP server is not configured correctly. This error might occur if the system is not configured as an installation client on the DHCP server.

Solution:

In the DHCP manager software, verify that installation options and macros are defined for the client system. For more information, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

Initial Installation of the Solaris OS

Initial installation fails

Solution:

If the Solaris installation fails, you must restart the installation. To restart the installation, boot the system from the Solaris DVD, the Solaris Software - 1 CD, or from the network.

You cannot uninstall the Solaris software after the software has been partially installed. You must restore your system from a backup or begin the Solaris installation process again.

/cdrom/sol_Solaris_10/SUNWxxxx/reloc.cpio: Broken pipe

Description:

This error message is informational and does not affect the installation. The condition occurs when a write on a pipe does not have a reading process.

Solution:

Ignore the message and continue with the installation.

WARNING: CHANGE DEFAULT BOOT DEVICE (x86 based systems only)

Cause:

This is an informational message. The default boot device set in the system's BIOS might be set to a device that requires you to use the Solaris Device Configuration Assistant to boot the system.

Solution:

Continue with the installation and, if necessary, change the system's default boot device specified in the BIOS after you install the Solaris software to a device that does not require the Solaris Device Configuration Assistant.

x86 only –

If you are using the locale keyword to test a custom JumpStart profile for an initial installation, the pfinstall -D command fails to test the profile. For a workaround, see the error message “could not select locale,” in the section, Upgrading the Solaris OS.

x86: To Check IDE Disk for Bad Blocks

IDE disk drives do not automatically map out bad blocks like other drives supported by Solaris software. Before installing Solaris on an IDE disk, you might want to perform a surface analysis on the disk. To perform surface analysis on an IDE disk, follow this procedure.

Become superuser or assume an equivalent role.

Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

Boot to the installation media.

When you are prompted to select an installation type, select option 6, Single user shell.

Start the format(1M) program.
# format

Specify the IDE disk drive on which you want to perform a surface analysis.
# cxdy
cx

Is the controller number

dy

Is the device number

Determine if you have an fdisk partition.
- If a Solaris fdisk partition already exists, proceed to Step 7.
- If a Solaris fdisk partition does not exist, use the fdisk command to create a Solaris partition on the disk.
  format> fdisk

To begin the surface analysis, type:
format> analyze

Determine the current settings, type:
analyze> config

(Optional) To change settings, type:
analyze> setup

To find bad blocks, type:
analyze> type_of_surface_analysis
type_of_surface_analysis

Is read, write, or compare

If format finds bad blocks, it remaps them.

To exit the analysis, type:
analyze> quit

Determine if you want to specify blocks to remap.
- If no, go to Step 13.
- If yes, type:
  format> repair

To exit the format program, type:
quit

Restart the media in multiuser mode by typing the following command.
# exit

Upgrading the Solaris OS

Upgrading, Error Messages

No upgradable disks

Cause:

A swap entry in the /etc/vfstab file is causing the upgrade to fail.

Solution:

Comment out the following lines in the /etc/vfstab file:

All swap files and slices on disks not being upgraded
Swap files that are no longer present
Any unused swap slices

usr/bin/bzcat not found

Cause:

Solaris Live Upgrade fails because of needing a patch cluster.

Solution:

A patch is needed to install Solaris Live Upgrade. Ensure that you have the most recently updated patch list by consulting http://sunsolve.sun.com. Search for the info doc 72099 on the SunSolve web site.

Upgradeable Solaris root devices were found, however, no suitable partitions to hold the Solaris install software were found. Upgrading using the Solaris Installer is not possible. It might be possible to upgrade using the Solaris Software 1 CDROM. (x86 based systems only)

Cause:

You cannot upgrade with the Solaris Software - 1 CD because you do not have enough space.

Solution:

To upgrade, you can either create a swap slice that is larger than or equal to 512 Mbytes or use another method of upgrading such as the Solaris installation program from Solaris DVD, a net installation image, or JumpStart.

ERROR: Could not select locale (x86 based systems only)

Cause:

When you test your JumpStart profile by using the pfinstall -D command, the dry run test fails under the following conditions:

The profile contains the locale keyword.
You're testing a release that contains GRUB software. Starting with the Solaris 10 1/06 release, the GRUB boot loader facilitates booting different operating systems installed on your system with the GRUB menu.

With the introduction of GRUB software, the miniroot is compressed. The software can no longer find the list of locales from the compressed miniroot. The miniroot is the smallest possible Solaris root (/) file system and is found on the Solaris installation media.

Solution:

Perform the following steps. Use the following values.

MEDIA_DIR is /cdrom/cdrom0/
MINIROOT_DIR is $MEDIA_DIR/Solaris_10/Tools/Boot
MINIROOT_ARCHIVE is $MEDIA_DIR/boot/x86.miniroot
TEMP_FILE_NAME is /tmp/test

Become superuser or assume an equivalent role.

Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

Uncompress the miniroot archive.

# /usr/bin/gzcat $MINIROOT_ARCHIVE > $TEMP_FILE_NAME

Create the miniroot device by using the lofiadm command.

# LOFI_DEVICE=/usr/sbin/lofiadm -a $TEMP_FILE_NAME
# echo $LOFI_DEVICE
/dev/lofi/1

Mount the miniroot with the lofi command under the Miniroot directory.
# /usr/sbin/mount -F ufs $LOFI_DEVICE $MINIROOT_DIR

Test the profile.

# /usr/sbin/install.d/pfinstall -D -c $MEDIA_DIR $path-to-jumpstart_profile

After the testing is completed, unmount the lofi device.
# umount $LOFI_DEVICE
Delete the lofi device.
# lofiadm -d $TEMP_FILE_NAME

Upgrading, General Problems

The upgrade option is not presented even though there is a version of Solaris software that's upgradable on the system.

Cause:

Reason 1: The /var/sadm directory is a symlink or it is mounted from another file system.

Solution:

Reason 1: Move the /var/sadm directory into the root (/) or /var file system.

Cause:

Reason 2: The /var/sadm/softinfo/INST_RELEASE file is missing.

Solution:

Reason 2: Create a new INST_RELEASE file by using the following template:

OS=Solaris
VERSION=x 
REV=0

x: Is the version of Solaris software on the system

Cause:

Reason 3: SUNWusr is missing from /var/sadm/softinfo.

Solution:

Solution 3: You need to do an initial installation. The Solaris software is not upgradable.

Couldn't shut down or initialize the md driver

Solution:

Follow these instructions:

If the file system is not a RAID-1 volume, comment out in the vsftab file.
If the file system is a RAID-1 volume, break the mirror and reinstall. For information about unmirroring, see Removing RAID-1 Volumes (Unmirroring) in Solaris Volume Manager Administration Guide.

The upgrade fails because the Solaris installation program cannot mount a file system.

Cause:

During an upgrade, the script attempts to mount all the file systems that are listed in the system's /etc/vfstab file on the root (/) file system that is being upgraded. If the installation script cannot mount a file system, it fails and exits.

Solution:

Ensure that all file systems in the system's /etc/vfstab file can be mounted. Comment out any file systems in the /etc/vfstab file that cannot be mounted or that might cause the problem so that the Solaris installation program does not try to mount them during the upgrade. Any system-based file systems that contain software to be upgraded (for example, /usr) cannot be commented out.

The upgrade fails

Description:

The system does not have enough space for the upgrade.

Cause:

Check Upgrading With Disk Space Reallocation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade for the space problem and see if you can fix it without using auto-layout to reallocate space.

Problems upgrading RAID–1 volume root (/) file systems

Solution:

If you have problems upgrading when using Solaris Volume Manager RAID-1 volumes that are the root (/) file system, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.

To Continue Upgrading After a Failed Upgrade

The upgrade fails and the system cannot be soft-booted. The failure is for reasons beyond your control, such as a power failure or a network connection failure.

Reboot the system from the Solaris DVD, the Solaris Software - 1 CD, or from the network.

Choose the upgrade option for installation.

The Solaris installation program determines if the system has been partially upgraded and continues the upgrade.

x86: Problems With Solaris Live Upgrade When You Use GRUB

The following errors can occur when you use Solaris Live Upgrade and the GRUB boot loader on an x86 based system.

ERROR: The media product tools installation directory path-to-installation-directory does not exist.

ERROR: The media dirctory does not contain an operating system upgrade image.

Description:

The error messages are seen when using the luupgrade command to upgrade a new boot environment.

Cause:

An older version of Solaris Live Upgrade is being used. The Solaris Live Upgrade packages you have installed on your system are incompatible with the media and the release on that media.

Solution:

Always use the Solaris Live Upgrade packages from the release you are upgrading to.

Example:

In the following example, the error message indicates that the Solaris Live Upgrade packages on the system are not the same version as on the media.

# luupgrade -u -n s10u1 -s /mnt
	Validating the contents of the media </mnt>.
	The media is a standard Solaris media.
	ERROR: The media product tools installation directory 
</mnt/Solaris_10/Tools/Boot/usr/sbin/install.d/install_config> does 
not exist.
	ERROR: The media </mnt> does not contain an operating system upgrade 
image.

ERROR: Cannot find or is not executable: </sbin/biosdev>.

ERROR: One or more patches required by Solaris Live Upgrade has not been installed.

Cause:

One or more patches required by Solaris Live Upgrade are not installed on your system. Beware that this error message does not catch all missing patches.

Solution:

Before using Solaris Live Upgrade, always install all the required patches. Ensure that you have the most recently updated patch list by consulting http://sunsolve.sun.com. Search for the info doc 72099 on the SunSolve web site.

ERROR: Device mapping command </sbin/biosdev> failed. Please reboot and try again.

Cause:

Reason 1: Solaris Live Upgrade is unable to map devices because of previous administrative tasks.

Solution:

Reason 1: Reboot the system and try Solaris Live Upgrade again

Cause:

Reason 2: If you reboot your system and get the same error message, you have two or more identical disks. The device mapping command is unable to distinguish between them.

Solution:

Reason 2: Create a new dummy fdisk partition on one of the disks. See the fdisk(1M) man page. Then reboot the system.

Cannot delete the boot environment that contains the GRUB menu

Cause:

Solaris Live Upgrade imposes the restriction that a boot environment cannot be deleted if the boot environment contains the GRUB menu.

Solution:

Use lumake(1M) or luupgrade(1M) commands to reuse that boot environment.

The file system containing the GRUB menu was accidentally remade. However, the disk has the same slices as before. For example, the disk was not re-sliced.

Cause:

The file system that contains the GRUB menu is critical to keeping the system bootable. Solaris Live Upgrade commands do not destroy the GRUB menu. But, if you accidentally remake or otherwise destroy the file system containing the GRUB menu with a command other than a Solaris Live Upgrade command, the recovery software attempts to reinstall the GRUB menu. The recovery software puts the GRUB menu back in the same file system at the next reboot. For example, you might have used the newfs or mkfs commands on the file system and accidentally destroyed the GRUB menu. To restore the GRUB menu correctly, the slice must adhere to the following conditions:

Contain a mountable file system
Remain a part of the same Solaris Live Upgrade boot environment where the slice resided previously

Before rebooting the system, make any necessary corrective actions on the slice.

Solution:

Reboot the system. A backup copy of the GRUB menu is automatically installed.

The GRUB menu's menu.lst file was accidentally deleted.

Solution:

Reboot the system. A backup copy of the GRUB menu is automatically installed.

System Panics When Upgrading With Solaris Live Upgrade Running Veritas VxVm

When you use Solaris Live Upgrade while upgrading and running Veritas VxVM, the system panics on reboot unless you upgrade by using the following procedure. The problem occurs if packages do not conform to Solaris advanced packaging guidelines.

Become superuser or assume an equivalent role.

Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

Create an inactive boot environment. See Creating a New Boot Environment in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Before upgrading the inactive boot environment, you must disable the existing Veritas software on the inactive boot environment.
1. Mount the inactive boot environment.
  # lumount inactive_boot_environment_name mount_point
  For example:
  # lumount solaris8 /mnt
2. Change to the directory that contains the vfstab, for example:
  # cd /mnt/etc
3. Make a copy of the inactive boot environment's vfstab file, for example:
  # cp vfstab vfstab.501
4. In the copied vfstab, comment out all Veritas file system entries, for example:
  # sed '/vx\/dsk/s/^/#/g' < vfstab > vfstab.novxfs
  The first character of each line is changed to #, which makes the line a comment line. Note that this comment line is different than the system file-comment lines.
5. Copy the changed vfstab file, for example:
  # cp vfstab.novxfs vfstab
6. Change directories to the inactive boot environment's system file, for example:
  # cd /mnt/etc
7. Make a copy of the inactive boot environment's system file, for example:
  # cp system system.501
8. Comment out all “forceload:” entries that include drv/vx.
  # sed '/forceload: drv\/vx/s/^/*/' <system> system.novxfs
  The first character of each line is changed to *, which makes the line a command line. Note that this comment line is different than the vfstab file comment lines.
9. Create the Veritas install-db file, for example:
  # touch vx/reconfig.d/state.d/install-db
10. Unmount the inactive boot environment.
  # luumount inactive_boot_environment_name

Upgrade the inactive boot environment. See Chapter 5, Upgrading With Solaris Live Upgrade (Tasks), in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Activate the inactive boot environment. See Activating a Boot Environment in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Shut down the system.
# init 0

Boot the inactive boot environment in single-user mode:
OK boot -s
Several messages and error messages that contain “vxvm” or “VXVM” are displayed that can be ignored. The inactive boot environment becomes active.

Upgrade Veritas.
1. Remove the Veritas VRTSvmsa package from the system, for example:
  # pkgrm VRTSvmsa
2. Change directories to the Veritas packages.
  # cd /location_of_Veritas_software
3. Add the latest Veritas packages to the system:
  # pkgadd -d `pwd` VRTSvxvm VRTSvmsa VRTSvmdoc VRTSvmman VRTSvmdev

Restore the original vfstab and system files:

# cp /etc/vfstab.original /etc/vfstab
# cp /etc/system.original /etc/system

Reboot the system.
# init 6

x86: Service Partition Not Created by Default on Systems With No Existing Service Partition

If you install the current Solaris release on a system that does not currently include a service or diagnostic partition, the installation program might not create a service partition by default. If you want to include a service partition on the same disk as the Solaris partition, you must re-create the service partition before you install the current Solaris release.

If you installed the Solaris 8 2/02 OS on a system with a service partition, the installation program might not have preserved the service partition. If you did not manually edit the fdisk boot partition layout to preserve the service partition, the installation program deleted the service partition during the installation.

Note –

If you did not specifically preserve the service partition when you installed the Solaris 8 2/02 OS, you might not be able to re-create the service partition and upgrade to the current Solaris release.

If you want to include a service partition on the disk that contains the Solaris partition, choose one of the following workarounds.

To Install Software From a Network Installation Image or From the Solaris DVD

To install the software from a net installation image or from the Solaris DVD over the network, follow these steps.

Delete the contents of the disk.

Before you install, create the service partition by using the diagnostics CD for your system.

For information about how to create the service partition, see your hardware documentation.

Boot the system from the network.

The Customize fdisk Partitions screen is displayed.

To load the default boot disk partition layout, click Default.

The installation program preserves the service partition and creates the Solaris partition.

To Install From the Solaris Software - 1 CD or From a Network Installation Image

To use the Solaris installation program to install from the Solaris Software - 1 CD or from a network installation image on a boot server, follow these steps.

Delete the contents of the disk.

Before you install, create the service partition by using the diagnostics CD for your system.

For information about how to create the service partition, see your hardware documentation.

The installation program prompts you to choose a method for creating the Solaris partition.

Boot the system.

Select the Use rest of disk for Solaris partition option.

The installation program preserves the service partition and creates the Solaris partition.

Complete the installation.

Appendix B Installing or Upgrading Remotely (Tasks)

This appendix describes how to use the Solaris installation program to install or upgrade to the Solaris OS on a machine or domain that does not have a directly attached DVD-ROM or CD-ROM drive.

Note –

If you are installing or upgrading the Solaris OS on a multi–domain server, refer to the system controller or system service processor documentation before beginning the installation process.

SPARC: Using the Solaris Installation Program to Install or Upgrade From a Remote DVD-ROM or CD-ROM

If you want to install the Solaris OS on a machine or domain that does not have a directly attached DVD-ROM or CD-ROM drive, you can use a drive that is attached to another machine. Both machines must be connected to the same subnet. Use the following instructions to complete the installation.

SPARC: To Install or Upgrade From a Remote DVD-ROM and CD-ROM

Note –

This procedure assumes that the system is running the Volume Manager. If you are not using the Volume Manager to manage media, refer to System Administration Guide: Devices and File Systems.

In the following procedure, the remote system with the DVD-ROM or CD-ROM is identified as remote system. The system that is the client to be installed is identified as client system.

Identify a system that is running the Solaris OS and has a DVD-ROM or CD-ROM drive.

On the remote system with the DVD-ROM or CD-ROM drive, insert the Solaris DVD or the Solaris Software for SPARC Platforms - 1 CD in the drive.

The Volume Manager mounts the disc.

On the remote system, change directories to the DVD or CD where the add_install_client command is located.
- For DVD media, type:
  remote system# cd /cdrom/cdrom0/Solaris_10/Tools
- For CD media, type:
  remote system# cd /cdrom/cdrom0

On the remote system, add the system that you want to install as a client.
- For DVD media, type:
  remote system# ./add_install_client \ client_system_name arch
- For CD media, type:
  remote system# ./add_install_client -s remote_system_name: \ /cdrom/cdrom0 client_system_name arch
remote_system_name

The name of the system with the DVD-ROM or CD-ROM drive

client_system_name

The name of the machine you want to install

arch

The platform group of the machine you want to install, for example sun4u. On the system that you want to install, find the platform group by using the uname -m command.

Boot the client system that you want to install.
client system: ok boot net
The installation begins.

Follow the instructions to type system configuration information if needed.
- If you are using DVD media, follow the instructions on the screen to complete the installation. You are finished.
- If you are using CD media, the machine reboots and the Solaris installation program begins. After the Welcome panel, the Specify Media panel appears with Network File System selected. Proceed to Step 7.

On the Specify Media panel, click Next.

The Specify Network File System Path panel appears and the text field contains the installation path.

client_system_ip_address:/cdrom/cdrom0

On the remote system where the DVD or CD is mounted, change directories to root.
remote system# cd /

On the remote system, check for the path to the slice that has been shared.
remote system# share

On the remote system, unshare the Solaris DVD or Solaris Software for SPARC Platforms - 1 CD by using the path that is found in Step 9. If paths lead to two slices, unshare both slices.
remote system# unshare absolute_path
absolute_path

Is the absolute path shown in the share command

In this example, slice 0 and slice 1 are unshared.
remote system# unshare /cdrom/cdrom0 remote system# unshare /cdrom/cdrom0

On the client system that you are installing, continue the Solaris installation by clicking Next.

If the Solaris installation program prompts you to insert the Solaris Software - 2 CD, repeat Step 9 through Step 11 to unshare the Solaris Software - 1 CD and to export and install the Solaris Software - 2 CD.

If the Solaris installation program prompts you to insert additional Solaris Software CDs, repeat Step 9 through Step 11 to unshare the Solaris Software CDs and to export and install the additional CDs.

If the Solaris installation program prompts you to insert the first Solaris Languages CD, repeat Step 9 through Step 11 to unshare the Solaris Software CDs and to export and install each Solaris Languages CD.

When you export a Solaris Languages CD, an installer window appears on the machine where the CD-ROM is mounted. Ignore the installer window while you install the Solaris Languages CD. After you complete the installation of the Solaris Languages CDs, close the installer window.