Error Code details
V-5-1-169
Severity: Error 
Component: Volume Manager 
Message:
cannot open /dev/vx/config Device is already open No such file or directory No such device or address Cannot open /etc/vfstab

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Generic
Release: Generic
Content:
The /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."

    The following are likely causes:

  • The Veritas Volume Manager package installation did not complete correctly.

  • The device node was removed by the administrator or by an errant shell script.

If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.Cannot open /etc/filesystems

Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: AIX 6.1 (POWER), AIX 5.1 (POWER), AIX 5.2 (POWER), AIX 5.3 (POWER)
Release: Generic
Content:
The /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."

    The following are likely causes:

  • The Veritas Volume Manager package installation did not complete correctly.

  • The device node was removed by the administrator or by an errant shell script.

If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.Cannot open /etc/filesystems

VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/filesystems: reason

vxconfigd could not open the /etc/filesystems file, for the reason given. The /etc/filesystems file is used to determine which volume (if any) to use for the /usr file system.

This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system.Cannot open /etc/fstab

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 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 /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."

    The following are likely causes:

  • The Veritas Volume Manager package installation did not complete correctly.

  • The device node was removed by the administrator or by an errant shell script.

If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.Cannot open /etc/filesystems

VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/fstab: reason

vxconfigd could not open the /etc/fstab file, for the reason given. The /etc/fstab file is used to determine which volume (if any) to use for the /usr file system.

This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system.

Cannot open /etc/fstab

Solution 4 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 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 /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."

    The following are likely causes:

  • The Veritas Volume Manager package installation did not complete correctly.

  • The device node was removed by the administrator or by an errant shell script.

If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.Cannot open /etc/filesystems

VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/fstab: reason

vxconfigd could not open the /etc/fstab file, for the reason given. The /etc/fstab file is used to determine which volume (if any) to use for the /usr file system.

This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system.

error messagesCannot open /etc/vfstab

Solution 5 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Solaris 10 (SPARC), Solaris 10 (x86-64)
Release: Generic
Content:
The /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."

    The following are likely causes:

  • The Veritas Volume Manager package installation did not complete correctly.

  • The device node was removed by the administrator or by an errant shell script.

If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:

# vxdctl -k stop

For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.Cannot open /etc/filesystems

VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/vfstab: reason

vxconfigd could not open the /etc/vfstab file, for the reason given. The /etc/vfstab file is used to determine which volume (if any) to use for the /usr file system.

This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service