Storage Testing in DTM Eric St.John Software Design Engineer in Test Storageマイクロソフトディベロップメント株式会社部署名名前

Basics Setup Check the Logo Program documentation for setup requirements for your program. Disk Storage / Adapters: be sure to follow the partition requirements. Adapters: be sure to install symbols on the test client. Optical / Removable-media: most tests require a particular type of media. Medium Changers: RSM is an optional component in Vista. Follow the steps to install and configure your changer before running any tests. Device Logo Make sure to check the documentation on which device in Device Console to select. Device/Driver Logo & Signature DTM will automatically select devices that load the exact same driver. Hash of driver must match. All files being submitted with the driver need to be referenced in the inf. Be sure that Device Console finds a device that’s using your drivers.

Device Targeting : Test parameters Determined automatically by DTM Client. Asynchronous and non-blocking: Refresh device console if hardware configuration changes. To check the parameters before test launching use “View device XML” in Device Console. To check the parameters of a test that has run, view the result report (see the effective parameters) of the root job in Job Monitor.

Device Targeting : Test parameters A yellow bang next to a selected job means that the job’s parameter’s need to be checked. IT DOES NOT INDICATE A PROBLEM. If you see a warning popup when scheduling a job, this indicates test parameters are missing. See the troubleshooting section in the Storage Docs to fix.

Device Targeting – Test Set Determined by input to Submission Wizard. Read all pages carefully. Determined automatically by DTM Studio. Detectable device characteristics are determined from the same data used to populate test parameters. If tests appear that should not (IE: SCSI Compliance for a SATA drive) or do not appear when the should (IE: UDF Formatter for an RW optical drive) it may indicate a device bug. Identify data Supported profiles IOCTL_STORAGE_QUERY_PROPERTY Your device must be present when saving a submission package. If the device is not present tests will appear as not run in the submission.

Serial ATA Devices New requirement: must pass SATA-IO testing Currently optional, but highly recommended. Many existing devices do not meet the electrical requirements required by SATA-IO Requirement becomes compulsory 6 months after Vista release. The test requires a certificate file provided by SATA-IO. See for more information.

SCSI Compliance Now required for all RAID adapters and external storage arrays. Key test case additions: Inquiry & VPD pages Mode pages: 0x08, 0x1C, & 0x3F VPD pages: 0x00, 0x80, & 0x83 Destructive write test cases added Check your drive partitions after running. Coming soon: Bus type verification by device class code. For more information see Designing RAID Adapters to work with Windows on

Fibre Channel HBA API Test cases added CT Pass through GIEL & GANXT SCSI Read Capacity Report LUNs FCP Target Mapping SM Management Pending specification completion. Will be required for SAS HBAs.

MMC Test Test has been re-written. Much more extensive. Issues with slim-drives & mechanical eject/inject drives. Errata exist which make the failures acceptable. Still require user to manually inject the drive to continue testing. Expect more profiles & test cases in the future.

Core Storage Tests SDStress – tuned to do more stress. Avg Runtime: 2 hours Data Verification Runtime: 3 days Crashdump Automated Debugger install. Manually install correct symbols. Ensure that system partition has Physical Memory + 1 MB Int13 Extensions

Core Storage Tests IFS Test – replaces file system tests. The device will be formatted automatically a number of times. Removable devices require user input during format.

Blogs.msdn.com\storwdk

© 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Version 3.0