- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: unsuccessful make_tape_recovery "system_cfg" c...
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
тАО01-19-2006 11:20 PM
тАО01-19-2006 11:20 PM
unsuccessful make_tape_recovery "system_cfg" cannot be parsed
Could someone please help me with the following error I get in the /var/opt/ignite/recovery/2006-01-20,13:34/recovery.log:
ERROR: "/var/opt/ignite/recovery/2006-01-20,13:34/system_cfg", line 52:
syntax error
ERROR: Problems were encountered while parsing config file:
"/var/opt/ignite/recovery/2006-01-20,13:34/system_cfg".
instl_adm: Config file: "/var/opt/ignite/recovery/2006-01-20,13:34/system_cfg" cannot be parsed.
ERROR: System error, /opt/ignite/bin/instl_adm failed checking
/var/opt/ignite/recovery/2006-01-20,13:34/system_cfg
======= 01/20/06 13:34:48 EET make_tape_recovery completed unsuccessfully
The command I used is:
make_tape_recovery тАУvI тАУx inc_entire=vg00 -a /dev/rmt/0mn
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:23 PM
тАО01-19-2006 11:23 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
(10 lines either side should suffice)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:26 PM
тАО01-19-2006 11:26 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
Was it a new installation or the running setup?
If it was new I suspect corruption in depot from which you installed.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:28 PM
тАО01-19-2006 11:28 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
usage=HFS
size=417792KB
mount_point="/stand"
minfree=10
file_length=LONG
blksize=65536
fragsize=8192
ncpg=32
nbpi=9444
rotational_delay=
(line 52) largefiles=FALSE
bad_block_relocate=false
contiguous_allocation=true
stripes=0
stripe_size=0KB
minor_number=0x01
disk[_hp_root_disk]
} # end logical_volume
logical_volume "lvol2" {
usage=SWAP_DUMP
size=12582912KB
mount_point="primary"
bad_block_relocate=false
contiguous_allocation=true
stripes=0
stripe_size=0KB
minor_number=0x02
disk[_hp_root_disk]
} # end logical_volume
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:34 PM
тАО01-19-2006 11:34 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
rotational_delay=0
which is (I believe) a symptom of the problem, the real question is why is there no value after "rotational_delay" in your system_cfg file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:34 PM
тАО01-19-2006 11:34 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
The version installed is B5725AA B.5.1.33 HP-UX Installation Utilities (Ignite-UX).
Is there a patch that corrects the situation?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:36 PM
тАО01-19-2006 11:36 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
Should I check sth in the system?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 11:43 PM
тАО01-19-2006 11:43 PM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
Instead of searching for a patch you can download the latest version and can reinstall this from here.
Allthough I can not see anything problematic in the file at line 52. It is same as on my server.
fragsize=8192
What happens if you repeat the backup procedure?
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2006 12:46 AM
тАО01-20-2006 12:46 AM
Re: unsuccessful make_tape_recovery "system_cfg" cannot be parsed
# tunefs -v /dev/vg00/lvol1
super block last mounted on: /stand
magic 95014 clean FS_OK time Tue Jan 3 11:24:43 2006
sblkno 16 cblkno 24 iblkno 32 dblkno 80
sbsize 2048 cgsize 2048 cgoffset 24 cgmask 0xfffffff8
ncg 47 size 114688 blocks 111637
bsize 8192 bshift 13 bmask 0xffffe000
fsize 1024 fshift 10 fmask 0xfffffc00
frag 8 fragshift 3 fsbtodb 0
minfree 10% maxbpg 77
maxcontig 1 rotdelay 0ms rps 60
csaddr 80 cssize 27648 csshift 9 csmask 0xfffffe00
ntrak 7 nsect 22 spc 154 ncyl 745
cpg 16 bpg 308 fpg 2464 ipg 384
nindir 2048 inopb 64 nspf 1
nbfree 9458 ndir 25 nifree 17959 nffree 173
cgrotor 7 fmod 0 ronly 0
fname fpack
featurebits 0x1 id 0x0,0x0
optimize FS_OPTTIME
Then look for something like
rotdelay 0ms