Support
Frequently Asked Questions
Below is a list we’ve compiled of common questions. If you have a question not listed please contact us by phone or email and we’ll be glad to help! Also don’t forget we have training video FAQ’s.
Getting started, hardware, and OS
What OS and HBA do you recommend I use with the STB Suite?
The STB Suite version 9.2 officially supports:
- Windows XP SP2 higher (32 and 64bit)
- Windows Server 2008 (32 and 64bit)
- Windows Server 2012 (32 and 64bit)
- Windows Vista (32 and 64bit)
- Windows 7 (32 and 64bit)
- Windows 8, 8.1 (32 and 64bit)
- Windows 10
- Redhat Linux Kernel 2.6 or newer (API’s only)
The STB Suite will work with any off the shelf HBA. The SCSItoolbox Suite supports, SCSI, Fibre Channel (FC), SAS, and SATA. For SAS and SATA testing the STB Suite works very well with LSI 3801E controllers. For SATA Task Register commands an onboard Intel based chipset SATA controller works best.
What hardware do I need to use the STB Suite for testing SATA drives?
Any computer running a current version of Windows, either 32 or 64-bit, which has as many PCIe slots as your situation requires. This system should have one or more LSI 3800 or 3801 3G or 9200 6G SAS host bus adapters. Drives must be powered and cooled – we recommend that you use an appropriate drive enclosure which supplies cooling and power and also has a SAS expander to allow connecting the most drives.
Why do I need a SAS HBA, I will be testing SATA drives?
Using a SAS HBA allows connecting up to 16 drives per port, or 32 drives per typical SAS HBA. This of course allows testing of that many drives simultaneously.
You can attach a SATA drive to a motherboard native SATA port if you only need to access one drive at a time.
I have a brand xyz SATA add-in card – can I use that for SATA testing with the STB Suite?
No. Because Windows sees all add-in SATA cards as if they are SCSI host bus adapters Windows will prevent issuing any ATA or SATA Task Register Commands through these cards. You could accomplish simple read and write testing, but will not be able to retrieve INDENTIFY or SMART information.
Why don’t I see any devices to test with the STB Suite?
This typically means the STBTrace driver didn’t properly get installed on your system.
The STBTrace driver, which handles some of the basic IO operations, can be installed via the executable InstallSTBTrace_V840.exe, which is included in the STB folder
Install the InstallSTBTrace_v840.exe and verify the status of the driver:

Typically this driver will fail to install if STB was installed without being logged into the test system Locally and as Administrator.
Does the SCSItoolbox support Windows 2003 or more specifically Microsoft’s new StorPort driver?
Yes. It does with some changes to the way the Toolbox interfaces with the devices. By using Windows native driver the NTPORT driver you can get the Toolbox to operate using the Storport.
Follow these steps below:
Open up the Registry Editor by clicking on “Start”, then “Run”, and then type in “regedit” (without the quotes). Open up the key HKEY_LOCAL_MACHINE\SOFTWARE\STB\SCSI ToolBox\DriverExceptions\Win2000. On the right hand pane in the editor you will see BufferMgr and DEFAULTDRIVER. Double-click on BufferMgr and change the value to 2. Then double-click on DEFAULTDRIVER and change the value to 4.
Commands, protocol, and block size
Can I specify protocol type of commands to specify data I/O methods such as DMA, PIO, DMA QUEUED?
Most likely you cannot. Windows only allows a certain level of access for issuing task register commands and it may override an I/O type with what it thinks is a better way.
Can I generate “broken” protocol?
No, because the STB Suite uses off-the-shelf HBA’s and controllers. These controllers strictly enforce proper protocol and will not allow any deviation from the protocol standard.
Can I issue any SATA/ATA task register command?
Yes.
Does the STB Suite require a specific block size?
No, disks can be tested with any block size.
Does the STB Suite implement command queuing?
Yes, the requested queue depth can be entered as a test parameter and the test engine will attempt to issue commands up to that queue depth.
I recently noticed that there are SATA drives available which have 4,096 (4K) byte block size. Will the STB Suite work with these new drives?

You bet it will!
The STB Suite is what we call “block size agnostic” – we don’t care what the block size is. For each drive, we ask it for its capacity – its block size and the number of blocks it has.
We then use that block size in all of our calculations and I/O.
So the good answer is “yes- the STB Suite will work with drives of any and all block sizes”
Here is a screenshot of a current 12G SAS drive which uses 4K blocks –

Can I change HDD/SSD block sizes?
Q. I am used to being able to change block size on SAS and FC drives, from 512 bytes to 520 etc, so the drives can be used in RAID systems. How do I change block size on SATA drives?
A. Yes, SAS & FC drives will usually allow you to change to block size of the drive, from 512 to 520, from 520 to 512, etc. The main reason this is possible is because the SCSI specification supports this operation.
On the other hand, the SATA specification does NOT support block change operations. This means that without special custom or OEM firmware in the drive a SATA drive’s block size is fixed and cannot be changed.
There are some RAID manufacturers, EMC for one, who do sell RAID systems using SATA drives. If you examine one of these drives you will see that it does report a blocksize of 520 bytes. However, this is done by using a special interposer card between the drive and the RAID enclosure. This interposer fakes things and makes the drive appear to have 520 byte sectors. If you remove the interposer from these drives and examine the bare drive you will see it is 512 byte drive. We have also recently seen some RAID SATA drives with no interposers, which report a 520 byte block size. These drives have special OEM firmware and have no means to change the block size back to 512.
So – the short answer is, you cannot change the block size on a SATA drive.
How can I issue a Bus Reset using the SCSItoolbox Suite?
You can issue a Bus Reset using the Bus Reset Tool that is included with the SCSItoolbox Suite. Read more about the Bus Reset Tool.
How can I tell if my testing software is sending the commands I think it is to my devices?
You can look at the commands (CDB’s) using the Bus Analyzer Module that is included in the SCSItoolbox Suite. Read more about the Bus Analyzer Module
Can I read the SMART data off of my ATA Drive using the SCSItoolbox?
You can – and a lot more! A new feature in the SCSItoolbox Suite Version 6.0 is the ability to issue any task register ATA command to any ATA/SATA storage device. This allows test scenarios that include ATA commands that are not implemented in ATAPI such as retrieving SMART data, ATA IDENTIFY data, SEEK, SET MAX ADDRESS, and more. Read more about the Task Register Functionality
Firmware
Can I download firmware to my SATA drives?
Yes, you can download firmware to as many drives at a time as you have connected.
Does STB provide firmware files to its customers?
No, due to our complying with copyright and non-disclosure agreements with our drive manufacturing partners we are not allowed to distribute drive firmware.
Can I read the firmware out of one drive and then reload it into other drives?
No. Extracting firmware from a drive is not supported by any drives.
Is it possible for me to download the firmware from my HDD or Tape Drive and upload that firmware code to another drive?
No, this is not something that Manufacturers have allowed and thus the STB Suite cannot perform this task. Contact the HDD or Tape Drive manufacturer for the correct firmware files and the STB Suite can upload the firmware to the drive.
Disk purging
What is DOD purging?
DOD Purging means erasing all data on a drive to a standard defined by the Department of Defense (DOD), or by other government agencies. The basic DOD purge specification states that all blocks on a drive will be written with a data pattern, then all blocks will be written with the inverse of that data pattern, then all blocks will be written with another, usually random, data pattern, then the overwrite is verified.
Does the STB Suite accomplish DOD purging?
Yes, the STB Suite can DOD Purge SCSI, Fibre Channel, SAS, SATA, and ATA drives. Look at the Disk Manufacturing & Screening Module.
Can the STB Suite DOD purge drives which are attached to a RAID?
Typically no, although if you can configure the RAID into JBOD (Just a bunch of disks) mode so that each physical drive appears on your system by itself then you could purge it.
Can the STB Suite DOD Purge drives across a network?
No.
Does the STB Suite use the SECURITY ERASE command to purge SATA drives?
In most cases your computer will lock all ATA and SATA drives as the system boots up, preventing any destructive commands like SECURITY ERASE from being issued. There are methods to circumvent this lock or freeze condition in which case the command can then be issued and executed. It is beyond the scope of this FAQ to define this further – feel free to contact sales@stbsuite.com to set up a tech conference call.
Does the STB Suite support SATA SECURE/SECURITY ERASE?
First, what is SECURE ERASE?
The actual name of these commands is SECURITY ERASE, not SECURE ERASE. We’ll just call it SE from now on. The SE commands were developed as a method for an ATA/SATA disk drive to erase all data on itself. This functionality is built into the firmware of virtually all ATA and SATA drives manufactured since the early 2000’s. It is a government agency approved method of purging all data from a disk drive.
There are two levels of SE – Normal and Enhanced, with the enhanced level being an option that may or may not be implemented on any particular drive.
This table from the T13 ATA/ATAPI Command Set 4 documentation shows the differences –

Drives that implement SE will report:
- If they support SE or not
- If they support SE Enhanced Mode or not
- An estimate of how long a normal and an enhanced SE will take to complete
Does the STB Suite have a SE function?
Yes, as of version 9.0 the STB Suite has the ability to run a SE on either individual drives or on multiple drives simultaneously.
You can watch videos showing how to run a SATA SE from the Single Drive (Orginal Mode) and the Multi-Drive (DMM) from our Virtual Training Center here:https://stbsuite.com/support/virtual-training-center
How much per drive does it cost to purge data with the STB Suite?
Q. Our company is wanting to get into the service business of purging sensitive data off of disk drives, to government standards.
Many of the software disk purge solutions we are considering will have us pay them a fee for each disk that we purge. We hope to eventually be purging thousands of drives so we see that this per-drive-purge charge could amount to a LOT of money. I can’t find any information on your web site showing how much STB charges me to purge drives – can you help me find this information?
A. Our per-drive purge price is not found anywhere on our web site because we do not charge per disk purge.
In other words, our “extra” charge for you using the STB Suite to purge drives is zero dollars per drive.
Zilch, nada, nothing.
As an example, if you purge 10 drives a month, you would owe us an extra $0 that month. Or if you purge 1,000 in a month, your add-on charge that month would be $0 too. The formula is easy. It isn’t graded by volume, there is no discount available – it’s just always “no extra charge”. Keep that money for yourself – do something fun with it – enjoy!
Disk purging used to actually require the purge method to be tested and approved/accepted by a government agency. If you wanted to have a product to purge disks you had to find a government agency to “sponsor” you and work with you in conjunction with (at the time) the Defense Investigative Service (DIS) to grant you an official approval.
All of which we did with our DataScrubber product. Way back in the dark ages of computing – around 1993 or so. All of that work to get approval…it took about a year of solid testing and proving to earn it. Memories fade in our quickly changing marketplace, but I seem to remember that at the time there was one other company which actually completed that same process. It was a lot of work!
These days all product-explicit (disk purge) testing and approving is done away with. The specifications for a purge operation are just published and companies providing purge solutions are supposed to just conform to that specification.
One thing that means is that pretty much without exception there is NO difference in the way ANY purge software on the market actually works to accomplish the purge. They all do the same thing, and the facts are the disk manufacturers are actually making this process easier and easier with the new SAS and SATA command specifications.
So, do we not charge per purge because our purge is somehow inferior?
In a word, “No!”.
In the 1990’s we knew enough about disk purging that we were able to earn our endorsement, working with the Air Force and DIS. Believe me, we haven’t forgotten how to purge disks! I don’t remember any of today's disk purge companies being around back then…If so it would be fun to compare notes about what getting that approval was like.
We were there then. We’re here today. Then it was MUCH harder to do the purge, and it was certainly much harder to provide purge software when that approval was required…
So here’s a few other purge questions and answers for you to consider:
- Do our various disk purge techniques conform to government standards? – Yes
- How many drives per system can STB Suite Purge? – Hundreds at a time. At full disk speed.
- Can STB Suite Purge print a certificate detailing the purge process for each drive? – Yes
- Is there any other audit trail created by STB Suite Purge? – Yes, three separate records and databases record everything on a per-drive basis in addition to the certificate for your customer.
- Is the STB Suite Purge function being maintained? – Yes. All of the latest T10 & T13 purge technique proposals are already integrated (Sanitize, Crypto, SAS, SATA). Many new features in recent STB Suite releases have had to do with disk purging.
- Does the STB Suite Purge functionality quit working if I don’t do annual maintenance? – No. Without annual maintenance you will miss getting new features, access to technical support and such, but you will always be able to run the version of STB Suite which you last had covered. Including Disk Purge with NO Per-Purge charges.
- Can we customize the purge – number of passes, data patterns, how is the purge verified, etc? – Yes to all of that. We are even happy to help you configure your purge setup for getting the maximum number of drives purged per month.
Summary
You will want to maximize the number of drives you can purge per day/week/month/year ASAP.
We want to help you do that, like we’ve been helping companies do for the past 24 years.
After all, it will cost you the same to purge 5,000 drives in a month as to do 1 – it will cost you nothing more!
Read about the most advanced unlimited HDD/SSD purging tool on the market here (no it’s not PAY PER PURGE).
Is there a faster way to execute a DoD 5220/NIST disk purge?
Q. Dear Dr. SCSI – My customer requires that as part of our test procedure we “execute a DoD-5220/NIST disk purge”.
My understanding is that that type of purge requires 3 full write passes of the entire drive. I just tried a 4TB drive and can see that it is going to take over 6 hours per pass – 18 hours total!
Is there anything I can do to meet the customer requirement but in a faster way?
A. Yes, you can cut your old purge time down to one-third of the previous because of a change made to the DoD5220/ NIST specification in 2012!
Previously the DoD 5220.22-M specification defined an acceptable purge method as this (3-pass method):
2006 – Overwrite all addressable locations with 1)a character, 2)its complement, 3)then a random character and verify..
Clearly three passes was specified at that time. Actually the argument could be made for four passes, since there is the vague requirement to “verify”. Does that mean verify every block on the drive? One block? The official specification doesn’t make this very clear.
But that lack of clarity doesn’t matter now because in 2012 the specification was changed to this –
2012 – If neither of the first two options is supported, use the native read and write interface to write least a single pass with a fixed data value, such as all zeros. Multiple passes or more complex values may alternatively be used.
You can download the newest specification here – NIST SP 800-88 Rev. 1
Appendix A of this document has all the details – here is a repeat from that appendix –
SCSI Hard Drives This includes SCSI, SAS, Fibre Channel, etc. Clear: Overwrite media by using organizationally approved and validated overwriting technologies/methods/tools. The Clear pattern should be at least a single pass with a fixed data value, such as all zeros. Multiple passes or more complex values may alternatively be used.
The new specification document describes the newer purge methods such as the SANITIZE and CRYPTO ERASE commands, but this article is mainly about the question of “how many passes does the DoD 5220 spec require” – and the answer to that is “one pass”. You can do more passes if you like, but one pass will meet the DoD requirement.
Note: all current purge commands such as the SANITIZE and CRYPTO commands are supported by the STB Suite. In the next STB Suite release an option to specify either a “1-pass DoD” or a “3-Pass DoD” purge will be supported.
Is there any way to write less than the entire drive but still remove any partition, FAT, or RAID volume information?
Yes, but there could definitely be bad consequences of doing so…
First, you would have to know where the FAT or partition information resides on the drive.
Usually one copy of the FAT or partition information is written at the first part of the drive. So if for example you ran a Sequential Write test on the first 1MB of the drive (2,000,000 blocks) you would probably overwrite the first copy of the FAT or partition information. But be aware that most if not all OSs keep multiple copies of FAT/partition information, spread over the full area of the drive. In order to be able to recover if the base FAT is damaged.
So, if you overwrote the first MB of drive, then connected the drive back to the original system it was on, there is a very strong possibility that the OS will still be able to recover the FAT and make the drive mountable again.
But, even if the OS can’t recover the FAT or partition information, just overwriting the FAT does NOT remove the actual user data that the FAT pointed to.This would be the exact same result you would get if you were to use Windows to delete all files on the drive. Yes, the FAT will be empty, but the user data is still resident and is recoverable.
In summary – There are problems with the concept of deleting just FAT, partition, or RAID volume information:
- Each OS that creates a FAT or partition may create these structures in different places on the drive. You would need to experiment or be very familiar with each OS that you are trying to work with. It is not as simple as just overwriting one section of the drive.
- Most OSs create more than one copy of the FAT or partition info, spread all over the drive. To completely clean the drive of all copies of the FAT information might require 10’s or even hundreds of copies of the FAT to be found on the drive and overwritten.
- Removing just the FAT or partition information does not remove the actual user data.
Saving time by trying to just remove FAT or partition information could lead to shipping refurbished drives that still contain original user data. In our opinion this is not an acceptable practice!
How long will it take to purge my drive?
Q. “Dear Dr SCSI, I have a pallet of 600GB drives. I need to zero out all blocks. How long will this take?”
A. That depends on two things, and is easy to calculate. Just follow the simple steps below.
How long will it take?
The answer to this question depends on two things:
- What is the size of the drive, and
- How fast can you transfer data to the drive
What size is the drive?
This one is pretty easy. We will do all of our calculations using megabytes (MB).
Your drives are 600GB, which in MB equals 600,000.
1 GB = 1,000 MB, 1TB = 1,000,000 MB
So – for calculations we will say that your drives are 600,000 MB size.
If you don’t already know what the size of your drives is, then go into STB Suite Original Mode and look at the drive display for your drive. In our example our drive is 1,953,513 MB (2 TB)

