09-20-2007
You didn't mention what changed on the server? New disk installed, new controller installed, patches installed, new SDT10000 driver installed...something caused the change.
Taking a guess, I would assume that the controller use to be 0 and now is 1
(0,0,6,0) versus (1,0,6,0) - you should still be able to access the tape drive - just have to find the correct device. What did you use to use to access the drive before? Try changing the device from 0 to 1 in those commands.
10 More Discussions You Might Find Interesting
1. Red Hat
Hi...
this is the situation.
I have a server with redhat Advance Server 3 and the operating system is installed in /dev/sda disk... when i include new Luns dinamically they take the following special files /dev/sdb and /dev/sdc.... ok.. until now is everything ok... but the problem begins... (2 Replies)
Discussion started by: lenux78
2 Replies
2. UNIX for Dummies Questions & Answers
I am a beginer in unix .
I would like to know what is the command in orser to change NIC and Device NO (1 Reply)
Discussion started by: Ilias Kappatos
1 Replies
3. 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
4. Shell Programming and Scripting
Hi,
I'm struggling to write a script to do the following,
-will go through each line in the file
-in a specific character positions, changes
the value to a new value
-These character positions are fixed througout the file
-----------------------
e.g.: file1.sh will have the following 3... (4 Replies)
Discussion started by: vini99
4 Replies
5. AIX
Hi
how to change the primary dump device in a vio server ?
$ ioslevel
2.2.0.11-FP-24 SP-01
$ oem_setup_env
# sysdumpdev -l
primary /dev/sysdumpnull
secondary /dev/hd6
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump... (1 Reply)
Discussion started by: newtoaixos
1 Replies
6. Programming
we asked to create a sender and receiver for a signals. sender knows his receiver by it's(receiver) PID .... my question is if i go to other computer and run my program will the pid chages than the first pid i got from old computer? (2 Replies)
Discussion started by: fwrlfo
2 Replies
7. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
8. 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
9. Shell Programming and Scripting
I'm new to Linux (Ubuntu 16.04), and very new to BASH scripting. I have a Numato 8-channel USB GPIO device, which is a DAQ that appears in the system as a serial port. In Linux it appears as ttyACM0. I can easily manipulate a GPO with, for example:
echo "gpio set 7" > /dev/ttyACM0
...followed... (12 Replies)
Discussion started by: Chalk-X
12 Replies
10. OS X (Apple)
Mac Version 10.15.2 (macOS Catalina)
Does anyone know how to change the name of a connected bluetooth device from the command line on macOS?
I am having trouble with various bluetooth devices which I cannot get the "rename" option in the GUI to "save" properly and so I cannot rename a few... (0 Replies)
Discussion started by: Neo
0 Replies
TM(4) Kernel Interfaces Manual TM(4)
NAME
tm - TM-11/TE-10 magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
# Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250
# controller. For more details, see /sys/pdpuba/tm.c.
NTM tm_drives # TM11
AVIVTM YES # AVIV 800/1600/6250 controller
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
tm ? 172520 224 5 tmintr # tm11 driver
major device number(s):
raw: 7
block: 1
minor device encoding:
bits 0003 specify TS drive
bit 0004 specifies no-rewind operation
bits 0030 specify recording density:
0000: 800BPI
0010: 1600BPI (AVIVTM and some other controllers)
0020: 6250BPI (AVIVTM only)
DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive interface as described in mtio(4). The standard DEC tm-11 operates only at 800
bpi. Other controllers of this type may also allow operation at 1600 bpi, under software control or by switching manually.
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), ht(4), ts(4), mt(4), dtab(5), autoconfig(8)
DIAGNOSTICS
te%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.
te%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.
te%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.
te%d: hard error bn%d er=%b. A tape error occurred at block bn; the tm error register is 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.
te%d: lost interrupt. A tape operation did not complete within a reasonable time, most likely because the tape was taken off-line during
rewind or lost vacuum. The controller should, but does not, give an interrupt in these cases. The device will be made available again
after this message, but any current open reference to the device will return an error as the operation in progress aborts.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
3rd Berkeley Distribution January 28, 1988 TM(4)