- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ignite make recovery error??
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО06-14-2002 12:00 PM
тАО06-14-2002 12:00 PM
When I run the command /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v inc_entire=vg00
I get the following error ....
* Creating local directories for configuration files and archive.
======= 06/14/02 15:58:55 EDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Jun 14 15:58:55 EDT 2002)
@(#) Ignite-UX Revision B.3.6.82
@(#) net_recovery (opt) $Revision: 10.567 $
* Testing pax for needed patch
* Passed pax tests.
* Recovery Archive Description = Recovery Archive
* Recovery Archive Location = /dev/rmt/0mn
* Number of Archives to Save = 2
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
** 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
* Checking Versions of Ignite-UX filesets
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
ERROR: The list_expander command failed. This could be due to a problem with
the file: "/var/opt/ignite/recovery/latest/archive_content" - see
messages above.
======= 06/14/02 15:58:59 EDT make_tape_recovery completed unsuccessfully
[wtsdb15:/] /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 06/14/02 15:59:14 EDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Jun 14 15:59:14 EDT 2002)
@(#) Ignite-UX Revision B.3.6.82
@(#) net_recovery (opt) $Revision: 10.567 $
* Testing pax for needed patch
* Passed pax tests.
* Recovery Archive Description = Recovery Archive
* Recovery Archive Location = /dev/rmt/0mn
* Number of Archives to Save = 2
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
** 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
* Checking Versions of Ignite-UX filesets
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - see messages above.
======= 06/14/02 15:59:19 EDT make_tape_recovery completed unsuccessfully
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2002 12:02 PM
тАО06-14-2002 12:02 PM
Re: ignite make recovery error??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2002 12:04 PM
тАО06-14-2002 12:04 PM
Re: ignite make recovery error??
Do you, in fact, have a stale entry in '/etc/fstab', notablely, "/dev/vgicedbs/lvbk"? If so, try removing it and rerunning.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-14-2002 12:09 PM
тАО06-14-2002 12:09 PM
Re: ignite make recovery error??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2002 11:25 AM
тАО06-16-2002 11:25 AM
Re: ignite make recovery error??
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2002 03:43 PM
тАО06-16-2002 03:43 PM
Re: ignite make recovery error??
circumstances will not continue if there is an
'error' message as opposed to a warning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2002 12:03 AM
тАО06-18-2002 12:03 AM
Re: ignite make recovery error??
I had a similar experience where ignite also failed because it could not get status information for a certain file. The file did in fact not exist.
However, the file was supposed to be located in the /tmp directory, and I created it manually by "touch", whereafter the following ignite backup completed successfully.
As this was done in /tmp I considered the above, non-authorized action low-risk: in your case I would not suggest anything like that. Instead you should try to check the file system and repair the possible errors in it.
regards John K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2002 08:36 AM
тАО06-18-2002 08:36 AM
SolutionFirst check your command as you posted it:
# make_tape_recovery -a /dev/rmt/0mn -I -v inc_entire=vg00
It should be:
# make_tape_recovery -Iv -x inc_entire=vg00 -a /dev/rmt/0mn
The same thing can be accomplished with:
# make_tape_recovery -IvA -a /dev/rmt/0mn
By using the "-I" option you are forcing make_tape_recovery to be interactive when restoring, this is not the default which should be non-interactive, make sure this is what you want.
make_tape_recovery creates configuration files that will be used in the restoration of your system if the need ever arises. These include /etc/lvmtab among many others. While it is true that you are not archiving vgicedbs, the system configuration still knows about it and ignite is running LVM commands to create configuration files that would also know about it. This usually indicates not an ignite problem but an underlying LVM issue or file system problem.
Have you run fsck on the filesystem? Since this under / you will need to boot into single user mode to do so. This function (fsck) is performed during a normal boot sequence for you so a simple reboot may clean up the filesystem.
1. Are there any messages in dmesg output that indicate a problem with any filesystems?
# dmesg
2. Run some of the LVM commands and look for errors:
vgdisplay -v /dev/vgicedbs
lvdisplay -v /dev/vgicedbs/lvbk
3. The name lvbk suggests that this is a logical volume that was possibly created for use with lvsplit and online backups that may be left behind after the logical volumes were merged back together (lvmerge)? If so you may simply be able to remove it.
Thanks for participating in the forums,
Martin
Chaos reigns within. Reflect, repent, and reboot. Order shall return.