Steps to verify if the boot image is missing should the LDOM fail to boot

Asset ID:	1-71-1020076.1
Update Date:	2011-05-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1020076.1 : Steps to verify if the boot image is missing should the LDOM fail to boot

Applies to:

Sun Netra T2000 Server
Sun Netra T5220 Server
Sun Netra T5440 Server
Sun Fire T1000 Server
Sun Fire T2000 Server
All Platforms

Goal

This Document refers to what needs to be checked if the LDOM fails to boot and if the boot image is missing.

Symptoms:

Unable to boot the LDOM Guest OS.

Error while booting LDOM.

Solution

Description
Available Documents:

Please note the Primary domain is also referred to as the Control domain is where the services are running. The Control domain should be installed with the LDOM base package SUNWldm and Please check the "LDOM administration Guide" and the LDOM release notes in http://download.oracle.com/docs/cd/E19608-01/index.html.

Steps to Follow
Below are the steps to verify if the boot image is missing:
The Boot disk can be configured as a image or as an entire dedicated disk itself.

This image or disk will be exported to the ldom configuration.

All the virtual storage is serviced by the virtual disk service (VDS).

Below is the example How to add a disk image.

# mkfile 10g /ldoms/ldom1_vdsk0_10gb.img
# mkfile 10g /ldoms/ldom1_vdsk1_10gb.img
# ldm add-vdsdev /ldoms/ldom1_vdsk0_10gb.img ldom1-vdsk0@primary-vds0
# ldm add-vdsdev /ldoms/ldom1_vdsk1_10gb.img ldom1-vdsk1@primary-vds0
If we had wanted to add a SAN device, the command would look like this:

   # ldm add-vdsdev /dev/dsk/c6t60060160B5681200944\
                               2F7677A81DB11d0s2 ldom1-vdsk2@primary-vds0
Now that the VDS devices are added, they must be assigned to the guest
domain:
# ldm add-vdisk ldom1-vdsk0 ldom1-vdsk0@primary-vds0 ldom1
# ldm add-vdisk ldom1-vdsk1 ldom1-vdsk1@primary-vds0 ldom1

There are situation where the boot disk might be missing from the Guest Domain which cause the Guest Domain not to boot.

An important thing to keep in mind is that any virtual storage device bound to a guest domain will appear as if it were a locally attached disk. This removes any additional management layers and simplifies the storage stack for   the kernel in the guest domain.

However, it is important to note that virtual storage devices are not presented with SCSI targets to Solaris in guest domains. As such, the device names will be missing the familiar target in the
cXtXdXsX standard and appear as cXdXsX.

For example, a storage device in the control domain may appear as c4t1d0s0, but in the guest domain it may appear as c0d1s0. The controller number will be determined by the order in which a VDS device was added to the guest domain. There can only be one VDS per service domain.
By default the primary domain is the first control and service domain, so all of your disks will be under controller 0. The disk number is determined by the order in which you add the VDSDEV to the guest domain.

In our example, ldom1-vdsk0 will appear as c0d0s0 and ldom1-vdsk1 will appear as c0d1s0 the guest domain. This may affect JumpStart configurations, but it does not affect anything operationally.

Each logical domain has its own instance of the OpenBoot PROM (OBP).
As such, standard variables can be configured as if it were a stand-alone server. These variables are stored in the hypervisor configuration. These variables can be defined from within the OBP or through the LDM software.

Troubleshooting
_______________

Check in the OBP whether the disks are available or not:

OBP:          Each logical domain has its own OpenBoot[TM] PROM instance. The NVRAM variables are stored within the domain.

If the disk are not visible in the OBP prompt:

Make sure the vdisk service is defined correctly on the control domain.

Make sure the vdisk device is defined correctly on the control domain.

Check for the vdisk status for Read only device / slice or partition.

From the control domain run ldm list-bindings and check the disks are listed properly or not.

Make sure the ldom services are running as per 1020054.1

Try to stop and start the ldmd and vntsd services.

Make sure the LDOM patches are latest as per the Sun recommendation.

Make sure the firmware version is up-to-date as per the latest revisions.

Please read the Readme.info file in the firmware patch of the respective hardware for upgrade procedure.

Make sure we backup the ldom configuration before doing the firmware upgrade as per 1019720.1

If after the above steps fail to make the services up please contact Sun[TM] Support with the following information:

The latest explorer output using the latest version of explorer script. If there is any specific error, please provide session log illustrating the error concerned.

Please follow 1020212.1 to collect the LDOM related logs.

Product
Logical Domain Manager
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server
Sun Netra T5220 Server
Sun Netra T5440 Server
Netra T5220 AC
Sun SPARC Enterprise T5220 Server

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:

Normalization Lead: global-systems-tsc-domain-engineers@Sun.COM

Normalized, ldom, ldm, boot, vdisk, boot image, guest domain

Attachments

This solution has no attachment