When trying to create a make_recovery tape, get msg: WARNING - non terminated volume (verify ANSI co

[Glenn Mitchell_4]

Trying to create a make_recovery tape on a D220 server running 10.20 hpux.

Getting the following error when the program tries to write to tape:
tape hardware path 56/52.0.0.0: WARNING - non terminated volume (verify ANSI com
pliance of media).
make_recovery(472): /usr/bin/dd failed,res=512,errno=0

This is the entire output from 'make_recovery -Av' command:

buenyc # /opt/ignite/bin/make_recovery -Av
Option -A specified. Entire Core Volume Group/disk will be backed up.



***************************************
HP-UX System Recovery
Validating append file
Done

File Systems on Core OS Disks/Volume Groups:

vg name = vg00
pv_name = /dev/dsk/c0t5d0

vg00 /dev/vg00/lvol3 /
vg00 /dev/vg00/lvol5 /home
vg00 /dev/vg00/lvol6 /opt
vg00 /dev/vg00/lvol1 /stand
vg00 /dev/vg00/lvol4 /tmp
vg00 /dev/vg00/lvol7 /usr
vg00 /dev/vg00/lvol8 /var

/opt is a mounted directory
It is in the Core Volume Group
Mounted at /dev/vg00/lvol6


/var is a mounted directory
It is in the Core Volume Group
Mounted at /dev/vg00/lvol8

Destination = /dev/rmt/0m
Boot LIF location = /var/tmp/uxinstlf.recovery



***************************************
Creating the configuration file.
Done
Modifying the configuration file.
Done
Backing up vg configurations
Volume Group vg00
Done
Going to create the tape.
Processing tape
Invoking instl_adm -T
Creating boot LIF
Done
Writing boot LIF to tape /dev/rmt/0mn
tape hardware path 56/52.0.0.0: WARNING - non terminated volume (verify ANSI com
pliance of media).
make_recovery(472): /usr/bin/dd failed,res=512,errno=0
Cleanup

[Glenn Mitchell_4]

I tried cleaning the drive with a cleaning tape and also tried a different tape.

[Helen French]

Is the device filename right? Check and post the output of:

# ioscan -fnC tape

[Jeff Schussele]

Hi Glenn,

Not sure about this, but I think it might mean that you're using the wrong tape type - i.e. a DDS3 tape in a DDS2 drive.

Rgds,
Jeff

[Glenn Mitchell_4]

Yes, here is the output from ioscan -fnCtape:

buenyc # ioscan -fnCtape
Class I H/W Path Driver S/W State H/W Type Description
===============================================================
tape 0 56/52.0.0 tape2 CLAIMED DEVICE HP HP35480A
/dev/diag/rmt/c0t0d0 /dev/rmt/c0t0d0BEST
/dev/rmt/0m /dev/rmt/c0t0d0BESTb
/dev/rmt/0mb /dev/rmt/c0t0d0BESTn
/dev/rmt/0mn /dev/rmt/c0t0d0BESTnb
/dev/rmt/0mnb

[Helen French]

To narrow down the situation: Do you get the same error if you just do a tar backup to the same tape in the same drive:

# tar -cvf /dev/rmt/0m /dir_name

[Glenn Mitchell_4]

Hi Jeff,

The site is using the same style of tapes (2.6Gb)that we use every night for nightly backups. I'm able to run
'tar cvf /dev/rmt/0m /etc' and write an entire directory to this tape.

[Helen French · Accepted solution]

If possible, I would suggest you to upgrade the Ignite-UX software to the new tool - make_tape_recovery and apply the latest patches. That may solve the issue.

[Jeff Schussele]

Hi (again) Glenn,

Well, if the tape type is correct it's possibly a SCSI subsystem problem - somewhere, cable, terminator, device, etc.

I can only find one thread

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x029e663ce855d511abcd0090277a778c,00.html

In a search for that error. Although it contains no rock-solid resolution, all hints point to a SCSI problem of some sort. Note that the user got different errors depending on just how much was being written to the tape.

Is this the 1st time you've tried make_recovery? That's an intensive write operation - what with it having to write the LIF volume & all.

I also agree w/Shiju that you should upgrade Ignite & use make_tape_recovery. You might also try a much larger tar (or better yet fbackup) write to see if the error pops up then. /etc may not be big enough.

HTH,
Jeff