Technical data

st(7D) Devices SunOS 5.5
SEE ALSO mt(1), modload(1M), modunload(1M), read(2), write(2), driver.conf(4), esp(7D), isp(7D),
mtio(7I), ioctl(9E)
DIAGNOSTICS Error for command ’<command name>’Error Level: Fatal
Requested Block <n>, Error Block: <m>
Sense Key: <sense key name>
Vendor ’<name>’: ASC = 0x<a> (<extended sense code name>),
ASCQ = 0x<b>, FRU = 0x<c>
The command indicated by <command name> failed. The Requested Block is
the block where the transfer started and the Error Block is the block that
caused the error. Sense Key, ASC, ASCQ and FRU information is returned by
the target in response to a request sense command.
write/read: not modulo <n> block size
The request size for fixed record size devices must be a multiple of the
specified block size.
recovery by resets failed
After a transport error, the driver attempted to recover with device and bus
reset. This recovery failed.
Periodic head cleaning required
The driver reported that periodic head cleaningis now required.
Soft error rate (<n>%) during writing/reading was too high
The soft error rate has exceeded the threshold specified by the vendor.
SCSI transport failed: reason ’xxxx’: {retrying|giving up}
The host adapter has failed to transport a command to the target for the rea-
son stated. The driver will either retry the command or, ultimately, give up.
WARNINGS Beginning with Solaris 2.4, the ST_NO_RECSIZE_LIMIT flag is set for the built-in config
entries of the ArchiveDAT and Exabyte drivers by default. Refer to Large Record Sizes.
Tapes written with large block sizes prior to Solaris 2.4 may cause some applications to
fail if the number of bytes returned by a read request is less than the requested block size
(e.g. asking for 128 Kbytes and receiving less than 64 Kbytes).
The ST_NO_RECSIZE_LIMIT flag can be disabled in the config entry for the drive as a
work around. Refer to Tape Configuration. This action disables the ability to read and
write with large block sizes and allows the reading of tapes written prior to Solaris 2.4
with large block sizes.
Refer to mtio(7I) for a description of maximum record sizes.
BUGS Tape devices that do not return a BUSY status during tape loading prevent user com-
mands from being held until the device is ready. The user must delay issuing any tape
operations until the tape device is ready. This is not a problem for Sun Microsystem
Computer Corporation supplied tape devices.
7D-312 modified 30 Aug 1995