- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- save_config error in make_tape_recovery
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
Forums
Discussions
Discussions
Discussions
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
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
10-27-2003 04:29 AM
10-27-2003 04:29 AM
save_config error in make_tape_recovery
Just recently when I would run /make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00, I would get the following error:
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2003-10-27,12:20/system_cfg vg00
save_config: error - unable to determine file system length
ERROR: /opt/ignite/bin/save_config failed
======= 10/27/03 12:20:53 EST make_tape_recovery completed unsuccessfully
Checked the /var/opt/ignite/recovery/latest/recovery.log and doesn't meantion any other errors. Anyone have any ideas. Thanks is advance!!!
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2003 05:01 AM
10-27-2003 05:01 AM
Re: save_config error in make_tape_recovery
I possible cause is a discrepency between /etc/lvmtab and the actual disk setup, sometimes caused by a missing disk.
I'm attaching a script that checks that.
PLEASE, change the email address in this script prior to running it.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2003 06:11 AM
10-27-2003 06:11 AM
Re: save_config error in make_tape_recovery
I get the same message whether I run the command manually or in the cron. I ran your script and didn't find any discrepencies between the /etc/lvmtab and the actual disk setup. Any more ideas, Thanks again!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2003 06:15 AM
10-27-2003 06:15 AM
Re: save_config error in make_tape_recovery
lifls -C /dev/rdsk/######
Get that from the boot disk on the first command.
Post the output.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2003 06:23 AM
10-27-2003 06:23 AM
Re: save_config error in make_tape_recovery
Here is the output from both command. I used the boot disk device file for the lifls command.
/root > lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t4d0 (10/0.4.0) -- Boot Disk
/dev/dsk/c0t5d0 (10/0.5.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t4d0
/dev/dsk/c0t5d0
Root: lvol3 on: /dev/dsk/c0t4d0
/dev/dsk/c0t5d0
Swap: lvol2 on: /dev/dsk/c0t4d0
/dev/dsk/c0t5d0
Dump: lvol2 on: /dev/dsk/c0t4d0, 0
Current path "/dev/dsk/c8t2d6" is an alternate link, skip.
Current path "/dev/dsk/c8t2d7" is an alternate link, skip.
Current path "/dev/dsk/c8t3d0" is an alternate link, skip.
Current path "/dev/dsk/c8t3d1" is an alternate link, skip.
Current path "/dev/dsk/c8t3d2" is an alternate link, skip.
Current path "/dev/dsk/c8t3d3" is an alternate link, skip.
Current path "/dev/dsk/c8t3d4" is an alternate link, skip.
Current path "/dev/dsk/c8t3d5" is an alternate link, skip.
/root > lifls -C /dev/rdsk/c0t4d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD
SLDEV SLDRIVERS SLSCSI MAPPER IOTEST
PERFVER PVCU SSINFO HPUX ISL
AUTO LABEL
Thanks again!!!
Tom