How fast can I write data?
To determine your real-world data transfer speed we will use DMM. Go into the STB Suite Advanced Multi-Drive testing mode (DMM).
Select your drive in the Devices list, then click the Sys Thruput button –

DMM will run a quick non-destructive test and will display the average sustained data rate in the Test Progress window –

Our system with this particular drive can run at 136 MB/sec.
NOTE: if you will be zeroing out multiple drives, then select them all in the step above. The System Throughput test will display the real-world transfer rate which your particular test system can sustain with multiple drives.
Another NOTE: However, if you choose to use the WRITESAME zero method for zeroing out the drives then only select one of the drives and use that number in your calculations.
“What’s the frequency, or time, Kenneth?”
Take the capacity of your drive (in MB), and divide it by the speed from above –
Our test system setup
1,953,513 / 136 = 14,364 seconds, or 239 minutes, or about 4 hours.
Your 600G drives
600GB = 600,000 MB
600,000 / 136 = 4,411 seconds, or 73 minutes, or about 1.2 hours
I’m looking for your DOD (Department of Defense) certified product the SCSI Data Scrubber, do you still offer that product?
The DOD standards for disk erasure can be found at: http://www.dss.mil/documents/odaa/nispom2006-5220.pdf From STB’s Website: nispom2006-5220.pdf
The bottom line for disks with data classified lower than Top Secret is that they may be erased by writing a data pattern to all disk blocks, then writing the complement of the first data pattern to all blocks, then writing random data to all blocks. The STB Disk Manufacturing Module (DMM) test sequence file may be downloaded here : https://stbsuite.com/gfx/DiskScrub.zip – download it and you can erase multiple drives simultaneously and quickly with DMM.
What about disks with Top Secret or above data? Magnetic degaussing or physical destruction is the only approved solution.
Testing, logging, and DMM
What types of logs does STB Suite generate?
Several types of logs are generated during testing. First, an Access database log is created that journals every step taken during the test. Second, individual text logs are generated for each drive under test.
What information is in the STB Suite logs?
- The log files describe all device parameters and identification, such as manufacturer, model, firmware level, and serial number. All test parameters for each test step are described, and the status or results of the test are logged – such as “Passed” or “Failed”, or in the case of a test step with gathers data, such as the SATA Info test the data gathered is logged.
- If the test transfers data then detailed performance metrics describing the transfer I/O performance are logged. This will include transfer rate in MB/s. IO/s per second, Number of blocks transferred, the fastest, slowest, and average command-completion time, and the standard deviation of the command completion times.
- If an error occurs during a test all error information will be logged, such as “Passed” or “Failed”, in the case of a command CHECK CONDITION all bytes of the CDB will be logged along with the Sense Key, Code, and ASQ., as well as all SENSE DATA returned by the drive.
- If the error is a data compare error the block number and byte index into the block where the error occurred will be displayed along with the expected data and the actual data.
How are errors dealt with during testing?
STB Suite error handling is highly complex. At the simplest level upon an error the DUT may have the current test step stopped and then proceed to the next step. Or all further testing on the DUT may be stopped. Or the error may be ignored. In addition any executable program may be run upon an error.
Is it possible to asynchronously log information to a device’s DMM logfile?
New in the 7.1.0 version is the feature where one can log information to the device’s DMM logfile, even while the device is currently under testing within DMM! In the 7.1.0 version is included the executable AsyncTest.exe – within this application you can asynchronously log information to a device’s DMM logfile, or, if you like, you can use the source code contained in the AsyncTest project and put it into your own application.
Is it possible to asynchronously fail a device while testing is undergoing in DMM?
New in the 7.1.0 version is the feature where one can fail a device while it is undergoing testing within DMM. What happens after the device fails is determined by the “Stop on Error” option you choose for that test step (you can continue to the next step, stop all testing on the drive, or run an external program). In the 7.1.0 version is included the executable AsyncTest.exe – within this application you can asynchronously fail a device during testing within DMM, or, if you like, you can use the source code contained in the AsyncTest project and put it into your own application.
Can I modify an existing test sequence so I don’t have to start over from scratch?
Yes, there sure is! Just follow these steps:
- Load your existing test sequence
- Make sure that the Test Setup tab is selected
- In the upper right corner (in the Test Sequence window) highlight the first test step
- Make whatever changes you want made. In this case you want to change the path to the log file folder, so click on the Advanced Options button, use the Browse button […] next to the Path to Log Files box and choose the new location where you want the log files to be created.
- Now click OK to exit the Advanced Options
- Now click the Modify Current Test Step button – this will save the change(s) you just made.
- When you have made all the changes you want re-save your test sequence using the Save Setup button.
Note: you can repeat steps 3-6 to make as many changes as you need to make.
Just remember –
- Highlight the test step you want to modify
- Make your changes on the Test Setup and/or Advanced Options tabs
- Click Modify Current Test Step to save your changes to each test step
- Re-save your test sequence when you’re done
I need to set the Mode Pages on a batch of drives to certain settings, then test, then return the Mode Pages all to their factory default values.
First – Create a “Golden” drive – Set the Mode Pages for testing
Use the STB Suite Original Mode Edit Mode Page function to set all the Mode Pages the way you want for testing.
Next, Save those settings.
The use Original Mode top-menu Disk->Create Mode Page File for Diskscreening choice to save all of your Mode Page/Parameter settings to a disk file –

