OS Provisioning Issues

This section describes the known OS provisioning (deployment) issues.

OS Deployment of Red Hat Linux 3.0 Update 2 Might Stop and Enter Interactive Mode

OS deployment of Red Hat Linux 3.0 Update 2 might stop and enter interactive mode due to a time out issue. This is an intermittent problem.

Workaround: Stop the OS deployment job and retry the OS deployment again. If OS deployment consistently fails, you will have to use a later version of the Red Hat OS.

Unrequired Mount Point Must Be Specified for Swap Partition When Creating OS Profile

When specifying the swap partition for an OS profile using either the browser interface or the command line, you must specify an unrequired mount point. If you specify a mount point, a separate file system is actually created.

Workaround: Specify swap as the mount point for the swap partition, which serves as a placeholder and is ignored. The following is a command line example:

add osprofile myprofile partition swap type swap size 1024 device c0t0d0s1 sizeoption fixed

Setting Baud Rate for the BIOS Console Makes OS Deployment Fail on Sun Fire V20z and V40z Servers (6322295)

The baud rate for the BIOS console must be set to 9600 (default) or OS deployment to a Sun Fire V20z or V40z server will fail. This means that you cannot change the consolebaudrate value in the load server command or the Load OS wizard in the browser interface.

If the SP console baud rate is set to something other than 9600, the OS deployment will succeed but the console through the connect server command will display garbage characters.

Workaround: You must change the baud rate for the BIOS console manually after an OS deployment. To do this, reboot the target server and enter the BIOS setup screen during the boot sequence. Consult the server's user manual to see how to change its BIOS settings.

An OS Profile Name Cannot Contain a Period When Using the Browser Interface (6331294)

If you specify a period in an OS profile name when using the browser interface wizard to create an OS profile, an "invalid profile name" error occurs. A period should be an acceptable character for an OS profile name.

Workaround: If you want to include a period in the OS profile name, use the create osprofile command.

The Same SUSE OS Profile Cannot Be Used on Sun Fire V20z/V40z Servers and Sun Fire X4000 Series Servers (6344382)

Once you load a SUSE OS profile on a Sun Fire X4000 series server, that same OS profile and associated OS distribution cannot be used on Sun Fire V20z and V40z servers. Loading a SUSE OS profile on a Sun Fire X4000 series server actually modifies the associated SUSE OS distribution, which makes that OS distribution unusable by Sun Fire V20z and V40z servers.

Workaround: You must create separate SUSE OS distributions and OS profiles for Sun Fire V20z/V40z servers and Sun Fire X4000 series servers.