Sponsored Content
Full Discussion: TAPE drive
Operating Systems HP-UX TAPE drive Post 302911470 by Randydog on Thursday 31st of July 2014 06:34:48 PM
Old 07-31-2014
I entered: tar -tvm /dev/rmt/0m the system returned: Tar: tape read error

Thanks in advance for you help

Last edited by rbatte1; 08-01-2014 at 05:33 AM.. Reason: Added ICODE tags
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tape drive install

I'm trying to install a tape drive on a compaq SCO OS 505. well I have gone through the mkdev tape comands and what have you yet no luck. when I reboot and do a simple tape rewind it gives me an error no such device etc.etc. IS there a diference in the xct0 and rct0 a the default? help.. (2 Replies)
Discussion started by: kikkin
2 Replies

2. Linux

Installing tape drive?

Hello. I have Redhat 8.0 on a laptop. Working good. I wanted to install the tape drive that is physically attached to it. The tape drive worked fine under Windows98SE. It's one of those parallel QIC-80 drives and I confirmed that it is supported by FTape. It appears that FTape might already... (0 Replies)
Discussion started by: RuralTurtle
0 Replies

3. UNIX for Dummies Questions & Answers

tape drive

Hi, I need to restore my tape backup, when I type "tape status" it gives; status : ready beginning-of-tape write-protected soft errors : 0 hard errors : 0 underruns : 3 but... (4 Replies)
Discussion started by: alisevA3
4 Replies

4. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How... (1 Reply)
Discussion started by: pernasivam
1 Replies

5. SCO

Tape Drive Configuration

Dear All, I have a tape drive which has worked for offer 3yrs properly on SCO Openserver Release = 3.2v5.0.5. I tried to clean it all invain. I did a fresh installation of unix of the same OS and did the configuration still didn't bear fruits. The tape is a scsi and the configuration is as... (4 Replies)
Discussion started by: njoroge
4 Replies

6. Solaris

Help with tape drive

Hey folks, Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes. I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V. As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly. ... (2 Replies)
Discussion started by: eddy_sysad
2 Replies

7. SCO

Tape Drive Logs?

I've recently been tasked with "refurbishing" an HP Proliant ML370 running SCO 5.0...something. This is primarily used for legacy support and is kept on a shelf for safe keeping. The scope of work includes hardware diagnostics and blowing the dust out. I have run HP diagnostics on the array,... (1 Reply)
Discussion started by: v1corp
1 Replies

8. UNIX for Dummies Questions & Answers

Quantum tape drive

Hi, Using Redhat 5.7. I have Quantum tape drive connected to the server. I am trying to install the Netbackup software. Just wondering how can I see the Quantum is connected to the server. is any command I run to see the tape drive is connected? I used to work on Solaris, I used to do... (1 Reply)
Discussion started by: samnyc
1 Replies
TM(4)							     Kernel Interfaces Manual							     TM(4)

NAME
tm - TM-11/TU-10 magtape interface DESCRIPTION
The files mt0, ..., mt7 refer to the DEC TU10/TM11 magtape. When closed it can be rewound or not, see below. If it was open for writing, two end-of-files are written. If the tape is not to be rewound it is positioned with the head between the two tapemarks. If the 0200 bit is on in the minor device number the tape is not rewound when closed. A standard tape consists of a series of 512 byte records terminated by an end-of-file. To the extent possible, the system makes it possi- ble, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps. The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files are named rmt0, ..., rmt7. Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given. During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A zero byte count is returned when a tape mark is read, but another read will fetch the first record of the new tape file. FILES
/dev/mt?, /dev/rmt? SEE ALSO
tp(1) BUGS
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward and backward record and file spacing and to write an EOF mark. TM(4)
All times are GMT -4. The time now is 09:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy