topic Re: tar on LTO3 drive in Operating System - HP-UX

tar on LTO3 drive

Sachin Patel — Thu, 10 Nov 2005 16:19:31 GMT

tar or dd fails with following message

# tar cvf /dev/rmt/72m mk_sf
a mk_sf 3 blocks
Tar: end of tape
Tar: to continue, enter device/file name when ready or null string to quit.

User entered a null name for next device file.

planck# ls -la mk_sf
-rwxrwxrwx 1 root sys 1162 Apr 8 2003 mk_sf

swlist -l fileset | grep stape
# PHKL_24221 1.0 SCSI Tape (stape) cumulative
# PHKL_29898 1.0 SCSI Tape (stape) cumulative

system information.
HP-UX B.11.00 U 9000/800 609359313 unlimited-user license

ioscan output
tape 54 0/12/0/0.4.0 stape CLAIMED DEVICE IBM ULT3580-TD3
/dev/rmt/c51t4d0BEST /dev/rmt/c51t4d0BESTb /dev/rmt/c51t4d0BESTn /dev/rmt/c51t4d0BESTnb
tape 72 0/12/0/1.3.0 stape CLAIMED DEVICE IBM ULT3580-TD3
/dev/rmt/72m /dev/rmt/72mn /dev/rmt/c52t3d0BEST /dev/rmt/c52t3d0BESTn
/dev/rmt/72mb /dev/rmt/72mnb /dev/rmt/c52t3d0BESTb /dev/rmt/c52t3d0BESTnb

Re: tar on LTO3 drive

Steven E. Protter — Thu, 10 Nov 2005 16:44:19 GMT

Hello Sachin,

maybe rewind the tape before writing the tar file?

Nicely formulaed question good detail.

SEP

Re: tar on LTO3 drive

Devender Khatana — Thu, 10 Nov 2005 16:45:33 GMT

HI,

Is the status same when the drive is powered on and the backup is fired?

What does "mt -t /dev/rmt/72mn rew" say ?

Is the drive firmware compatible/upto date?

HTH,
Devender

Re: tar on LTO3 drive

A. Clay Stephenson — Thu, 10 Nov 2005 16:58:26 GMT

Let's do something fairly low-level with an explicit block size and go from there:

dd if=/stand/vmunix bs=64k count=10 of=/dev/rmt/72m
STAT=${?}
echo "Status = ${STAT}"

I assume that you have made sure that the medium is not write-protected. Dd is a good test because it is lower-level than tar; be sure to post the ${?} value as well as any stdout/stderr messages. You can choose any other input file you like as long as it is at least 640KB in size. I intentionally did not choose /dev/zero because I wanted data that would essentially infinitly compress.

Re: tar on LTO3 drive

Sachin Patel — Thu, 10 Nov 2005 16:59:52 GMT

Hi steven
not so nice forgot to mention I did rewind. status, offline all works fine.
mt -f /dev/rmt/72m rewind
planck# mt -f /dev/rmt/72m status
Drive: IBM ULT3580-TD3
Format:
Status: [41114018] BOT online compression immediate-report-mode
File: 0
Block: 0

dd fails as well with different device file name

lanck# dd if=/home/sachin/ of=/dev/rmt/72m
I/O error
1+0 records in
0+1 records out
planck#
planck# dd if=/home/sachin/ of=/dev/rmt/c52t3d0BEST
I/O error
1+0 records in
0+1 records out
planck# dd if=/home/sachin/mk_sf of=/dev/rmt/c52t3d0BEST
I/O error
1+0 records in
0+1 records out

someone in programming says there is permission problem.

planck# grep 13 /usr/include/sys/errno.h

#define EACCES 13 /* Permission denied */

thanks
Sachin

Re: tar on LTO3 drive

Sachin Patel — Thu, 10 Nov 2005 17:03:01 GMT

Mr Clay
Here is output. Yes I personally check that tape is not write protected.

dd if=/stand/vmunix bs=64k count=10 of=/dev/rmt/72m
I/O error
1+0 records in
0+1 records out
# STAT=${?}
# echo "Status= ${STAT}"
Status= 2

Re: tar on LTO3 drive

Devender Khatana — Thu, 10 Nov 2005 22:28:18 GMT

Hi,

The I/O error indicates that either the drive or the media inside is faulty. The easiest confirmation can be done by putting this media in other similar drive and put another working media in this drive and then retry the backup operation.

HTH,
Devender

Re: tar on LTO3 drive

A. Clay Stephenson — Thu, 10 Nov 2005 23:41:08 GMT

Someone is programming is wrong, you are seeing errno 5 which is an I/O error. I suspect that you have a tape drive problem or it may simple be bad or improper cabling or termination.

Re: tar on LTO3 drive

KVK — Fri, 11 Nov 2005 00:43:30 GMT

It's look like H/W issue . Better use the new or well known working tape cartridge to check the TAPE mechanisms .

I faced the same error with DLT8000 replacing the TAPE drive has resolved the issue

Try to eliminate the H/W part .No need to check from S/W side

Re: tar on LTO3 drive

Sachin Patel — Fri, 11 Nov 2005 09:17:26 GMT

Problem is fixed. Someone put LTO1 tape on that LTO3 drive. As soon as we put LTO2 tape it started working.

Thanks
Sachin