Hitachi Global Storage Technologies

Drive Diagnostics & Disposition

Version 5.88

Quality Assurance
Hitachi Global Storage Technologies

Doc#DDD588236ext
© Copyright Hitachi Global Storage Technologies

Hitachi Global Storage Technologies

5600 Cottle Road
San Jose, CA 95193
Produced in the United Kingdom
2/03
Microsoft, Windows XP, and Windows are trademarks of Microsoft Corporation in the United States, other
countries, or both.
Other product names are trademarks or registered trademarks of their respective companies.
References in this publication to Hitachi Global Storage Technologies products, programs or services do not
imply that Hitachi Global Storage Technologies intends to make these available in all countries in which Hitachi
Global Storage Technologies operates.
Product information is provided for information purposes only and does not constitute a warranty.
Information provided is believed to be true as of the date of publication but is subject to change and is supplied
without guarantee.
This publication is for general guidance only.

Doc#DDD588236ext
 Table of Contents

1 Table of Contents
1 Table of Contents................................................................... 1
2 Release History...................................................................... 4
3 Introduction ......................................................................... 5
3.1 Drive failure mechanisms............................................................................... 5
3.2 What is DDD-SI................................................................................................ 5
3.2.1 OEM Integration ........................................................................... 6
3.2.2 OEM Field..................................................................................... 6
3.3 When to use DDD-SI ........................................................................................ 6
3.3.1 Optimise a disk drive ..................................................................... 6
3.3.2 Analyse / repair a disk drive ........................................................... 6
3.3.3 Assist with disk drive integration ..................................................... 6
3.3.4 Provide production line support ....................................................... 7
3.4 Enhancements In Version 5.88 Bld 236.......................................................... 7
3.4.1 New Features................................................................................. 7
3.4.2 Improvements ............................................................................... 7
3.4.3 Errata........................................................................................... 7
3.5 Platform Requirements .................................................................................. 7
3.5.1 Hardware...................................................................................... 7
3.5.2 Operating System........................................................................... 7
3.5.3 Drive Adapters............................................................................... 8
4 DDD Distribution and Installation ............................................. 10
4.1 Installation ..................................................................................................... 10
4.2 Registration ................................................................................................... 12
4.2.1 IDE ............................................................................................ 13
4.2.2 SCSI ........................................................................................... 13
4.3 Uninstall ......................................................................................................... 14
5 Starting DDD ..................................................................... 15
5.1 DDD can be started in a number of ways .................................................... 15
5.2 Command Line Switches............................................................................... 16
5.3 Front panel switches...................................................................................... 19
5.3.1 The DDD Device Control Center .................................................... 19
5.3.2 Release information ..................................................................... 20
-1-
Doc#DDD588236ext
 Table of Contents

5.3.3 Configuration .............................................................................. 21

5.3.4 Preparing for Test ........................................................................ 22
6 DDD Profiler ...................................................................... 23
6.1 Version of the Profile: ................................................................................... 24
6.2 Purpose of the Profile:................................................................................... 24
6.3 Procedure Description .................................................................................. 24
6.4 Supported Products ....................................................................................... 24
6.5 Minimum DDD-Version Required............................................................... 24
6.6 Tips and Tricks.............................................................................................. 24
7 Testing.............................................................................. 25
7.1 Completion of test ......................................................................................... 26
7.2 Drive Properties box ..................................................................................... 27
7.3 An Error Occurred - Check Event Log.......................................................... 27
7.4 Events Window............................................................................................... 28
7.5 Manual Entry ................................................................................................. 29
7.6 Dead drives .................................................................................................... 29
8 Results Logging ................................................................... 32
8.1 Drive by drive logging ................................................................................... 32
8.1.1 Binary Log Object file (.BLB) ......................................................... 34
8.2 Test logging .................................................................................................... 34
9 Utilities ............................................................................. 35
9.1 Using the Mode Page Tool............................................................................. 35
9.2 Command Line Exerciser ............................................................................. 37
9.2.1 SCSI ........................................................................................... 38
9.2.2 ATA ............................................................................................ 38
9.2.3 Available Commands .................................................................... 39
10 Appendix......................................................................... 43
10.1 Real Life Situations ..................................................................................... 43
10.2 A note on password protected drives ......................................................... 43
10.3 Hints and Tips ............................................................................................. 44
10.3.1 Installing Centos ATA CI-1500 adapters on Windows 95 Platform ..... 44
10.3.2 No ATA Drives Appear In The Control Panel Window After a Rescan . 44
10.3.3 The Test Doesn’t Start Having Pressed The Go Button .................... 44

-2-
Doc#DDD588236ext
 Table of Contents

