Error Code details
V-5-1-1186
Severity: Error 
Component: Volume Manager 
Message:
Volume for mount point /usr not found in rootdg disk group

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:51 PST
Platform: HP-UX 11i v1 (IA-64/PA-RISC), HP-UX 11i v2 (IA-64/PA-RISC), HP-UX 11i v3 (IA-64/PA-RISC)
Release: Generic
Content:
The system is configured to boot with /usr mounted on a volume, but the volume associated with /usr is not listed in the configuration of the boot disk group.

    The following are possible causes of this error:

  • The /etc/fstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume named is not in the boot disk group. This should happen only as a result of direct manipulation by the administrator.

    Boot the system on a CD-ROM or networking-mounted root file system. If the root file system is defined on a volume, then start and mount the root volume. If the root file system is not defined on a volume, mount the root file system directly. Edit the /etc/fstab file to correct the entry for the /usr file system.

  • The system somehow has a duplicate boot disk group, one of which contains the /usr file system volume and one of which does not (or uses a different volume name), and vxconfigd somehow chose the wrong boot disk group. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (causing the apparent access order of the two disk groups to be reversed). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.

    In case 2, either boot with all drives in the offending version of the boot disk group turned off, or import and rename the offending boot disk group from another host.

    See the vxdg(1M) manual page.

    If you turn off drives, run the following command after booting:

    # vxdg flush bootdg

    This updates time stamps on the imported version of the boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact Veritas Technical Support.

Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:51 PST
Platform: Red Hat Enterprise Linux 4 (x86-32), Red Hat Enterprise Linux 4 (IA-64), Red Hat Enterprise Linux 4 (x86-64), Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER), SUSE Linux Enterprise Server 9 (x86-32), SUSE Linux Enterprise Server 9 (IA-64), SUSE Linux Enterprise Server 9 (x86-64), SUSE Linux Enterprise Server 10 (x86-32), SUSE Linux Enterprise Server 10 (IA-64), SUSE Linux Enterprise Server 10 (x86-64), SUSE Linux Enterprise Server 10 (POWER)
Release: Generic
Content:
The system is configured to boot with /usr mounted on a volume, but the volume associated with /usr is not listed in the configuration of the boot disk group.

    The following are possible causes of this error:

  • The /etc/fstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume named is not in the boot disk group. This should happen only as a result of direct manipulation by the administrator.

    Boot the system on a CD-ROM or networking-mounted root file system. If the root file system is defined on a volume, then start and mount the root volume. If the root file system is not defined on a volume, mount the root file system directly. Edit the /etc/fstab file to correct the entry for the /usr file system.

  • The system somehow has a duplicate boot disk group, one of which contains the /usr file system volume and one of which does not (or uses a different volume name), and vxconfigd somehow chose the wrong boot disk group. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (causing the apparent access order of the two disk groups to be reversed). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.

  • In case 2, either boot with all drives in the offending version of the boot disk group turned off, or import and rename the offending boot disk group from another host.

    See the vxdg(1M) manual page.

    If you turn off drives, run the following command after booting:

    # vxdg flush bootdg

    This updates time stamps on the imported version of the boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact Veritas Technical Support.

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:51 PST
Platform: Solaris 10 (SPARC), Solaris 10 (x86-64)
Release: Generic
Content:
The system is configured to boot with /usr mounted on a volume, but the volume associated with /usr is not listed in the configuration of the boot disk group.

    The following are possible causes of this error:

  • The /etc/vfstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume named is not in the boot disk group. This should happen only as a result of direct manipulation by the administrator.

    Boot the system on a CD-ROM or networking-mounted root file system. If the root file system is defined on a volume, then start and mount the root volume. If the root file system is not defined on a volume, mount the root file system directly. Edit the /etc/vfstab file to correct the entry for the /usr file system.

  • The system somehow has a duplicate boot disk group, one of which contains the /usr file system volume and one of which does not (or uses a different volume name), and vxconfigd somehow chose the wrong boot disk group. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (causing the apparent access order of the two disk groups to be reversed). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.

    In case 2, either boot with all drives in the offending version of the boot disk group turned off, or import and rename the offending boot disk group from another host.

    See the vxdg(1M) manual page.

    If you turn off drives, run the following command after booting:

    # vxdg flush bootdg

    This updates time stamps on the imported version of the boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact Veritas Technical Support.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service