NAME

scsi.diag − scsi interface and disk diagnostic

DESCRIPTION

The scsi.diag tests internal SCSI circuitry and external disk. 

DETAILS

none required. 

BOARDS THAT MUST BE INSTALLED

This test requires a CPU board, at least one memory board and the I/O board.  If an external SCSI disk is installed, it too will be tested.  Note: the address mapper is used during this test.  Run mapper.diag first to assure that the mapper is functioning properly before attempting this test. 

SPECIAL COMMAND LINE PARAMETERS

parameters

c[ontroller]
controller number, 0 for SCSI A and 1 for SCSI B, default value is -1 which means no controller present.

t[arget]
Specifies SCSI target number, default is -1 (an illegal value)

lu[n] or log[ical]
Specifies the logical unit number (lun), default is 0.

p[artition]
Specifies the partition number (Prtn), default value is 0.

f[rom]
Specifies the starting block number of area to be tested, default is 0.

to
Specifies the ending end block number of area to be tested, default is 1.

all
If all is given on the command line, this test is executed in non-interactive mode.  The tested area is defined by parameters described above. 

MENU ITEMS SPECIFIC TO THIS TEST

register function test
This test makes internal function test for SCSI interface. It does
•   read write pattern test for the stacker, DMA registers and SCSI controller WD33C93 on-chip registers,
•   issue reset command to the SCSI controller and examine whether proper interrupt and status are got,
•   enable DMA and examine proper interrupt.

disk subtest
∗∗∗ RED FLAG ∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗
The disk subtest part of this test may be superceded entirely by the periph.diag test.  Potential source of error, for example, is that the user could select a disk area that already contains user-data that will therefore be destroyed.  Periph.diag does not have this problem in that it locates and uses the maintenance partition of the disk for the disk testing.
∗∗∗ RED FLAG ∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗∗
This test write/read blocks of a SCSI disk. The disk under the test needs to be formatted properly, and this test will modify the contents of tested area on the disk. The tested area is defined by following parameters; controller number (0 for SCSIA, 1 for SCSIB), target number, logical unit number, partition number, block number of the start and block number of the end. The user is prompted for these parameters in each subtest, except during non-interactive execution. (See SPECIAL COMMAND LINE PARAMETERS for more information).

sequential read/write
This test sequentially fills out the entire tested area with each block number, and then read back and verify.

random read/write
This test intends to read and write random positions of the block. The program generates random pattern of data and random block number within the tested area. The test sequence is as follows;

In the current implementation, n=2.  This test may not test the entire tested area because the block number for test may overlap. 

block_test
This test write/read onto single block using several patterns of data. It uses all-zeros, all-ones, walking-one, walking-zero and sequential-pattern.

dumpThis dumps out the contents of the block. 

INTERPRETING THE ERROR CODES

The following errors may be generated by this test.  (The actual error wording may differ, however the type of error is as summarized here.) 

101Attempted to access the SCSI disk using the Unix open() function, but the disk did not respond.  (Disk partitions are mapped by name into the Unix filing system − the partition that the user requested should be tested was not mapped). 

103,105
An attempt was made to read the volume header of the SCSI disk under test (the volume header contains information about bad tracks and bad sectors on the disk) but an error happened when trying to read this information.

107A seek error has occured on the target disk.  The system has stepped to a particular cylinder, but the information on the disk says the disk read/write head is now positioned over a different cylinder than Was expected.   Happened during a write operation. 

109A write error has occured at a specified location on the target disk. 

111Same as 107 except happened during a read operation. 

113,115
A read error has occured at a specified location on the target disk. The actual and expected values are reported for error 115.

121Error while pattern tests being run on SCSI_LODATA registers.  Failing register, actual and expected value are reported. 

123Error while pattern tests being run on SCSI_HIDATA registers.  Failing register, actual and expected value are reported. 

125Error while pattern testing the SCSI Stacker.  The failing stacker register, along with the actual and expected pattern are reported. 

127Error while pattern testing the SCSI DMA registers.  The failing stacker register, along with the actual and expected pattern are reported. 

129,131
Error while testing the SCSI DMA control register.   Reports the actual and expected values.

133,135
Data error while using SCSI DMA to transfer data to or from memory. Failing location, actual and expected value are reported.

137,139
After a reset, all of the registers in the SCSI chip should contain a value of zero except the WD93_DATA register).  These error codes happen if the chip did not reset as expected.  Could indicate a faulty SCSI chip.

140Following a SCSI reset, the SCSI interrupt bit should be set, and it was not set. 

141One channel (at least one, that is) of the SCSI failed to reset. 

142An incorrect ID value was found in the ID register of the SCSI chip. 

145,147
Attempting to enable DMA on channel A or B but found the DMA already enabled.  Actual and expected values in the WD93_CONTROL register are reported.

149Cannot enable DMA on SCSI channel A. 

151Received undexpected NXA (non existent address) exception during a test of SCSI output. 

153If error 151 was generated, a bus time out (BTO) should also have happened.  The BTO did not happen. 

155The error that SHOULD follow error 151. 

157Cannot enable DMA. 

158Incorrect value found in dmalo register; actual and expected values are reported. 

159Incorrect value found in dmahi register; actual and expected values are reported. 

September 02, 1992