GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_net_recovery list_expander failure
Operating System - HP-UX
1844012
Members
3541
Online
110226
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 05:52 AM
07-07-2008 05:52 AM
make_net_recovery list_expander failure
We have been running make_net_recovery on a server now for well over a year. The server using Veritas Storage Foundation for the rootdg.
This week the make_net_recovery failed with the following messages:
ERROR: There is a problem with entirely including device
'/dev/vx/dsk/rootdg'. Check the existence of the device 'inc_entire'.
** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - Check the existence of the included
device(s).
I am using the following command for the make_net_recovery:
make_net_recovery -v -x inc_entire=/dev/vx/dsk/rootdg -s cdcign1-8 -P s -a cdcign1-8:/var/opt/i
gnite/recovery/archives/osglbhp2
This week the make_net_recovery failed with the following messages:
ERROR: There is a problem with entirely including device
'/dev/vx/dsk/rootdg'. Check the existence of the device 'inc_entire'.
** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - Check the existence of the included
device(s).
I am using the following command for the make_net_recovery:
make_net_recovery -v -x inc_entire=/dev/vx/dsk/rootdg -s cdcign1-8 -P s -a cdcign1-8:/var/opt/i
gnite/recovery/archives/osglbhp2
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 06:00 AM
07-07-2008 06:00 AM
Re: make_net_recovery list_expander failure
ps: I can also do the list_expander command manually and it works ok:
/opt/ignite/lbin/list_expander
/opt/ignite/lbin/list_expander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 08:56 AM
07-07-2008 08:56 AM
Re: make_net_recovery list_expander failure
Found the problem, when I did a vxprint I received the following:
=>vxprint -ht
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
=>ps -efx |grep vxconfig
root 296 1 0 10:46:43 ? 0:00 /usr/sbin/vxconfigd -k -m enable
I did notice in the server startup log the following messages:
vxvm:vxconfigd: ERROR: Disk group rootdg: Cannot recover temp database:
Duplicate record in configuration
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
Duplicate record in configuration; transactions are disabled.
VxVM general startup ................................................ vxvm:vxconfigd: ERROR: Disk group rootdg: Cannot recover temp database:
Duplicate record in configuration
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
Duplicate record in configuration; transactions are disabled. OK
Performed the following to resolve:
1. Stop and restart the VxVM configuration daemon:
# vxdctl stop
# vxconfigd -x cleartempdir
2. Create one or more dummy volumes in the disk group in which the error is occurring, until the file /etc/vx/tempdb/ increases. For example,
# vxassist -g rootdg make dummy1 100m
# vxassist -g rootdg make dummy2 100m
3. Remove the dummy volumes, such as:
# vxedit -g rootdg -rf rm dummy1
# vxedit -g rootdg -rf rm dummy2
4. Again, stop and restart the VxVM configuration daemon:
# vxdctl stop
# vxconfigd -x cleartempdir
The cause of the problem was introduced in patches: PHKL_36995 and PHCO_36994 and will only occur after a server reboot...
=>vxprint -ht
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
=>ps -efx |grep vxconfig
root 296 1 0 10:46:43 ? 0:00 /usr/sbin/vxconfigd -k -m enable
I did notice in the server startup log the following messages:
vxvm:vxconfigd: ERROR: Disk group rootdg: Cannot recover temp database:
Duplicate record in configuration
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
Duplicate record in configuration; transactions are disabled.
VxVM general startup ................................................ vxvm:vxconfigd: ERROR: Disk group rootdg: Cannot recover temp database:
Duplicate record in configuration
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
Duplicate record in configuration; transactions are disabled. OK
Performed the following to resolve:
1. Stop and restart the VxVM configuration daemon:
# vxdctl stop
# vxconfigd -x cleartempdir
2. Create one or more dummy volumes in the disk group in which the error is occurring, until the file /etc/vx/tempdb/
# vxassist -g rootdg make dummy1 100m
# vxassist -g rootdg make dummy2 100m
3. Remove the dummy volumes, such as:
# vxedit -g rootdg -rf rm dummy1
# vxedit -g rootdg -rf rm dummy2
4. Again, stop and restart the VxVM configuration daemon:
# vxdctl stop
# vxconfigd -x cleartempdir
The cause of the problem was introduced in patches: PHKL_36995 and PHCO_36994 and will only occur after a server reboot...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 08:58 AM
07-07-2008 08:58 AM
Re: make_net_recovery list_expander failure
See my last posting for cause and resolution.... Patches to fix the patches that introduced the issue have not been released by HP yet..
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP