By using the Developers Toolbox (DTB) api you can send any command to any type of device.

This example will illustrate how to run a SATA SMART Self Test as a DMM test step, logging the results to the DMM device log file.

Using Microsoft Visual Studio C++ and the STB Suite Developers Toolbox api we can send any command we need to any type of device. Since DMM is communicating with SATA devices via a SAS controller which implements SAT (SCSI->ATA Translation) such as the LSI 3800 or 3801 we must write our program to issue the SATA command imbedded into a SCSI command, according to the SAT standard.

Our example project retrieves the address of the drive from the command line arguments passed by DMM. In addition DMM allows you to pass additional user defined command line arguments to your program. For example, you could modify this project to allow you to specify any of the different SATA Self Tests.

These files are used by Disk Manufacturing Module (DMM) to scrub/sanitize disks.

• DiskPurge-long.seq – this test does three write passes of the entire drive, using three different data patterns. After each write pass an entire read pass with data compare is done to verify the data overwrite. Note: These read passes are not required to meet the DOD 5220-22m spec
• DiskPurge-short.seq – this test does three write/verify passes of the entire drive using three different data patterns. It will run in half the time of the long test
• DiskErase-Speedy.seq – this test does on complete overwrite of every block on the drive, using a random data pattern.

This test sequence does:

1. Writes entire drive with alternating 0/1 data pattern
2. Reads entire drive doing data compare
3. Writes entire drive with alternating 1/0 data pattern
4. Reads entire drive doing data compare
5. Writes entire drive with random data pattern
6. Reads entire drive doing data compare

The test will fail if any WRITE or READ command fails, or if any data compare fails.

This is the same process done on DOD certified tests.

Erases the first blocks of the disk. Useful to wipe out master boot records or other OS remnants

Writes all blocks of the drive using the block number as the data pattern

Reads all blocks of the drive – insures that the drive is readable.

1. Writes and read with data compare. 1000000 blocks at beginning, 100000, and 2000000 blocks into drive.
2. 2 minute random access write/read with data compare
   
3. Records P and G defects to log file at beginning and end of test

Writes all blocks of disk using random data with LBA overlay

DOD compliant disk purge. Writes and reads three data patterns using data compare. Test will execute a total of 6 passes (3 write, 3 read) over the entire drive and may take a long time to complete.

1. 2 minutes of random access write/read with data compare, with FUA set on to force access to the drives physical media (rather than cache access).
2. 2 spin down/spin up cycles
3. 2 minutes of butterfly access write/read with data compare and FUA set on
4. 2 spin down/spin up cycles
5. 2 minutes of random access write/read with data compare and FUA set on
   
   All data patterns use random with LBA overlay

1. 2 minute random access read, 128 blocks/transfer, FUA set off
2. 1 spin down/spin up
3. 2 minute butterfly access read, 128 blocks/transfer, FUA set off
4. 1 spin down/spin up
5. 4 minutes random access read, as above
6. 1 spin down/spin up
7. 4 minute butterfly access read as above

1. The same functionality as the original STB “Disk Confidence Test 1”
2. 1GB sequential write, incrementing data pattern
3. 1GB sequential read with data compare
4. 5000 random access seeks (1 block read)
5. 4 spin down/spin up cycles

1. Make sure blocksize is 512 bytes/block
2. Make sure there are no more than 1 grown defect
3. Spin up all drives
4. Clear drive LOG pages
5. Sequential write 1000000 blocks, LBA data pattern
6. Sequential read 1000000 blocks with data compare
7. 5 minute butterfly write/read with data compare
8. Log number of primary and grown defects to log file

A read only test – 15 minutes of butterfly access reads

1. 11 minutes of write, 4 minutes of read
2. Incrementing data pattern with LBA overlay
3. Data compare on reads

1. Test to simulate a data server application
2. 15 minute random write/read, random transfer lengths, data compare

A quick test to verify data write/read and positioning

A test that writes file sets and file marks, then uses various space commands to move between file sets.

1. Writes and reads 2GB of 2:1 compressible data with compress set on and off. Clears LOG pages before each test, records LOG pages after each test.
2. Writes 3 files marks at beginning of tape, and skips over them during testing – to help test using a tape that is worn at the beginning of tape.