The test expects the drives to report the tray status in the sense code. The test would fail if these sense codes are not properly reported.

There is an exception to this requirement for the slot type drives. The slot type drives would not have tray so they will not be able to report tray status in the sense code.  But the slot drive must report the media loading mechanism type as 0 in the Removable medium feature.  The WLK 1.2 version of the optical logo test is not considering this value. But in future, the test would depend on this value to skip the tray status verification test cases for slot type drives.

The following are the loading mechanism type values from MMC5r4.

The WLK 1.2 version of the optical logo test causes timeout failures for slot type drives, because it relies on the sense code to wait for the tray open/closed operation to complete. The slot type drives will not be able to report the tray status in the sense code. So, the test would cause a time out failure after waiting for 20 seconds. The following errata filter would cover those failures

https://winqual.microsoft.com/EC/ECDetails.aspx?id=1172

The optical logo test verifies if the identical test drives report unique serial numbers.  But there is a test issue that would cause the test case to fail. The test case failures are covered by the following erratas.

Filter ID: 1254

https://winqual.microsoft.com/EC/ECDetails.aspx?id=1167

Filter ID: 1255

https://winqual.microsoft.com/EC/ECDetails.aspx?id=1168

This test case would be fixed for the next release of the WLK.

 https://www.microsoft.com/whdc/device/storage/RAID_design.mspx

Inquiry test case

Mode Sense test case

These test cases validate the Inquiry/Modesense SCSI command with random allocation lengths. This is to make sure the device handles the command properly with any allocation length. But the generated random allocation length might be an odd number and that data transfer size will not supported by the SATA protocol.

Serial Number test case

This test case uses the Inquiry command to verify the drive serial number. It sends the Inquiry command with allocation length of “5” to get the additional length required to get the complete Inquiry response. The Inquiry command will fail because the requested data transfer size, "5" is an odd number of bytes.

The test queries the device and gets the supported write speeds for the test media. Then it will try to validate the write scenario for all the reported write speeds. The test expects the calculated write speeds for each write scenario is close to the write speed set to the drive. The test allows 10% tolerance for the measured write speed. The test validates the write speed as below:

The test writes data to the media and monitors the amount of data being written. It excludes the timing for the initial 10% written data the final 10% written data. It measures the timing only for the in between 80% data and calculates the speed for that data and adds 10% tolerance to that value. So, if ‘x’ is the calculated the speed for the middle 80% data then the final calculated speed is 1.1x. The test expects this value to be greater than or equal to the speed set to the drive before beginning the write.

                | ß Initial 10% excluded à | ß Write speed measurement (80%) à | ß Final 10% excluded à |

                                                                                                 (x)

The test excludes the initial 10% of data written timing to allow the drive to prepare for writing. The final 10% data timing is excluded to allow the drive to do the proper cleanup for the data written to the media.

The test sends the IOCTL_STORAGE_QUERY_PROPERTY with STORAGE_PROPERTY_ID set to StorageAdapterProperty/StorageDeviceProperty to get the device bus type from the storage miniport driver.  The miniport driver should report the correct bus type from the following bus type enumeration values

typedef enum _STORAGE_BUS_TYPE {

  BusTypeUnknown = 0x00,

  BusTypeScsi = 0x01,

  BusTypeAtapi = 0x02,

  BusTypeAta = 0x03,

  BusType1394 = 0x04,

  BusTypeSsa = 0x05,

  BusTypeFibre = 0x06,

  BusTypeUsb = 0x07,

  BusTypeRAID = 0x08,

  BusTypeiSCSI = 0x09,

  BusTypeSas = 0x0A,

  BusTypeSata = 0x0B,

  BusTypeMaxReserved = 0x7F

} STORAGE_BUS_TYPE,  *PSTORAGE_BUS_TYPE;

The documentation for these bus type values can be found at: https://msdn2.microsoft.com/en-us/library/aa363465.aspx

The test gets the storage controller PCI class code from the OS generated PNP compatibility IDs  and determines the controller bus type based on the PCI class code. The test verifies if the bus type reported by the miniport driver matches with the bus type for the storage controller PCI class code. The test also verifies if the user supplied device bus type in the DTM submission matches with the corresponding bus type for the controller PCI class code.

The test uses the following PCI class code table to determine the storage controller bus type

The controller bus type validation testing will continue to be a key test scenario in the Storage HBA category, but it will be modified to stop checking  the Programming Interface byte (IF), of the 0x0101 (IDE) and 0x0104 (RAID) types to determine the bus type. 

This results in being the following required class code definitions that must be present:

IDE Type:  Mass Storage Device (0x01), ATA Parallel - IDE Type (0x01), Programming Interface (Don’t Care - 0xXX )

RAID Type:  Mass Storage Device (0x01), RAID Type (0x04), Programming Interface (Don’t Care - 0xXX)

