10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. UNIX for Dummies Questions & Answers
Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies
9. SCO
i have a sco-unix box. I want to access tape driver (sdt-700) on scsi. but i dont know how? where is this device file for tape driver is located? how do i access this tape? pls help this fool. (1 Reply)
Discussion started by: mchitrakar
1 Replies
10. 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
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)
DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)