Now test with DMM
In DMM Pre-Test Actions check MODE Pages, Set Mode Pages with file, and browse to your saved Mode Page settings file –

Then do your testing
And finally, set all Mode Pages back to their factory defaults in Post-Test Actions –

That’s all there is to it!
Note – you could also choose to set all Mode Pages with a Mode Page Settings file after testing.
But wait, there’s more!
You could also set all Mode Pages to factory default in Pre-Test Actions.
Leave them alone, set them to default, set them to a Golden drive setting, before testing, after testing.
I have a test sequence which I loop to run for 48 hours. If any drive(s) fails at any time I want to no longer test the failed drive on subsequent loops.
Yes – the STB Suite DMM has exactly what you need!

When you start your DMM test sequence run you will see this dialog box –

Simply check the option show here and all failed drives will not be tested in subsequent loops.
Can you tell me how to test if vibration in my enclosure could be causing problems?

I saw a video on the internet illustrating how vibration can effect drive performance and even cause errors –
You and the video are absolutely correct – vibration from or within a drive enclosure can cause problems. Here’s how to use the STB Suite to test for this.
To do this test we are going to use two simultaneous instances of STB Suite DMM. One instance will select all drives minus 1 and execute a random access test on those drives. That will set up the right circumstances for maximum vibration within the enclosure as each drive randomly seeks.
While those drives are shaking themselves and the enclosure we will execute a Sequential Write and then Read test on the remaining drive. This drive should be a SAS, SCSI, or FC drive so we can monitor the drives Log Pages for various types of uncorrected and corrected errors.
Here are the steps to accomplish this vibration testing:
- Load up your enclosure with your normal load of drives. We recommend that at least one of the drives be a SAS, SCSI, or FC drive because these types of drives have much better error reporting than SATA drives. It’s OK for only one drive to be SAS/SCSI/FC.
In this example we have a total of 8 drives. - Start an instance of the STB Suite in Multi-Drive Mode (DMM)
- Now run a quick test to get an error baseline picture of your main test drive. Select the SAS/SCSI/FC drive that will be running the sequential test and run this short test sequence –

- Run this test on one drive. This will record what type of errors this drive will report during a sequential test with no induced vibrations. We will run this baseline test on Target 264.
- Now start another instance of STB Suite – Multi-Drive Mode. Leave the first instance up and running.
We will use DMM Instance #1 to induce the vibration by running Random seek tests on all but one drive.

Define the Random test in DMM #1 like this:

- Select all but one drive in DMM #1. We will leave the first drive at Target 263 not selected.

- Now in DMM #2 define the sequential Write and Read test, like this

Note that the Write and Read test uses the default transfer size of 128 blocks and does NOT have the Advanced Option FUA Set turned on. - Select the drive that was not selected in step 6 – Target 264
- Start the test on DMM #1, then start the test on DMM #2
- When the Sequential test on DMM #2 finishes open the DMM Log File for drive 264 and examine the Write and Read Error Log Page entries. This .Log file will have the first baseline Log Page results, measured while the enclosure is not vibrating, and then at the end of the file it will have the Log File results from when the other drives were vibrating the enclosure.
Here are the Write and Read Error Count Log page baseline values –

And here are the Write and Read Error Count Log Pages while the other drives were vibrating –

In our case there is a very small increase in the number of corrected errors while the enclosure is vibrating. In this case it would probably be prudent to run the above tests for a longer period of time. We recommend that if you do see a small difference like this that you change the test definitions to run for the same length of time that your standard disk tests run for, and see what the increase in errors is over that period of time.
If you see that the second set of log page Write & Read Error entries have significantly more errors, particularly various corrected errors, then you likely do have a vibration issue in your enclosure.
And if you see an increase in UnCorrected errors during vibration run the test again for a longer time. If you still get Uncorrected errors during vibration that indicates that there is a serious vibration issue with your enclosure.
If your normal testing does any screening on Log Page error Page/Parameters be certain that you take this vibration issue into account so you won’t be fooled by errors caused by enclosure vibration instead of actually drive problem errors.
I started some FORMATs running, and after about three hours the formats all failed.
Yes, we have occasionally seen this problem. Most of the time it is caused by a Windows feature called PCIe Link State Power Management (LSPM).
LSPM is an OS power savings feature which will turn off PCIe cards if they haven’t been accessed for some period of time.
When a SCSI command which takes a long time to complete, such as a FORMAT command, is issued to a drive the command is in an intermediate state until the format operation completes. To the operating system this appears as being inactive and so eligible for the LSPM feature to shut the power off to the HBA.
This has disastrous results – when the Format completes the drive signals this to the HBA, but the HBA is asleep and so ignores the completion of the command.
The end result is the Format command never completes and so the drives format is corrupted, leaving the drive showing up with zero blocks capacity.
The cure to a corrupt format is to reformat the drive and be certain that the format completes.
To view your test systems’ LSPM settings go to the Power & Sleep settings by typing Power and Sleep into the search box. Scroll down to Related Settings -> Additional Power Settings, choose Change Power Settings, then choose Change Advanced Power Settings

Scroll down and select the PCI Express choice and open the Link State Power Management choice

The only proper setting is OFF – if your system is set to anything else then change it to OFF.
This will prevent the OS from shutting down your HBA .
What is the difference between using a format command and doing a sequential write test
A format command is actually not guaranteed to do anything at all to a disk drive.
It may in fact overwrite all blocks on the drive, but then again it may not. OTOH a sequential write test of the entire will guarantee that all blocks have been overwritten.
What do the official specifications say about Format commands?
For SAS/SCSI/FC drives
the T10 SCSI Block Commands (SBC-3) document says this:
The FORMAT UNIT command requests that the device server format the medium into application client accessible logical blocks as specified in the number of logical blocks and logical block length values received in the last mode parameter block descriptor in a MODE SELECT command. In addition, the device server may certify the medium and create control structures for the management of the medium and defects. The degree that the medium is altered by this command is vendor specific. (Emphasis mine).
And what about SATA?
The T13 ATA/ATAPI Command Set (ACS-2) document says this about the Format Command…nothing. That’s right – there isn’t a Format command in the SATA/ATA command specification! The closest thing found is in the SCSI->ATA Translation (SAT-3) document, describing how a SCSI FORMAT UNIT command may be mapped to an ATA/SATA drive –
The FORMAT UNIT command verifies that all logical block addresses accessible to SCSI application clients are formatted and ready for data transfers.
That’s pretty vague. In fact the SAT-3 specification further states this concerning the FORMAT UNIT Op Code:
Set to 04h. If no defect list header is provided or a defect list header is provided with the DCRT bit set to one, then the SATL shall return GOOD status without issuing any commands to the ATA device.
So in reality, issuing a FORMAT UNIT command to a SATA drive is not guaranteed to do much of anything. It may, or it may not. And for SAS/SCSI/FC drives? Remember that the spec states The degree that the medium is altered by this command is vendor specific.
It may overwrite the drive, but then again it may not, at the drive vendor’s discretion.
When you absolutely, positively…
If you need to be 100% certain that every block on the drive has been overwritten then you must take matters into your own hands and explicitly overwrite all blocks yourself. This is easily accomplished in the STB Suite DMM by defining a Sequential Write test which will write your chosen data pattern to all blocks on the drive. Using the DMM Test Setup tab define your test step like this:

(The Blocks -1 tells DMM to write all blocks on the drive)
Confirmation
If you need 100% assurance that every block on the drive was indeed overwritten, simply define a second test step to run a Sequential Read test across all blocks, doing a data compare operation – like this:

If there was a block which wasn’t correctly overwritten the DMM test will mark the drive as failed and the DMM log file will look like this:
09/10/2012 12:16:42 TEST 1 of 1: Read Test; Sequential; for 1 Minutes Fixed-Length Transfers of 128 (0x0080) Blocks Start Block: 0 Data Pattern: Random; Data Compare ON Queue Depth = 1 FUA = OFF Stop-on-Error Type: Stop Current Test
09/10/2012 12:16:42 CDB = 28 00 00 00 00 00 00 00 80 00 Miscompare: LBA 0xA at 0x00000014 Exp: 41 54 47 32 65 20 20 22 94 A8 7A 55 61 74 67 52 Act: 30 30 36 32 30 4E 53 20 20 20 20 20 43 43 30 31 >>> Current Test Aborted <<<
09/10/2012 12:16:42 *** FAIL ***
If there were no data compare errors i.e. the drive was successfully completely overwritten, the DMM log file will show that the sequential read test with data compare passed.
Conclusion
There really isn’t any good reason to ever use a Format command. Of course if your customer asks you to format the drive, then go ahead and do it. But don’t count on that comm
We’ve been getting RMA’s from end users buying SATA drives saying they have “bad sectors.” I don’t know what test they use to determine this, but they pass a DST and SMART test when I plug them in.
Hello… some further questions…
Are you wanting to test that every sector on a drive can be written and read back correctly, as in writing a pattern then reading with data compare, failing if the compares don’t compare?
If so use a simple DMM test sequence of:
- Sequential write, entire drive (-1 blocks), any data pattern
- Sequential read, entire drive, same data pattern as #1, check the “Compare on Reads” box
This will test every block on the drive to ensure you that they all can be reliably written, read, and don’t have any data errors.
Or are you trying to determine if a drive is having problems but is getting past them using ECC or retries?
In this case you’ll need to look at the drives history, using View Log Pages for SAS/SCSI/FC,or View SMART Data for SATA.
Or are you trying to determine if a drive has had data errors in the past?
Same as above, you need to see the drives history of what error correction it’s had to do.
BTW…
I think it would be pretty rare to not have any reallocated sectors on a drive…
SATA Drives
You can see how many reallocated sectors a SATA drive has by looking at its SMART data.
Go to STB original mode->ATA/SATA->Commands-View SMART Data and select your drive.
SMART attribute 5 is the reallocated sector count – here’s one of my drives –

If you want to screen for these errors, in DMM you’d choose the SMART test step then define your criterion like this –

Add this test step into your test sequence. Then when you test any SATA drive that has more reallocated sectors than you defined will fail and the info will all be logged.
SAS/SCSI/FC drives
You can see how many reallocated sectors a SAS/SCSI/FC drive has by looking at its Log Page data.
Go to STB original mode and select your drive.
Right-click on the drive and choose View Log Pages –

This example shows a drive that has done 4 error corrections on Writes since the last time the log pages were reset. An “error corrected with possible delays” is most likely an error that required either a re-seek, or an error that required remapping the destination LBA.
You can also double-click on a drive, then select the Error Data tab

To see the drives error history.
If you want to screen for these errors in DMM click on the Test Thresholds tab and either use the Re-Reads or Re-Writes fields, or you can explicitly specify a Log Page/Log Paramemer/Value
combination.
Tape and libraries
I am trying to move media in a jukebox, but it tells me I can only move media from mail-slot.
Go to Options, Settings, click on Safe Jukebox Mode to remove Check mark
Can SCSI toolbox read and interpret the MAM on LTO tape technology?
In the SCSItoolbox Suite v.7.1 or later we display and interpret all MAM (LTO G1,G2,G3, and even G4).
We need the ability to change a WWNN/WWPN on a LTO drive. Do you offer this tool?
Drives can have their WWNN/WWPN changed, but it is done via a serial diagnostic port on the drive or on the library the drive resides in. It is not done via SCSI. This is not an operation that is support via any documented SCSI command.
Does the SCSItoolbox work with Fibre Channel (FC) Tape drives?
Yes.
Can I reset the G List on my drive? If my G-List is corrupt can it be fixed?
You can issue a Format command in the SCSItoolbox and tell it to ignore the G List.
Installation and error messages
During the install of SCSItoolbox I’m getting the message ‘A previous version of SCSItoolbox was found – you must remove this version first. SCSItoolbox install will exit’. I have already removed the previous version thru the Control Panel – what do I do now?
Unfortunately, during the uninstall process or lack thereof the STBSuite has been left in the Windows System Registry.
You will need to remove information contained in the Registry. To accomplish this you will need to launch the Registry Editor – this can be done by clicking “Start”, then “Run”, then typing in “regedit” (without the quotes). Once the Registry Editor is up, open the folder HKEY_LOCAL_MACHINE\SOFTWARE. Locate the STB folder and then right-click on it. Then click “delete”. Now you can run the new install without any problems.
I successfully installed the STB Suite version 8, but now when I try to use BAM I get the error message “HASP Not Found (-129) – why?
You need to have us upgrade your USB key. Go to your “STB\SCSI toolbox32\HASP Files” folder and use the program “STBKeyUpdateV722.exe”, send the authorization file to STB and we will send you a new file to upgrade your key for version 8.
What are the most common installation errors reported by customers doing an upgrade or an install
The answers are 1. seeing the error message “Access is denied” and 2. Seeing the error message “Performa Support period expired”
Access is Denied
This error is caused by attempting to run the STB Suite installation from a CD or DVD drive.
To avoid this error simply copy or unzip the STB Suite installation package on to your test systems hard drive and run the install from there.
Performa Expired

This error is caused by your USB key not having been updated when you renewed your Performa coverage. Navigate to the folder HASP Files in your STB folder and run the program STBCustomerKeyUpdateVer81.exe. You will see this screen –

Click on Create Request File and you will see

Email the file to support@stbsuite.com. You will receive an update file in response. When you get the update file run STBCustomerKeyUpdateVer81.exe again, this time click on Load Key Update File. Select the update file and your key will be updated with your new Performa information and you will see the message

Note: The above process is assuming that you have indeed renewed or kept your Performa coverage current and just forgot to do the key update process at that time. If you have any questions as to the status of your Performa coverage such as expiration date just email a question to support@stbsuite.com and include the four-digit serial number from the label on your USB key, or include the update request file from the steps above.
Licensing, support, and comparisons
What support is included with the STB Suite?
Each purchase of the STB Suite comes with 12 months of Performa coverage.
What happens if I have lost or had my hardware key (dongle) stolen? Can SCSI Toolbox just send me a new key, or can I buy just the hardware key?
The license IS the hardware key, and will not be replaced for loss or theft. What you will need to do is file a claim with your insurance company and report the loss or theft. They will then reimburse you for another purchase of the license, and subsequent hardware key.
If the HWK is broken, please contact support to have the HWK replaced. (Your broken or defective key will need to be returned to STB)
Can I upgrade to the latest version of the STB Suite?
Start your STB Suite license. Go to the Help menu. Select About SCSI ToolBox.