However, because the PCI Conventional specification (2.3) declares two unique values for the SATA Type (Non-ATA Compatible Mode) Programming Interface, the following is required for AHCI-enabled controllers:

AHCI Type:  Mass Storage Device (0x01), SATA Type (0x06), AHCI Type (0x01)

Software Requirements:

1.       Windows Server 2008

2.       Software components included with the device that is being tested.

3.       Unsupported Software: Third Party MPIO Solution that does not use a Microsoft MPIO DSM.

The 4^th requirement is misleading the users to assume that, the MPIO test is not applicable for logoing the third party DSMs. But this is a required test for 3^rd party DSM submissions. We reworded this software requirements section as below to avoid confusion.

Software Requirements:

1.       Windows Server 2008

2.       Hardware Storage RAID array that uses either the Microsoft DSM (device specific module) or a 3rd party DSM that interfaces to Microsoft MPIO core architecture

3.       Software components included with the DSM or Hardware Storage RAID array being tested

You may see this change in the WLK 1.2.

           The bus type or drive type controls appear as edit boxes, but internally they are combo boxes. To work around this problem the user has to select these controls and use the up/down arrow keys to choose an item from those hidden combo boxes items.

0xEFFF0002L : ISDSC_LOGIN_FAILED             
Login Failed.

0xEFFF0003L : ISDSC_CONNECTION_FAILED        
Connection Failed.

0xEFFF0004L : ISDSC_INITIATOR_NODE_ALREADY_EXISTS
Initiator Node Already Exists.

0xEFFF0005L : ISDSC_INITIATOR_NODE_NOT_FOUND 
Initiator Node Does Not Exist.

0xEFFF0006L : ISDSC_TARGET_MOVED_TEMPORARILY 
Target Moved Temporarily.

0xEFFF0007L : ISDSC_TARGET_MOVED_PERMANENTLY 
Target Moved Permanently.

0xEFFF0008L : ISDSC_INITIATOR_ERROR          
Initiator Error.

0xEFFF0009L : ISDSC_AUTHENTICATION_FAILURE   
Authentication Failure.

0xEFFF000AL : ISDSC_AUTHORIZATION_FAILURE    
Authorization Failure.

0xEFFF000BL : ISDSC_NOT_FOUND                
Not Found.

0xEFFF000CL : ISDSC_TARGET_REMOVED           
Target Removed.

0xEFFF000DL : ISDSC_UNSUPPORTED_VERSION      
Unsupported Version.

0xEFFF000EL : ISDSC_TOO_MANY_CONNECTIONS     
Too many Connections.

0xEFFF000FL : ISDSC_MISSING_PARAMETER        
Missing Parameter.

0xEFFF0010L : ISDSC_CANT_INCLUDE_IN_SESSION  
Can not include in session.

0xEFFF0011L : ISDSC_SESSION_TYPE_NOT_SUPPORTED
Session type not supported.

0xEFFF0012L : ISDSC_TARGET_ERROR             
Target Error.

0xEFFF0013L : ISDSC_SERVICE_UNAVAILABLE
Service Unavailable.

0xEFFF0014L : ISDSC_OUT_OF_RESOURCES         
Out of Resources.

0xEFFF0015L : ISDSC_CONNECTION_ALREADY_EXISTS
Connections already exist on initiator node.

0xEFFF0016L : ISDSC_SESSION_ALREADY_EXISTS   
Session Already Exists.

0xEFFF0017L : ISDSC_INITIATOR_INSTANCE_NOT_FOUND
Initiator Instance Does Not Exist.

0xEFFF0018L : ISDSC_TARGET_ALREADY_EXISTS    
Target Already Exists.

0xEFFF0019L : ISDSC_DRIVER_BUG
The iscsi driver implementation did not complete an operation correctly.

0xEFFF001AL : ISDSC_INVALID_TEXT_KEY         
An invalid key text was encountered.

0xEFFF001BL : ISDSC_INVALID_SENDTARGETS_TEXT 
Invalid SendTargets response text was encountered.

0xEFFF001CL : ISDSC_INVALID_SESSION_ID       
Invalid Session Id.

0xEFFF001DL : ISDSC_SCSI_REQUEST_FAILED      
The scsi request failed.

0xEFFF001EL : ISDSC_TOO_MANY_SESSIONS        
Exceeded max sessions for this initiator.

0xEFFF001FL : ISDSC_SESSION_BUSY
Session is busy since a request is already in progress.

0xEFFF0020L : ISDSC_TARGET_MAPPING_UNAVAILABLE
The target mapping requested is not available.

0xEFFF0021L : ISDSC_ADDRESS_TYPE_NOT_SUPPORTED
The Target Address type given is not supported.

0xEFFF0022L : ISDSC_LOGON_FAILED             
Logon Failed.

