"ERROR 1(0xc0500001) vxboot vxboot: Group : Duplicate virtual device number(s)" is reported when importing disk groups during boot
Article ID: 100020159
Updated On:
Description
Error Message
ERROR 1(0xc0500001) vxboot vxboot: Group : Duplicate virtual device number(s)
Resolution
What is affected
A problem has been identified with Storage Foundation for Windows (SFW) that can lead to secondary disk groups not importing automatically on system reboot or vxboot will log messages for a disk groups regarding a VVR Replicated Volume Group (RVG) that needs recovery.
This issue has been identified and a private fix is available from Veritas Enterprise Technical Support which will allow the SFW Dynamic Secondary disk groups to automatically import during a system reboot which will also stop the errors about vxboot and the VVR RVG needing recovery. To obtain the private fix, contact Veritas Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix.
Files included in this hotfix
Windows 2003
Windows 2008
Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.
A problem has been identified with Storage Foundation for Windows (SFW) that can lead to secondary disk groups not importing automatically on system reboot or vxboot will log messages for a disk groups regarding a VVR Replicated Volume Group (RVG) that needs recovery.
This issue has been identified and a private fix is available from Veritas Enterprise Technical Support which will allow the SFW Dynamic Secondary disk groups to automatically import during a system reboot which will also stop the errors about vxboot and the VVR RVG needing recovery. To obtain the private fix, contact Veritas Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix.
Files included in this hotfix
Windows 2003
| File | Win2003 x86 | Win2003 x64 | Win2003 IA64 |
|---|---|---|---|
| vxboot.sys | 5.1.14.398 | 5.1.14.398 | 5.1.14.398 |
| file size | 329,232 bytes | 501,776 bytes | 954,384 bytes |
| vxconfig.dll | 5.1.14.398 | 5.1.14.398 | 5.1.14.398 |
| file size | 840,720 bytes | 834,048 bytes | 834,048 bytes |
Windows 2008
| File | Win2008 x86 | Win2008 x64 | Win2008 IA64 |
|---|---|---|---|
| vxboot.sys | 5.1.14.398 | 5.1.14.398 | 5.1.14.398 |
| file size | 327,184 bytes | 381,456 bytes | 855,568 bytes |
| vxconfig.dll | 5.1.14.398 | 5.1.14.398 | 5.1.14.398 |
| file size | 855,056 bytes | 855,056 bytes | 855,056 bytes |
Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.
Issue/Introduction
After server reboot, Storage Foundation for Windows (SFW) 5.1 Dynamic Secondary disk groups do not automatically import if they contain Veritas Volume Replicator (VVR) objects. The Microsoft Windows System log file has entries regarding vxboot and duplicate virtual device numbers.
Additional Information
ETrack: 1503593
ETrack: 1406565
Was this article helpful?
Yes
No
Powered by
