IN THIS EDITION
Introduction SATA disk drives can run a variety of self tests. Running these self tests will thoroughly test drive functionality in a fairly quick manner, and will not change or damage customer data. A self test can be run at any time, and the detailed self test logs can be retrieved and saved – see the paper Introduction to SATA SMART logs paper, available from sales@scsitoolbox.com What are the different Self Tests?There are four different self tests available –
Running Self Tests on single drives in STB Original ModeFor drives which are connected directly to a motherboard native SATA port you will use the STB Original mode to run the self tests. Go to the top menu ATA/SATA->Tests->Execute SMART Self Test choice. Select your drive from the drives displayed in the Devices menu – the various self-test completion times for this drive will now be populated. The drive model and serial number will be shown as well as the completion times for the various types of tests – Click the Start Test button to begin testing – the status of the test will be reflected in the Results window and can be estimated by the Self Test Progress bar. The elapsed time the test has been running will also be displayed – Running Self Tests on multiple drives in the Disk Manufacturing ModuleAs of STB Suite version 8.1 running SMART Self Tests in DMM mode is accomplished by using the DTB DMMSataSelfTest application. You can obtain a copy of this application including the full source and project files by contacting sales@scsitoolbox.com SummaryThe SATA SMART Self Tests provide a consistent and easy-to-use method to determine the overall health of a drive. The STB Suite Original mode provides an interactive tool to run these tests on single drives, and the DTB application available from STB lets you run these tests in a multi-drive manufacturing environment.
Introduction Scrubbing or purging disk drives describes the process of removing all data from a disk drive in such a way that it is virtually impossible to retrieve any previously stored data from the drive. Other terms used for this process are sanitizing, overwriting, clearing, or in a very broad sense erasing. There are various US government agency specifications describing what type of data (secure, secret, top secret, etc) may be removed from a drive. In the case of the highest level of secret data the requirement is for the drive to be physically destroyed. The next step down from that would be erasing everything from the drive platters by a powerful magnetic degaussing tool. Degaussing not only removes data but it also removes all drive servo information leaving the drive unusable. The next step which can be addressed with the STB Suite is the overwriting process, which involves writing one or more data patterns to every block of the disk drive, and can also require reading back every data block to confirm or verify that the expected overwrite data pattern has been written. It is essential to insure that any drives which have been used and might contain any remnants of customer data be purged to entirely erase such data. Agency Requirements Different government agencies have different specifications or requirements to define what processes are needed to officially sanitize a drive. Some of those agencies are shown here along with a summary of their requirements: Since the most common agency requirement for companies in the United States who need to purge disk drives is the DoD 5220.22-M specification we will focus on that. DoD 5220.22-M Specification This DoD standard for sanitizing rigid magnetic disk drives is: Overwrite all addressable locations with a character, its complement, then a random character and verify. This process is extremely easy to implement using the STB Suite Disk Manufacturing Module (DMM). Implementation in DMM Implementing a DMM test sequence which meets all requirements of the DoD 5220.22-M specification is simple and creates an extremely efficient disk sanitization process. Because each separate disk drive being sanitized using DMM is processed with a entirely separate processing thread each drive can proceed at its maximum speed, regardless of any other drives being purged. This also allows you to mix various sizes of drives, and various interface (SCSI, FC, SATA, etc) drives within the same purge operation. A separate text log file will be created for each drive, giving you complete documentation of the purge process and most importantly the status each step or pass. The test sequence for DoD purging is made up of four simple DMM test steps:
Here is the detailed test sequence to accomplish the DoD-compliant sanitization:
How long will it take? You can accurately predict how long the purge operation will take by either looking at the Test Status tab while each test step is running – this will display the current I/O transfer rate along with the estimated time to complete. You can also obtain this information after the fact from the log files. Once you have run a purge on a few drives of each interface type you will be able to quickly estimate the time it will take to complete a purge on any size drive. Of course the time it takes to complete will be affected by how many drives at a time are running on each of your test systems HBAs. Experimentation will show for any given system how many drives can be run at a time while still maintaining their maximum throughput. As an example, a test system can sustain a write rate of 123 MB/s, and a read rate of 125 MB/s to one drive. This drives capacity is 70 GB (71,687 MB), and so the time to complete the purge operation will be In actually running the purge process on this drive the sustained rates were slightly less than predicted, most likely due to different transfer rates across different zones of the drive. The log file shows that the purge process took a total of 48 minutes. Here is the output log created by purging our example drive: Summary If your customer requirements call for higher levels of overwriting it is a simple matter to define a test sequence which completes as many write and/or verify passes, with whatever data pattern is required.
Here is a list of some recent customer training sessions that STB has conducted - live, interactive web sessions presented by STB programmers:
Contact Jeremy Wolfe at (720) 249-2641 today to schedule your own custom training session!
A. "Great question! Two of the oldest disk tests in the STB Suite are the Confidence Test 1 and Confidence Test 2. These tests were first included in the original DOS version of the SCSI Toolbox in the early 1990s. The philosophy of these tests was to stress and test as many drive functions as possible in a relatively short time. The tradition of these tests is continued into the SATA world with the new pair of SATA confidence tests. This article will describe the first test, which is the quicker running of the two. These new tests issue native SATA task register commands and so it is necessary to have your disk drive connected to your test system via one of your motherboard SATA ports." What the test testsSATA Confidence #1 is accessed via the STB Suite Original Mode top menu ATA/SATA->Tests->Drive Confidence 1 (Quick Test) menu choice. This SATA Quick Test runs the following test steps: As the test progresses the various steps will be shown in blue as the step executes, and once the step is complete it will be displayed either in green if the step passed or in red if the step failed – here the test has executed the first three steps with no errors – Test Results Output Test results may be viewed by scrolling the Test Status/Results window or by saving the log to a file. The saved log file will be a text file – here is an example: Summary This SATA Quick Test runs the following test steps: This test will run in a short time and will give you confidence that the drive is functional. It also provides a detailed log of the test results.
Thinking about upgrading your old STB Suite licenses? Now is the time!
You can purchase your upgrades online: http://www.scsitoolbox.com/buy.asp and save 5%, or call Jeremy 720.249.2641 in sales to get a customized quote.
|
|