Note: This section does not allow for customized installations and does not address complex multiple tape drive issues. Take care not to violate your maintenance agreements.
Use the hinv command to see if the operating system recognized the tape drive at boot time. This is one of the most basic and critical tests to check hardware. (An output similar to the following is returned with the hinv command.)
Iris Audio Processor: version A2 revision 4.1.0 1 100 MHZ IP22 Processor FPU: MIPS R4010 Floating Point Chip Revision: 0.0 CPU: MIPS R4000 Processor Chip Revision: 3.0 On-board serial ports: 2 On-board bi-directional parallel port Data cache size: 8 Kbytes Instruction cache size: 8 Kbytes Secondary unified instruction/data cache size: 1 Mbyte Main memory size: 64 Mbytes Integral Ethernet: ec0, version 1 Integral SCSI controller 0: Version WD33C93B, revision D CDROM: unit 4 on SCSI controller 0 Disk drive: unit 1 on SCSI controller 0 Graphics board: Indy 24-bit Vino video: unit 0, revision 0, Indycam connected
If hinv does not report an attached tape drive, then your operating system cannot use the drive. You need to check the installation of the hardware. What you can do at this time depends on your maintenance support agreements.
Simple hardware checks are
If none of the above causes hinv to report the tape drive, then the most likely problem is faulty hardware. Contact your support provider.
If you are reasonably sure the tape drive is correctly installed on the computer, but your software does not seem to be able to use it, the tape device's SCSI address may have changed when other SCSI devices were added to your system.
The system assumes that if /dev/nrtape exists and appears to be a tape drive of some kind, then it does not need to remake the default tape drive links of /dev/tape, /dev/nrtape, and so on. It also assumes that the first tape drive that it finds is the main tape drive. It searches for devices starting at the highest SCSI ID numbers, so the tape device on SCSI ID 7 gets the default links before a tape device on SCSI ID 3.
The default tape drive for most commands is /dev/tape. If the tape drive installation proceeded correctly, you should have at least /dev/tape and /dev/nrtape special device files. You may have several others, depending on the type of tape drive.
The mt command can be used to confirm that /dev/tape exists and that the tape drive is responding. Output similar to the following from the mt status command confirms that
Controller: SCSI Device: ARCHIVE: Python 25601-XXX2.63 Status: 0x20262 Drive type: DAT Media : READY, writable, at BOT
The following output means that you have another process accessing the drive right now:
/dev/nrtape: Device or resource busy
The following output appears when a special device file does not exist:
/dev/nrtape: No such file or directory
The output when a device file exists, but no hardware is responding at that address, is
/dev/nrtape: No such device
If the hardware appears to be present, but /dev/tape does not appear to be valid, confirm the file links. Take the device unit number from hinv output
Tape drive: unit 3 on SCSI controller 0: DAT
In this example the device unit number is 3 (this is likely to be different on your system). Use the following ls command to confirm that /dev/tape is linked to the correct device (change the numeral 3 to the correct numeral for your drive):
ls -l /dev/tape /dev/mt/tps0d3*
crw-rw-rw- 2 root sys 23, 96 Sep 21 11:11 /dev/mt/tps0d3
crw-rw-rw- 2 root sys 23, 97 Jun 20 05:55 /dev/mt/tps0d3nr
crw-rw-rw- 2 root sys 23, 99 Jul 8 09:57 /dev/mt/tps0d3nrns
crw-rw-rw- 2 root sys 23,103 Jun 20 05:55 /dev/mt/tps0d3nrnsv
crw-rw-rw- 2 root sys 23,101 Jun 20 05:55 /dev/mt/tps0d3nrv
crw-rw-rw- 2 root sys 23, 98 Jun 20 05:55 /dev/mt/tps0d3ns
crw-rw-rw- 2 root sys 23,102 Jun 20 05:55 /dev/mt/tps0d3nsv
crw-rw-rw- 2 root sys 23,100 Jun 20 05:55 /dev/mt/tps0d3v
crw-rw-rw- 1 root sys 23,102 Jun 23 09:19 /dev/tape
The major and minor device numbers are the key here. They are the two numbers separated by a comma (23 and 102)
crw-rw-rw- 1 root sys 23,102 Jun 23 09:19 /dev/tape
Match these numbers with one of the lines from /dev/mt. In this example, it should match to
crw-rw-rw- 2 root sys 23,102 Jun 20 05:55 /dev/mt/tps0d3nsv
Compare the major and minor device numbers that are reported with /dev/tape and the ones reported for /dev/mt/tps0dX*. Is there a match? If not, remove /dev/tape and /dev/nrtape and run MAKEDEV as root from the /dev directory. Give the command
./MAKEDEV tapelinks
The MAKEDEV command can be verbose in describing what it is doing. Your output may differ in the number of devices made and the unit number. Once the MAKEDEV program has completed, go through these same checks again to be sure of success.
The MAKEDEV command does not let you choose which tape device to link to. You must make the links by hand if the MAKEDEV program does not default to the drive that you wish to use.
This covers the basic problems that administrators experience regarding missing tape drives. See the following reference pages for more information on the commands used in this section: mt(1), ls(1), hinv(1M). For more technical information about tapes, see mtio(7), tps(7M), or mt(1).
Often there is a quick and simple fix for an error message that is caused by a tape drive malfunction or the tape itself. Both recoverable and unrecoverable errors can be caused by something as basic as a dirty read/write head, a poorly tensioned tape, or a dropout, which is a physically bad spot on the tape. An EOT message can also mean that there is no data on the tape.
The following information covers some of the basic tape maintenance/performance functions that should be considered as factors that could either prevent future error conditions from occurring or act as aids in recovering from an existing error message: