topic Re: make_tape_recovery FAILURE in Operating System - HP-UX

make_tape_recovery FAILURE

pranay142 — Thu, 19 May 2016 16:17:08 GMT

make_tape_recovery FAILED.Fix the problem and restart the tape by executing /opt/sr/bin/srtape from the command line.

======= 05/02/16 12:00:00 BEGIN System Recovery Tape Session

Executing: /opt/ignite/bin/make_tape_recovery -vI -x inc_entire=vg00 -a /dev/rmt/0mn

======= 05/02/16 12:00:06 EDT Started /opt/ignite/bin/make_tape_recovery.
(Mon May 02 12:00:06 EDT 2016)
@(#)Ignite-UX Revision C.7.12.519
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA1103/ignite/src@82875 Last Modified: 2011-01-20
21:10:40 +0530 (Thu, 20 Jan 2011)

* 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/c2t6d0 /dev/dsk/c1t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /usr 2
/dev/vg00/lvol5 /var 2
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /tmp 2
/dev/vg00/lvol8 /home 2
0 v /dev/vg01 0x02 /dev/dsk/c21t0d0 /dev/dsk/c25t0d0 /dev/dsk/c23t0d0 /dev/dsk/c27t0d0
/dev/vg01/lvol1 /dwtredo 0
0 v /dev/vg02 0x03 /dev/dsk/c23t1d2 /dev/dsk/c27t1d2 /dev/dsk/c25t1d2 /dev/dsk/c21t1d2
/dev/vg02/lvol1 /dwt01 0
0 v /dev/vg03 0x04 /dev/dsk/c21t0d1 /dev/dsk/c25t0d1 /dev/dsk/c23t0d1 /dev/dsk/c27t0d1
/dev/vg03/lvol1 /fistredo 0
0 v /dev/vg04 0x05 /dev/dsk/c23t0d6 /dev/dsk/c27t0d6 /dev/dsk/c25t0d6 /dev/dsk/c21t0d6
/dev/vg04/lvol1 /fist01 0
0 v /dev/vg05 0x06 /dev/dsk/c23t0d7 /dev/dsk/c27t0d7 /dev/dsk/c25t0d7 /dev/dsk/c21t0d7
/dev/vg05/lvol1 /fist02 0
0 v /dev/vg06 0x07 /dev/dsk/c23t1d0 /dev/dsk/c27t1d0 /dev/dsk/c25t1d0 /dev/dsk/c21t1d0
/dev/vg06/lvol1 /hype01 0
0 v /dev/vg07 0x08 /dev/dsk/c23t1d1 /dev/dsk/c27t1d1 /dev/dsk/c25t1d1 /dev/dsk/c21t1d1
/dev/vg07/lvol1 /mdmd01 0
0 v /dev/vg08 0x09 /dev/dsk/c23t1d3 /dev/dsk/c27t1d3 /dev/dsk/c25t1d3 /dev/dsk/c21t1d3
/dev/vg08/lvol1 /dwd01 0
0 v /dev/vg09 0x0a /dev/dsk/c23t1d4 /dev/dsk/c27t1d4 /dev/dsk/c25t1d4 /dev/dsk/c21t1d4
/dev/vg09/lvol1 /fisd01 0
0 v /dev/vg10 0x0b /dev/dsk/c23t0d3 /dev/dsk/c27t0d3 /dev/dsk/c25t0d3 /dev/dsk/c21t0d3
/dev/vg10/lvol1 /u00e 0
0 v /dev/vg11 0x0c /dev/dsk/c23t0d4 /dev/dsk/c27t0d4 /dev/dsk/c25t0d4 /dev/dsk/c21t0d4
/dev/vg11/lvol1 /u01 0
0 v /dev/vg12 0x0d /dev/dsk/c23t0d5 /dev/dsk/c27t0d5 /dev/dsk/c25t0d5 /dev/dsk/c21t0d5
/dev/vg12/lvol1 /u02 0
0 v /dev/vg13 0x0e /dev/dsk/c23t1d5 /dev/dsk/c27t1d5 /dev/dsk/c25t1d5 /dev/dsk/c21t1d5
/dev/vg13/lvol1 /misc_backup 0
0 v /dev/vg14 0x0f /dev/dsk/c23t1d6 /dev/dsk/c27t1d6 /dev/dsk/c25t1d6 /dev/dsk/c21t1d6
/dev/vg14/lvol1 /dwbacktemp 0
0 v /dev/vg25 0x40 /dev/dsk/c21t2d4 /dev/dsk/c25t2d4 /dev/dsk/c23t2d4 /dev/dsk/c27t2d4
/dev/vg25/lvol1 /u100_test 0
0 v /dev/vg26 0x41 /dev/dsk/c21t2d5 /dev/dsk/c25t2d5 /dev/dsk/c23t2d5 /dev/dsk/c27t2d5
/dev/vg26/lvol1 /u101_test 0
0 v /dev/vg27 0x42 /dev/dsk/c21t2d6 /dev/dsk/c25t2d6 /dev/dsk/c23t2d6 /dev/dsk/c27t2d6
/dev/vg27/lvol1 /u102_test 0
0 v /dev/vg28 0x43 /dev/dsk/c21t2d7 /dev/dsk/c25t2d7 /dev/dsk/c23t2d7 /dev/dsk/c27t2d7
/dev/vg28/lvol1 /u103_test 0
0 v /dev/vg40 0x31 /dev/dsk/c21t3d3 /dev/dsk/c25t3d3 /dev/dsk/c23t3d3 /dev/dsk/c27t3d3
/dev/vg40/lvol1 /u204e_test 0
0 v /dev/vg41 0x32 /dev/dsk/c21t3d2 /dev/dsk/c25t3d2 /dev/dsk/c23t3d2 /dev/dsk/c27t3d2
/dev/vg41/lvol1 /u203e_test 0
0 v /dev/vg42 0x33 /dev/dsk/c21t3d1 /dev/dsk/c25t3d1 /dev/dsk/c23t3d1 /dev/dsk/c27t3d1
/dev/vg42/lvol1 /u202e_test 0
0 v /dev/vg43 0x35 /dev/dsk/c21t3d0 /dev/dsk/c25t3d0 /dev/dsk/c23t3d0 /dev/dsk/c27t3d0
/dev/vg43/lvol1 /u201e_test 0
0 v /dev/vg509 0x34 /dev/dsk/c23t2d1 /dev/dsk/c27t2d1 /dev/dsk/c25t2d1 /dev/dsk/c21t2d1
/dev/vg509/lvol1 /dwbackup 0
0 v /dev/vg600 0x21 /dev/dsk/c23t2d2 /dev/dsk/c27t2d2 /dev/dsk/c25t2d2 /dev/dsk/c21t2d2
/dev/vg600/lvol1 /u01e 0
0 v /dev/vgswap 0x4c /dev/dsk/c21t2d0 /dev/dsk/c25t2d0 /dev/dsk/c23t2d0 /dev/dsk/c27t2d0
/dev/vgswap/lvol1
0 v /dev/vg44 0x3a /dev/dsk/c21t0d2 /dev/dsk/c23t0d2 /dev/dsk/c25t0d2 /dev/dsk/c27t0d2
/dev/vg44/lvol1 /u205e_test 0
0 v /dev/vg45 0x4a /dev/dsk/c23t1d7 /dev/dsk/c21t1d7 /dev/dsk/c27t1d7 /dev/dsk/c25t1d7
/dev/vg45/lvol1 /u104e_test 0

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.

======= 05/02/16 12:00:16 EDT make_tape_recovery completed unsuccessfully

make_tape_recovery FAILED. Sending email with the logfile.

Output of some other commands :

ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 0 0/12/0/0.3.0 stape NO_HW DEVICE QUANTUM DLT8000
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c3t3d0BESTn
/dev/rmt/0mb /dev/rmt/c3t3d0BEST /dev/rmt/c3t3d0BESTnb
/dev/rmt/0mn /dev/rmt/c3t3d0BESTb

#grep -i dev /etc/rc.config.d/srconf
# The tape drive device file to use for make_tape_recovery.
# Make sure this is a no-rewind device!!
MTR_TAPE_DRIVE="/dev/rmt/0mn"

Please suggest what could the possible reason for failure.

Re: make_tape_recovery FAILURE

Patrick Wallek — Thu, 19 May 2016 20:44:43 GMT

Your tape drive is dead, powered off, or not connected to your system.

Your 'ioscan' output show that the state of the device is NO_HW. That means that the system can't talk to the device.

You'll need to check at a hardware level or fix the device and then rerun your make_tape_recovery command.

Another way to check the device status is:

# mt -f /dev/rmt/0mn status

Re: make_tape_recovery FAILURE

pranay142 — Thu, 19 May 2016 23:11:53 GMT

Hi Patrick,

Thanks for your reply. The out of mt -f command says no such file or device.

#mt -f /dev/rmt/0mn status
on tape open: No such device or address

Re: make_tape_recovery FAILURE

Bill Hassell — Fri, 20 May 2016 03:12:12 GMT

What does this command show?

ioscan -knfCtape

Re: make_tape_recovery FAILURE

Patrick Wallek — Fri, 20 May 2016 13:12:14 GMT

As I mentioned in my original post, your tape device is dead, broker, powered off or not attached to the system.

The 'ioscan' that you included in your original post, shown below, shows that the device is in a NO_HW state. That means that HP-UX can NOT communicate with it. Until the device is fixed you will NOT be able to communicate with it.

Go to your system and make sure the device is turned on, is plugged into the system, and does NOT have any fault lights on it.

When you do an 'ioscan' and can see the device in a CLAIMED state, only then will you be able to use it.

Re: make_tape_recovery FAILURE for rush

Bill Hassell — Fri, 20 May 2016 15:31:54 GMT

Although ioscan shows the tape drive reponding to an ID request (CLAIMED, C1537A), it is not reporting any status (mt command). If you can power cycle the drive (not internal), try that. Otherwise for an internal drive, try a complete shutdown and power cycle. If this doesn't bring the drive back, you'll likely need to replace the drive.

Re: make_tape_recovery FAILURE

pranay142 — Mon, 23 May 2016 16:23:07 GMT

Thanks Patrick,

We have a cron that runs on 2nd of every month, i'll get it fixed before that and see if it goes through successfully.

Re: make_tape_recovery FAILURE for rush

pranay142 — Mon, 23 May 2016 16:24:38 GMT

Thanks Bill,

For rush i'll get the drive power cycled and in case it didn't work i'll go for a complete shutdown and power cycle.

Re: make_tape_recovery FAILURE

pranay142 — Tue, 28 Jun 2016 18:21:41 GMT

Hi Patrick,

I got the tape drive replaced and now the status of tape drive is claimed, however it is not able to detect any tape.

#insf -H 0/12/0/0.0.0
#
#ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 1 0/12/0/0.0.0 stape CLAIMED DEVICE QUANTUM DLT8000
#

When this did not work I rebooted the server but no use.

Please suggest.

Thanks in advance.

Re: make_tape_recovery FAILURE

Bill Hassell — Tue, 28 Jun 2016 20:40:02 GMT

>> the status of tape drive is claimed, however it is not able to detect any tape.

I see the tape drive in the ioscan you provided but I have no idea what you mean by 'detecting a tape'. Did you use the mt command to report the status of the drive? Or did you run a complicated backup program to test the drive?