Hitest Standard Manual R1
Hitest Standard Manual R1
3.8 Logs for Hitachi GST representative for further Analysis ...................................................... 38
APPENDIX – A
DNR Result Entry Aid - Barcode List .......................................................................................... 46
HiTest is developed to support Hitachi HDD distributors or customers of distributors focused on customer Line
Integration Reject or Field Reject Failure Diagnostics. This software can be given to distributors or their
customers.
*Note
“Do not return to Hitachi GST” of disposition has two means.
NFF: No Failure Found.
There are no error records in a drive and
Head Amp and Servo Measurement is Good.
CID: Customer Induced Damage Failure (Handling Damage).
RRO Measurement is criteria over and
Seems that Disk Shift was caused by handling damage.
Hardware / Software Pre-requisites for using HiTest for Corporate Level 1.0 Failure Analysis
"HiTest" requires data entry for the drive Serial Number, Model ID and Customer Serial Numbers when the
tested drive is DNR .(refer to 3.5) A barcode reader will increase the efficiency and accuracy of logging in such
data. Following pages are the reference information for barcode readers and also adaptor cards and other
suppliers that have been tested with HiTest.
There are many barcode readers available and below are just a few that we known to work. The only
requirement is that it can read code types 39 and 128.
For Travelstar 40GN and 60GH only, one will require it to support code type 412.
IDAutomation $99 on
P'nP USB http://www.idautomation.com/scanners/
HighPoint HighPoint
http://www.highpoint-tech.com/ Rocket RAID 1520 SATA controller
Rocket RAID 1540 SATA controller
Rocket RAID 1542 SATA controller
During the first boot of the test system after installing new IDE PCI Controllers, Windows will declare "New
Hardware Found" and offer the option to install a driver. At this stage hit "Cancel". This will occur at every re-
boot.
The reason for this is that with the drivers installed, the OS is free to poll the drive when ever it wants for what
ever reason. HiTest communicates to the drive directly through the port address out of sight of the OS. If both
occur at the same time during certain operations it can be detrimental to the test routine and function of HiTest.
This package must be installed prior to the installation of HiTest. The install package is available from your
technical support representative or the following URL.
http://www.microsoft.com/downloads/details.aspx?FamilyId=262D25E3-F589-4842-8157-
034D1E7CF3A3&displaylang=en
Start the installation by clicking “Download” . Run directly from the web by selecting or to
your hard drive for installation later.
Follow the on screen instructions for installation until complete.
The latest releases of HiTest install package can be obtained from your local technical support representative of
the Hitachi GST.
Double Click the “Setup.exe" file and follow the on screen instructions until installation is complete.
You have now installed the HiTest application on your system.
You should see the following shortcut in your Windows Programs listing;
Double click the icon on your desk top. Log-in information is required here that will be used in the summary data
and must be entered accurately if report generation is to be accurate and efficient.
For the first time user, the PCI Check screen will appear. Please refer to the relevant sections for further advice.
HiTest supports upto 10 port addresses through which it can test a drive. These will include any detected
controllers resident in the host PC (on the motherboard) as well as added PCI controllers, for PATA and SATA.
With some modern systems there can be to sets of PATA as well as SATA controllers on-board which can
consume mst of the available ports, thus, when one adds PCI controllers they may not be visible on the HiTest
screen.
In this event one can re-order the port assignments in the PCI Card setup window as described below;
From the main HiTest window select the drop down menu ad choose the option.
The ports defined in the PCI Card Information (0 to 9) equate to the Ports defined in the HiTest main window
(1 to 10)
As one can see above, the number of ports in the PCI Check window exceed 9, 13 in fact. In this case any
drives attached to the last 4 ports would not be seen when scanned in HiTest.
* Note here the positions of the controllers remain the same but the port assignment has changed. In the first
window drives on ports
During the launch of HiTest / Login one will be asked to enter various data about the User and their Location.
HiTest is an integral part of the Failure Analysis process. It's main purpose is to test Hard Disk Drives to a
common routine and to record those details for pareto analysis. For those purposes to be meaningful it is
essential that the information be entered consistently and accurately.
The User Login information allows the individual drive test data to be linked to a particular Customer / User.
The details one enters must be consistent for all tests performed for that user.
Note:
The fields are designed for alpha-numeric characters. Please refrain from using any other characters such as ",",
"." and "-"
(C) 2004-2006 Hitachi Global Storage Technologies, inc. Page23/47
2.1.4 : User Login Requirements for GENERIC Customer
Before one tests any products, it is essential for HiTest to gather information about the user and location that the
tests are to be conducted. These details will be sorted in the results files for each drive tested.
The following details will help your Customer Support representative, and subsequently the Hitachi GST FA
Labs, to understand where the drive has failed and returned from. It will help to understand if there are certain
trends in returns;
For example, Customer A has 2 PC's running and PC1 is exhibiting more DNR (Drive Not Ready) errors than
PC2. This could indicate hardware issues with that system and not real drive failures.
Or Customer B has multiple locations and one location is showing a significantly higher failure rate than the
other locations. This could indicate a unique problem at that location or a specific system or environment that
the drive is being used in, and not real drive failures.
All of this will help to isolate any issues quickly and improve overall quality.
Once the User Login completed, the main HiTest screen will appear and you can start testing drives.
NOTE: Please check that the Date and Time are reported correctly. If not, please correct in the system settings
before continuing.
HiTest's prime function is to perform level 1.0 Failure Analysis. This involves collecting parametric data from
the drive in order to assess if the drive is fundamentally good or defective.
Drives that are NFF ( No Fault Found ) are parametrically good, however in order to be confident that the drive
can be returned to a user environment one must test the entire user area.
The following describes the process for setting the test routine to include a Read Verify to all sectors of the
drive for all drives that have passed the standard sequence as NFF.
"STD SEQ + Sequential xxx" option are performed only when the result of STD SEQ is NFF-XXX.
"WRITE ABORT DETECTION"option is performed only when the result of STD SEQ is RHE=1.
*Note
About "Firmware Update" and "WRITE ABORT DETECTION" option explain in chapter 4 more detail.
You need this operation every HiTest start up. (This option Selection won't be saved when HiTest rebooted)
Once the drive has been "logged in". One can attach it to the bus and run HiTest.
Attach the drive as a Master drive to an approved Controller port. One can attach multiple drives and test
multiple drives at the same time. Once all drives to be tested are attached, apply power.
Allow some time for the drives to spin up and make themselves known on the bus, then, on the HiTest screen,
All rows turning YELLOW, indicating a successful scan and awaiting test start.
If the Result field holds a "DNR", please push this button once again.
If the drive is a true DNR then the HiTest program will eventually classify it as such and present the row as
follows;
Turning the DNR drives rows PINK indicates a true DNR, please execute DNR login process (refer to 3.5).
Once you have established the number of drives you wish to test and all show a YELLOW row after scanning
the bus, one can start the test by clicking the button on the main HiTest screen.
A new window will appear indicating the test steps and their progress. The rows will also turn PALE BLUE to
indicate they are running.
After a test is completed, a result can be judged by the color of a line as shown in the following figures.
If the drive(s) fail to initialize for what ever reason on HiTest, it is classified as a DNR (Drive Not Recognized)
and will be highlighted "pink", as the two in the capture below show;
(1) Wand in the Serial Number barcode from the HDD label. * mandatory required
(3) Enter the Mfg Date, obtained from the HDD Label. (option: if available)
Note. If the Drive Serial Number is missing or a carriage return has not been used after inputting the text, the
following message will pop-up.
When HiTest completes testing a drive it will create all the relevant output files and store them in the main
HiTest log folder or one of it's sub-folders as seen below;
Individual Log
Summary Log
(Sample image)
There are 2 types of logs which are not in the text format.
Sample :
Sample :
These files are created for Hitachi GST Failure Analysis Engineer use only. Please pass those files for your
Hitachi GST representative.
4. Please select the firmware file of the revision which you are going to update since file select window is
displayed.
5. HiTest updates only the drive which matched the selected file.
Double CLICK
CLICK
CLICK
Type Code-128-B
Output JPEG
Styles Draw border
Size W:120 H:60
Xres 1
HDD-OTHER IDENTIFY/INQUIRY
02 NR002 30500000
ERROR
HDD-DNR-SPINS/NO ACTUATOR
08 NR008 31400000
LOADING
HDD-DNR-SPINS/HEAD LOADING
11 NR011 31900000
SOUNDS OK