Sponsored Content
Operating Systems SCO Tape Status shows 2 Hard errors and 5 Underruns on new tape Post 302186887 by psytropic on Friday 18th of April 2008 10:47:32 AM
Old 04-18-2008
Thank you guys for your responses. It seems I needed to clean the drive more than once. I just sat there inserting the cleaning tape, letting it eject, and doing it again. I did it about 7 times and now the backups work again. I think it's time for a new drive.
 

10 More Discussions You Might Find Interesting

1. 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... (0 Replies)
Discussion started by: josramon
0 Replies

2. UNIX for Advanced & Expert Users

Space free on tape /delete a single file on tape

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

3. UNIX for Dummies Questions & Answers

Mounting DLT tape and to backup file to tape

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

4. UNIX for Dummies Questions & Answers

mt command shows /dev/tape: inappropriate ioctl for device

Hello guys, on my Red Hat machine the /bin/mt status command gives the output dev/tape: inappropriate ioctl for device. This messages comes up after the Server has been rebooted. Anybody an idea? Thx masterofdesaster (8 Replies)
Discussion started by: masterofdesaste
8 Replies

5. Solaris

Hard Error:DAT Tape Drive

Well I have just added new tape drive to my server (lto) However I am getting few errors in using it. I have checked status with #iostat -En : giving me few hard errors, few soft errors and execution error. Also tape status is not visible as "no sense" its coming as "no additional sense". I... (5 Replies)
Discussion started by: saurabh84g
5 Replies

6. AIX

Tape status command

We sometime run backups to tape in the background using the cron. Is there a command that will show me how fast the information is being written and or how much data has been written? I know if we enter the information via the command prompt or smit it shows the speed and amount written. (2 Replies)
Discussion started by: daveisme
2 Replies

7. AIX

Tape drive write status

Is there a command on AIX that will show the write status of a tape? We have sysback running via a cron job backing up to a tape. I want to be able to check the progress of the backup. I need a command that will show ne the progress of the backup or the speed of the backup while it is taking... (5 Replies)
Discussion started by: daveisme
5 Replies

8. UNIX for Dummies Questions & Answers

Check tape drive status on HP-UX

Hi all, We have an ESL tape library with legato networker software. From GUI - networker administrator, i can see that 3 of our tape drives are in service mode. How can i view the same thing by issuing commands in HP-UX. Thanks in advance! (1 Reply)
Discussion started by: *Jess*
1 Replies

9. AIX

Ejecting tape on AIX & Some Tape commands

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. Shell Programming and Scripting

Handling tape errors in script

AIX 7.1 Here's the script #!/bin/ksh find . -print > filelist.txt backup -ivqf/dev/rmt0 < filelist.txt > backup.log if ; then echo "Backup to tape failed!" >> backup.log else echo "Backup to tape successfull!" >> backup.log fi mail -v -s "Backup report" maillist < backup.log ... (4 Replies)
Discussion started by: landog
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)
All times are GMT -4. The time now is 05:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy