Sun N1 System Manager 1.1 Administration Guide

Troubleshooting OS Distributions

This section describes scenarios that cause OS deployment to fail and explains how to correct failures.

Distribution Copy Failures

If the creation of an OS distribution fails with a copying files error, check the size of the ISO image and ensure that it is not corrupted. You might see output similar to the following in the job details:

bash-3.00# /opt/sun/n1gc/bin/n1sh show job 25
Job ID:   25
Date:     2005-07-20T14:28:43-0600
Type:     Create OS Distribution
Status:   Error (2005-07-20T14:29:08-0600)
Owner:    root
Errors:   1
Warnings: 0

Steps
ID     Type             Start
Completion                 Result
1      Acquire Host     2005-07-20T14:28:43-0600
2005-07-20T14:28:43-0600   Completed
2      Run Command      2005-07-20T14:28:43-0600
2005-07-20T14:28:43-0600   Completed
3      Acquire Host     2005-07-20T14:28:46-0600
2005-07-20T14:28:46-0600   Completed
4      Run Command      2005-07-20T14:28:46-0600
2005-07-20T14:29:06-0600   Error 1

Errors
Error 1:
Description: INFO   : Mounting /images/rhel-3-U4-i386-es-disc1.iso at
/mnt/loop23308
INFO   : Version is 3ES, disc is 1
INFO   : Version is 3ES, disc is 1
INFO   : type redhat ver: 3ES
cp: /var/opt/SUNWscs/data/allstart/image/3ES-bootdisk.img: Bad address
INFO   : Could not copy PXE file bootdisk.img
INFO   : umount_exit: mnt is: /mnt/loop23308
INFO   : ERROR: Could not add floppy to the Distro

Results
Result 1:
Server:   -
Status:   -1
Message:  Creating OS rh30u4-es failed.

Patching Solaris 9 Distributions

The inability to deploy Solaris 9 OS distributions to servers from a Linux management server is usually due to a problem with NFS mounts. To solve this problem, you need to apply a patch to the mini-root of the Solaris 9 OS distribution. This section provides instructions for applying the required patches. The instructions differ according to the management and patch server configuration scenarios in the following table.

Table 6–1 Task Map for Patching a Solaris 9 Distribution


Management Server	Patch Server	Task
Red Hat 3.0 u2	Solaris 9 OS on x86 platform	To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on x86 Patch Server
Red Hat 3.0 u2	Solaris 9 OS on SPARC platform	To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on SPARC Patch Server

Using a Provisionable Server to Patch OS Distributions

When you are using a patch server to perform the following tasks, you need to have root access to both the management server and the provisionable server at once. For some tasks, you need to first patch the provisionable server, then mount the management server and patch the distribution.

To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on x86 Patch Server

This procedure describes how to patch a Solaris 9 OS distribution in the N1 System Manager. The steps in this procedure need to be performed on both the patch server and the management server. Consider opening two terminal windows to complete the steps. The following steps first guide you through patching the patch server and then provide steps for patching the distribution.

Before You Begin

Create a Solaris 9 OS distribution on the management server. See To Copy an OS Distribution From CDs or a DVD or To Copy an OS Distribution From ISO Files. Type show os os-name at the command line to view the ID of the OS distribution. This number is used in place of DISTRO_ID in the instructions.
Install the Solaris 9 OS on x86 platform software on a machine that is not the management server.
Create a /patch directory on the Solaris 9 x86 patch server.
For a Solaris OS on x86 distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117172-17 and 117468-02. You can access these patches from http://sunsolve.sun.com.
For a Solaris OS on SPARC distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117171-17, 117175-02, and 113318-20. You can also access these patches from http://sunsolve.sun.com.

Steps

Patch the Solaris 9 OS on x86 patch server.
1. Log in as root.
  % su password:password
  The root prompt appears.
2. Reboot the Solaris 9 patch server to single-user mode.
  # reboot -- -s
3. In single-user mode, change to the patch directory.
  # cd /patch
4. Install the patches.
  # patchadd -M . 117172-17 # patchadd -M . 117468-02
  Tip –
  Pressing Control+D returns you to multiuser mode.

Prepare to patch the distribution on the management server.
1. Log in to the management server as root.
  % su password:password
  The root prompt appears.
2. Edit the /etc/exports file.
  # vi /etc/exports
3. Change /js *(ro,no_root_squash) to /js *(rw,no_root_squash).
4. Save and close the /etc/exports file.
5. Restart NFS.
  # /etc/init.d/nfs restart

