03-25-2008
hmmm, coming up every time the same *is* the default behavior. There must be something wrong with your machine.
I can only guess, but i suspect that something with the ODM is wrong and therefore the cfgmgr which runs at boot time tries (probably in vain) to correct that. Maybe the following helps: completely remove the tape drive from the ODM (use "rmdev -dl" generously) and make sure the tape drive shows up nowhere in the ODM (check CuAt and PdDv tables primarily). Then reboot the machine so that the drives configuration is written anew.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Following the below info:
----------------------------------------------------------------------------------
# SYNTAX: /dev/rmt/<unit number><density>
· Density: l, m, h, u/c (low, medium, high, ultra/compressed, respectively)
· BSD behavior: (optional) b
· no rewind: (optional) n
· For... (5 Replies)
Discussion started by: guest100
5 Replies
2. Solaris
hi all ,
i have just installed solris 9 on a sun 280R ,and i have appleid the recommended patches .
after the installation i have found that /dev/rmt/ directory is empty , i thought that was normal , so i attached my DDS4 external tape drive and treid :
devfsadm -C
devfsadm -v
reboot --... (1 Reply)
Discussion started by: ppass
1 Replies
3. AIX
Hi.
After the shutdown for SWIFT Alliance Server, tape backup process will be done. Unfortunately, I encountered this error message when I performed the database tape backup. The error was "/dev/rmt 0.1 block size is 0; variable; must be 1024 fixed. Consider reconfiguration through 'chdev'... (2 Replies)
Discussion started by: MariaLuisa
2 Replies
4. Solaris
Hi Guys,
I a newbie in Unix environment. I need a help to detect my external SCSI tape drive. I tried with command drvconfig;devlinks;tapes.. but when I go to /dev/rmt/, the directory is still empty.
I also tried with add_drv -v st but I'm getting this message
# add_drv -v st
exit... (8 Replies)
Discussion started by: akuslive
8 Replies
5. Solaris
I have an HP Proliant DL380 with Intel Processors that I recently loaded Solaris 10 with latest patches on it. I'm trying to do a ufsdump to an HP DAT 40 tape drive via SCSI, but I can't get it to do anything because /dev/rmt is empty. I've tried the following with luck:
touch /reconfigure,... (7 Replies)
Discussion started by: cvaughn
7 Replies
6. Hardware
# mt stat
HP DDS-4 DAT (Sun) tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
mt -f /dev/rmt/0mn erase
/dev/rmt/0mn: write protected or reserved.
Getting error while ufsdump ....
--- Dumping / to /dev/rmt/0mn ---
DUMP: Date... (1 Reply)
Discussion started by: vickyingle5
1 Replies
7. Solaris
# mt stat
HP DDS-4 DAT (Sun) tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
mt -f /dev/rmt/0mn erase
/dev/rmt/0mn: write protected or reserved.
Getting error while ufsdump ....
--- Dumping / to /dev/rmt/0mn ---
DUMP: Date... (5 Replies)
Discussion started by: vickyingle5
5 Replies
8. AIX
Hello,
I attached a tape drive to one of my partitions but i cannot find the device.
I run the command lsdev|grep rmt but i dont get anything in return.
When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Discussion started by: omonoiatis9
6 Replies
9. Solaris
Hi Peeps,
Got a very wierd problem (not a show stopper, but really annoying).
I've recovered a system for a DR test and by the looks of it every night (between 1030 and 11pm) it's creating a file called 1hbn in /dev/rmt and literally looks like it's utilizing all the remaining space in /... (2 Replies)
Discussion started by: callmebob
2 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 - 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)