USB 2.0 & 3.0 SCSI Compliance test for UAS on EHCI (LOGO)

This test verifies Small Computer System Interface (SCSI) Command Descriptor Blocks (CDBs) sent to the Universal Serial Bus (USB) UAS device. For more information, see the SCSI Compliance Test (LOGO).

Test details

Running the test

Before you run the test, complete the test setup as described in the test requirements: Hard Disk Drive Testing Prerequisites.

In addition this test requires a UAS device connected to a USB 2.0 Controller.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Storage Testing.

Also, the test writes the results to the log files Scsicompliance.wtl and Scsicompliance.wtl.txt. You can use the results to determine:

• If a device is compliant with the SCSI specification

• The optional SCSI commands that are supported by a device

To pass, the SCSI device must support every mandatory command and must be fully compliant with those commands. Each command has a different threshold for pass or fail, and the expectations are specified explicitly in the test and in the log file.

Optional commands are also tested. If a device supports the optional commands and the commands are found to be non-compliant, the test fails. If the device does not support optional commands, the test passes.

Note  

Errors from this test occur via issues identified in the log file and in bugchecks produced through stressing the driver under test.

During the test, if you are having trouble removing a LUN that is failing or are unable to create a LUN from the storage controller, follow these steps:

1. Prior to running this test, verify that the storage device works properly. Open diskmgmt.msc, select the disk, and make sure that you can put the device Online and in Initialized state.

2. Restart the Windows HCK test computer.

3. Select and rerun the SCSI Compliance Test 2.0. Do not run any test before it.

4. Run the SCSI Compliance Test (not the SCSI Compliance Test 2.0 (LOGO)) on the same test client and same test storage device. If the test fails again, verify that the storage device is working properly.If the test fails during steps 3 and 4, run the individual failing command data blocks (cdbs) one at a time with the logging verbosity level set to 4 (the highest level of test logging). This will show what data was sent and what data was returned. A test can fail after several cdbs are completed but pass standalone. If this occurs, there is a problem in the firmware or the test.

If you have a device reset that results in the device falling off the bus and subsequent commands to fail, follow these steps:

1. Copy the test binary (Scsicompliance.exe) from the Windows HCK controller. This file is located at \\controllername\tests\[processorarchitectureofyourclient]\NTTEST\DriversTest\storage\wdk\

2. Copy the wttlog.dll file from the Windows HCK controller. This file is located at \\<controllername>\Tests\<processorarchitectureofyourclient>\wtt

3. Place both of these files on the test computer in a separate folder.

4. From a command prompt, from the directory containing the test binary, type the following command: Scsicompliance.exe /device <deviceID> /verbosity 4 /operation test /scenario <scenario> /CDB <failingcdbname>

   Note  

   DeviceID and scenario values can be found by checking the repro line within the test log. The failingcdbname can be found by running the test binary with the /?option (scsicompliance.exe /?).

    

5. Go back to the same directory and review the results to see if you can determine the reason for the test failure.

6. If you need additional help, collect the txt and wtl logs and share the logs with Microsoft Customer Support.

More information

Run the test as an HCK Manager job.

For test assertions, see the SCSI Compliance Test (LOGO).

Command syntax

Note  

For command-line help for this test binary, type /?.

File list

Send comments about this topic to Microsoft