Tape drive issues with SCO 5.0.5!!! Post: 93242

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Tape Drive SCO 5.0.7

Hi guys I had a system running 5.0.6 , we upgraded it to 5.0.7 everything was fine till i try to do a test backup. The error was cannot open (cannot open /dev/xct0 no such file or directory)what i did was, removed the tape , reboot the system and the try to install it again, but its...

2. UNIX for Dummies Questions & Answers

second tape drive on SCO 505

I need to run a back up that will take more than one tape. What is the command that will continue the back up on to a second tape drive. the first is /dev/rStp0 second is /dev/rStp1. Anyone?

3. UNIX for Dummies Questions & Answers

SCO 5.0.5 Tape Drive errors

hi guys, I.m trying to remove and add a new tape drive by using the mkdev tape command and when i try to update the Kernel this is what i'm getting, i386ld: Symbol Sdsk_no_tag in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/blad/s pace.o is multiply defined. First defined in...

4. SCO

SCO hard drive with data - No SCO computer

Situation - i have an IDE hard drive from server apparently running SCO last used in 2003. No access to computer it was formerly in. I need to access the drive to pull off data files from a billing/scheduling program. I have no SCO machine or access to one atm. Have some limited Linux...

5. SCO

SCO Openserver Release 5 and HP VS160 Tape Drive

Hi, Does anyone know if a HP VS160 Tape drive will work with SCO Openserver Release 5? If so what driver would it use? alad, cha? Thanks John

6. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How...

7. Solaris

Help with tape drive

Hey folks, Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes. I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V. As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly. ...

8. SCO

SCO 5.0.7 Tape Drive swap

Our tape drive died and I installed a newer Quantum DAT72 drive in it's place with the same SCSI ID. It still works, but with one major flaw, the system will lock up if I try to upgrade BackupEDGE or view NFS settings in scoadmin. I get a Transition to ready failure on ha=0* message when the...

LEARN ABOUT BSD

ht

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)