08-18-2010
If you have both the diskette drive and the tape drive on the same cable, is one of them set to master, and the other slave. (same rules as with IDE, but finding the jumpers may be a problem.)
The tape drive might show up in the BIOS list. Remove the diskette drive and try again. If it now shows the tape, and the error message is gone, either do without the diskette drive, or set the jumpers (or get a diskette cable with a twist in it).
Upgrading or changing the BIOS has nothing to do with the operating system.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Discussion started by: Minguccio75
3 Replies
2. UNIX for Dummies Questions & Answers
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies
3. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
4. Solaris
Hello,
I'm brand new to Sun/Solaris.
I have a Sun Blade 150, with SunOS 5.8.
I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies
5. Hardware
Hi All,
I installed Ubuntu10.04LTS after using it for some day , a problem started ,at system boot time error is coming
Bad BIOS checksum.Starting BIOS recovery.
checking for floppy.checking for CD is coming repeatedly but system is not cuming up.
After sometime output was also not... (0 Replies)
Discussion started by: arvindk.monu
0 Replies
6. Red Hat
Hey there,
i run 1: on my server (RHEL 6) and getting response that the libodbc is not installed. If i use yum for installation, it tells me, there is no package like this ( 2: ). Since in the description of Definiens is mentioned that the Run-time dependency is unixODBC (libodbc.so.1), I assume... (2 Replies)
Discussion started by: rkirsten
2 Replies
7. Shell Programming and Scripting
Why I get bad replace when using eval?
$ map0=( "0" "0000" "0")
$ i=0
$ eval echo \${map$i}
0000
$ a=`eval echo \${map$i}` !!!error happens!!!
bash: ${map$i}: bad substitution
How to resolve it ?
Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies
8. IP Networking
Hello
I am communicating with two devices using my computer over UDP protocol. The application is running fine. When I monitored the UDP traffic using Wireshark software, I found that there were too many Checksum errors.
Please find attached the png file showing this error. I am about to... (0 Replies)
Discussion started by: AustinCann
0 Replies
9. AIX
I am trying to use this command to eject the tape
mt -f /dev/rmt/0 unload
but it gives me error
mt -f /dev/rmt/0 unload
mt: 0511-575 unload is not a recognized subcommand.
Usage: mt Subcommand
Valid subcommands are:
weof
eof
fsf
bsf
... (5 Replies)
Discussion started by: filosophizer
5 Replies
10. UNIX for Beginners Questions & Answers
Hello Forum,
I'm issuing a one line bash command to look for the version of an installed application and saving the result to a variable like so:
APP=application --version
But if the application is not installed I want to return to my variable that the Application is not installed. So I'm... (2 Replies)
Discussion started by: greavette
2 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)