Re: Mysterious Ignite failure. (284 Views)
Reply
Exalted Contributor
Steven E. Protter
Posts: 33,806
Registered: ‎08-15-2002
Message 1 of 9 (284 Views)
Accepted Solution

Mysterious Ignite failure.

Had a tape hardware problem, replaced the cable, tape drive now works with fbackup.

Ignite fails with every make_tape_recovery

Message is meaningless to me, and I know Ignite.

Attaching the log file.

Real head scratcher here.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Honored Contributor
Helen French
Posts: 3,934
Registered: ‎07-11-2000
Message 2 of 9 (284 Views)

Re: Mysterious Ignite failure.

Could you post the error again? I can't read it properly.

Did you check a simple pax or tar command with the new drive?
Life is a promise, fulfill it!
Exalted Contributor
Steven E. Protter
Posts: 33,806
Registered: ‎08-15-2002
Message 3 of 9 (284 Views)

Re: Mysterious Ignite failure.

The script:

#!/usr/bin/sh
/opt/ignite/bin/make_tape_recovery -Av -x inc_entire=vg00

The error:

* Creating local directories for configuration files and archive.

======= 12/04/03 11:00:29 CST Started /opt/ignite/bin/make_tape_recovery.
(Thu Dec 04 11:00:29 CST 2003)
@(#) Ignite-UX Revision B.4.4.29
@(#) net_recovery (opt) $Revision: 10.611 $

* 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

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c1t2d0 /dev/dsk/c2t2d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/images /images 2
/dev/vg00/lvol9 /utmp 2
/dev/vg00/lvol8 /var 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /usr 2
0 v /dev/vg01 0x01 /dev/dsk/c6t8d1 /dev/dsk/c6t8d2 /dev/dsk/c6t8d3 /dev/dsk/c6t8d4 /dev/dsk/c6t8d5 /dev/dsk/c6t8d6 /dev/dsk/c6t8d0 /dev/dsk/c6t8d7
/dev/vg01/lvol1 /oracle1 0
/dev/vg01/lvol2 /oracle3 0
/dev/vg01/lvol3 /backups 0
/dev/vg01/lvol4 /oracle2 0
/dev/vg01/lvol5 /oracle 0
/dev/vg01/lvol6 /ias 0
/dev/vg01/lvol7 /sag 0
/dev/vg01/lvol11
/dev/vg01/sys.data
/dev/vg01/sys.asso
/dev/vg01/sys.pl
/dev/vg01/sys.cl
/dev/vg01/sys.work
/dev/vg01/ada.sort
/dev/vg01/ada.temp
/dev/vg01/lvol19 /data 0
/dev/vg01/lvol20 /oradata 0
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2003-12-04,11:00/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile /dev/vg01
vgexport: Volume group "/dev/vg01" is still active.

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2003-12-04,11:00/archive_cfg -g
/var/opt/ignite/recovery/2003-12-04,11:00/flist -n 2003-12-04,11:00 -r
64 -d Recovery\ Archive -t -i 1 -m t
WARNING: There is a problem reading a file list line, unexpected file name
length for file: 17 tmp/swverify.doc
.
WARNING: There is a problem reading a file list line, unexpected file name
length for file: 100644 1042060405 231117 226
.
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
Adding /opt/ignite/Version file to LIF.
* Writing boot LIF to tape
46061+1 records in
46061+1 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2003-12-04,11:00 -m t -w
/var/opt/ignite/recovery/2003-12-04,11:00/recovery.log -u -R -g
/var/opt/ignite/recovery/2003-12-04,11:00/flist -a 30630670

* Preparing to create a system archive

* Archiving contents of tzfat.juf.net via tar image to local device/dev/rmt/0mn.
pax: tmp/veritas45 : Optional ACL entries are not backed up.
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log

WARNING: There was a problem with the list of files/directories to archive.
Input: /var/opt/ignite/recovery/2003-12-04,11:00/flist
The following line(s) had too few/incorrect entries in each of them.
Problem lines:
line: 17 tmp/swverify.doc
line: 100644 1042060405 231117 226

======= 12/04/03 11:45:47 CST make_tape_recovery completed unsuccessfully

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Honored Contributor
RAC_1
Posts: 5,920
Registered: ‎03-21-2002
Message 4 of 9 (284 Views)

Re: Mysterious Ignite failure.

Check flist file. Check line no 17.

Any problem on that line?
There is no substitute to HARDWORK
Honored Contributor
Helen French
Posts: 3,934
Registered: ‎07-11-2000
Message 5 of 9 (284 Views)

Re: Mysterious Ignite failure.

Did you check the flist file? The first entry is normally the number of characters in that filename. Check and makes that a proper file exists on the destination with the correct file length.

Also, try doing a pax command or make_tape_recovery manually by specifying your output device file (/dev/rmt/0mn).
Life is a promise, fulfill it!
Honored Contributor
Robert-Jan Goossens
Posts: 7,384
Registered: ‎04-04-2000
Message 6 of 9 (284 Views)

Re: Mysterious Ignite failure.

SEP,

Check this thread from a few hours ago.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=291826

Regards,
Robert-Jan
Honored Contributor
Helen French
Posts: 3,934
Registered: ‎07-11-2000
Message 7 of 9 (284 Views)

Re: Mysterious Ignite failure.

This document will be helpful too (TKB #UIUXKBRC00013434):

http://support2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000070742469
Life is a promise, fulfill it!
Honored Contributor
Paula J Frazer-Campbell
Posts: 3,242
Registered: ‎07-21-1998
Message 8 of 9 (284 Views)

Re: Mysterious Ignite failure.

Hi

check the file tmp/swverify.doc as that appears to be where it is stopping

paula
If you can spell SysAdmin then you is one - anon
Exalted Contributor
Steven E. Protter
Posts: 33,806
Registered: ‎08-15-2002
Message 9 of 9 (284 Views)

Re: Mysterious Ignite failure.

Shiju,

The document cleared things up nicely.

I don't know why the error message said completed unsuccessfully.

Is that English or what my two year old speaks?

The tape is usable and I just burned half a day trying to diagnose a problem that really wasn't a problem. Certainly it wasn't drop dead crisis like I made it out to be.

I'm going to keep an eye on this one and try and figure out why my brain locked on this. After reading the document, I remembered I've seen this before and contaced support on it two years ago.

Duh.

Maybe the roots of those green leaves on my head are growing into my brain.

Also note: I came here before the support center. Usually I do both at the same time and make it a race.

Thanks to all participants.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.