Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations

ProcedureLocating the GRUB Menu's menu.lst File When the active menu.lst file is in Another Boot Environment

In the following procedure, the system contains two operating systems: Solaris and a Solaris Live Upgrade boot environment, second_disk. In this example, the menu.lst file does not exist in the currently running boot environment. The second_disk boot environment has been booted. The Solaris boot environment contains the GRUB menu. The Solaris boot environment is not mounted.

  1. 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.

  2. To locate the menu.lst file, type:

    # /sbin/bootadm list-menu

    The location and contents of the file are displayed.

    The location for the active GRUB menu is: /dev/dsk/device_name(not mounted)
    The filesystem type of the menu device is <ufs>
    default 0
    timeout 10
    0 Solaris
    1 Solaris failsafe
    2 second_disk
    3 second_disk failsafe
  3. Because the file system containing the menu.lst file is not mounted, mount the file system. Specify the UFS file system and the device name.

    # /usr/sbin/mount -F ufs /dev/dsk/device_name /mnt

    Where device_name specifies the location of the root (/) file system on the disk device of the boot environment that you want to mount. The device name is entered in the form of /dev/dsk/cwtxdysz. For example:

    # /usr/sbin/mount -F ufs /dev/dsk/c0t1d0s0 /mnt

    You can access the GRUB menu at /mnt/boot/grub/menu.lst

  4. Unmount the filesystem

    # /usr/sbin/umount /mnt

    Note –

    If you mount a boot environment or a file system of a boot environment, ensure that the file system or file systems are unmounted after use. If these file systems are not unmounted, future Solaris Live Upgrade operations on that boot environment might fail.