0xEFFF0023L : ISDSC_SEND_FAILED              
TCP Send Failed.

0xEFFF0024L : ISDSC_TRANSPORT_ERROR          
TCP Transport Error

0xEFFF0025L : ISDSC_VERSION_MISMATCH         
iSCSI Version Mismatch

0xEFFF0026L : ISDSC_TARGET_MAPPING_OUT_OF_RANGE
The Target Mapping Address passed is out of range for the adapter configuration.

0xEFFF0027L : ISDSC_TARGET_PRESHAREDKEY_UNAVAILABLE
The preshared key for the target or IKE identification payload is not available.

0xEFFF0028L : ISDSC_TARGET_AUTHINFO_UNAVAILABLE
The authentication information for the target is not available.

0xEFFF0029L : ISDSC_TARGET_NOT_FOUND         
The target name is not found or is marked as hidden from login.

0xEFFF002AL : ISDSC_LOGIN_USER_INFO_BAD
One or more parameters specified in LoginTargetIN structure is invalid.

0xEFFF002BL : ISDSC_TARGET_MAPPING_EXISTS    
Given target mapping already exists.

0xEFFF002CL : ISDSC_HBA_SECURITY_CACHE_FULL
The HBA security information cache is full.

0xEFFF002DL : ISDSC_INVALID_PORT_NUMBER
The port number passed is not valid for the initiator.

0xAFFF002EL : ISDSC_OPERATION_NOT_ALL_SUCCESS
The operation was not successful for all initiators or discovery methods.

0xEFFF002FL : ISDSC_HBA_SECURITY_CACHE_NOT_SUPPORTED
The HBA security information cache is not supported by this adapter.

0xEFFF0030L : ISDSC_IKE_ID_PAYLOAD_TYPE_NOT_SUPPORTED
The IKE id payload type specified is not supported.

0xEFFF0031L : ISDSC_IKE_ID_PAYLOAD_INCORRECT_SIZE
The IKE id payload size specified is not correct.

0xEFFF0032L : ISDSC_TARGET_PORTAL_ALREADY_EXISTS
Target Portal Structure Already Exists.

0xEFFF0033L : ISDSC_TARGET_ADDRESS_ALREADY_EXISTS
Target Address Structure Already Exists.

0xEFFF0034L : ISDSC_NO_AUTH_INFO_AVAILABLE
There is no IKE authentication information available.

0xEFFF0035L : ISDSC_NO_TUNNEL_OUTER_MODE_ADDRESS
There is no tunnel mode outer address specified.

0xEFFF0036L : ISDSC_CACHE_CORRUPTED          
Authentication or tunnel address cache is corrupted.

0xEFFF0037L : ISDSC_REQUEST_NOT_SUPPORTED    
The request or operation is not supported.

0xEFFF0038L : ISDSC_TARGET_OUT_OF_RESORCES   
The target does not have enough resources to process the given request.

0xEFFF0039L : ISDSC_SERVICE_DID_NOT_RESPOND  
The initiator service did not respond to the request sent by the driver.

0xEFFF003AL : ISDSC_ISNS_SERVER_NOT_FOUND    
The Internet Storage Name Server (iSNS) server was not found or is unavailable.

0xAFFF003BL : ISDSC_OPERATION_REQUIRES_REBOOT
The operation was successful but requires a driver reload or reboot to become effective.

0xEFFF003CL : ISDSC_NO_PORTAL_SPECIFIED      
There is no target portal available to complete the login.

0xEFFF003DL : ISDSC_CANT_REMOVE_LAST_CONNECTION
Cannot remove the last connection for a session.

0xEFFF003EL : ISDSC_SERVICE_NOT_RUNNING      
The Microsoft iSCSI initiator service has not been started.

0xEFFF003FL : ISDSC_TARGET_ALREADY_LOGGED_IN 
The target has already been logged in via an iSCSI session.

0xEFFF0040L : ISDSC_DEVICE_BUSY_ON_SESSION
The session cannot be logged out since a device on that session is currently being used.

0xEFFF0041L : ISDSC_COULD_NOT_SAVE_PERSISTENT_LOGIN_DATA
Failed to save persistent login information.

0xEFFF0042L : ISDSC_COULD_NOT_REMOVE_PERSISTENT_LOGIN_DATA
Failed to remove persistent login information.

0xEFFF0043L : ISDSC_PORTAL_NOT_FOUND         
The specified portal was not found.

0xEFFF0044L : ISDSC_INITIATOR_NOT_FOUND      
The specified initiator name was not found.

0xEFFF0045L : ISDSC_DISCOVERY_MECHANISM_NOT_FOUND
The specified discovery mechanism was not found.

0xEFFF0046L : ISDSC_IPSEC_NOT_SUPPORTED_ON_OS
iSCSI does not support IPSEC for this version of the OS.

