output file /dev/rmt/2m is not a valid device file for backup

[Robert Funk_1]

I just added a Exabyte Mammoth2 tape drive to my rp5450 server and everything appears to be setup correctly. I have reviewed other past postings with this problem, but still can't locate the answer other than to possibly update Ignite and/or load patches. Can anybody offer any other advise or tell me how to identify which patches may be required?

I can write and communicate to the tape by:

tar -cvf /dev/rmt/2m /tmp
mt -t /dev/rmt/2m status
mt -t /dev/rmt/2m rewind

icgstx1:/> mt -t /dev/rmt/2m status
Drive: EXABYTE Mammoth2
Format: QIC-5GB formatQIC-5GB format
Status: [10128d6] online immediate-report-mode
File: 0
Block: 15

Tried lssf /dev/rmt/2m:
stape card instance 0 SCSI target 15 SCSI LUN 0 at&t best density available at a
ddress 0/0/1/0.15.0 /dev/rmt/2m

ll on /dev/rmt/2m:
crw-rw-rw- 2 bin bin 205 0x00f000 Apr 1 10:05 2m

ioscan -fnC tape:
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI

/dev/rmt/0m /dev/rmt/c0t1d0BEST
/dev/rmt/0mb /dev/rmt/c0t1d0BESTb
/dev/rmt/0mn /dev/rmt/c0t1d0BESTn
/dev/rmt/0mnb /dev/rmt/c0t1d0BESTnb
tape 2 0/0/1/0.15.0 stape CLAIMED DEVICE EXABYTE Mammoth2
/dev/rmt/2m /dev/rmt/c0t15d0BEST
/dev/rmt/2mb /dev/rmt/c0t15d0BESTb
/dev/rmt/2mn /dev/rmt/c0t15d0BESTn
/dev/rmt/2mnb /dev/rmt/c0t15d0BESTnb

When I try to make a make_recovery_tape with the command:
make_tape_recovery -x inc_entire=vg00 -l -v -a /dev/rmt/2mn

The following error message is returned:
7897+0 records in
7896+1 records out
I/O error
ERROR: /usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/dev/rmt/2mn bs=2k failed
to write LIF onto tape.
ERROR: Failed to generate LIF on tape .

Also, I tried using SAM to interactively backup files and got the error message: output file /dev/rmt/2m is not a valid device file for backup.

I have Ignite B.3.5.89 installed on HP-UX 11.0:
B5725AA B.3.5.89 HP-UX Installation Utilit
ies (Ignite-UX)

Any ideas? Thanks in advance! ==Robert

[melvyn burnard]

Well the backup run by SAM is fbackup, and this will not recognize the drive type returned as this is not a supported tape drive, so this will not work.

I also believe this will be the same problem with Ignite

[T. M. Louah]

.: try
.; insf -e -H 0/0/1/0.1.0
.; insf -e -H 0/0/1/0.15.0

.: I would recommend to upograde to latest Ignite & patch pax :

http://www.software.hp.com/products/IUX/download.html
Cheers
T??

[Robert Funk_1]

Thanks for your replies - still no luck. Will upgrade to latest Ignite-UX and patch PAX and see if I have better luck.

==Robert

[John Dvorchak]

Maybe this link will help:

http://www.unixguide.net/hp/faq/5.8.3.shtml

Good luck

[Frank Slootweg]

For the SAM/fbackup part:

As mentioned this is not supported/recognized/valid/ device for SAM/fbackup.
You can 'fool' SAM/fbackup by letting it think that it does a remote backup, i.e. specify a remote tape drive and give the hostname of the local system.
For this 'remote' backup to work, first make sure that (for root) remsh(1) to the local system works, i.e.

# remsh `hostname` date

This should *not* ask for a password and should display the date/time. If not, fix that first.

For the Ignite-UX part:

As far as I know, you can not boot from a Exabyte (i.e. the boot 'ROM' does not contain code for this device). If you can not boot from it, making a Ignite-UX tape for it makes no sense.