Disk Verification Test
Type: Automated Test
The Disk Verification test verifies a disk by doing random raw writes and reads and comparing the results.
The test is passed the instance path of the target test device. The test then finds all hard disks that are equal to or connected to the test device. It will then choose the best target for the test in the following order:
RAW unpartitioned disk
RAW unformatted volume
Volume that can be dismounted
Volume that cannot be dismounted
The test will run a random verify scenario on this target.
The test is given a fixed run time of 72 hours. The test will display a dialog box with the current progress and bandwidth of the test. The size of the individual data transfers is determined by a command-line parameter; the default size for the logo test is 32 KB.
The test will try to do raw writes, bypassing any file system that is mounted on the hard disk if it can (as in cases 1, 2, and 3 in the preceding list).
The amount of space that the test uses is determined by the free space that is available on the test device. To ensure best device performance, you should delete unnecessary files off the test device and cleanly format or defragment the device before running the test. The test will warn you if the targets fragmentation might influence the test results.
Even though this test does measure device performance, there is currently no test case in the Logo version of this test that will pass or fail based on these measurements.
For more information about the DiskIO test application, see the "Disk Stress" topic.
Run Time: 3 daysLog File: diskio.wtlSystem Restart Required: NoTest Category: Storage Adapter, Hardware Based RAID System, Hard Disk DriveSupported operating systems for "DFW" logo testing:Windows VistaWindows Server 2003Windows XPProgram:
The test tool runs on the following Windows operating systems:
Running Disk Verification Test
If you are testing any drive that requires media or testing in system-mode on a computer that contains drives that require media, you must insert media into the drives. The media that is used must be formatted and contain data that occupies at least 50% of the media's capacity.
Run on all associated devices.
Block size (integer) in bytes of IO transactions. MB & KB supported. ex: /b 32KB
Scenarios to test. <scenarios> should be a list delimited with ','s or ';'s. Valid characters are: s: sequential scenario, x: random scenario, r: read access, w: write access, v: verify (writes followed by reads and data verification), ex: /c sv;xr;xw, ex: /c sv,xr,xw
Device identifiers of devices to test delimited with ','s or ';'s. If none are specified all disks are tested. Identifiers include: Instance path, PhysicalDriveX, and Drive letter. An identifier of "any" will cause the test to run on any device on the system. ex: /d "IDE\DISKMAXTOR_6L160M0__________________________BANC1G10\5&2A36C317&0&0.1.0" /d PhysicalDrive1;G:;"PCI\VEN_8086&DEV_2651&SUBSYS_01791028&REV_03\3&172E68DD&0&FA"
Force file mode. The test won't attempt to dismount volumes. This should not be used as an accurate measure of disk performance.
Iterations (integer) to run. Cannot be specified with /d. Default is 1 if /d is not specified.
Number of buckets to use for approximate latency measurements.
Enable testing of optical drives.
Depth of the IO queue (integer).
Size (integer) in bytes of one iteration. KB, MB, & GB supported. ex: /s 6GB
Time (integer) in seconds to execute. Cannot be specified with /i. You may also use TimeSpan formatting: dd.hh:mm:ss
Use verbose logging /x <file.xml> Name of XML File to use for reporting. If file.xml is undefined a unique name based on machine, date, and time will be used.