If your Performa date is expired, or expires, the highest version of STB Suite you can run is shown next to your Performa Expiration Date – in the case of this example version 9.2.2.
What is the difference between a Site/Lab and Corporate license?
A Site/Lab License is usually limited to a single facility within a company. A Site license utilizes a network hardware key (HWK or dongle) and is limited to a number of runtime licenses (minimum of qty 10). The hardware key is placed on a secure server, and up to the license limit of computers can launch the product(s) simultaneously.
Alternately, a Corporate License does not use a hardware key, and includes many more features, a custom build for the company, specific customization to the corporate build of SCSItoolbox, onsite training, and much more.
I’ve been looking at some other 3rd party testing tools, how do they compare to yours?
They don’t! The SCSItoolbox Suite is the Most Complete Suite of testing tools for your Peripheral testing needs. The SCSItoolbox doesn’t try and make you piece-meal your testing solution together. When you purchase the SCSItoolbox Suite you have access to every Module we offer. We know your testing needs can change so that’s why we’ve chosen to bundle everything you’ll ever need into one complete comprehensive package.
I used the Toolbox years ago – it looks similar today – what has changed?
Well, depending on how far back you go, the Toolbox has been around since the days of DOS, so a lot has changed. Over the past few years we’ve added hundreds of tests, including new Disk and Tape Screening/Manufacturing Modules, a 100% flexible Development API, Protocol support, graphing, database test reports, and much more. Read the full release notes here.
If I call into your support will I get to talk to someone that actually works on the product?
Yes. Our software is 100% engineered, developed, and supported by SCSI and storage experts in the USA. Your support questions go directly to the SCSI experts and programmers who work every day on nothing but the SCSItoolbox product. Because of this 90% of our support calls and emails are opened, answered, and closed within four hours. Our developers are readily available to answer your calls and emails directly. We do not use a 3rd party or contract group for our technical support, as we know how important your testing needs are. Having your questions answered accurately and quickly is our first and foremost goal. We know that actions speak louder than words, so feel free to call in or email a question and see for yourself that our support and service is second to none.
Some of your competitors seem to offer the same tests as you do – who’s is better?
That answer can only be answered by you. We are confident that if you do a side-by-side comparison of features, price, support, and ongoing commitment to our customers (as shown by the number of updates and new features) you will agree that there really is no comparison. We’re not afraid to put our money where our mouth is – our 30 day money back guarantee shows that we really believe our product is the best!
We have an in-house group providing our testing solution, why should I switch to use the SCSItoolbox?
This is a great question, and one that comes up often. Here are a few things to think about:
- At SCSI Toolbox, LLC we are here to help you do your job better. That being said, the SCSItoolbox has many features, and one that has become very popular among in-house development teams is the Developer Toolbox. This is a C++, VB, .NET, or in Linux a Shared Function library (DLL), that allows your testing engineers to write tests and focus on your results rather than fussing with low level functions, such as Command Tag queuing, logging, trapping errors, etc.
- Is the author(s) of your tests going to be willing to make changes to the tests as needed, and in a timely manner? At SCSItoolbox, we typically answer support calls and emails within a few hours.
- Many times the programmers writing in-house test applications end up transferring to other groups, departments, or leave the company. SCSItoolbox has been in business since 1992 working with every major storage peripheral company and continue to support the SCSItoolbox Suite and respond to an ever changing peripheral testing business.
Can STB help with our “in-house” testing solution?
STB Can Always Help!
For well over two decades the team at STB has been improving the incredible test tools that comprise what we call the STB Suite today!
The STB Suite tools are comprised of virtually every test tool you’ll need to accomplish your peripheral testing.
Engineering tools, Burn-In, ORT, MFG Screening, Compliance and more! The testing can be accomplished in a variety of ways also GUI setup, API’s, BUS Analysis, etc.
What happens if you’ve been using some in-house tools or a testing solution and for some reason you need to change? Maybe, someone has been developing the tests/tools internally for years and they’re no longer a viable option to maintain, change or improve those tests?
Recently we had a customer ask if we worked with National Instruments LabVIEW. We had reports of other customers using LabVIEW in the past with the STB Suite (in particular the Developer Toolbox API) but we hadn’t used it in-house at STB. So with a couple of on-site visits and technical support the Developer’s ToolBox (DTB), which is a set of APIs that are callable from other applications, was successfully imported into LabVIEW. In other words, if you have a LabVIEW application, and you need to issue I/O to a device (for example get Inquiry information from a drive, or read Log Pages), you can import our DTB into your LabVIEW application and call the API in DTB!
Once we verified that the APIs in our library was accessible from his LabVIEW application, anything is possible with the DTB library, including reading and writing from drives, to retrieving Log Page and Mode Sense data, to retrieving SMART data and IDENTIFY data from SATA drives, the sky is the limit!
So maybe you’re using LabVIEW another 3rd party test or automation system or maybe you’re using something that was written in-house, the simple fact is the STB Suite can be used to help improve, simplify and streamline your testing.
Contact STB today to find out how we can help improve your testing today!
Manufacturing Suite
What is the STB Manufacturing Package?
It is an economical way to greatly increase your disk testing throughput
What makes it economical?
An annual licensing price of $695 per seat
What are the licensing terms in simple language?
The seats are:
-
Annual Licenses (12 months at a time)
-
Include all updates released during the annual term
-
Available in quantities of 5 through 250 seats per key
What software is included?
-
The STB AME Automated Manufacturing Engine – executes DMM Test under Windows, and
-
the STB DME Disk Manufacturing Engine – runs many DMM Test Sequences under Linux
What other requirements are there?
You must own at least one full STB Suite and keep it under Performa coverage
How many drives can be tested at a time per license?
-
It depends on your test system configuration.
-
There are no limits in the software as far as number of drives which can be tested.
-
Existing customers commonly process hundreds of drives at a time per system.
How does it work- how do I use it?
You:
-
Use your full STB Suite to develop your Test Sequences.
-
Then run those Test Sequences using AME on your volume test systems.
-
All tests are run the same as under DMM
-
All logging is the same as under DMM
-
Test Sequences can be run but can’t be changed, making them safe to be operated by non-engineers.
Where can I get more information?
Just give us a call at (480) 600-9595, email info@stbsuite.com, or use our online form: Contact Us
About SCSI Toolbox
What’s the history of “Dr. SCSI” and what about Oct 21, 2015?
To try to make a long story short…
Our original, first generation SCSI tester product was being developed in the late 1980’s, as a “midnight engineering” project. We needed such a tester for my main disk drive distribution company, but that business kept us so busy we had to develop the tool a night, after normal hours.
Here’s an early prototype –
Sidebar: One of our first software products in the early 1980s was a customer/tape management product to computerize video tape rental stores – anyone remember those? Because of that we had a huge supply of movies on video tape, and something was always playing in the background while we worked.
Because we had several irons in the fire we needed a name for this SCSI tester product. One evening “Back to the Future” was playing in the background and I happened to be between thoughts when at the end of the movie Doc comes back to the future to pick up Marty to go into the future (Oct 21, 2015 to be precise). To refuel the time machine he dumped some garbage in the new “Mr. Fusion” power supply.
“Mr. Fusion”. For some reason that really tickled me.
Mr. Fusion.
Mr. Fusion…
Click! How about “Mr. SCSI”? The thought just snapped into place, one of those Eureka! moments.
Our tester had an internal name. Its officially marked name became the STM-100 –
Fast forward a few years. The hardware based Mr. SCSI tester had proven quite useful in our disk drive business. And as the ad shows we even sold it to other disk drive companies for testing and prepping drives.
But as with all hardware based products we had reached the end of what our original design could do.
So we decided to convert to a software based tester. In 2002 we left the disk drive distribution business and started a new company to do nothing but computer peripheral test and diagnostic tools – software tools this time.
This gave us so much more flexibility and power, we could adapt the product as technology evolved – it was just better all around. It was a much “smarter” solution.
So what should the smarter sibling or descendant of Mr. SCSI be known as?
That’s right – he was known as “Dr. SCSI”.
Dr. SCSI went on to have a car and a newsletter column –
And Oct 21, 2015?
That was the date that the time machine went to in “Back to the Future – Part 2”
Back to the Future day.
Mr. Fusion. Mr. SCSI. Dr. SCSI.
And that was the short version of the story – LOL!