0xEFFF0047L : ISDSC_PERSISTENT_LOGIN_TIMEOUT 
The iSCSI service timed out waiting for all persistent logins to complete.

0xAFFF0048L : ISDSC_SHORT_CHAP_SECRET        
The specified CHAP secret is less than 96 bits and will not be usable for authenticating over non ipsec connections.

0xEFFF0049L : ISDSC_EVALUATION_PEROID_EXPIRED
The evaluation period for the iSCSI initiator service has expired.

0xEFFF004AL : ISDSC_INVALID_CHAP_SECRET      
CHAP secret given does not conform to the standard. Please see system event log for more information.

0xEFFF004BL : ISDSC_INVALID_TARGET_CHAP_SECRET
Target CHAP secret given is invalid. Maximum size of CHAP secret is 16 bytes. Minimum size is 12 bytes if IPSec is not used.

0xEFFF004CL : ISDSC_INVALID_INITIATOR_CHAP_SECRET
Initiator CHAP secret given is invalid. Maximum size of CHAP secret is 16 bytes. Minimum size is 12 bytes if IPSec is not used.

0xEFFF004DL : ISDSC_INVALID_CHAP_USER_NAME   
CHAP Username given is invalid.

0xEFFF004EL : ISDSC_INVALID_LOGON_AUTH_TYPE  
Logon Authentication type given is invalid.

0xEFFF004FL : ISDSC_INVALID_TARGET_MAPPING   
Target Mapping information given is invalid.

0xEFFF0050L : ISDSC_INVALID_TARGET_ID        
Target Id given in Target Mapping is invalid.

0xEFFF0051L : ISDSC_INVALID_ISCSI_NAME       
The iSCSI name specified contains invalid characters or is too long.

0xEFFF0052L : ISDSC_INCOMPATIBLE_ISNS_VERSION
The version number returned from the Internet Storage Name Server (iSNS) server is not compatible with this version of the iSNS client.

0xEFFF0053L : ISDSC_FAILED_TO_CONFIGURE_IPSEC
Initiator failed to configure IPSec for the given connection. This could be because of low resources.

0xEFFF0054L : ISDSC_BUFFER_TOO_SMALL
The buffer given for processing the request is too small.

0xEFFF0055L : ISDSC_INVALID_LOAD_BALANCE_POLICY
The given Load Balance policy is not recognized by iScsi initiator.

0xEFFF0056L : ISDSC_INVALID_PARAMETER        
One or more paramaters specified is not valid.

0xEFFF0057L : ISDSC_DUPLICATE_PATH_SPECIFIED 
Duplicate PathIds were specified in the call to set Load Balance Policy.

0xEFFF0058L : ISDSC_PATH_COUNT_MISMATCH      
Number of paths specified in Set Load Balance Policy does not match the number of paths to the target.

0xEFFF0059L : ISDSC_INVALID_PATH_ID          
Path Id specified in the call to set Load Balance Policy is not valid

0xEFFF005AL : ISDSC_MULTIPLE_PRIMARY_PATHS_SPECIFIED
Multiple primary paths specified when only one primary path is expected.

0xEFFF005BL : ISDSC_NO_PRIMARY_PATH_SPECIFIED
No primary path specified when at least one is expected.

0xEFFF005CL : ISDSC_DEVICE_ALREADY_PERSISTENTLY_BOUND
Device is already a persistently bound device.

0xEFFF005DL : ISDSC_DEVICE_NOT_FOUND         
Device was not found.

0xEFFF005EL : ISDSC_DEVICE_NOT_ISCSI_OR_PERSISTENT
The device specified does not originate from an iSCSI disk or a persistent iSCSI login.

0xEFFF005FL : ISDSC_DNS_NAME_UNRESOLVED      
The DNS name specified was not resolved.

0xEFFF0060L : ISDSC_NO_CONNECTION_AVAILABLE
There is no connection available in the iSCSI session to process the request.

0xEFFF0061L : ISDSC_LB_POLICY_NOT_SUPPORTED
The given Load Balance policy is not supported.

0xEFFF0062L : ISDSC_REMOVE_CONNECTION_IN_PROGRESS
A remove connection request is already in progress for this session.

0xEFFF0063L : ISDSC_INVALID_CONNECTION_ID    
Given connection was not found in the session.

0xEFFF0064L : ISDSC_CANNOT_REMOVE_LEADING_CONNECTION
The leading connection in the session cannot be removed.

0xEFFF0065L : ISDSC_RESTRICTED_BY_GROUP_POLICY
The operation cannot be performed since it does not conform with the group policy assigned to this computer.

0xEFFF0066L : ISDSC_ISNS_FIREWALL_BLOCKED
The operation cannot be performed since the Internet Storage Name Server (iSNS) firewall exception has not been enabled.