Tape drive error

[UniRock]

#ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
tape 2 1/0/4/1/0.3.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/2m /dev/rmt/c6t3d0BEST
/dev/rmt/2mb /dev/rmt/c6t3d0BESTb
/dev/rmt/2mn /dev/rmt/c6t3d0BESTn
/dev/rmt/2mnb /dev/rmt/c6t3d0BESTnb

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

Hi Again,

This particular tape drive is working fine when attached to another server.
I have tried rmsf and then insf also but no use.

Any ideas as to what shall I do?

Thanx in advance....
RKK

[sachit patil]

Hi,
You have log the call with HP to replace it.


On another server are u tried for backup using tar
#tar -cvf /dev/rmt/2m /stand

[Ganesh.A]

Hi RKK,

I hope it is an external tape drive.As it works fine with another m/c means drive is OK.

1. Check the Cable, try changing the SCSI ID, if possible.

2. Run ioscan -fn & insf -e

3. if doesnot work, remove the drive and do ioscan,check status, reattach the device rmeove/recreate deivce files..also check with lssf to ensure that it is Ok.

4. For mostly it looks like the SCSI Terminator that is attached with the device is defective/not present.Pls Check the SCSI Terminatior by swapping from the working one.

[Jeeshan]

HI

try to run this

#mt -t /dev/rmt/2m

and if you want to rewind the tape, use

#mt -t /dev/rmt/2mnb

[UniRock]

Hi All,

Now that somehow the ignite is started (tape being detected), its NOT getting completed (HANGED in between). Its showing "SLEEP" in "top" command.
Below is the o/p and all files except one has 600 permission. Its not like this in other servers.
#################################

NOTE: File: /var/tmp/tmp_cfg_file is not world-readable, this may cause
clients to fail to read it during an installation.
NOTE: File: /var/tmp/tmp_cfg_file is not world-readable, this may cause
clients to fail to read it during an installation.
* Writing boot LIF to tape
136748+0 records in
136748+0 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/2mn -t n -s
local -n 2008-04-17,15:56 -m t -w
/var/opt/ignite/recovery/2008-04-17,15:56/recovery.log -u -R -g
/var/opt/ignite/recovery/2008-04-17,15:56/flist -a 61512030

* Preparing to create a system archive.

* Archiving contents of sigma via tar image to local device/dev/rmt/2mn.



#################################

#ll /var/opt/ignite/recovery/2008-04-17,15:56
total 222192
-rw-r--r-- 1 root sys 3647 Apr 17 16:01 archive_cfg
-rw------- 1 root sys 17 Apr 17 15:56 archive_content
-rw------- 1 root sys 473 Apr 17 15:57 control_cfg
-rw------- 1 root sys 113713782 Apr 17 16:01 flist
-rw------- 1 root sys 5231 Apr 17 16:02 recovery.log
-rw------- 1 root sys 7936 Apr 17 15:57 system_cfg
-rw------- 1 root sys 0 Apr 17 16:01 tape


What should I do now?
-RKK
--RKK

[Torsten.]

Are you really sure it hangs?

Next messages should be

"* Creation of system archive complete."

It takes some time ... 30min is not too much.

[UniRock]

#tail -20 recovery.log
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/2mn -t n -s
local -n 2008-04-17,15:56 -m t -w
/var/opt/ignite/recovery/2008-04-17,15:56/recovery.log -u -R -g
/var/opt/ignite/recovery/2008-04-17,15:56/flist -a 61512030

* Preparing to create a system archive.

* Archiving contents of sigma via tar image to local device/dev/rmt/2mn.
* Creation of system archive complete.

Unhandled exception; exiting!
Exception kind is status,value is 11. Thread 1 .
sh: 642 Abort(coredump)
WARNING: swlist returned 34304
* Cleaning up old configuration file directories


======= 04/17/08 17:06:04 IST make_tape_recovery completed successfully!

#######################

#pwd
/var/opt/ignite/recovery/2008-04-17,15:56
sigma#
sigma#
sigma#ll
total 222224
-rw-r--r-- 1 root sys 3647 Apr 17 16:01 archive_cfg
-rw------- 1 root sys 17 Apr 17 15:56 archive_content
-rw------- 1 root sys 473 Apr 17 15:57 control_cfg
-rw------- 1 root sys 113713782 Apr 17 16:01 flist
-rw------- 1 root sys 9941 Apr 17 17:06 manifest
-rw------- 1 root sys 5548 Apr 17 17:06 recovery.log
-rw------- 1 root sys 7936 Apr 17 15:57 system_cfg
-rw------- 1 root sys 0 Apr 17 16:01 tape

#########################

Hi All,

Torsten, it is completed, but can I rely on today's backup????
Whats those errors above?
And why is these file have 600 permission only bcoz everywhere else the permission is 644.
:(

--RKK