Error Code details
Severity: Error 
Component: Volume Manager 
Reconnection to %s failed: %s

The exact cause of this message varies from case to case, and Symantec Technical Support must investigate it appropriately for analysis and resolution. This section describes two of the more common causes.


This message may display when the volume configuration daemon, vxconfigd, is not up and vxnotify cannot communicate with it. This issue occurs when vxconfgd core dumps or takes too long to come up. The causes of this issue include:


  • Back-end issues due to hardware errors, operating system SCSI driver level errors, and issues with vendor products or patches that affect disk access.
  • Upgrading or applying patches, either for VxVM or other disk and multi-pathing related products.

This message may also display if the system hangs while the root file systems are being checked. The causes of this issue include:


  • Back-end disk I/O issues.
  • The / file system is very large, and the first fsck command takes a long time to run.
  • The file system may be corrupted, and the fsck command does not run properly. This is an extreme case.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2010-10-29 19:23:37 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: 5.0MP1

For problems related to a vxconfigd core dump or vxconfigd not coming up:

  1. Resolve the disk errors or the patch issues.
  2. Restart vxconfigd.

For problems related to the system hanging while the root file system is being checked, do one of the following:

  • Resolve the back-end disk issues so that the disk discovery and I/O can succeed, and reboot the system.
  • Boot from alternate media until the cause of the problem is found and resolved.



User solutions
No user solutions yet.


Read and accept Terms of Service