05-13-2009
IBM Ultrium are not 100% supported on HP-UX. Check out itrc
So that can be the cause of your problem.
You maybe need firmware update or a patch, if available at all.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have problem detecting my tape drive.
In SAM, once I click on the either Automated Backups or Interactive Backup and Recovery icon, the screen will prompt searching for device and ..... nothing appears in the list.
In the end, I have the kill the SAM process and reboot the system and... (1 Reply)
Discussion started by: jennifer
1 Replies
2. UNIX for Dummies Questions & Answers
Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies
3. UNIX for Advanced & Expert Users
Hi,
1- how can I find my tape device on my server ?
2-I have a backup of a data base distributed on several file system. How using tar -x can I extract from tape to each apropriate file system ? For exemple the data base was on /d1 ; /d2 ; and /d3. Now I cd to which /dn and use tar -xvf /dev/nm0... (0 Replies)
Discussion started by: big123456
0 Replies
4. Solaris
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Discussion started by: spacewalker
4 Replies
5. Solaris
Hi to all,
I´m recovering a Solaris box trough jumpstart with restore of a flash archive on tape. The tape device is recognized by OBP in probe-scsi-all and by the operating system that is instaled on that box where i want to restore flar as /dev/rmt/2. But when a i boot with " (0) ok boot net -... (0 Replies)
Discussion started by: spacewalker
0 Replies
6. UNIX for Dummies Questions & Answers
I disconected external device which was configured as rmt0. When I connect it again and run cfgmgr device name has changed (internal drive which was rmt1 is now rmt0 and external drive was rmt0 and is rmt1) and I dont know how to back it out. The thing is that for all backups I use new modell... (2 Replies)
Discussion started by: fraydey
2 Replies
7. Solaris
After we upgraded one PW450 machine from (networker 7.2 & solaris 9) to (networker 7.4 and solaris 10) through scratch installation
Only one of two HP tape drives is shown in inquire command
And we are getting strange logs in messages file (attached)
For 2nd drive 1cbn character specific file... (4 Replies)
Discussion started by: kashif_islam
4 Replies
8. AIX
Hi All,
After (by accident) closing a session that ran a restore command I can not access the tape drive anymore.
I get the following error:
# tctl -f /dev/rmt0 rewind
/dev/rmt0: Resource temporarily unavailable
But I cannot find any processes associated with the tape device:
# ps... (2 Replies)
Discussion started by: petervg
2 Replies
9. AIX
Hi all
The situation is as follows:
We need to take an mksysb image from an AIX 6.1 server. From some reason (irrelevant to this discussion) this server does not have access to a local CD-ROM or a tape drive. We do have another server with AIX 6.1 (but different technology level) which got access... (1 Reply)
Discussion started by: abohmeed
1 Replies
10. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, 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 last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
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
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
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 count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
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 explicitly.
HT(4)