make_tape_recovery

 
Jeff Hagstrom
Regular Advisor

make_tape_recovery

I ran make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/1mn and I get back an error that says this is not a rewind device. Why?

ERROR: This is not a no rewind device file.
7 REPLIES 7
G. Vrijhoeven
Honored Contributor

Re: make_tape_recovery

Jef,

/dev/rmt/0mn stands for an non rewinding tape drive.
if you issue the same command without the n at the and:
/dev/rmt/0m it should work.

Gideon
A. Clay Stephenson
Acclaimed Contributor

Re: make_tape_recovery

Hi Jeff:

Do an ls -l /dev/rmt/1mn. There are two possible answers. Someone overwrote/replaced 1mn with a regular file or 1mn is not a rewind device. The 'n' means nothing - look to see if the last two hex digits when or'ed with 0x40 are non-zero. e.g. the last 2 digits should be
40 (no rewind) or 0x80 + 0x40 = 0xc0 (Berkeley + no-rewind).

I also suggest that you use the mnb device as typically the Berkeley-style (as opposed to AT&T) norewind devices are iconsidered to be more robust.

Clay
If it ain't broke, I can fix that.
Sridhar Bhaskarla
Honored Contributor

Re: make_tape_recovery

Do these to make sure your tape drive is ok.

#tar cvf /dev/rmt/1m /etc/passwd
#mt -t /dev/rmt/1mn fsf 1
#mt -t /dev/rmt/1m rew

Even if you are having problems, try without mn. i.e just specify 1m.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
A. Clay Stephenson
Acclaimed Contributor

Re: make_tape_recovery

Hi again Jeff:

I completely misread your question. Make_tape_recovery is asking for a rewind device in which case the last 2 hex digits must NOT be 0x40.

Clay
If it ain't broke, I can fix that.
Jeff Hagstrom
Regular Advisor

Re: make_tape_recovery

The devise I used didn't have the "n" included in the string.

It was all my bosses fault, he put a tape in that was write protected.
Gerardo Mora
Advisor

Re: make_tape_recovery

Only put this:
make_tape_recovery -x inc_entire=vg00 -I -v
because the dafault tape address is /dev/rmt/0m and its not necesary
share to learn
Eileen Millen
Trusted Contributor

Re: make_tape_recovery

If you device is SCSI id 1, you should use
1mn
Ignite writes the LIF area to tape 1st.
Then it writes the archive.
I was unable to recover when I used 0m and not 0mn. SCSI id 0 is the default and does not need to be used.

Eileen