10.3.4 FC-AL Drive Doesn’t Appear In The Control Panel Window After a
Rescan 44
10.3.5 Firmware Download Completes Without Successfully Loading
Microcode............................................................................................. 44
10.4 Finding the PCI addresses for an ATA controller...................................... 45
10.4.1 Windows 95 and 98 ..................................................................... 45
10.5 Installing the ATA Citirom PCMCIA card ................................................. 48
10.6 Frequently Asked Questions ....................................................................... 51
10.6.1 What is DDD? ............................................................................ 51
10.6.2 When would I use DDD? .............................................................. 51
10.6.3 How does DDD Work?................................................................. 51
10.7 PID File Definitions ..................................................................................... 53
10.7.1 Drive Health Verification ............................................................ 53
10.7.2 Drive Integration Support............................................................ 54
10.7.3 Drive Initialisation ..................................................................... 54
10.7.4 Drive Optimisation..................................................................... 55
10.7.5 Drive Data Collection.................................................................. 56
`

-3-
Doc#DDD588236ext
 Release History

2 Release History
Date Reason Doc Version
6/8/1999 Updated to reflect new material and updates in “DDD
for OEMs and Distributors”
8/11/1999 Updated to reflect the new System Integrators feature.
1/3/2000 DDD release V4.20 2.20
16/6/2000 DDD release V4.30 2.30
10/11/2000 DDD release V4.40 2.40
04/02/2001 DDD release V5.00 3.10
12/06/2001 DDD release V5.10 3.20
29/11/2001 DDD release V5.20 3.30
26/6/2002 DDD release V5.3 Bld 209 (w 210 Hotfix) 4.00
Updated textual / style format and layout
30/8/2002 DDD release V5.4 Bld 212 4.10
1/1/2003 DDD release V5.43 Bld 216 5.43
7/3/2003 DDD release V5.5 Bld 219 5.5
Conversion to MS Word
31/3/2003 DDD Release V5.6 Bld 223 5.6
5/11/2003 DDD Release V5.7 Bld 227 5.7
22/01/2004 DDD Release V5.81 Bld 229 5.8
18/02/2004 DDD Release V5.85 Bld 233 5.85
25/03/2004 DDD Release V5.86 Bld 234 5.86
05/04/2004 DDD Release V5.87 Bld 235 5.87
28/04/2004 DDD Release V5.88 Bld 236 5.88

-4-
Doc#DDD588236ext
 Introduction

3 Introduction
To assist Hitachi Global Storage Technologies Customers in the prompt and
accurate analysis of disk drives, DDD has been developed and qualified on
recognised hardware platforms. The tool is designed to fully test the drives
capabilities and disposition according to results into predefined categories. It also
provides useful utilities to assist configuring and integrating drives into the Customer
application.
3.1 Drive failure mechanisms
Drives tend to fall into three areas of failure;

Supplier responsibility - which will lead to analysis of failure modes as part of

contribution to continuous product improvement
NDF / NTF (No Defect Found) / (No Trouble Found) - while intermittent failures are
possible, the disk drive industry has found that between 40 to 80% of returns are in
this category. Disk drive manufacturers provide a means of storing data, according to
a directory structure (example: FAT32), defined by an operating system (example:
Microsoft Windows). The data, directory and operating system are all just data
recorded on the drive.
However, several failure mechanisms cause problems with the directory and
operating system relationship, rather than the data on the drive, including incorrect
operation during shutdown procedures. Many utilities and diagnosis systems cannot
determine this, and this results in drives being rejected which are operationally good.
DDD will identify these drives to a high confidence level, and will allow them to be re-
used rather than returned.
The Hitachi Drive Fitness Test (DFT) also addresses these failure modes with the
advantage of the drive remaining inside the end-user PC.
Handling damage - although they appear sturdy on the outside, disk drives contain
extremely sensitive internal mechanisms, which are vulnerable to drop and shock
damage. From the outside of the disk drive it will be impossible to determine if a
drive has been subjected to bad handling. However, by analysis of the servo and the
media surfaces, it can be determined if the disk platters have moved position or if
there has been head/disk contact. The latter often being identified by scratch
definition.
3.2 What is DDD-SI
DDD is an easy-to-use Windows software package that allows one to modify,
optimise, initialise and test industry leading Hitachi Global Storage Technologies
hard disk drives.
Once configured it can be used to;
Optimise a Disk Drive

• Analyse / Repair a Disk Drive

• Initialise a Disk Drive
-5-
Doc#DDD588236ext
 Introduction

• Assist with Disk Drive Integration

• Provide Production Line Support
DDD can perform various tasks through the availability of different routines (.PID
files) which can be prepared by, and available from, your support channel. This will
include testing of returned drives, and the capability to perform other tests and
upgrades. The .PID files can be selected from the DDD Control Centre.
DDD is supplied with standard disposition PID files that allows the user to perform
tasks such as drive capacity clipping, mode page changes etc. This also provides
the vehicle for Hitachi Support Engineers to prepare special one off tasks such as
firmware updates.
3.2.1 OEM Integration
To provide a mass screen of all drives and produce a yield for return for second
integration, subject to agreed marking / tracking procedures
To provide symptoms for failing drives, generally divided between Hitachi defective
drives and drives which have recognised symptoms of handling damage such as
disk shift or scratches.
3.2.2 OEM Field
DDD can also be used to analyse field drives, with disposition in the same way as
managed for drives in integration.
3.3 When to use DDD-SI
3.3.1 Optimise a disk drive
• AV Applications
• Power management
• RAID system integration
• Quiet seek mode
3.3.2 Analyse / repair a disk drive
• Run diagnostics
• Virtual repair (write aborts, off-track writes)
• Clear format degraded condition
• Rearrange data order
• Initialise a disk drive
• Wipe disk
• Clear boot / partition information
3.3.3 Assist with disk drive integration
• Downgrade UDMA/66 to UDMA/33
• Update microcode

-6-
Doc#DDD588236ext
 Introduction

• Change blocksize
• Change capacity (reduce from shipped default)
• Change any mode page
3.3.4 Provide production line support
• Production line monitoring
• Analyse disk drive handling
3.4 Enhancements In Version 5.88 Bld 236
3.4.1 New Features
• Add MFG Date to Allfiles.txt and Allfiles.dat
• Support "WRITE FAT32" in Single Command Line Exerciser for Microdrive
products >2GB. (not available in on-line Help screen)
• Support HighPoint 302 U133 card.
3.4.2 Improvements
3.4.3 Errata
3.5 Platform Requirements
DDD development recommends the following minimum platform requirements, using
an industry standard PC. It is possible to run DDD on lower specification platforms,
but problems may be encountered. The resources required will also vary depending
on the number of drives under test at any one time.
3.5.1 Hardware
Pentium 600 MHz or faster processor
192MB memory
100MB empty hard disk space
PCI - a motherboard with a minimum of 4 PCI slots is recommended - the maximum
PCI configuration. This is required to support up to 3 PCI-IDE controllers + a
graphics card on a typical PC. If using a PCI network card one should consider a
motherboard with 5 PCI slots.
Monitor / graphics - 800 x 600 minimum, 1024 x 768 suggested, 64K colours
3.5.2 Operating System

Windows 98

Windows NT 4.0 (Service Pack 4 minimum, or service pack 6B must be installed)

These can be obtained from Microsoft at:

Http://www.microsoft.com/support/winnt/default.htm
-7-
Doc#DDD588236ext
 Introduction

Be careful to download versions which are approved exportable standard encryption

if outside of the US and Canada.

Windows 2000
3.5.3 Drive Adapters
3.5.3.1 ATA
The following adapters have been tested and known to
work with DDD. DDD will detect the adapter by use of
the “Detect PCI” button in the PCI / PCMCIA ATA
Addresses section in the File > Program Settings drop
down menu

• Centos CI-1500 - Ultra-DMA/33

• Centos CI-1520U10 - Ultra 100 (RAID) using the HPT370 chipset
• PATA / SATA adapters using the HPT374 and 372A chipset
• Highpoint Rocket 133 (HPT 302 chipset)
• Ultra-133 controllers using the Sil-680 chipset
• ESL ATA100 RAID (SIL680)
• Promise ATA-33
• Promise ATA-66
• Promise ATA-100
• Promise ATA-100 TX2
• Promise ATA-133 TX2
• Promise FastTrak 100 TX2 (RAID)
• Promise FastTrak TX2000 (RAID)

With all ATA PCI controllers please ensure that the PCI card is enabled in the
command line of the DDD icon properties. Please refer to Section 5.2
Command Line Switches on page 16.

• Shining CitiRom and Cardbus PCMCIA IDE support

DDD can be installed on a laptop with PCMCIA IDE support using a standard driver.
However, DDD will not automatically detect this card and manual intervention is
required. Please refer to section 10.5 Installing the ATA Citirom PCMCIA card on
page 48.

Note: In all cases testing will only be performed on a MASTER configured

drive, so there is one ATA drive per IDE cable.

3.5.3.2 SCSI
-8-
Doc#DDD588236ext
 Introduction

• ASPI compliant controller: for example, Adaptec 2940UW (and similar 2940xx
cards, including U2W with LVDS support). Up to 6 of these cards can be
supported, although this is normally bounded by PCI implementation
constraints.
3.5.3.3 Fibre Channel
The following ASPI compliant controllers have been tested with DDD;
• ATTO EPCI-UL3S-000
• ATTO EPCI-FC64-000
• Emulex Light Pulse 6000
• Emulex Light Pulse 7000
• Qlogic QLA2100
• Qlogic QLA2310 (2Gb)

-9-
Doc#DDD588236ext
 Distribution and Installation

4 DDD Distribution and Installation

Your Hitachi Global Storage Technologies technical support representative will
advise when DDD updates are needed, both to support new models of HDD and to
update and enhance the DDD function. DDD updates may be distributed to you by
your technical support representative using CD-ROM or downloaded from the
“Partners” area of the Hitachi Global Storage Technologies web site
(http://www.hgst.com). Your technical support representative can also attend internal
forums to discuss any issues, comments and feedback you may have.
Installation of DDD is only to be made to systems agreed with your technical
representative and entered in a registration database which they have access to.
It is your responsibility to ensure that your copy of Windows is properly licensed.
4.1 Installation
The typical downloadable will be an executable file i3dsetup.exe and will be installed
using InstallShield protocols.
Some target PCs for DDD may only have a floppy disk drive, which is limited to
1.4MB per floppy diskette. The best way of working around this problem is to create
a set of spanned .zip format floppy diskettes. There are a number of packages that
can do this. External packages are available to non-Hitachi parties from
http://www.cdrom.com/pub/infozip/ Freeware
http://www.pkware.com/ Commercial
http://www.winzip.com/ Commercial
A suitable package will also need to be placed on the target system to unzip the
image of the single file that should be created in a suitable temporary folder such as
c:\temp\i3dsetup.exe.
Now run i3dsetup.exe - typically using Windows Explorer or from the Run option in
the Windows start dialog

Note 1: If DDD is removed using the ‘remove software’ option in the Windows
control panel, the installation process will require the license details to be re-
entered. If you are installing an update of a DDD version already installed on
your system, the install program will automatically check whether DDD has
been previously installed. If it has, the follow screens will not appear and you
will not need to re-enter the license information. In this case, the next screen to
appear will be the Win-DDD Setup window. However, you will need to re-enter
the IDE command line switches in the properties of the desktop icons. These
are described in section 5.2 Command Line Switches on page 16.
Note 2: If you change or upgrade your system hard drive, the license number
will need to be recreated.
Note 3: The ‘Input’ and ‘Output’ folders required by DDD will automatically be
added. If a previous installation of DDD still exists on the system, the data
within the ‘output’ folder will remain intact.

- 10 -
Doc#DDD588236ext
 Distribution and Installation

When i3dsetup is started, you will be guided through a series of screens. Follow the
instructions presented. Where multiple decisions or input is required then these will
be explained below.
As you continue through you will be asked to define where the system boot drive is
located.

Select the correct one and click Next to continue. Usually this will be the Primary
Master.
Once you are happy with the details of registering this software and have
acknowledge the information given, continue.
You must accept that you understand the license agreement presented to continue.

- 11 -
Doc#DDD588236ext
 Distribution and Installation

4.2 Registration
DDD no longer requires registration, however in some regions this is still favourable.
If one is using a License version then the following applies.
During installation the installation program will generate a Registration ID. This will
be of the format 1234-ABCD-1234-ABCD-1234-ABCD. This needs to be noted down
in order to determine a serial number, which will be needed to complete the
installation.

To determine the License Key (serial number) please communicate with your
technical support representative, or contact the Hitachi Global Storage Technologies
hard disk drive call centre, the latest contact details for all countries can be found on
our web site at http://www.hgst.com/hdd/support/sources/tsc.htm
They will take your registration ID and respond with a License Key. A new license
key is required for each machine with DDD-SI installed.

Once you have obtained the DDD Serial number from your Hitachi representative,
enter the details in the appropriate box. This number can be entered with or without
the dashes(-) but there must be no blank spaces between the digits.

Note that the hyphen “-” characters in the serial number are optional.

Hit “Next>” to continue.

- 12 -
Doc#DDD588236ext
 Distribution and Installation

Choose a destination folder, unless you need to, just continue, accepting the default
provided.
Agree or change the Program Folder Name, unless you need to, just continue,
accepting the default provided.
This will complete your installation. At the end of which, a window may appear which
provides the ASPI layer Upgrade.

Select Yes to perform this and complete installation. Subsequent installations of the
same version may not perform this step.
Four shortcuts to I3DMAIN.EXE will appear on the desktop.
You have the option to create a further shortcut in
c:\windows\start\menu\programs\startup if the target system is dedicated to
supporting DDD.
The Install Shield utilities will install suitable ASPI and IDE drivers. For reference
these are;
4.2.1 IDE

Win 98

WINDRVR.VXD will be present in c:\win95\system\vmm32 and will have been

updated in the registry.

Win NT

WINDRVR.SYS will be present in c:\winnt\system32\drivers and will have been

updated in the registry.
4.2.2 SCSI

Win 98

ASPI32 Windows 9x files: ASPIENUM.VXD (system directory), APIX.VXD (iosubsys

directory), WNASPI32.DLL (system directory) and WINASPI.DLL (system directory)

Win NT

ASPI32 Windows NT files: ASPI32.SYS (drivers directory), WNASPI32.DLL

(system32 directory), WINASPI.DLL (system directory), WOWPOST.EXE (system
directory).

- 13 -
Doc#DDD588236ext
 Distribution and Installation

Tip: If Windows has problems initializing the ASPI layer, verify the file
WNASPI32.DLL is not located in the DDD Working Directory.

4.3 Uninstall
Uninstall of DDD can be performed using Control Panel->Add/Remove Programs.
This will remove the program. Certain drivers will be left on the system, but they will
not be reloaded upon subsequent boots.

- 14 -
Doc#DDD588236ext
 Starting DDD

5 Starting DDD
DDD is delivered with 4 standard PID files for the purposes of disk drive failure
analysis and test. These being the FAScreenFullCheckDispo.PID,
FAScreenQuickCheckDispo.PID, Exercise.PID and a data collection PID called
FAScreen.PID. Other standard PID files are available to perform adjustments or
changes to drives, an example being to adjust a SCSI drive's internal configuration to
optimise it for an AV task.
Win-DDD FA Screen Full Test with Disposition
This will perform 100% coverage, testing the entire disk surface. Pass disposition
can only be concluded following this test. It will perform detailed tests of the drives
servo system, media surface, SMART condition and Read / Write component
characteristics. It will also gather essential data required by your technical support
representative in the event that further failure analysis is needed.
Win-DDD FA Screen Quick Test with Disposition
This routine will perform the same tests and data gathering as the full test above but
only on a percentage of the drive. This is advantageous when needing to establish
that the drive “basically” is accessible and can perform all functions correctly. To
establish disposition the Full test is required.
Win-DDD Drive Exerciser
This offers a long-term exercise of the drive, performing Read / Write / Compares
with a butterfly seek.
Win-DDD FA Screen
This PID would be used for failure analysis data collection only. The drive(s) under
test will never fail any of the individual test steps. Test steps performed are the same
as those for the Full test but for data gathering only, required by your technical
support representative in the event that further failure analysis is needed.
5.1 DDD can be started in a number of ways
Using one of the four standard icons that are automatically created on your
desktop when DDD is installed. Each one of these icons will load the associated PID
file.

- 15 -
Doc#DDD588236ext
 Starting DDD

From within the main Win-DDD folder, where it is recommended that a

shortcut is created from i3dmain.exe shown here, which will be located in the folder
where DDD is installed.

If you wish DDD to start automatically at Windows boot time then create a
shortcut in the c:\Windows\Start Menu\Programs\StartUp folder
5.2 Command Line Switches

To support PCI or PCMCIA ATA devices, the command line must include
IDE=PCI1 IDE=PCI2... For more detail regarding PCMCIA ATA installation
please refer to section 10.5 Installing the ATA Citirom PCMCIA card on page
48.

These can be entered in the right click/ Properties box for Win-DDD icon, at the end
of the target, as illustrated here.

- 16 -
Doc#DDD588236ext
Starting DDD

Turn off the ISA attached IDE ide=!isa Saves time if not attached

Enable PCI attached IDE (1st) ide=pci1 Mandatory to enable

Enable PCI attached IDE (nth) ide=pcin (n=1,2,3..) Mandatory to enable

Note: There must be an IDE=PCIn statement for every ATA PCI card installed

Load PID file during launch PID=filename.PID

List drives by serial number List=bysn List all drives found in the Device
Control Centre by their serial number
instead of their model id string
Force a model where not model=xxxx Where xxxx relates to the
identified model type; IC25ATCS,
IC25ATDA, IC35AVER,
IC35AVV2, IC35AVVA,
IC35UWD2, IC35UWDY,
IC35UWPR. Earlier models will
use the Dxxx convention. All
drives attached will be treated
as this model.
Note: This is useful when a temporary circumstance arises where a new model
HDD can be supported as a preceding model known to DDD or where a
customer unique drive version is not totally compatible with DDD recognition
Prevent testing of the ide=!sec Useful if the boot drive is on the
secondary port IDE Secondary port and the
drive under test is attached to
the Primary.
Test drive attached to the ide=primary Useful when testing drives on a
primary port standard PC without additional
IDE support hardware.
Normally the primary IDE is
reserved for the boot drive, but
this switch can be used to
override this.

- 17 -
Doc#DDD588236ext
 Starting DDD

Note: Drive test built on single E-IDE using ide=primary ide=!sec switches

Restrict number of id=maxn (n=1,2,3,4). Limits the

addresses in SCSI scan number of drives scanned
to a number between 1
and 4.
Note: This is useful when it is noted that serial attachments (FC-AL
and SSA) can have address ranges up to 128 drives and searching for
drives will take an extended amount of time, not required in a test-
bench configuration

Examples:
i3dmain.exe ide=pci1 ide=pci2 ide=pci3 pid=driveinfo.pid
This will run the executable file supporting three PCI attached IDE adapters and will
look for an ISA attached IDE adapter as well. The pid file ‘driveinfo.pid’ will
automatically be loaded.
i3dmain.exe ide=pci1 model=DTTA
This will run the executable file supporting one PCI attached IDE adapters, will look
for an ISA attached IDE adapter as well, and will treat all attached drives as model
DTTA.
i3dmain.exe list=bysn ide=pci1 model=DTTA
- 18 -
Doc#DDD588236ext
 Starting DDD

This will run the same options as the previous example. However, when the attached
drives appear in the Control Centre windows after a rescan has been initiated, the
drives will be listed by their serial numbers rather than the device model type.
5.3 Front panel switches
The ability to completely turn on or off adapters can be performed in the Device
Control Center.
5.3.1 The DDD Device Control Center
When DDD is launched, the following screen will appear;

This is the primary Navigation utility used within DDD to select drives to be tested
and the tests which will be executed.
The Controllers detected: 1 line is a count of the active drivers related to controllers.
There is no driver for the ISA attached card already used for DDD. This number can
be confusing and can give unexpected results, which should not be of concern.
When the tick is removed against either the SCSI or IDE selection boxes, DDD does
not search for these types of controller when it starts. The chosen settings are
maintained across power-cycles in the Windows registry configuration settings.

- 19 -
Doc#DDD588236ext
 Starting DDD

5.3.2 Release information

This will be important for support. This is the function of the About pull-down menu.
Note: The version declared in the image below may not reflect the latest level.

Please refer to section

Please note that within the version number there is a build number, this will also be
required should you require support.

- 20 -
Doc#DDD588236ext
 Starting DDD

5.3.3 Configuration
Firstly complete the registration and configuration data using the File pull-down
menu followed by Program Settings.

User Information - enter your name, company and location data. We are
aware that this is presented in a USA format and request that you adjust
appropriately according to local addressing.
Data Saving/Retrieving Options - enter folders for input and output from DDD.
Ensure that these folders exist in your directory and create suitable directories if
appropriate. These should have been automatically created during the installation
process. Logging for each drive tested will be accumulated in the directory chosen
for program output, it may be suitable to change this on a monthly basis or at the

- 21 -
Doc#DDD588236ext
 Starting DDD

similar time when you either analyse the logging or return it for analysis within
Hitachi Global Storage Technologies.
Program Logging Options - the files showing all files tested are stored in two
formats, one plain text and the other ready for importation in comma separated text
format. Note that the program logging options should be entered as file names only
without DOS path definition. These will be saved in the same path as defined in the
Data Saving/Retrieving Options. The two files defined, shown as allfiles.txt and
allfiles.dat are cumulative logging files.
PCI/PCMCIA ATA Addresses - PCI attached IDE controllers can normally be
automatically configured by using the Detect PCI button, however this will only have
affect for those controllers that DDD has been programmed to recognise.
If you are attaching through PCMCIA, or using a PCI controller that has not
been automatically detected, one can manually enter the IO range assigned to that
controller. Please refer to section 10.4 Finding the PCI addresses for an ATA
controller on page 45 or section 10.5 Installing the ATA Citirom PCMCIA card on
page 48.
Press OK to complete.
5.3.4 Preparing for Test

To see the drives attached and which are available for test press the button.
After a short wait, the drives will be seen in the appropriate columns for ATA (IDE) or
SCSI. The SCSI column will also show drive attached via FC-AL or SSA interface
adapters as these are also in the SCSI family attached by their respective ASPI
drivers.
A typical control panel may look like this;

Having determined the drives available, the next step is to select the drives for test.
Using the mouse and clicking on the individual drive can accomplish this.

Alternatively the key can be used to select all drives, and press the key to
start the tests.

- 22 -
Doc#DDD588236ext
 DDD Profiler

6 DDD Profiler
To load a specially prepared .PID file either from your Technical representative or
the standard profile list, press the Configuration > Profiler pull down menu on the
Control Centre. The following screen will appear.
To load the PID file, click on the required profile in the ‘Select a Profile’ window. Text
may or may not appear in the ‘Profile Information Preview’ windows. This will
describe the purpose of the selected profile, the procedure sequence together with
other relevant data to this particular test sequence.

For a more detailed understanding of when to use specific PID tests, please refer to
section 10.1 Real Life Situations on page 43.

- 23 -
Doc#DDD588236ext
 DDD Profiler

There are 6 separate windows within the profiler window that describe attributes of
the PID file. These are;
6.1 Version of the Profile:
This is an optional field that provides a means of knowing which version of DDD a
particular PID was created on. There is no version checking carried out by DDD.
6.2 Purpose of the Profile:
Used to describe the purpose of the PID file. In the above example, the test will
erase all data from the selected drive(s) under test.
6.3 Procedure Description
This would be used to describe the test sequence that the saved PID file will run. It
can also provide information on why you may want to run this test.
6.4 Supported Products
Supported model types can be added or removed when creating the PID file. To
date, this is only a text window and no functional checking is carried out. In future
releases, this function will be used as a means of controlling the drive types under
test.
6.5 Minimum DDD-Version Required
These windows are used to specify a specific level of DDD required for the testing. If
the criteria are not met, the PID file will not be loaded.
6.6 Tips and Tricks
Useful, extra, information that the user may need to consider. e.g. ‘Please ensure
that the jumper settings are set to Master and Device 0’
These are used as an aid and reference to the user.
Once the PID is loaded, press the Apply button. From the control panel, select the
drive(s) to be tested and press the ‘Go’ button to initiate the test

- 24 -
Doc#DDD588236ext
 Testing

7 Testing
To start testing go to the Actions pull-down and select Explore or simply press the
button. Testing will start. For each drive an execution box will appear. This
shows the progress and status of the test. Note that there are four tab marked
functions in this box.

Note the colour coding in the box at the top left.

Running
Pass - NDF
Fail - Threshold Exceeded condition
Aborted or stopped with condition to be further examined

The Explorer Step progress box shows the progress through the
current test, which is named in the box below. In some tests this
will be over very quickly - in less than a second, but in others
progress will be slow, for example in read or write sequential
testing.
The Explorer Sequence progress box
shows the test-by-test progress. In this case, the test at about
33% complete, suggesting a 3 stage test, with one stage
complete.

The Elapsed Time box is a measure of the elapsed time.

- 25 -
Doc#DDD588236ext
 Testing

7.1 Completion of test

Explorer Sequence bar is at 100% and the Drive Explorer Completed status is
present. Note that the Print and View buttons are now available.

The Print and View buttons allow completed tests to be reviewed. Drive by drive
records are kept for each test using the serial number as part of the filename for
identification.

The pass / fail result will be found by scrolling down this window.

- 26 -
Doc#DDD588236ext
 Testing

7.2 Drive Properties box

The amount of data returned will vary by drive interface and model. Therefore it's
important that blank data is not dconsidered as being a problem. The source of the
data shown above is the standard ATA Identify command defined in each of the
drive OEM specifications and available on the Hitachi Global Storage Technologies
website, http://www.hgst.com. The accuracy of the information in this box cannot be
guaranteed, as seen in the part number (P/N) field above.
It’s possible to update the fields manually where these need to be overridden or
where supplemental information is available, in particular part number information.
The POH data is extracted for some HDD models using proprietary access
commands.
7.3 An Error Occurred - Check Event Log
This message is implemented to make the user aware of an error condition that is
not directly attributable to a fault with the device under test but has caused a task to
fail or not initiate and requires further investigation by the user. This message can
also occur if a custom PID is used with an incorrect parameter. You may need to
consult with your technical support representative to resolve.
In this screen it is required that manual analysis is used to determine reasons for
rejection.
Here is an example of a failure - for a recognised symptom where a SCSI drive has
been partially formatted and interrupted by a RESET or power interruption. This is
not a defect if a reformat of the drive clears the symptom, which is caused by an
internal logical protection mechanism.

- 27 -
Doc#DDD588236ext
 Testing

7.4 Events Window

The Events tab provides status during test. The event log can be saved as a
separate .EVT log in the output folder by pressing the ‘Dump to File’ button.
Ordinarily, the event log does not get saved. This can be useful if the drive failure
information is reported in the event log.
When a DDD test sequence is completed, a ‘footprint’ of this test will be written to
the DFT reserved area of the drive. This will show as ‘DFT: Appending Log...rc=n’ at
the end of the event log. This will allow any future DFT test to interrogate and know
whether the drive has been tested by DDD.

- 28 -
Doc#DDD588236ext
 Testing

7.5 Manual Entry

When a drive will not identify for testing, it is necessary to perform manual entry. This
will be the case when a drive fails to spin-up for example. Manual entry is required -
results are needed for statistical failure analysis today, and as part of the RMA
procedures.

DDD allows you to start another test without having to rescan or re-select the drives.
If you replace the drive model type and select a test without re-scanning the bus, a
message will appear to say that the device under test is not the same as the
selected device. A rescan must now be performed to detect the new drive type.
7.6 Dead drives
A special pull-down is provided under Actions - Manual Record Generator which
leads to the following menu, which has two tabbed pages.

The part number selector can be used to paste the Model and Part Number info into
the relevant fields.

- 29 -
Doc#DDD588236ext
 Testing

Note - The part number generator should be activated before opening the
‘Manual Record Generator’ window. If it isn’t, the ‘Paste Model Info’ button is
not enabled.

Start the “Part Number Selector” from the DDD Programs in the “Programs” list
under the Windows “Start” tab.
Select the correct drive using the scroll buttons in the Drive Type window. Select the
correct part number from the list and then press the Copy to DDE Buffer button. Now
open the Manual record Generator window. The ‘Client Successfully Connected’
message will appear at the bottom of the Part Number window, confirming that
Manual Record Generator window has been opened. The Paste Model Info button
can now be pressed and the selected information will automatically be entered.

Fill these in for defective drives that fail to provide any information. Manual entry is
for statistical failure analysis, and potentially for business procedures in the
forthcoming period.

- 30 -
Doc#DDD588236ext
 Testing

The “Drive not correctly identified” box is provided to cover the case where a Hitachi
Global Storage Technologies drive does not return correct IDENTIFY or INQUIRY
data to the tester. However, you should always ensure that this is not related to the
tester platform itself.
There will be situations when the “Defective Drive” path needs to be used to enter
Other symptoms - for example
• When a drive has an intermittent problem clearly seen in extended running at
a customer but not replicated in DDD SI
• when a drive is a repeated NTF failure (returned twice) for a clearly
documented and justified technical cause.
Your Hitachi Global Storage Technologies technical support representative will ask
customers to share the logging files created by DDD as part of ongoing customer
quality engineering analysis. A statistical exercise can then be used to look for trends
in failure rates.

- 31 -
Doc#DDD588236ext
 Results Logging

8 Results Logging
It is important that the DDD user is aware that logging is present, and where the
logging is kept, as on a periodic basis this will be requested by Hitachi Global
Storage Technologies for technical analysis.
8.1 Drive by drive logging
A test result file is kept for each drive tested on each occasion that it is tested. These
are kept in the location defined in the File - Program Settings dialog under Data
Saving/Retrieving Options. The logging is kept in the Program Output path.

- 32 -
Doc#DDD588236ext
 Results Logging

The naming convention is “serial#.model#” followed by the number n suffix if the

drive has been tested multiple times.
For example
A01234567.AB1.REP
A01234567.AB1.001.REP
A01234567.AB1.002.REP
is a drive of serial number A01234567 of manufacturing model type AB1 (an internal
code, not the product model), which has logging for 3 test events.
If the ‘Dump To File’ button is pressed from the explorer event log window, a text
(.EVT) file will appear in the output folder using the serial number of the drive for it’s
name, which contains the list of events as seen in the event log window.

- 33 -
Doc#DDD588236ext
 Results Logging

8.1.1 Binary Log Object file (.BLB)

In addition to the summary report, DDD will create a further binary file record type
serialnumber.blb.GZ for each drive. These files are automatically created as a
zipped up file when the explorer test window is closed (Exit button).
These files contain detailed results of tests and may be required by your support
team to further investigate problems should they arise and to understand specific
failures as part of the failure analysis process
8.2 Test logging
Each time a drive is tested, an entry is made in the allfiles.txt and allfiles.dat files (or
any other named files) in the Program Logging Options boxes. One is a plain text
file, and the other is a comma separated text readable format for spreadsheet input.
These are the files that your support representative will ask to be sent periodically

- 34 -
Doc#DDD588236ext
 Utilities

9 Utilities
9.1 Using the Mode Page Tool
Mode Sense and Select operations only apply to SCSI drives.
To start this utility, use the Actions - Utilities - Mode Page Tool pull-down menu.
There will be a pause while DDD interrogates the current Mode Page settings using
Mode Sense commands, after which the following screen will be seen.

Each available mode page is listed across the top of the screen, with a scrolling
facility at the top right. Where a bit is not supported by a drive type, you will see that
it is in grey rather than black.
All input in this screen must be in decimal. Hex input data can be achieved by
pressing the Edit Hex.. button. (it’s always a good idea to have a hexadecimal
capable calculator available or to use the View - Scientific option in the Windows
calculator accessory). When this button is pressed, the following screen will appear;

- 35 -
Doc#DDD588236ext
 Utilities

Buttons allow:
9.1.1.1 Edit Hex
This allows the Mode Sense information to be edited as hexadecimal data
9.1.1.2 Repeat Sense
This repeats Mode Sense operation and is useful for confirming that an update has
been made.
9.1.1.3 Apply Changes
This performs a Mode Select operation. It is often good practice to follow this with a
Repeat Sense to check that the intended change has been made.
9.1.1.4 Write to File
This file will be useful if you need your technical support representative to create a
Mode Page Download PID, to update multiple drives simultaneously.
The Current / Default / Saved values reflect the options in the Mode Sense
command. In most cases, operations will be made to adjust current values.
Save Permanently: Mode Select changes can be made to a drive either for the
current session, allowing the drive to return to its saved values upon a power cycle;
or permanently. If reconfiguring a drive for a customer, then this box must be
selected using the mouse.
Extensive Help information is provided, both by cursor positioning over the bit being
adjusted, or by pressing the Help button. However, it is recommended that the
product manuals are available in order to understand the full meanings of all the
sense bits.

- 36 -
Doc#DDD588236ext
 Utilities

9.2 Command Line Exerciser

The purpose of the command line exerciser is to allow the user to send single
commands to a selected drive. It also has the capability of viewing the contents of
individual sectors and sense commands.
To open the viewer from the DDD control centre, press the Actions>
Utilities>ATA+SCSI Command Line pull down menus. This window will appear.

To send commands to a drive, it does not have to be detected within the control
centre window. It is not a requirement to select the drive in the DDD control centre.
Drives can be selected within the command exerciser by the following method;

- 37 -
Doc#DDD588236ext
 Utilities

9.2.1 SCSI
To initiate a test to SCSI drives, type the following commands in the command
center window.
SCSI This selects the SCSI sub-system
Host (n) This selects the SCSI adapter card. This is the adapter card number,
not the SCSI ID
Target (n) This selects the drive where (n) is the SCSI ID
Init This scans the bus for all available drives

9.2.2 ATA
To initiate a test to AT drives, type the following commands in the command centre
window.
ATA This selects the ATA subsystem
Port (n) This selects the drive where (n) is the port number as displayed in
the IDE drives window of the DDD Control Center
Commands can be reselected from the command history window, as displayed in the
above example.
The sense data window at the bottom of the viewer will have a green background
when a command completes successfully. If there is an exception, the background
will turn red and the sense data will be displayed.
Using the ‘Save To File’ button will save the contents of the output window to a file
called Data.Txt in the output folder. This file will be overwritten each time this button
is pressed.

- 38 -
Doc#DDD588236ext
 Utilities

9.2.3 Available Commands

Program Control Query Command
x ¦ q ¦ bye Quit single command qry Query current settings
exerciser
ver Query program version
Environmental Settings C/H/S List Commands
ata Set interface to ATA The application maintains a list of LBA / CHS
coordinates for device operations that access the
scsi Set interface to SCSI Defect Lists and Error Logs
cls Clear Exerciser screen chslist clear Clear all entries in the list
chslist view Display the contents of the list
ecc n Set number of ecc bytes chslist plot Create a polar plot of the list

n = number of bytes (e.g.

Note: The plot function
34)
requires that the device type
dev dxxx Set device type is set appropriately to apply
Dxxx = model type (e.g. the correct zone information
DNES)
Note: Dxxx is no longer
required for most
products
Buffer Commands
The application maintains an internal buffer for data in / out commands. For ATA and SCSI drives
the data is kept in a separate buffer.
buffer view Display buffer in main buffer load fn Load buffer from file
window
buffer fill Pattern fill entire buffer fn = filename (e. g.
pattern pattern = 4byte patter
INBUF. BIN)
(e.g. 0xAABBCCDD buffer save fn Save current buffer to
buffer fillto Pattern fill entire buffer
file
fn = filename (e. g.
offset pattern up to offset OUTBUF. BIN)
offset = offset in buffer buffer size size Set the buffer size
pattern = 4byte pattern Size = Buffer size
buffer fillfrom Pattern fill entire buffer
offset pattern from offset
offset = offset in buffer
pattern = 4byte pattern
buffer setbyte Set a byte to a value
byte value byte = byte# (e.g.
0x100)
value = value to set (e.g
0xFF)

Note: Buffer load and save will automatically append the extension “.BUF” to the filename
provided

- 39 -
Doc#DDD588236ext
 Utilities

ATA Commands
port number Set ATA port
number =
0 = Primary 0x1F0 Write fat16 Write FAT16 partition to
1 = Secondary 0x170 Microdrive products (<=2GB)
2-7 = Centos 6 ch card
8-15 = PCI & PCMCIA Write fat32 Write FAT32 partition to
reset Performs soft reset Microdrive products
ident Identify drive
execdiag Execute diagnostic
read ¦ rd sect Read sectors
lba num lba = LBA to read
num = num blocks, 0x00 =
256
smart enable Enable SMART operations rd verify lba Read Verify
num
smart disable Disable SMART operations lba = LBA to read
smart attr Read attribute values num = num blocks, 0x00 =
256
smart thresh Read threshold values rd long lba Read Long
lba = LBA to read
Rd long ext Read Long (48 bit addr mode)
lba = LBA to read
smart rdlog Read smart log sector
addr addr = rd cont lba num Read Continuos
0x01 = SMART self test log lba = LBA to read
0x06 = Self Test log num = repetitions (0xffffffff)
0x80 = Vendor specific
smart wrlog Write smart log sector rd maxlba Read max native LBA
addr addr = Rd maxlba ext Read max native LBA
0x80 = Vendor specific (48bit addr mode)
smart selftest Execute smart selftest
smart status Return smart status
selfseek ¦ ssk Perform auto seek
cyl OPS mode cyl = target cylinder
OPS = ops per second
mode = fullstroke
(random if not specified)

- 40 -
Doc#DDD588236ext
 Utilities

ATA Commands continued

wr sect lba Write sectors set max lba lba Set max LBA to lba
num lba = LBA to write Set max lba ext lba Set max LBA to lba (48bit
num = num blocks, 0x00 = addr mode)
256
set max lba Set max LBA password
password password to password
wr long lba Write Long set max lock Lock set max LBA
lba = LBA to write password
set max unlock Unlock set max LBA
password
Wr long ext Write Long (48bit addr mode)
note: drive needs to be power cycled if setmax
lba lba = LBA to write
lba cmd is used more than once

set features Issue a set features cmd

parameter with required parameter

security ¦ Query security mode

Note: Set features parameters are device
sec query
dependent. Please refer to the device spec for
sec setpw master = set master p/w supported parameters
parameter user = set user p/w power ¦ pwr standby Issues a Standby
max = set max security mode Immediate
high = set high security mode power ¦ pwr idle Issues an Idle Immediate
password = password
sec disable Disable password
sec unlock Unlock drive

- 41 -
Doc#DDD588236ext
 Utilities

SCSI Commands
host id Set SCSI Controller senddiag lba ¦ Translate LBA to phys. CHS
id = 0 - n xlate lba addr addr = LBA to translate
target id Set SCSI target ID senddiag chs ¦ Translate phys. CHS to LBA
xlate chs cyl hd
id = 0 - n cyl = phys. Cylinder
sect
hd = phys head
init Reinitialize ASPI driver if new
targets have been connected sect = phys. sect
to the bus read ¦ rd ex ¦ Read extended ¦ read verify
verify addr num
unit start Start unit num = num blocks, 0x00 =
256
unit stop Stop unit
lba = LBA to read
cdb6 / cdb10 / Send custom CDB rd long lba Read Long
cdb12 parameter = in / out / no (data) lba = LBA to read
parameter bufsize = buffer size rd cap Read capacity
bufsize bytes
bytes = number of CDB rd cont lba num Read Continuos
logsns page Return log parameters lba = LBA to read
num page = page code num = repetitions (0xffffffff)
num = bytes to return
rd maxlba Read max native LBA
logsns vendor Vendor unique log sense rd def list Read defect list
p1 p2 page p1 = Byte 0 of rsvd field list = GLIST, PLIST
num p2 = Byte 1 of rsvd field rd def12 list Read defect list
page = page code
list = GLIST, PLIST
num = byte to return
logsns format Return log parms and format rd buf mode Read buffer
page control output with page control offs len mode = mode
offs = offset
modesns page Return Mode Parameters
ctrl len = allocation length
page = page code
ctrl = page control (current, rd verify lba lba = LBA to read
saved, defaults) num = num blocks, 0x00 =
tur Test unit ready 256
reassign lban Reassign blocks
lban lban = LBA to reassign (1 to 4) write ¦ wr ex Write extended
marklog text SJ drives only. Use write buffer addr num num = num blocks, 0x00 =
in vendor mode to write a 256
string into the media log lba = LBA to write
note: the write extended command requires
text = any text upto 16 byte that a read capacity has been executed in
w/o white space characters order to aquiant the program with the drive’s
blocksize
selfseek ¦ ssk Perform auto seek wr long lba Write Long
cyl OPS mode cyl = target cylinder lba = LBA to write
OPS = ops per second
mode = fullstroke Note: The number of ECC bytes needs to be
(random if not specified) set appropriately for the device.

- 42 -
Doc#DDD588236ext
 Appendix

10 Appendix
10.1 Real Life Situations
Apart from testing of drives to determine their state, DDD can also be set-up to
perform other tasks, such as reconfiguration exercises, and also to assist in
investigative activities.
Examples:
Format unit only
Change of block size or number of LBAs on a SCSI drive
Change of number of LBAs on an ATA drive
Unique Mode Select settings for a customer requirement
Changing drives to and from nominal optimised AV settings / customer optimised AV
settings
Updating HDD firmware
Adjustment of DDD parameters to match a unique process
Recovery of a SCSI drive from degraded mode
In these cases, and as required your Hitachi technical support representative can
create new sequences, which in turn can be passed to you to load into DDD using
the File - Setup File menu as covered in the earlier Loading the tests or task
sequence section, or loaded using an PID = line in a Properties box.
10.2 A note on password protected drives
A customer can set a password on a drive during a manufacturing process or in his
laptop end-user application.
It is not possible for DDD to unlock a password protected drive. DDD will detect if a
security mode is set and will report this in the Explorer Status.
The password protected data needs to be unlocked by the normal user to the data in
his system.

- 43 -
Doc#DDD588236ext
 Appendix

10.3 Hints and Tips

10.3.1 Installing Centos ATA CI-1500 adapters on Windows 95
Platform
When installing the Centos 2 channel PCI ATA adapters on a Windows 95 platform,
the adapter drivers should be installed before installing the hardware.
10.3.2 No ATA Drives Appear In The Control Panel Window
After a Rescan
There are several reasons why this may happen. The first items to check are;
1. Has the detect PCI button been pressed in the File/Program Settings menu?
2. Do the adapter addresses look correct? Please refer to section 10.4 Finding
the PCI addresses for an ATA controller on page 45
3. Have you set the IDE=PCI1 IDE=PCI2 ... statements in the DDD icon
properties? (Please refer to section 5.2 Command Line Switches on page 16 for
details)
4. Is the drive set to ‘master’?
5. Is the drive powered on?
6. If using a ‘Promise’ ATA adapter, ensure that a drive is attached when the
system is initially powered on. Check the Control Panel/ System/ Device manager
has no yellow exclamation marks against the ATA adapter.
10.3.3 The Test Doesn’t Start Having Pressed The Go Button
Select the drive(s) by pressing the + button or clicking the mouse on the desired
drive.
10.3.4 FC-AL Drive Doesn’t Appear In The Control Panel
Window After a Rescan
One reason that a good drive may not appear after a rescan is because the ‘disable
Target Originated Loop Initialisation’ (DTOLI) bit is set to 1 in mode page 19h, byte
3. The only options available to determine this are (a) use a different application
such as ‘code update’ to check the mode page setting, or (b) reboot the system
whilst the FC-AL drive is attached.
10.3.5 Firmware Download Completes Without Successfully
Loading Microcode
Ensure that the firmware is resident in the ‘input’ folder.

- 44 -
Doc#DDD588236ext
 Appendix

10.4 Finding the PCI addresses for an ATA controller

In most cases the PCI configuration of the controller should be automatic from the
File / Program Settings pull-down. However, it is possible that the motherboard
may have allocated the PCI addressing in an unusual way, as this is configured by
Plug & Play and in rare cases a manual intervention may be required. The following
information may then be useful in getting DDD running.
This only applies if you are going to be using the PCI attached ATA controller for
DDD systems. This manual procedure only applies for Win95/98.
The same underlying PCI negotiation takes place in the system before NT boot, but
the addressing cannot be readily accessed using the standard NT utilities.
10.4.1 Windows 95 and 98
Use the Start Menu and select Control Panel, followed by System as shown here.

- 45 -
Doc#DDD588236ext
 Appendix

Select the Device Manager tab and expand the Hard Disk Controllers as shown
here. This installation has only one CMD controller.

The CMD PCI-0646U Ultra DMA IDE Controller is the IDE controller and has
associated Primary CMD and Secondary CMD ports. The VIA Bus Master PCI IDE
controller indicates that the chipset on the motherboard is VIA, and again the
Primary and Secondary are seen - these are supporting the operating system HDD
attached to the primary controller.
Looking at the example of the CMD controller, select the controller and then proceed
to select the Resources tab. As an example the following was seen - this will vary
from system to system;
Resource Type Setting
Interrupt Request 10 Primary & Secondary
Input/Output Range 6500 - 6507 Primary
Input/Output Range 6600 - 6603 Primary
Input/Output Range 6700 - 6707 Secondary
Input/Output Range 6800 - 6803 Secondary
Input/Output Range 6900 - 690F Secondary

Looking at the primary and secondary IDE resources in a similar way it is found that
the primary has the following resources;
Interrupt Request 10

- 46 -
Doc#DDD588236ext
 Appendix

Input/Output Range 6500 - 6507 select 6500

Input/Output Range 6600 - 6603 select 6602 (6603-1)
and the secondary;
Input/Output Range 6700 - 6707 select 6700
Input/Output Range 6800 - 6803 select 6802 (6803-1)
Input/Output Range 6900 - 690F
The WinDDD Program Options in File - Program Settings should be set as follows
(in PCI address range 1):

Although in this example the address ranges appear to be set in ascending ranges, it
is possible to see descending ranges and interleaved ranges. The above
associations still apply even where the order does not seem “natural”.

- 47 -
Doc#DDD588236ext
 Appendix

10.5 Installing the ATA Citirom PCMCIA card

Before installing the Citirom ATA PCMCIA card, please read the instruction manual
that is supplied with the product.
Having connected a disk drive to the PCMCIA card, plug the card into the socket and
run the device driver software that comes with the product. On a Windows 95
system, the following driver wizard will appear:

Once the driver has been installed, your PC will require a re-boot for the settings to
take effect. Once the system has re-booted, check that the ‘Shining’ hard disk
controller and the attached disk drive appear in the device manager. An example is
shown below.

- 48 -
Doc#DDD588236ext
 Appendix

If the Shining PCMCIA IDE Controller shows a yellow exclamation mark against it,
you may need to check the resources have no conflicts marked against them. These
can be found by double clicking on the Shining controller and pressing the
Resources tab.
If there are no conflicts against the adapter resources, take the option to remove the
Shining controller (with the PCMCIA card still plugged in), re-boot the system and let
windows find the relevant drivers for the card.
Further help can be found on the Shining Corporation web site,
HTTP://www.Shining.com
The example below shows the address range for the ‘Shining PCMCIA IDE
Controller’ that are entered in the PCMCIA ATA address settings of DDD for
PCMCIA ATA attached drives to be recognized:

- 49 -
Doc#DDD588236ext
 Appendix

The address range shown here for the PCMCIA controller is 0160 - 016F. The DDD
address setting needs to be set to 0160 - 016E as shown below (First address to the
last address -1).

- 50 -
Doc#DDD588236ext
 Appendix

10.6 Frequently Asked Questions

10.6.1 What is DDD?
DDD is an easy-to-use, Windows software tool that allows you to modify, optimize,
initialize or test industry leading Hitachi Global Storage Technologies hard disk
drives for integration.
10.6.2 When would I use DDD?
10.6.2.1 Optimize a disk drive
• AV Applications
• Power management
• RAID system integration

10.6.2.2 Analyze / repair a disk drive

• Run diagnostics
• Virtual repair (write aborts, off-track writes)
• Clear format degraded condition
• Rearrange data order

10.6.2.3 Initialise a disk drive

• Wipe disk
• Clear boot / partition information

10.6.2.4 Assist with disk drive integration

• Downgrade UDMA/66 to UDMA/33
• Update microcode
• Change blocksize
• Change capacity
• Change any mode page

10.6.2.5 Provide production line support

• Production line monitoring
• Analyse disk drive handling
10.6.3 How does DDD Work?
DDD provides an easy-to-use interface that enables you to accomplish custom
configuration in four easy steps;
Using the relevant interface controller, connect the disk drives you would like to
configure or analyse to the testing station with DDD-SI installed. You will need a
separate power supply for the disks, and you should ensure that they receive proper
airflow.

Click the icon DDD to allow the software to find the connected drives. A list of
their model numbers or serial numbers will appear in the window corresponding to
their interface.

- 51 -
Doc#DDD588236ext
 Appendix

Select the profile that best suits your needs from the Profiler menu under the
Configuration title on the main toolbar.

Select the drives to run this PID and press the icon.

- 52 -
Doc#DDD588236ext
 Appendix

10.7 PID File Definitions

10.7.1 Drive Health Verification
Name Short Description Comments

FullCheckDispo Complete drive health check Highest confidence level

with disposition. Includes handling damage check
Recover from user / system induced errors
Recover from previous installation errors
Destructive - data integrity not maintained

FAScreenFullChec Complete drive health check Highest confidence level

kDispoNon- with disposition. Includes FA Includes handling damage check
Destructive screen data collection. Recover from user / system induced errors
Recover from previous installation errors
This sequence collects all data for failure
analysis before recovery actions are started
QuickCheckDispo Quick drive health check with Lower confidence level
disposition. Includes handling damage check
Recover from previous installation errors
Destructive - data integrity not maintained
FAScrenQuickChe Quick drive health check with Lower confidence level
ckDispoNon- disposition. Includes FA screen Includes handling damage check
Destructive data collection. Recover from previous installation errors
This sequence collects all data for failure
analysis before recovery actions are started
FullCheck (DMDM) Complete drive health check As FullCheckDispo, without SMART check
with disposition, especially and erase MBR
designed for Microdrive
Exercise Drive Exerciser without Exercising tool with (almost) infinite run time
disposition Destructive - data integrity not maintained
ExerciseNonDestr Non-destructive drive exerciser Exercising tool with (almost) infinite run time
without disposition No writes - data integrity maintained
CheckSmart Check S.M.A.R.T. Status

- 53 -
Doc#DDD588236ext
 Appendix

10.7.2 Drive Integration Support

Name Short Description Comments

Clip32GB Clip drive to 32 GB overcome 32 GB limitation of some BIOSes

Clip8GB Clip drive to 8 GB overcome 8 GB limitation of some BIOSes

Clip4GB Clip drive to 4 GB overcome 4 GB limitation of some BIOSes

Clip2GB Clip drive to 2 GB overcome 2 GB limitation of some BIOSes

UnClip Recover original drive

capacity
DriveInfo Displays basic drive
information
SCAMoff Disable SCAM Overcome problems with SCSI controllers that don’t
support SCAM properly
SCAMon Enable SCAM

10.7.3 Drive Initialisation

Name Short Description Comments

CleanDisk Clean up entire disk Recover from user / system induced errors
Clear “Format Degraded” condition
Recover full capacity after clip
Secure privacy
Merge Glist to Plist where supported
EraseBoot Erase boot / partition Recover from previous installation errors
information Remove operating system dependency
ResetModePages Reset SCSI Mode Pages INFORMATION ONLY - how to reset Mode Pages
to shipped values using the Mode Page Tool

- 54 -
Doc#DDD588236ext
 Appendix

10.7.4 Drive Optimisation

Name Short Description Comments

SetAV Optimise for AV AV optimisation with support for “normal” operation

Applications
SetAVrc Optimise for AV Systems For pure AV streaming systems only
Turns off read error correction
Read data integrity not guaranteed!
SetRAIDgeneric Generic optimisation for Cache utilisation
use in RAID system Command Queuing
Hot plug support
SetWSgeneric Generic optimisation for Cache utilisation
use in single user Command Queuing
workstation
QuietSeekMode Optimizes Telesto drive Seek profile optimized for quiet operation
for quiet acoustic mode Remains active across power cycles
NormalSeekMode Sets Telesto drives into Remains active across power cycles
normal seek profile Seek profile optimized for normal operation
ReadRepair Performs a complete read performs a complete read scan of a drive
scan of a drive and tries tries to repair all corrupted sectors.
to repair corrupted recover drives that saw aborted or off-track write
sectors. operations

- 55 -
Doc#DDD588236ext
 Appendix

10.7.5 Drive Data Collection

Name Short Description Comments
FAScreenFullCheck Complete drive health Highest confidence level
Dispo check with disposition. Includes handling damage check
Includes FA screen data Recover from user / system induced errors
collection
Recover from previous installation errors
Destructive - data integrity not maintained
This sequence collects all data for failure
analysis before recovery actions are started
FAScreenQuickChe Quick drive health check Lower confidence level
ckDispo with disposition. Includes Includes handling damage check
FA screen data Recover from previous installation errors
collection
Destructive - data integrity not maintained
This sequence collects all data for failure
analysis before recovery actions are started
FAScreen Analysis data collection This sequence collects data for failure analysis.
The drive will not be manipulated in any way.
Test will never fail
SMTT Baseline Servo performance tool Verify enclosure performance for rotational
vibration caused by adjacent drives
To be used under the direction of Hitachi Global
Storage Technologies support engineers
SMTT Reference Servo performance tool Verify enclosure performance for rotational
vibration caused by adjacent drives
To be used under the direction of Hitachi Global
Storage Technologies support engineers
SMTT Seek Servo performance tool Verify enclosure performance for rotational
vibration caused by adjacent drives
To be used under the direction of Hitachi Global
Storage Technologies support engineers
SMTT Idle Servo performance tool Verify enclosure performance for rotational
vibration caused by adjacent drives
To be used under the direction of Hitachi Global
Storage Technologies support engineers

- 56 -
Doc#DDD588236ext