The SCSI Port driver supplies only one compatible ID, one of the variable-sized generic type codes from the previous table. For example, the compatible ID for a disk drive is as follows: GenDisk. The generic identifier is used in INF files for SCSI devices more than any other, because SCSI drivers. The Vista drivers should work for the Windows 7 installation. Your SCSI device is probably your optical drive, unless you have a high performance hard drive in your laptop. The RAID host controller is a system for attaching multiple hard drive together. Unless you have multiple hard drives in.

This file contains brief information about the SCSI tape driver.The driver is currently maintained by Kai Mäkisara (

Discuss: Tandberg SLR 5 - tape drive - SLR - SCSI Series Sign in to comment. Be respectful, keep it civil and stay on topic. We delete comments that violate our policy, which we encourage you to. Tape drives do not function on RAID controllers. Multi-channel RAID / SCSI controllers should be installed with the SCSI driver in order to work with a tape drive. Slot where the controller card is installed.

Last modified: Tue Feb 9 21:54:16 2016 by kai.makisara


The driver is generic, i.e., it does not contain any code tailoredto any specific tape drive. The tape parameters can be specified withone of the following three methods:

1. Each user can specify the tape parameters he/she wants to usedirectly with ioctls. This is administratively a very simple andflexible method and applicable to single-user workstations. However,in a multiuser environment the next user finds the tape parameters instate the previous user left them.

2. The system manager (root) can define default values for some tapeparameters, like block size and density using the MTSETDRVBUFFER ioctl.These parameters can be programmed to come into effect either when anew tape is loaded into the drive or if writing begins at thebeginning of the tape. The second method is applicable if the tapedrive performs auto-detection of the tape format well (like someQIC-drives). The result is that any tape can be read, writing can becontinued using existing format, and the default format is used ifthe tape is rewritten from the beginning (or a new tape is writtenfor the first time). The first method is applicable if the drivedoes not perform auto-detection well enough and there is a single“sensible” mode for the device. An example is a DAT drive that isused only in variable block mode (I don’t know if this is sensibleor not :-).

The user can override the parameters defined by the systemmanager. The changes persist until the defaults again come intoeffect.

3. By default, up to four modes can be defined and selected using the minornumber (bits 5 and 6). The number of modes can be changed by changingST_NBR_MODE_BITS in st.h. Mode 0 corresponds to the defaults discussedabove. Additional modes are dormant until they are defined by thesystem manager (root). When specification of a new mode is started,the configuration of mode 0 is used to provide a starting point fordefinition of the new mode.

Using the modes allows the system manager to give the users choicesover some of the buffering parameters not directly accessible to theusers (buffered and asynchronous writes). The modes also allow choicesbetween formats in multi-tape operations (the explicitly overriddenparameters are reset when a new tape is loaded).

If more than one mode is used, all modes should contain definitionsfor the same set of parameters.

Many Unices contain internal tables that associate different modes tosupported devices. The Linux SCSI tape driver does not contain suchtables (and will not do that in future). Instead of that, a utilityprogram can be made that fetches the inquiry data sent by the device,scans its database, and sets up the modes using the ioctls. Anotheralternative is to make a small script that uses mt to set the defaultstailored to the system.

The driver supports fixed and variable block size (within bufferlimits). Both the auto-rewind (minor equals device number) andnon-rewind devices (minor is 128 + device number) are implemented.

In variable block mode, the byte count in write() determines the sizeof the physical block on tape. When reading, the drive reads the nexttape block and returns to the user the data if the read() byte countis at least the block size. Otherwise, error ENOMEM is returned.

In fixed block mode, the data transfer between the drive and thedriver is in multiples of the block size. The write() byte count mustbe a multiple of the block size. This is not required when reading butmay be advisable for portability.

Support is provided for changing the tape partition and partitioningof the tape with one or two partitions. By default support forpartitioned tape is disabled for each driver and it can be enabledwith the ioctl MTSETDRVBUFFER.

By default the driver writes one filemark when the device is closed afterwriting and the last operation has been a write. Two filemarks can beoptionally written. In both cases end of data is signified byreturning zero bytes for two consecutive reads.

Tandberg Scsi & Raid Devices Driver Download

Writing filemarks without the immediate bit set in the SCSI command block actsas a synchronization point, i.e., all remaining data form the drive buffers iswritten to tape before the command returns. This makes sure that write errorsare caught at that point, but this takes time. In some applications, severalconsecutive files must be written fast. The MTWEOFI operation can be used towrite the filemarks without flushing the drive buffer. Writing filemark atclose() is always flushing the drive buffers. However, if the previousoperation is MTWEOFI, close() does not write a filemark. This can be used ifthe program wants to close/open the tape device between files and wants toskip waiting.

If rewind, offline, bsf, or seek is done and previous tape operation waswrite, a filemark is written before moving tape.

The compile options are defined in the file linux/drivers/scsi/st_options.h.

4. If the open option O_NONBLOCK is used, open succeeds even if thedrive is not ready. If O_NONBLOCK is not used, the driver waits forthe drive to become ready. If this does not happen in ST_BLOCK_SECONDSseconds, open fails with the errno value EIO. With O_NONBLOCK thedevice can be opened for writing even if there is a write protectedtape in the drive (commands trying to write something return error ifattempted).

Minor Numbers¶

The tape driver currently supports up to 2^17 drives if 4 modes foreach drive are used.

The minor numbers consist of the following bit fields:

The non-rewind bit is always bit 7 (the uppermost bit in the lowermostbyte). The bits defining the mode are below the non-rewind bit. Theremaining bits define the tape device number. This numbering isbackward compatible with the numbering used when the minor number wasonly 8 bits wide.

Sysfs Support¶

The driver creates the directory /sys/class/scsi_tape and populates it withdirectories corresponding to the existing tape devices. There are autorewindand non-rewind entries for each mode. The names are stxy and nstxy, where xis the tape number and y a character corresponding to the mode (none, l, m,a). For example, the directories for the first tape device are (assuming fourmodes): st0 nst0 st0l nst0l st0m nst0m st0a nst0a.

Each directory contains the entries: default_blksize default_compressiondefault_density defined dev device driver. The file ‘defined’ contains 1if the mode is defined and zero if not defined. The files ‘default_*’ containthe defaults set by the user. The value -1 means the default is not set. Thefile ‘dev’ contains the device numbers corresponding to this device. The links‘device’ and ‘driver’ point to the SCSI device and driver entries.

Each directory also contains the entry ‘options’ which shows the currentlyenabled driver and mode options. The value in the file is a bit mask where thebit definitions are the same as those used with MTSETDRVBUFFER in setting theoptions.

A link named ‘tape’ is made from the SCSI device directory to the classdirectory corresponding to the mode 0 auto-rewind device (e.g., st0).

Sysfs and Statistics for Tape Devices¶

The st driver maintains statistics for tape drives inside the sysfs filesystem.The following method can be used to locate the statistics that areavailable (assuming that sysfs is mounted at /sys):

  1. Use opendir(3) on the directory /sys/class/scsi_tape
  2. Use readdir(3) to read the directory contents
  3. Use regcomp(3)/regexec(3) to match directory entries to the extendedregular expression “^st[0-9]+$”
  4. Access the statistics from the /sys/class/scsi_tape/<match>/statsdirectory (where <match> is a directory entry from /sys/class/scsi_tapethat matched the extended regular expression)

The reason for using this approach is that all the character devicespointing to the same tape drive use the same statistics. That meansthat st0 would have the same statistics as nst0.

The directory contains the following statistics files:

  1. in_flight
    • The number of I/Os currently outstanding to this device.
  2. io_ns
    • The amount of time spent waiting (in nanoseconds) for all I/Oto complete (including read and write). This includes tape movementcommands such as seeking between file or set marks and implicit tapemovement such as when rewind on close tape devices are used.
  3. other_cnt
    • The number of I/Os issued to the tape drive other than read orwrite commands. The time taken to complete these commands uses thefollowing calculation io_ms-read_ms-write_ms.
  4. read_byte_cnt
    • The number of bytes read from the tape drive.
  5. read_cnt
    • The number of read requests issued to the tape drive.
  6. read_ns
    • The amount of time (in nanoseconds) spent waiting for readrequests to complete.
  7. write_byte_cnt
    • The number of bytes written to the tape drive.
  8. write_cnt
    • The number of write requests issued to the tape drive.
  9. write_ns
    • The amount of time (in nanoseconds) spent waiting for writerequests to complete.
  10. resid_cnt
    • The number of times during a read or write we foundthe residual amount to be non-zero. This should mean that a programis issuing a read larger thean the block size on tape. For writenot all data made it to tape.


The in_flight value is incremented when an I/O starts the I/Oitself is not added to the statistics until it completes.

The total of read_cnt, write_cnt, and other_cnt may not total to the samevalue as iodone_cnt at the device level. The tape statistics only countI/O issued via the st module.

When read the statistics may not be temporally consistent while I/O is inprogress. The individual values are read and written to atomically howeverwhen reading them back via sysfs they may be in the process of beingupdated when starting an I/O or when it is completed.

The value shown in in_flight is incremented before any statstics areupdated and decremented when an I/O completes after updating statistics.The value of in_flight is 0 when there are no I/Os outstanding that areissued by the st driver. Tape statistics do not take into account anyI/O performed via the sg device.

BSD and Sys V Semantics¶

The user can choose between these two behaviours of the tape driver bydefining the value of the symbol ST_SYSV. The semantics differ when afile being read is closed. The BSD semantics leaves the tape where itcurrently is whereas the SYS V semantics moves the tape past the nextfilemark unless the filemark has just been crossed.

The default is BSD semantics.


The driver tries to do transfers directly to/from user space. If thisis not possible, a driver buffer allocated at run-time is used. Ifdirect i/o is not possible for the whole transfer, the driver bufferis used (i.e., bounce buffers for individual pages are notused). Direct i/o can be impossible because of several reasons, e.g.:

  • one or more pages are at addresses not reachable by the HBA
  • the number of pages in the transfer exceeds the number ofscatter/gather segments permitted by the HBA
  • one or more pages can’t be locked into memory (should not happen inany reasonable situation)

The size of the driver buffers is always at least one tape block. In fixedblock mode, the minimum buffer size is defined (in 1024 byte units) byST_FIXED_BUFFER_BLOCKS. With small block size this allows buffering ofseveral blocks and using one SCSI read or write to transfer all of theblocks. Buffering of data across write calls in fixed block mode isallowed if ST_BUFFER_WRITES is non-zero and direct i/o is not used.Buffer allocation uses chunks of memory having sizes 2^n * (pagesize). Because of this the actual buffer size may be larger than theminimum allowable buffer size.

NOTE that if direct i/o is used, the small writes are not buffered. This maycause a surprise when moving from 2.4. There small writes (e.g., tar without-b option) may have had good throughput but this is not true any more with2.6. Direct i/o can be turned off to solve this problem but a better solutionis to use bigger write() byte counts (e.g., tar -b 64).

Asynchronous writing. Writing the buffer contents to the tape isstarted and the write call returns immediately. The status is checkedat the next tape operation. Asynchronous writes are not done withdirect i/o and not in fixed block mode.

Buffered writes and asynchronous writes may in some rare cases causeproblems in multivolume operations if there is not enough space on thetape after the early-warning mark to flush the driver buffer.

Read ahead for fixed block mode (ST_READ_AHEAD). Filling the buffer isattempted even if the user does not want to get all of the data atthis read command. Should be disabled for those drives that don’t likea filemark to truncate a read request or that don’t like backspacing.

Scatter/gather buffers (buffers that consist of chunks non-contiguousin the physical memory) are used if contiguous buffers can’t beallocated. To support all SCSI adapters (including those notsupporting scatter/gather), buffer allocation is using the followingthree kinds of chunks:

  1. The initial segment that is used for all SCSI adapters includingthose not supporting scatter/gather. The size of this buffer will be(PAGE_SIZE << ST_FIRST_ORDER) bytes if the system can give a chunk ofthis size (and it is not larger than the buffer size specified byST_BUFFER_BLOCKS). If this size is not available, the driver halvesthe size and tries again until the size of one page. The defaultsettings in st_options.h make the driver to try to allocate all of thebuffer as one chunk.
  2. The scatter/gather segments to fill the specified buffer size areallocated so that as many segments as possible are used but the numberof segments does not exceed ST_FIRST_SG.
  3. The remaining segments between ST_MAX_SG (or the module parametermax_sg_segs) and the number of segments used in phases 1 and 2are used to extend the buffer at run-time if this is necessary. Thenumber of scatter/gather segments allowed for the SCSI adapter is notexceeded if it is smaller than the maximum number of scatter/gathersegments specified. If the maximum number allowed for the SCSI adapteris smaller than the number of segments used in phases 1 and 2,extending the buffer will always fail.

EOM Behaviour When Writing¶

When the end of medium early warning is encountered, the current writeis finished and the number of bytes is returned. The next writereturns -1 and errno is set to ENOSPC. To enable writing a trailer,the next write is allowed to proceed and, if successful, the number ofbytes is returned. After this, -1 and the number of bytes arealternately returned until the physical end of medium (or some othererror) is encountered.

Module Parameters¶

The buffer size, write threshold, and the maximum number of allocated buffersare configurable when the driver is loaded as a module. The keywords are:

buffer_kbs=xxxthe buffer size for fixed block mode is setto xxx kilobytes
write_threshold_kbs=xxxthe write threshold in kilobytes set to xxx
max_sg_segs=xxxthe maximum number of scatter/gathersegments
try_direct_io=xtry direct transfer between user buffer andtape drive if this is non-zero

Note that if the buffer size is changed but the write threshold is notset, the write threshold is set to the new buffer size - 2 kB.

Boot Time Configuration¶

If the driver is compiled into the kernel, the same parameters can bealso set using, e.g., the LILO command line. The preferred syntax isto use the same keyword used when loading as module but prependedwith ‘st.’. For instance, to set the maximum number of scatter/gathersegments, the parameter ‘st.max_sg_segs=xx’ should be used (xx is thenumber of scatter/gather segments).

For compatibility, the old syntax from early 2.5 and 2.4 kernelversions is supported. The same keywords can be used as when loadingthe driver as module. If several parameters are set, the keyword-valuepairs are separated with a comma (no spaces allowed). A colon can beused instead of the equal mark. The definition is prepended by thestring st=. Here is an example:

The following syntax used by the old kernel versions is also supported:


  • aa is the buffer size for fixed block mode in 1024 byte units
  • bb is the write threshold in 1024 byte units
  • dd is the maximum number of scatter/gather segments


The tape is positioned and the drive parameters are set with ioctlsdefined in mtio.h The tape control program ‘mt’ uses these ioctls. Tryto find an mt that supports all of the Linux SCSI tape ioctls andopens the device for writing if the tape contents will be modified(look for a package mt-st* from the Linux ftp sites; the GNU mt doesnot open for writing for, e.g., erase).

The supported ioctls are:

The following use the structure mtop:

Space forward over count filemarks. Tape positioned after filemark.
As above but tape positioned before filemark.
Space backward over count filemarks. Tape positioned beforefilemark.
As above but ape positioned after filemark.
Space forward over count records.
Space backward over count records.
Space forward over count setmarks.
Space backward over count setmarks.
Write count filemarks.
Write count filemarks with immediate bit set (i.e., does notwait until data is on tape)
Write count setmarks.
Rewind tape.
Set device off line (often rewind plus eject).
Do nothing except flush the buffers.
Re-tension tape.
Space to end of recorded data.
Erase tape. If the argument is zero, the short erase commandis used. The long erase command is used with all other valuesof the argument.
Seek to tape block count. Uses Tandberg-compatible seek (QFA)for SCSI-1 drives and SCSI-2 seek for SCSI-2 drives. The file andblock numbers in the status are not valid after a seek.
Set the drive block size. Setting to zero sets the drive intovariable block mode (if applicable).
Sets the drive density code to arg. See drivedocumentation for available codes.
Explicitly lock/unlock the tape drive door.
Explicitly load and unload the tape. If thecommand argument x is between MT_ST_HPLOADER_OFFSET + 1 andMT_ST_HPLOADER_OFFSET + 6, the number x is used sent to thedrive with the command and it selects the tape slot to use ofHP C1553A changer.
Sets compressing or uncompressing drive mode using theSCSI mode page 15. Note that some drives other methods forcontrol of compression. Some drives (like the Exabytes) usedensity codes for compression control. Some drives use anothermode page but this page has not been implemented in thedriver. Some drives without compression capability will acceptany compression mode without error.
Moves the tape to the partition given by the argument at thenext tape operation. The block at which the tape is positionedis the block where the tape was previously positioned in thenew active partition unless the next tape operation isMTSEEK. In this case the tape is moved directly to the blockspecified by MTSEEK. MTSETPART is inactive unlessMT_ST_CAN_PARTITIONS set.
Formats the tape with one partition (argument zero) or twopartitions (argument non-zero). If the argument is positive,it specifies the size of partition 1 in megabytes. For DDSdrives and several early drives this is the physically firstpartition of the tape. If the argument is negative, its absolutevalue specifies the size of partition 0 in megabytes. This isthe physically first partition of many later drives, like theLTO drives from LTO-5 upwards. The drive has to support partitionswith size specified by the initiator. Inactive unlessMT_ST_CAN_PARTITIONS set.

Is used for several purposes. The command is obtained from countwith mask MT_SET_OPTIONS, the low order bits are used as argument.This command is only allowed for the superuser (root). Thesubcommands are:

  • 0

    The drive buffer option is set to the argument. Zero meansno buffering.


    Sets the buffering options. The bits are the new states(enabled/disabled) the following options (in theparenthesis is specified whether the option is global orcan be specified differently for each mode):


    write buffering (mode)


    asynchronous writes (mode)


    read ahead (mode)


    writing of two filemarks (global)


    using the SCSI spacing to EOD (global)


    automatic locking of the drive door (global)


    the defaults are meant only for writes (mode)


    backspacing over more than one records canbe used for repositioning the tape (global)


    the driver does not ask the block limitsfrom the drive (block size can be changed only tovariable) (global)


    enables support for partitionedtapes (global)


    the logical block number is used inthe MTSEEK and MTIOCPOS for SCSI-2 drives instead ofthe device dependent address. It is recommended to setthis flag unless there are tapes using the devicedependent (from the old times) (global)


    sets the SYSV semantics (mode)


    enables immediate mode (i.e., don’t wait forthe command to finish) for some commands (e.g., rewind)


    enables immediate filemark mode (i.e. whenwriting a filemark, don’t wait for it to complete). Pleasesee the BASICS note about MTWEOFI with respect to thepossible dangers of writing immediate filemarks.


    enables setting the SILI bit in SCSI commands whenreading in variable block mode to enhance performance whenreading blocks shorter than the byte count; set this onlyif you are sure that the drive supports SILI and the HBAcorrectly returns transfer residuals


    debugging (global; debugging must becompiled into the driver)


    Sets or clears the option bits.


    Sets the write threshold for this device to kilobytesspecified by the lowest bits.


    Defines the default block size set automatically. Value0xffffff means that the default is not used any more.


    Used to set or clear the density (8 bits), and drive bufferstate (3 bits). If the value is MT_ST_CLEAR_DEFAULT(0xfffff) the default will not be used any more. Otherwisethe lowermost bits of the value contain the new value ofthe parameter.


    The compression default will not be used if the value ofthe lowermost byte is 0xff. Otherwise the lowermost bitcontains the new default. If the bits 8-15 are set to anon-zero number, and this number is not 0xff, the number isused as the compression algorithm. The valueMT_ST_CLEAR_DEFAULT can be used to clear the compressiondefault.


    Set the normal timeout in seconds for this device. Thedefault is 900 seconds (15 minutes). The timeout should belong enough for the retries done by the device whilereading/writing.


    Set the long timeout that is used for operations that areknown to take a long time. The default is 14000 seconds(3.9 hours). For erase this value is further multiplied byeight.


    Set the cleaning request interpretation parameters usingthe lowest 24 bits of the argument. The driver can set thegeneric status bit GMT_CLN if a cleaning request bit patternis found from the extended sense data. Many drives set one ormore bits in the extended sense data when the drive needscleaning. The bits are device-dependent. The driver isgiven the number of the sense data byte (the lowest eightbits of the argument; must be >= 18 (values 1 - 17reserved) and <= the maximum requested sense data sixe),a mask to select the relevant bits (the bits 9-16), and thebit pattern (bits 17-23). If the bit pattern is zero, oneor more bits under the mask indicate cleaning request. Ifthe pattern is non-zero, the pattern must match the maskedsense data byte.

    (The cleaning bit is set if the additional sense code andqualifier 00h 17h are seen regardless of the setting ofMT_ST_SET_CLN.)

The following ioctl uses the structure mtpos:

Reads the current position from the drive. UsesTandberg-compatible QFA for SCSI-1 drives and the SCSI-2command for the SCSI-2 drives.

The following ioctl uses the structure mtget to return the status:

Returns some status information.The file number and block number within file are returned. Theblock is -1 when it can’t be determined (e.g., after MTBSF).The drive type is either MTISSCSI1 or MTISSCSI2.The number of recovered errors since the previous status callis stored in the lower word of the field mt_erreg.The current block size and the density code are stored in the fieldmt_dsreg (shifts for the subfields are MT_ST_BLKSIZE_SHIFT andMT_ST_DENSITY_SHIFT).The GMT_xxx status bits reflect the drive status. GMT_DR_OPENis set if there is no tape in the drive. GMT_EOD means eitherend of recorded data or end of tape. GMT_EOT means end of tape.

Miscellaneous Compile Options¶

The recovered write errors are considered fatal if ST_RECOVERED_WRITE_FATALis defined.


The maximum number of tape devices is determined by the defineST_MAX_TAPES. If more tapes are detected at driver initialization, themaximum is adjusted accordingly.

Immediate return from tape positioning SCSI commands can be enabled bydefining ST_NOWAIT. If this is defined, the user should take care thatthe next tape operation is not started before the previous one hasfinished. The drives and SCSI adapters should handle this conditiongracefully, but some drive/adapter combinations are known to hang theSCSI bus in this case.

The MTEOM command is by default implemented as spacing over 32767filemarks. With this method the file number in the status iscorrect. The user can request using direct spacing to EOD by settingST_FAST_EOM 1 (or using the MT_ST_OPTIONS ioctl). In this case the filenumber will be invalid.

When using read ahead or buffered writes the position within the filemay not be correct after the file is closed (correct position mayrequire backspacing over more than one record). The correct positionwithin file can be obtained if ST_IN_FILE_POS is defined at compiletime or the MT_ST_CAN_BSR bit is set for the drive with an ioctl.(The driver always backs over a filemark crossed by read ahead if theuser does not request data that far.)

Debugging Hints¶

Debugging code is now compiled in by default but debugging is turned offwith the kernel module parameter debug_flag defaulting to 0. Debuggingcan still be switched on and off with an ioctl. To enable debug atmodule load time add debug_flag=1 to the module load options, thedebugging output is not voluminous. Debugging can also be enabledand disabled by writing a ‘0’ (disable) or ‘1’ (enable) to the sysfsfile /sys/bus/scsi/drivers/st/debug_flag.

If the tape seems to hang, I would be very interested to hear wherethe driver is waiting. With the command ‘ps -l’ you can see the stateof the process using the tape. If the state is D, the process iswaiting for something. The field WCHAN tells where the driver iswaiting. If you have the current in the correct place (in/boot for the procps I use) or have updated /etc/psdatabase (for kmemps), ps writes the function name in the WCHAN field. If not, you haveto look up the function from

Note also that the timeouts are very long compared to most otherdrivers. This means that the Linux driver may appear hung although thereal reason is that the tape firmware has got confused.

Search the Knowledge Base:

SCSI bus configuration tips
(KB # D8F6E3FB)

Improper bus configuration or bad cables are by far the most likely culprits when facing issues such as:

  • Devices not being seen in the operating system.
  • Intermittent or unexpected 'I/O' errors.
  • Losing communication with a tape drive during backup.
  • Event ID 9 or 11 errors in Windows.
  • Unexpected bus resets.
  • Parity errors.

If your tape drive is not being detected by the operating system, or if the system is experiencing unstable operation, try the following items.

Don't mix devices of different SCSI interface types. The Host Bus Adaptor, the SCSI terminator, and all SCSI peripherals attached to a SCSI bus should be of the same SCSI type. The SCSI interface types are High Voltage Differential (HVD), Low Voltage Differential (LVD), and single-ended.

  • High Voltage Differential (HVD) devices should never be connected to a SCSI bus with either single-ended or Low Voltage Differential (LVD) devices.
  • In theory it's ok to mix multimode Low Voltage Differential (LVD) and single-ended devices. By doing so, however, all devices will run in single-ended mode. Shorter cable length requirements for the single-ended bus must be met. Also, single-ended transfer rates are slower. This could become a transfer bottleneck in your system, decreasing the speed at which data can be transferred to and from your tape drives.
    Warning: Because of the high risk of SCSI bus stability issues, Tandberg Data does not support the use of an LVD library connected to a single-ended bus. For optimum performance and stability, only connect LVD devices to an LVD bus.

Check that total SCSI cable length does not exceed limits. Using cables which are longer than the required limits will result in unstable operation. For more information, see the Knowledge Base item What is the maximum SCSI cable length I can use with my tape drive, autoloader or library?

Terminate both physical ends of the SCSI bus. The terminator's job is to closely match the impedance of the SCSI bus cable to prevent the signals from reflecting back down the cable. Without termination, reflected signals will cause line noise problems and possible data errors. For more information, see the Knowledge Base item What kind of termination do I need on my SCSI bus?

Make sure that all devices are at unique SCSI IDs. The Host Bus Adaptor and any peripherals attached to the SCSI bus must all be set to unique SCSI IDs. (The terminator does not use a SCSI ID.)

Check that there are no bent pins at any cable connectors. If any of the cable pins are bent, unstable operation will result.

Check that all SCSI connectors are well seated. Make sure that all cables are well-seated, whether they are external cables or internal to the server. Some external cables are heavy and stiff and may pull away from the device after initially being connected. For wide cables, make sure that the cable jack screws are completely screwed into the device.

Check that the SCSI cables are of good quality. Not all cables are created equally, and poor quality cables will result in unstable operation. If you have provided the SCSI cables for your system, make sure that they meet the minimum requirements as specified in your Tandberg Data Product Manual.

Try another cable. Even a 'trusted' cable which worked in one situation may prove to be the root cause of problems later on.

Check that the SCSI controller card is well seated. If your SCSI controller is a card installed in your system, make sure that it is well-seated and secured in the system slot. You may want to try moving it to another available slot.

Make sure that a device driver is installed for the SCSI controller. Refer to the installation instructions for your SCSI controller for specifics about a device driver for your operating system.

Do not connect the tape drive, autoloader or library to a SCSI RAID controller. SCSI RAID controllers are manufactured with hard disks as the primary target type. These controllers may not fully support commands and responses for SCSI tape drives, autoloaders and libraries.

Tandberg Scsi & Raid Devices Drivers

Try connecting only the tape drive or library to the bus. Remove as many SCSI devices from the bus as possible. After confirming stable operation, add other devices one at a time, each time confirming stable operation.

Tandberg SCSI & RAID Devices Driver