topic make_tape_recovery device failed in Operating System - HP-UX

make_tape_recovery device failed

Andrew Pollard — Tue, 19 Oct 2004 08:11:12 GMT

Hi,
I have started trying to do a make_tape_recovery on a RP8400 using an LTO1. I am receiving the error "This is not a character special device" "Check tape device failed". A make_tape_recovery on a DDS tape would use /dev/rmt/0mn, would I still use /dev/rmt/0mn with LTO1 or just use /dev/rmt/0m or is this not causing my problem?

Thanks

Andrew Pollard

Re: make_tape_recovery device failed

Borislav Perkov — Tue, 19 Oct 2004 08:17:06 GMT

Hi,
you need norewind tape device to use with IgniteUX because tape should be bootable.
Regards,
Borislav

Re: make_tape_recovery device failed

Borislav Perkov — Tue, 19 Oct 2004 08:22:11 GMT

Hi again.
Can you tell me LTO is connected with FC or SCSI?

Re: make_tape_recovery device failed

Andrew Pollard — Tue, 19 Oct 2004 08:26:14 GMT

Hi,

The LTO is connected using scsi.

Re: make_tape_recovery device failed

Steven E. Protter — Tue, 19 Oct 2004 08:28:34 GMT

Maybe this:

insf -e

This will recreate the device drivers, just in case you've accidentally overwritten your tape device driver.

You should also look at the permissions on the device driver ll /dev/rmt/0m or whatever device your script uses.

SEP

Re: make_tape_recovery device failed

Borislav Perkov — Tue, 19 Oct 2004 08:30:04 GMT

Than you can boot from it.
Try then to recreate the device files with
insf -e
command
Regards

Re: make_tape_recovery device failed

Bharat Katkar — Tue, 19 Oct 2004 08:34:41 GMT

Hi Andrew,
Probably your /dev/rmt/0mn is not a character device file. You should get the following output with the file command.

# file /dev/rmt/0mn
/dev/rmt/0mn : character special (xx/y)

If not then it's a normal file. Delete it and recreate the special file by using "insf -e" command as told earlier.

Hope that helps.
Regards,

Re: make_tape_recovery device failed

Andrew Pollard — Tue, 19 Oct 2004 10:03:50 GMT

Hi,

After reading all the suggestions and doing more investigation, it seems that "Too many hands in the cookie jar" has caused human error and not device file error.

I do believe that the problem is fixed. Thanks for all the suggestions and help on this problem. 10 points all around!!

Thanks

Andrew