Patch the distribution that you copied to the management server.
1. Log in to the Solaris 9 patch server as root.
  % su password:password
  The root prompt appears.
2. Mount the management server.
  # mount -o rw management-server-IP:/js/DISTRO_ID /mnt
3. Install the patches by performing one of the following actions:
  - If you are patching an x86 distribution, type the following commands:
    # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117172-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117468-02
  - If you are patching a SPARC distribution, type the following commands:
    # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117171-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117175-02 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 113318-20
    Note –
    You will receive a partial error for the first patch installation. Ignore this error.
4. Unmount the management server.
  # unmount /mnt

Restart NFS on the management server.
1. Edit the /etc/exports file.
  # vi /etc/exports
2. Change /js *(rw,no_root_squash) to /js *(ro,no_root_squash).
3. Restart NFS.
  # /etc/init.d/nfs restart
  NFS is restarted.
  
  The Solaris 9 OS on SPARC distribution is ready for deployment to target servers.

Fix the Solaris 9 OS on x86 distribution.
1. Change to /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris.
  # cd /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris
2. Re-create the bootenv.rc link.
  # ln -s ../../tmp/root/boot/solaris/bootenv.rc .
  The Solaris 9 OS on x86 distribution is ready for deployment to target servers.

Troubleshooting

If you want to patch another distribution, you might have to delete the /patch/117172-17 directory and re-create it using the unzip 117172-17.zip command. When the first distribution is patched, the patchadd command makes a change to the directory that causes problems with the next patchadd command execution.

To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on SPARC Patch Server

This procedure describes how to patch a Solaris 9 OS distribution in the N1 System Manager. The steps in this procedure need to be performed on the provisionable server and the management server. Consider opening two terminal windows to complete the steps. The following steps first guide you through patching the provisionable server and then provide steps for patching the distribution.

Before You Begin

Create a Solaris 9 OS distribution on the management server. See To Copy an OS Distribution From CDs or a DVD or To Copy an OS Distribution From ISO Files. Type show os os-name at the command line to view the ID of the OS distribution. This number is used in place of DISTRO_ID in the instructions.
Install the Solaris 9 OS on SPARC software on a machine that is not the management server. See To Load an OS Profile on a Server or a Server Group.
Create a /patch directory on the Solaris 9 SPARC patch server.
For a Solaris OS on x86 distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117172-17 and 117468-02. You can access these patches from http://sunsolve.sun.com.
For a Solaris OS on SPARC distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117171-17, 117175-02, and 113318-20. You can access these patches from http://sunsolve.sun.com.

Steps

Set up and patch the Solaris 9 OS on SPARC machine.
1. Log in to the Solaris 9 machine as root.
  % su password:password
2. Reboot the Solaris 9 machine to single-user mode.
  # reboot -- -s
3. In single-user mode, change to the patch directory.
  # cd /patch
4. Install the patches.
  # patchadd -M . 117171-17 # patchadd -M . 117175-02 # patchadd -M . 113318–20
  Tip –
  Pressing Control+D returns you to multiuser mode.

Patch the distribution that you copied to the management server.
1. Log in to the Solaris 9 machine as root.
  % su password:password
2. Mount the management server.
  # mount -o rw management-server-IP:/js/DISTRO_ID /mnt
3. Install the patches by performing one of the following actions:
  - If you are patching a Solaris OS on x86 software distribution, type the following commands:
    # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117172-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117468-02
  - If you are patching a Solaris OS on SPARC software distribution, type the following commands:
    # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117171-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117175-02 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 113318-20
    Note –
    You will receive a partial error for the first patch installation. Ignore this error.
4. Unmount the management server.
  # unmount /mnt

Restart NFS on the management server.
1. Edit the /etc/exports file.
  # vi /etc/exports
2. Change /js *(rw,no_root_squash) to /js *(ro,no_root_squash).
3. Restart NFS.
  # /etc/init.d/nfs restart
  NFS is restarted.
  
  The Solaris 9 OS on SPARC distribution is ready for deployment to target servers.

Fix the Solaris 9 OS on x86 distribution.
1. Change to /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris.
  # cd /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris
2. Re-create the bootenv.rc link.
  # ln -s ../../tmp/root/boot/solaris/bootenv.rc .
  The Solaris 9 OS on x86 distribution is ready for deployment to target servers.

Troubleshooting

If you want to patch another distribution you might have to delete the /patch/117172-17 directory and re-create it using the unzip 117172-17.zip command. When the first distribution is patched, the patchadd command makes a change to the directory that causes problems with the next patchadd command execution.