scsi(7) — SPECIAL FILES AND DEVICES
NAME
scsi − Common SCSI information
DESCRIPTION
This information is common to the MVME328, MVME187 and MVME197 SCSI controllers. For information that is specific to each SCSI controller, such as the master.d entrys and error messages, refer to the controller man page.
SUPPORTED DEVICES
Disk Drives
Disk drives currently supported are:
| DESCRIPTION | ddefs(1M) FILE | TYPE |
| 150MB CDC 94161 Wren III | mcdcIII | Hard |
| 300MB CDC 94171 Wren IV | mcdcIV | Hard |
| 600MB CDC 94181 Wren V | mcdcV | Hard |
| 1.2GB CDC 94601 Wren VII | mcdcVII | Hard |
| 135MB FUJITSU M2613 | mfuj2613 | Hard |
| 180MB FUJITSU M2614 | mfuj2614 | Hard |
| 330MB FUJITSU M2622 | mfuj2622 | Hard |
| 525MB FUJITSU M2624 | mfuj2624 | Hard |
| 1.0GB SEAGATE ST11200 | msea11200 | Hard |
| 2.0GB SEAGATE ST12400 | msea12400 | Hard |
| Toshiba XM3201B CDROM | none | CDROM |
| Toshiba XM3301B CDROM | none | CDROM |
| 1.2MB TEAC 5¼ inch FC−1 | see next table | Floppy |
| 2.88MB TEAC 3½ inch FC−1 | see next table | Floppy |
| 650MB IBM 0632 | mibm0632 | Multi-function |
Note that in all tables, each entry in the ddefs(1M) FILE column is the name of a file that defines the characteristics of the disk in the /etc/dskdefs directory. Each entry in the BLOCKS column is the number of specified blocks when making a file system with mkfs(1M).
The types of floppy diskettes currently supported are listed in the following two tables.
| 5¼ INCH DISKETTES | ||||
| ddefs(1M) | MEDIA | |||
| DESCRIPTION | FILE | BLOCKS | TYPE | SLICE |
| Double density Motorola format | mdsdd5 | 1276 | MFD-2DD | 0 |
| Single density PC/XT 8 sect./track | mpcxt8 | 640 | MFD-2DD | 12 |
| Single density PC/XT 9 sect./track | mpcxt9 | 720 | MFD-2DD | 9 |
| Double density PC/AT | mpcat | 2400 | MF2-HD | 8 |
| 3½ INCH DISKETTES | ||||
| ddefs(1M) | MEDIA | |||
| DESCRIPTION | FILE | BLOCKS | TYPE | SLICE |
| Double density PC/XT 9 sect./track | mpcxt9_3 | 1440 | MFD-2DD | 13 |
| Double density PS/2 | mps2 | 2880 | MF2-HD | 10 |
| Super High Density (2.88MB formatted) | mshd | 5760 | PMF2-ED | 11 |
Tape Drives
Tape drives currently supported by the SCSI host adapters are:
| DESCRIPTION | FORMAT | TYPE |
| Archive 2150S | QIC24, QIC120, QIC150 | Streaming |
| Archive 2525 | QIC24, QIC120, QIC150 | Streaming |
| Archive Python | DAT | Streaming |
| Exabyte EXB-8200 | 8mm | Streaming |
| Kennedy 9660 | 9-track | Start/Stop |
| M4 Data 9914 | 9-track | Start/Stop |
DISK SUPPORT
During system initialization, the SCSI device driver will spin-up any disks that are strapped to spin-up.
The hard disk drives supported by the SCSI controller will handle all defects internally. A list of known defective locations is recorded on the medium. During format, any data that would normally be loaded into these locations are automatically assigned alternate locations. Also during format, the drive is checked for defects in addition to those on the known list. If any additional defective locations are found, any data that would be stored there are assigned alternate locations.
The SCSI device drivers comply with the disk support standard specified on the disk(7) man page with the following exceptions:
DKGETCFG ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI drivers and controllers.
DKGETINFO ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
DKSETCFG ioctl command
The SCSI driver sets only the parameters that are relevant to the SCSI driver and controller.
DKSETINFO ioctl command
The SCSI driver sets only the parameters that are relevant to the SCSI driver and controller.
DKFORMAT ioctl command
The SCSI FORMAT command is used to format the device. The argument arg is not used. Because the bad block strategy is perfect, no defect list is passed to the drive. By turning on a bit in the controller attribute word of the disk definition file passed to dinit, the drive can be told to ignore the grown defect list on the disk. Refer to the description of the controller attribute word on the disk(7) man page for more information.
TAPE SUPPORT
The SCSI device driver complies with the tape support standard specified on the tape(7) man page with no exceptions.
FLOPPY DISK SUPPORT
The SCSI supported floppy drives provide level one support as defined by the 88open PC Floppy Emulation Supplement to the Binary Compatibility Standard.
The SCSI device driver complies with the floppy disk support standard specified on the floppy(7) manual page with the following exceptions:
DKFIXBADSPOT ioctl command
This command always returns EINVAL.
DKGETCFG ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
DKGETINFO ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
DKSETCFG ioctl command
This command performs no operation; it returns with no effect and no error.
DKSETINFO ioctl command
This command performs no operation; it returns with no effect and no error.
DKSETSLC ioctl command
This command performs no operation; it returns with no effect and no error.
FL_PC_LEVEL ioctl command
The SCSI driver currently only supports level 1, so the integer pointed to by arg is always set to 1 by this call.
Slicing
Floppy diskettes do not have volume ID blocks or Volume Table of Contents (VTOC). A floppy drive can be thought of as a hard disk with a single slice. The slice bits of the minor number select the drive geometry as described later in this manual page.
V_PDREAD ioctl command
This command always returns EINVAL.
V_PDWRITE ioctl command
This command always returns EINVAL.
V_RVTOC ioctl command
This command always returns EINVAL.
V_WVTOC ioctl command
This command always returns EINVAL.
dinit/ddef
The ddef files for floppy disks are treated as placeholders. Although they are required for dinit(1M) to work, the information is not used. The format of the diskette is determined via the slice number of the device. Please refer to the supported floppy tables at the beginning of this man page for more information.
Bad blocks may not be mapped out on a floppy disk. A bad block on a floppy disk make the entire floppy unacceptable.
CDROM SUPPORT
The SCSI device driver will not spin-up CDROM devices at system initialization time. The SCSI device driver complies with the CDROM support standard specified on the cdrom(7) manual page with the following exceptions:
DKGETCFG ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
DKGETINFO ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
DKGETCFG ioctl command
The SCSI driver returns only the parameters that are relevant to the SCSI driver and controller.
PASSTHRU SUPPORT
The SCSI device driver complies with the passthru support standard specified on the passthru(7) man page with no exceptions.
SPECIAL CONSIDERATIONS
When an error occurs while writing or reading a tape, the best course of action in this case is to rewind the tape and repeat the operation.
Removing a cartridge tape during an MTBSF operation hangs the tape drive.
An incorrect transfer count may be returned by the SCSI device driver when using variable mode tape devices (e.g. 9-tracks, EXABYTE) in variable mode. This is due to a BUG in the XAM firmware and it is not found in any later firmware.
The problem shows itself when an odd length read is used to read a tape that contains even length records. The returned transfer count will be one less than it should be. The work-around is to read tapes with even length reads equal to or larger than the maximum size of the records found on the tape.
The longest I/O operation which SCSI host adapters can allow to occur on a tape device operating in variable mode depends on two factors. If the SCSI host adapter is using revision XAM firmware, the maximum length is 65535 bytes. For all other boards and firmware combinations, the maximum length will vary from a minimum of 252K bytes (worst case page alignment) to 256K bytes (page aligned). The actual maximum length may be either larger or smaller than the SCSI host adapter may support. Refer to the device’s documentation for more information.
WARNING
When an ARCHIVE 2150 or 2525 tape device is opened for the first time and a tape is present in the drive, the tape will be rewound. This occurs because this is the only way to insure that drive has its parameters set properly.
ERROR MESSAGES
The SCSI driver will occasionally print error or warning messages about problems or conditions it detects during normal operations.
Non-Motorola VID on device-name (disk)
The specified disk does not contain a Motorola Volume ID.
Non-Motorola VID on device-name (CDROM)
The specified CDROM does not contain a Motorola Volume ID.
Invalid VID on device-name (disk)
The specified disk does not contain the correct VID signature.
Invalid VID on device-name (CDROM)
The specified CDROM does not contain the correct VID signature.
Invalid VTOC on device-name (disk)
The specified disk does not contain a valid Volume Table of Contents.
Invalid VTOC on device-name (CDROM)
The specified CDROM does not contain a valid Volume Table of Contents.
Attempting spin up on device-name
This message occurs during system initialization. The specified disk device is strapped for spin up using software commands. The SCSI driver is attempting to spin up the drive.
Device not ready on device-name
This message occurs during system initialization. The specified disk could not be brought on-line.
Device write protected on device-name (tape)
The specified tape contains write protected media.
Device not ready on device-name (tape)
The specified tape is either off-line or does not contain media.
Error from r4dbufopen on device-name (tape)
The specified tape failed to initialize its double buffering information correctly.
Additionally, the SCSI device driver may report problems via the standard error logging mechanism. These messages will clearly indicate the device name, attempted command name, and the final status of the command. If the problem occurs on a disk device (e.g. disk, floppy, or CDROM) the block number of the disk that the error occurred on will also be reported.
Two possible outcomes are common: FATAL ERROR and RECOVERED ERROR.
Fatal error status means that the drive was not able to complete the command successfully.
Recovered error status means that the drive was able to complete the command successfully after some recovery action.
FILES
/dev/dsk/m328_∗
/dev/rdsk/m328_∗
/dev/rmt/m328_∗
/dev/generic/m328_∗
/dev/dsk/m187__∗
/dev/rdsk/m187__∗
/dev/rmt/m187__∗
/dev/generic/m187__∗
/dev/dsk/m197__∗
/dev/rdsk/m197__∗
/dev/rmt/m197__∗
/dev/generic/m197__∗
/etc/dskdefs/m∗
/usr/include/sys/dk.h
/usr/include/sys/mtio.h
/usr/include/sys/m328scsi.h
/usr/include/sys/m328sio.h
/usr/include/sys/m328space.h
/usr/include/sys/mvme328.h
/usr/include/sys/pcflio.h
SEE ALSO
mt(1), ddefs(1M), dinit(1M), close(2), ioctl(2), open(2), read(2), write(2), edt_data(4), cdrom(7), disk(7), floppy(7), intro(7), tape(7), passthru(7), scsi1x7(7), mvme328(7),