Hi Subhashni,
Here is the doc, I've edited it to make it a little smaller
//Quote//
How do I boot my system from Support Media on 11.00 ?
DocId: OZBEKBRC00000582
Updated: 1/28/00 11:06:37 AM
PROBLEM : My system won't boot due to problems with the LIF area, a missing kernel, or other missing files on my system.
RESOLUTION
FOR HPUX 11.XX ---------
Activate an LVM Root Volume Group from the Install/Support Media on a 11.00 system with 24MB of memory or more
This document details how to access your LVM Root Volume Group from the Install/Support Media at 11.00.
NOTE
1. Boot from the Install/Support Media.
Boot from the path of the CD media and do NOT interact with ISL.
You will get a menu with the following options:
Install HP-UX
Run a recovery shell
Advanced Options
2. Select "Run a Recovery Shell" from the menu.
3. Enter x from the SUPPORT MEDIA MAIN MENU, to exit to the shell.
4. Type chroot_lvmdisk. Something similar to the following will be displayed:
Enter the hardware path associated with the '/'(ROOT) file system (example: 7.6.9.37 )
5. Type to accept the example (default) as your root file system hardware path; otherwise, enter the hardware path for the root file system hardware you wish to specify in its place.
6. If you type , the following will be displayed:
Is 7.6.9.37 the hardware path of the root/boot disk?[y|n|q]-
7. Enter y, and something similar to the following will be displayed:
If your disk IS an LVM disk, you will see the following:
/sbin/fs/hfs/fsck -c 0 -y /dev/rdsk/c2t1d0s2lvm
** /dev/rdsk/c2t1d0s2lvm
** Last Mounted as /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
6256 files, 0 icont, 1494 used, 1563824 free (928 frags, 195362 blocks)
/sbin/fs/hfs/mount /dev/dsk/c2t1d0s2lvm /ROOT
/sbin/fs/hfs/mount /dev/dsk/c2t1d0s1lvm /ROOT/stand
loading /usr/sbin/chroot
x ./usr/sbin/chroot 123456 bytes 96 blocks
Enter 'cd /ROOT; chroot /ROOT /sbin/sh' at the shell prompt to chroot to the customer's /(root) disk.
(NOTE: If this command fails with a "bad superblock.." message, your boot disk may not be an LVM disk.
If so, try: fsck /dev/rdsk/c2t1d0 (use your special file!)
If you see fsck messages akin to those above, you are making progress and your disk is NOT an LVM disk.)
8. Enter cd ROOT; chroot /ROOT /sbin/sh at the shell prompt.
9. Enter vgchange -a y /dev/vg00.
This will "activate" vg00, so that you can get to your swap area, /usr, etc.
Mount /usr.
10. Enter vgdisplay -v at the prompt.
The logical volumes within the disk corresponding to the various components (/stand, swap, /, /home, /opt, /tmp, /usr, /var) are listed.
You must know which lvol is for swap (usually lvol2), which lvol is for /usr (usually lvol6), etc.
11. Enter the swapon command; for example, swapon /dev/vg00/lvol2.
Usually, install makes lvol2 your swap area with a default value of 48mb, but you must know which lvol is actually your swap area.
Executing this command will yield the error no room in system tables to add paging to lvol2, but this just means that it couldn't configure all the swap in lvol2; however, enough swap is configured to prevent possible memory faults caused by lack of swap.
12. Enter fsck /dev/vg00/rlvol6; that is, use the lvol number where /usr resides. (You may have to umount /dev/vg00/lvol6)
13. Enter the mount command; e.g., mount /dev/vg00/lvol6 /usr.
14. Repeat steps 12 and 13 for /var and /tmp.
You can now repair any file damage that has occurred.
//Endquote//
Hope this helps.
Regds
