ACE Lab PC-3000 Express User manual

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 1
SEAGATE
F3 architecture
Table of contents
1. Introduction.....................................................................................................................................................................2
2. Supported drive families.................................................................................................................................................6
3. Getting started.................................................................................................................................................................8
4. Launching the utility.......................................................................................................................................................8
5. Frequent malfunctions ..................................................................................................................................................12
5.1. Motor seizure........................................................................................................................................................12
5.2. "Stuck" heads .......................................................................................................................................................12
5.3. HDD returns HDD ID (the host system detects it), but reports capacity = 0.......................................................13
5.4. Host system does not detect a HDD, which permanently remains BSY..............................................................14
5.5. Host system detects a HDD, drive beginning is visible but starting with a certain LBA continuous space until
the end is filled with UNC errors........................................................................................................................15
5.5.1. Automatic translator restoration (for the entire LBA space) .......................................................................16
5.5.2. Automatic location correction for a specific LBA (beginning with a certain LBA) ...................................17
5.5.3. Data Extractor task ......................................................................................................................................18
5.5.4. Manual translator restoration.......................................................................................................................18
5.5.4.1. "Delicate" work with Non Resident G-List........................................................................................23
5.6. Diagnostics using the list of 32 recent RW commands..........................................................................................23
6. Tests menu....................................................................................................................................................................27
6.1. Utility status .........................................................................................................................................................27
6.2. Loader ..................................................................................................................................................................28
6.3. Create loader ........................................................................................................................................................28
6.4. Update Microcode................................................................................................................................................28
6.5. Work with terminal ..............................................................................................................................................29
6.6. Service information..............................................................................................................................................30
6.6.1. HDD resources backup................................................................................................................................31
6.6.2. Work with ROM..........................................................................................................................................31
6.6.3. Work with RAM..........................................................................................................................................32
6.6.3.1. Heads maps in Seagate F3 drives........................................................................................................33
6.6.4. Work with service area................................................................................................................................35
6.7. Logical test...........................................................................................................................................................36
6.8. Defect lists............................................................................................................................................................39
6.9. S.M.A.R.T. erase..................................................................................................................................................39
6.10. Solutions.............................................................................................................................................................39
6.11. User commands..................................................................................................................................................39
7. Specialized tools of the utility.......................................................................................................................................41
7.1. View and edit HDD resources..............................................................................................................................41
7.2. Work with Flash ROM image file........................................................................................................................45
8. Unlocking HDD in case of LED: CC error...................................................................................................................49
8.1. Disconnection of the controller board from HDA (isolation of the spindle motor connector) ............................50
8.2. Short connection of the read channel...................................................................................................................50
8.3. Operating principle of the main part of the unlocking procedure........................................................................52
8.4. Searching for the short connection points............................................................................................................53
9. Appendix 1. Replacement of the controller board........................................................................................................54
10. Appendix 2. Testing the HDD controller board..........................................................................................................55
11. Appendix 3. Testing the motor winding coils.............................................................................................................56
12. Appendix 4. Selecting a donor heads stack.................................................................................................................57

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
2ts.acelaboratory.com
13. Appendix 5. Location of the read channel checkpoints on Barracuda F3 3.5" HDD ................................................ 58
13.1. PCB 100466725 REV A (DLAJ-4)....................................................................................................................58
13.2. PCB 100466824 REV A (UJAJ-6).....................................................................................................................59
13.3. PCB 100466824 REV B (UJAJ-6).....................................................................................................................60
13.4. PCB 100466824 REV C (UJAJ-6).....................................................................................................................61
13.5. PCB 100496208 REV A.....................................................................................................................................62
13.6. PCB 100504364 REV B.....................................................................................................................................63
13.7. PCB 100512588 REV A.....................................................................................................................................64
13.8. PCB 100475720 REV A (ZKAJ-7)....................................................................................................................65
14. Appendix 6. Location of the checkpoints on Barracuda F3 2.5" HDD...................................................................... 66
14.1. PCB 100536286 REV E.....................................................................................................................................66
14.2. PCB 100513573 REV B.....................................................................................................................................67
15. Appendix 7. Functional purpose of modules in Seagate Arch F3 HDD.................................................................... 68
16. Appendix 8. Correspondence between the service data modules and System Files in Barracuda 7200.12
(Pharaoh) HDD.......................................................................................................................................................... 69
1.
Introduction
By the year 2008 Seagate evolved from manufacture of the classic 3.5" Barracuda HDD line (3.5" Barracuda - …
7200.7, 7200.8, 7200.9, 7200.10, Barracuda ES; 2.5" Momentus - … 5400.2, 5400.3, 5400.4 …) to the new F3
architecture intended to unify the production of ATA and SCSI drives. That new architecture is mostly based on
mechanics and the firmware kernel from the ATA hard drives, but a large part of firmware microarchitecture has been
revised in accordance with the design used in SCSI Seagate drives. ROM has been extended and supplemented with the
code enabling the controller board to function in ATA mode without the HDA attached. Furthermore, the manufacturer
moved to ROM adaptive data and HDD ID information (due to that fact a board disconnected from HDA can return via
the ATA interface HDD ID containing correct HDD information1). However, together with useful effects of that
combination the new architecture also inherited a number of problems from both its parent lines. In particular, it
includes a number of problems related to translator corruption (issues typical of SCSI HDD), the Pending Bug problem,
etc. The new architecture also encountered some issues related to the integration of previously independent platforms
and addition of new functionality. In this guide we describe the Arch F3 platform, typical problems of its models, drive
diagnostics, and the methods available for work with these HDD in the PC-3000 suite.
1FW in the ROM of some Seagate drives contains the default HDD ID, which is updated with the information from
disk surface in individual drives. Moreover, when the firmware on disk surface appears to be inaccessible for some
reason, a drive may return the HDD ID template with the default model name and serial number (while the actual
serial number is preserved in the ROM data structures).

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 3
Barracuda 7200.12 HDD
Fig. 1.1. A Barracuda 7200.12 HDD
1 − manufacturer – Seagate; 2 − drive family − Barracuda 7200.12;
3 − serial number − 5VM428EF; 4 − model – ST3160318AS;
5 − FW version – CC37; 6 - Site code (code of the manufacture location) – WU.
Barracuda 7200.11 HDD
Fig. 1.2. A Barracuda 7200.11 HDD
1 − manufacturer – Seagate; 2 − drive family − Barracuda 7200.11;
3 − serial number − 9QM040C5; 4 − model – ST3500320AS;
5 − FW version – SD04; 6 - Site code (code of the manufacture location) – KRATSG.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
4ts.acelaboratory.com
Barracuda ES.2 HDD
1 − manufacturer – Seagate; 2 − drive family − Barracuda ES.2;
3 − serial number − 9QM7D0QK; 4 − model – ST3500320NS;
5 − FW version – SN05; 6 - Site code (code of the manufacture location) – KRATSG.
Desktop HDD
Fig. 1.3. A Barracuda ES.2 HDD
Fig. 1.4. A Desktop HDD

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 5
1 − manufacturer – Seagate; 2 − drive family − Desktop HDD;
3 − serial number − W300H8J4; 4 − model – ST4000DM000;
5 − FW version – CC52; 6 - Site code (code of the manufacture location) – WU.
Laptop SSHD
1 − manufacturer – Seagate; 2 − drive family − Laptop SSHD;
3 − serial number − W38051SR; 4 − model – ST1000LM014;
5 − FW version – SM11; 6 - Site code (code of the manufacture location) – WU.
Momentus 7200.3 HDD
Fig. 1.5. A Laptop SSHD

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
6ts.acelaboratory.com
Fig. 1.6. A Momentus 7200 HDD
1 − manufacturer – Seagate; 2 − drive family − Momentus 7200.3;
3 − serial number − 5TH0BV0S; 4 − model – ST9250421AS;
5 − FW version – SD13; 6 - Site code (code of the manufacture location) – WU.
2. Supported drive families
Drive family Model
2.5"
Momentus 5400.5
ST9320320AS
ST9320320ASG
ST9250320AS
ST9200321AS
ST9160310AS
ST9160310ASG
ST9120310AS
ST9120310ASG
ST980310AS
ST980310ASG
Barracuda 5400.6
ST9500325AS
ST9400326AS
ST9320325AS
ST9250315AS
ST9160314AS
ST9160301AS
ST9120315AS
ST980313AS
ST9500325ASG
ST9320325ASG
ST9250315ASG
ST9160314ASG
ST9120315ASG
ST980313ASG
Momentus 7200.3
ST9320421AS
ST9320421ASG
ST9250421AS
ST9250421ASG
ST9200421AS
ST9200423ASG
ST9160411AS
ST9160411ASG
ST9120411AS
ST9120411ASG
ST980411AS
ST980411ASG
Momentus 7200.4
ST9500420AS
ST9500420ASG
ST9320423AS
ST9320423ASG
ST9250410AS
ST9250410ASG
ST9160412AS
ST9160412ASG
ST9120410AS
ST9120410ASG
Constellation,
ST91000640NS
ST9500620NS

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 7
Constellation.2
ST9250610NS
ST9160511NS
Momentus XT
ST95005620AS
FreePlay
ST1500LM003
ST91000LM010
ST91000430AS
ST9888430AS
ST9750430AS
Momentus Thin
ST500LT012
ST320LT020
ST320LT007
ST500LT012
ST250LT012
ST250LT007
Drive family Model
3.5"
ES.2
ST31000340NS
ST3750330NS
ST3500320NS
ST3250310NS
Barracuda 7200.11
ST31500341AS
ST31000340AS
ST31000333AS
ST3750630AS
ST3750330AS
ST3640323AS
ST3500620AS
ST3500320AS
ST3320613AS
ST3160813AS
Barracuda 7200.12
ST31000528AS
ST3750528AS
ST3500418AS
ST3500410AS
ST3320418AS
ST3250318AS
ST3160318AS
Bara LP / Green
ST2000DL003
ST1500DL003
ST32000542AS
ST31500541AS
ST31000520AS
Barracuda XT
ST32000641AS
Constellation ES / ES.2
ST2000NM0011
ST2000NM0031
ST2000NM0051
ST1000NM0011
ST1000NM0031
ST1000NM0051
ST500NM0011
ST500NM0031
ST500NM0051
ST33000650NS
ST33000651NS

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
8ts.acelaboratory.com
ST33000652NS
ST32000645NS
ST32000646NS
ST32000647NS
3. Getting started
For details about preparation for work with the utility and HDD connection to the suite, please refer to chapter 3 of
Seagate documentation, part 1.
Attention! HDD ROM contains adaptive data. Check to ensure that the controller board matches the heads and disk
assembly (HDA). To do that, you can even use a board disconnected from HDA, which returns HDD ID information
via the ATA interface anyway. Having read HDD ID, you can compare the model and its serial number to the
information printed on HDA label. If the returned HDD ID contains a template, use the tools for operations with ROM
described further to obtain the serial number from it (see section 7.2, Work with Flash ROM image file and Correction
of HDD ID data in ROM).In addition, in cases when the terminal command mode is available you can extract the serial
number by sending the [Ctrl]+[R] and [Ctrl]+[L] pair of commands; the HDD will respond then with a report similar to
the following:
GrenadaBP LuxorPlus2 4K, GPF1 MC with new serpent DFW
Product FamilyId: 58, MemberId: 03
HDA SN: W1F23RHF, RPM: 7199, Wedges: 188, Heads: 6, OrigHeads: A, Lbas: 00002BB5420C, PreampType: CC 06
Bits/Symbol: C, Symbols/UserSector: BEB, Symbols/SystemSector: 1A5
PCBA SN: 0000E3246TRJ, Controller: LUXORLPLUS_2_0( 203)(FF-FF-FF-F, Channel: STX_DUNRAVEN, PowerAsic: Unknown Rev 00,
BufferBytes: 4000000
Package Version: GPG17D.CCD2.AX0851.CC24, Package P/N: 100714019, Package Global ID: 00188399,
Attention! Please keep in mind that if a non-native controller board is used, then any operation involving recording to
disk surface may cause irreversible corruption of service data resulting in inaccessibility of user data.
4. Launching the utility
As soon as the utility starts, it displays the drive family selection dialog. The family is recognized automatically based
on the HDD ID information. If a drive returns no HDD ID (permanent BSY, ABR response in case of firmware
damage), you can select its family manually.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 9
Fig. 4.1
As soon as you click the 'Utility start' button, the utility will access the drive for automatic configuration requesting the
following information:
Family ID: 58
Selected family......................... : 58, Grenada
Model by ID............................. : ST2000DM001-9YN164
Loading default settings!
Use the options dialog to review and save utility settings.
Then press OK!
Family default settings loading!
Tech Key...
Requesting FW Pkg ver ........ GR753C.CCD4.BP01BG.CC4H
Detecting Phys Sct Size...
Result.................................. : 4096
Detecting Max Head number...
Phys. heads............................. : 4
Obtaining Saved Mode Pages File information...
Reading Saved Mode Pages...
Parsing Saved Mode Pages...
LBA alignment........................... : 0
Obtaining Registry File information...
Reading Registry File...
Parsing Registry File...
Media Cache
===========
MC : disabled
MC Size : 0x44C850
MCMT Ver : MCMTV03

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
10 ts.acelaboratory.com
Collecting Sys Files information...
ID Len
===============
0 36 Reserved Defect Table (SA defect table)
1 2 Drive Information File (DIF)
2 16 Performance Parameter File (PPF)
3 7372 Primary Defect File (P-List))
5 4 Manufacturing Information File (MIF)
8 4800
B 1000
C 122880 Serial Port Test Results File (Self Scan Log)
D 160
E 432 Data Integrity Check (DIC), HEAD 0
F 223 DIC Dummy File
13 8 Disc Registry File (settings, security, etc)
15 100 BGMS File (Directed Offline Scan)
16 2
17 40
19 24 Log File
1A 33 Log File
1B 1 Log File
1C 9
1D 128 Physical Overlay File 0
1E 128 Physical Overlay File 1
22 80 Drive Self Test (DST), Head 0
23 80 Drive Self Test (DST), Head 1
24 80 Drive Self Test (DST), Head 2
25 80 Drive Self Test (DST), Head 3
2A 9 Saved Mode Pages (HDD settings)
2B 9862 R/W Operating Parameters (translator, etc)
2C 432 Data Integrity Check (DIC), HEAD 1
2D 432 Data Integrity Check (DIC), HEAD 2
2E 432 Data Integrity Check (DIC), HEAD 3
33 4576
34 640 Packed CONGEN XML definition
39 8192
3A 4
42 4096
43 8192
Collecting Sys File Infos completed
Collecting DT Infos...
ROM:
ID MemOffs Len
===========================
0 40030200 37888 Read Adaptive Parameters File (RAP)
1 40030000 512 Controller Adaptive Parameters File (CAP)
4 1D400 7168 Servo Adaptive Parameter File (SAP)
40002000 13312
total 20480
5 6C000 81920 Servo Firmware Table
A 2574C0 1024 Seek Profile
13 4011EA98 1440 Dependent Zone Table for User Area
14 4011F038 60 Dependent Zone Table for System Area
15 0 524288 Flash ROM
1D 40030220 424 VBAR Configuration File
1E 400305B8 4016 Zone Format Parameters File
26 401179A0 28920
27 401178B0 240
RAM:
ID MemOffs Len
===========================
0 40030200 37888 Read Adaptive Parameters File (RAP)
1 40030000 512 Controller Adaptive Parameters File (CAP)
2 400303C8 496 Zone Table
4 1D400 7168 Servo Adaptive Parameter File (SAP)
40002000 13312
total 20480
5 6C000 81920 Servo Firmware Table
6 A63D00 81964 Servo Flaw Table
A 2574C0 1024 Seek Profile
13 4011EA98 1440 Dependent Zone Table for User Area
14 4011F038 60 Dependent Zone Table for System Area
15 0 524288 Flash ROM
16 40030200 32 Drive Configuration Table
17 400319A0 2016 Temperature Control Configuration
1D 40030220 424 VBAR Configuration File
1E 400305B8 4016 Zone Format Parameters File
1F 4020D858 3300 RW working user preamp table
20 4020E540 110 RW working system preamp table

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 11
26 401179A0 28920
27 401178B0 240
Collecting DT Infos completed
Reading autotuning buffer............... Ok
Searching module table in RAM... ....... Ok
Searching volume 3 file table in RAM.... Ok
Searching volume 0 file table in RAM.... Ok
Searching SMP RAM FID in RAM............ Ok
Searching Non Resident G-List FID in RAM Ok
Searching CFW OVL FID in RAM............ Ok
Searching DT table(RAM, WR) in RAM...... Ok
Searching DT table(RAM, RD) in RAM...... Ok
System Files I/O method detection... ATA(direct)
If errors are encountered during initialization, respective messages will be logged, and the utility will automatically
provide troubleshooting advice (see Fig.4.2 for an example).
Fig. 4.2
After completion of the device start and initialization procedure the main window of the utility (including terminal) will
become accessible (Fig. 4.3).
Fig. 4.3
Toolbar buttons:
1
−
drive power management;
2
−
loader (Update Microcode) creation and uploading;

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
12 ts.acelaboratory.com
3
−
utility status dialog (which allows, among other things, to re-read the lists of modules and DT);
4
−
reconnection to COM port (necessary when the USB to COM adapter freezes);
5
−
detection and switching of the rate of data exchange with HDD via terminal;
6
−
ROM reading/writing menu;
7
−
group of features for operations with the controller: DT reading/writing, modification of the heads map,
SAP flags, and HDD ID in drive RAM;
8
−
group of features for operations with the service area (backup of service information, reading/writing of
HDD modules and system files, HDD ID modification, translator recalculation and restoration, resetting
of passwords);
9
−
logical scanning of disk surface;
10
−
work with HDD defect lists: Non Resident G-List, P-List, Non Resident Primary DST List;
11
−
group of features for automatic repair of typical malfunctions;
12
−
a set of custom commands;
13
−
switch between PC-3000 windows;
14
−
exit from the utility.
We should separately mention the list of automated solutions for HDD problems available in the utility (Fig. 4.4):
Fig. 4.4
♦A drive may be detected in the system, but report zero capacity (0 Gb) (except for the situations when zero
capacity is caused by a damaged controller board / heads or non-native controller).
♦Host system cannot detect HDD presence because the drive permanently remains in the BSY state - HDD is
locked (LED: 000000CC).
5. Frequent malfunctions
5.1. Motor seizure
If a drive motor seizure occurs, then a HDD cannot spin up the disks even if the controller board and motor winding are
functional (confirmed by replacing the board with a known good board from another drive of the same family having the
same revision and checking the coils (as described in section 11, Appendix 3. Testing the motor winding coils). That
malfunction can be identified by typical tactile vibration of the HDA when power is switched on. When the HDA is
opened and the heads inside are not stuck, it is very difficult or impossible to turn the disks manually.
To solve the problem, move the disks stack into a donor HDA. In that case you can use the controller board, heads and
magnets from the damaged drive (if native heads get damaged, they can be replaced).
5.2. "Stuck" heads
"Stuck" heads have manifestations identical to the motor seizure case. When HDA is opened, the heads turn out to be
outside the parking area. They stick to the disk surface because of molecular attraction forces.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 13
Unfortunately, there are no universal methods "releasing" the heads. You should rely on your experience and the
expertise of your colleagues.
5.3. HDD returns HDD ID (the host system detects it), but reports
capacity = 0
This malfunction can be caused by the following reasons:
♦non-native controller board;
♦damaged read/write heads in the HDA;
♦broken contact between the controller board and HDA in the connector of the commutator preamplifier
(oxidized contacts, etc.) (Fig. 5.2);
♦damaged service information (SMART, G-List, translator…).
Section 0 of this manual describes the method that can be used to ensure that the board is native. At present there are no
methods for drive restoration if its native board is lost.
If a contact is broken, try cleaning the connector, for example, using a common office eraser (see Fig. 5.1).
If magnetic heads are damaged, a drive usually produces knocking sounds when powered up. In that case it is
recommended to replace the malfunctioning heads stack.
If service data get corrupted, use the "Troubleshoot "Invalid translation (0 GB)"" menu item (Fig. 5.3). Selection of that
item makes the utility perform automatically a sequence of operations to fix the problem (Fig. 5.4) resulting in
restoration of the access to user data.
Fig. 5.3
Fig. 5.2
Fig. 5.1

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
14 ts.acelaboratory.com
Fig. 5.4
5.4. Host system does not detect a HDD, which permanently
remains BSY
This malfunction can be caused by the following reasons:
♦hardware HDD malfunctions (malfunction of the controller board, heads, etc.);
♦damaged service information (SMART, G-List, translator, Media Cache data structure1).
In the former case, you should check the HDD controller board using the method described in section 10,Appendix 2.
Testing the HDD controller board. The latter situation can be resolved using software tools. If the terminal command
mode is available when the drive is powered, perform malfunction diagnostics as described in section 5.6, Diagnostics
using the list of 32 recent RW commands. If the command mode cannot be invoked because of HDD freeze or LED
error, select the "Solution for problem "HDD Lock (LED: 000000CC)"" menu item (Fig. 5.5) having bridged the
reading channel contacts. If the freeze of a powered drive is accompanied with the "LED: 000000СС" message output
to terminal, the procedure should be performed till the end. However, if the freeze has other symptoms, then once you
obtain access to terminal using the automated solution for the LED: 000000CC problem, click 'Cancel' in the main
window guiding you through the read channel bridging and continue HDD diagnostics as advised in section 5.6,
Diagnostics using the list of 32 recent RW commands. For details on unlocking the HDD locked with the LED:
000000СС error please see chapter 8, Unlocking HDD in case of LED: CC error .
1Media Cache is a drive's data cache located in its fastest disk surface area. Initially it was introduced in hybrid
HDD where it was located in NAND Flash on the controller board. As the technology was adjusted for better
affordability, the cache was relocated to the outer tracks of HDD surface, where linear rate of data exchange reaches
its maximum.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 15
Fig. 5.5
5.5. Host system detects a HDD, drive beginning is visible but
starting with a certain LBA continuous space until the end is filled
with UNC errors
When such HDD arrives for diagnostics, the host system recognizes it correctly, but the drive allows reading access just
to a portion of its surface. Beginning with a certain LBA, and until the end of disk space it returns UNC errors while
reading.
This malfunction is caused by data corruption in the translator. To explain the nature of corruption, a few words about the
HDD factory testing procedure are necessary. During the first stage Self Scan process builds the main list of drive defects
(P-List). It is used to generate the initial translator. Then during the presale preparation additional surface testing is
performed to reveal the areas where a HDD demonstrates slower or unstable performance. However, these areas are
relocated using directly the translator instead of P-List. Besides, when defects are added to the translator, information about
them is appended to Non Resident G-List, which allows to supplement the translator in series losing no information about
additional defects hidden earlier. An attempt to recalculate the translator based on P-List only discards information about
those defects both in the translator and in Non Resident G-List. At the same time ECC for each sector is generated using its
LBA number under which it will be recorded. When the information about defects found during post-processing gets lost,
the numbering of sectors becomes shifted beginning with the first "lost" defect: LBA used to read a sector no longer
matches the actual address where the sector data have been recorded. As a result, UNC errors will be returned at an attempt
to read from the surface starting with a certain LBA until the end of disk space.
Corruption of translator data can have various causes. The main of them are as follows:
♦Unlocking of LED 000000CC using the methods described in the Internet without prior backup of the
translator module.
♦Logical corruption of the translator module caused by its overwriting by the drive during G-List update
affected by writing malfunctions (in that case the drive may freeze during firmware start or return zero
capacity).
♦HDD errors occurring during translator recalculation. In particular, in some cases translator recalculation
may add erroneous data to Non Resident G-List; moreover, the flags field of such defect records may
contain code 20 preventing removal of such corrupted records by the recalculation procedure and thus
causing shifts in translation.
♦Mistakes made during work with the translator, Non Resident G-List, and P-List.
While the first situation results from unsafe operations performed by the user or repair technicians, the second case may
occur "for no reason" when a user is working with the device.
For troubleshooting of this issue, three approaches exist (for details please refer to the corresponding chapters):
♦Automatic solutions available from the menu 'Tests → Service information → Work with service area →
Translator → Recover translator and Single LBA position adjustment'.
♦Manual translator restoration using the tools available in the utility.
♦Creation of a DE task in translator restoration mode with the 'Read from active PC-3000 Utility' option
enabled for the reading command (the Seagate F3 utility must be running at the same time).

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
16 ts.acelaboratory.com
In the first and the second case the existing translator will be supplemented with the "translation forks" revealed during
the testing procedure (lost defects). In the third case Data Extractor will read data "as is" and ignore the translation
shifts; then it will build a virtual translator to access the data.
Attention! Before any operation with the HDD service information and with the translator in particular, please back
up the service information to a separate folder in the HDD profile to be able to roll back any erroneous changes.
We should also mention that besides the loss of information about Post-Process defects1the translator can be corrupted
by addition of "extra" defects to Non resident G-List or P-List. Although the utility contains a feature clearing Non
resident G-List, using it before translator restoration cannot be recommended unconditionally. As a matter of fact, Non
resident G-List may contain tracks of HDD surface representing thousands of sectors. Thus, manual analysis and repair
of the defect lists may appear quite useful. Its structure and the methods of manual restoration will be discussed in
detail in the section 5.5.4.1. "Delicate" work with Non Resident G-List."Extra" defects can also be introduced into P-
List when the command transferring G-List → P-List (implemented only in some firmware versions) is invoked. In this
case you should use the P-List editor of the utility having located physical coordinates of the records with problems. It
should be mentioned that in case of "extra" defects translation recovery using the automated solution in the utility is
impossible because the automatic method adds defect records on its own until it reaches a complete translation match.
As a result, the utility will discover data both to the left from the translator divergence location and to the right, in the
area unreadable with regular ATA commands, output a message about ambiguous condition, and terminate the process
abnormally. In that case you should analyze the divergence area manually, correct the information about defects and
either perform the restoration procedure manually or restart the automated solution.
5.5.1. Automatic translator restoration (for the entire LBA space)
This solution is available from the menu 'Tests → Service information → Work with service area → Translator →
Recover translator'. When the procedure starts, you have to select the appropriate profile for the drive being restored
and check the restoration settings in the dialog displayed next.
Fig. 5.6
If the 'First start' mode is selected, the utility will suggest saving a backup copy of the service information (specific
items and the destination folder for subsequent backup procedure), disable in the SA Autoreassign, Deferred defect
hiding, offline self-test, identify the type of command used to hide defects, and recalculate the base translator. Then it
will start surface scan beginning with LBA = 0.
1Factory detection of defects in Seagate Arch F3 uses several passes. The first pass occurs during the Self Scan
procedure. Subsequent passes are performed in a stand under external software control. Post-process defects are
specifically the defects revealed during these final passes. We should mention that they are added directly to the
translator instead of P-List. Therefore, when the translator is recalculated using P-List only, information about these
defects may be lost irreversibly.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 17
If the option to 'Continue (from LBA)' is selected, the utility will resume scanning from the LBA entered in the dialog.
If you interrupt the testing process, the utility will save in the profile data the LBA where the procedure was paused and
offer to resume it from that location the next time it is started.
The 'Take into account P-List' option must be selected if the drive has a valid P-List. If the P-List is corrupted (e.g.,
with erroneous data transferred from G-List) the option should be deselected.
The option 'At ambiguity hide "left" UNC' allows automatic handling of the situations when the algorithm cannot
reliably recognize the "fork" type because the area with translation deviation is preceded by some unreadable (UNC)
sectors (and so the algorithm cannot access their content for analysis).
The option to 'Process "32 byte tail" bug' prevents the utility from analyzing the last 32 bytes of each sector, which
some FW versions may misinterpret during reading in factory mode.
The option to 'Execute Reset after defect hiding' configures the utility to send a Soft Reset after each addition of defects
to the translator in order to update it.
In the dialog you can also define the file name for the list of "translation forks" where the scanning process will store
found nodes. If later a need arises to recalculate the translator considering P-List only, this list will allow you to restore
the initial translation by hiding the defects into the translator based on the file data.
The algorithm is automatic and requires operator participation only in cases when it cannot detect precisely the type of
node being hidden in the translator. In that case the utility will display a corresponding notification with a suggestion to
resolve the ambiguity manually1.
When the algorithm completes its work, the utility will display the list of found translation "forks". IT SHOULD NOT
BE HIDDEN TO THE TRANSLATOR! It is intended for two purposes ONLY: for your information and quick
restoration of the initial condition if for some reason translator recalculation based on P-List has been performed and
consequently the result of algorithm operation gets lost.
5.5.2. Automatic location correction for a specific LBA (beginning with a certain
LBA)
This solution is available from the menu 'Tests → Service information → Work with service area → Translator →
Single LBA position adjustment'. When the procedure starts, you have to select the appropriate profile for the drive
being restored and check the restoration settings in the dialog displayed next.
Fig. 5.7
1Please remember while doing that to append the list of found nodes. The step will allow you to continue correct
automatic translator restoration later.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
18 ts.acelaboratory.com
The feature is necessary in situations when it is impossible to restore translation correctly for the entire disk surface or
when such restoration appears to be complicated for some reason. In particular, it may prove helpful in case of multiple
BAD sectors preceding the area with the sought data (e.g., when reading via the utility discovers the sought second
partition or the body of the necessary file). In that case it may be possible to keep hiding sectors preceding the required
(and constantly tracked) surface location until the location becomes readable using logical level access. The feature
described here serves specifically for that purpose. Once the procedure completes successfully, the beginning of the
necessary area will be readable already. Then you may attempt restoring the translation further automatically using the
feature described in the previous section1.
The option 'Recalc translator to the default state' allows recalculating the translator to its initial state when the mode
starts. It is necessary when the mode is initiated for the first time and the results of earlier failed restoration attempts
have to be discarded.
The option 'Take into account P-List' indicates to the utility whether the P-List information should be used during the
procedure. In case of considerable discrepancies between the available P-List and the working one the option allows
you to exclude the list from the process and then use the same mode while restoring the translator in completely
automatic mode.
The option to 'Execute Reset after defect hiding' configures the utility to send a Soft Reset after each addition of defects
to the translator in order to update it.
'LBA for checking' defines the location for constant tracking while the procedure is being performed.
'Maximal defect chain length' defines the largest allowed size for a contiguous area to be hidden. The option is necessary to
prevent automatic hiding of an entire track by the drive when a certain number of hidden LBA is reached because it would
disrupt the algorithm operation. When the corresponding number of hidden LBA is reached, the utility will automatically
shift the LBA relocation area (before the one being monitored) to the left by the 'Inter-chain step' value.
5.5.3. Data Extractor task
When this solution is selected, you have to specify during creation of a new DE task that it should be generated in the
translator recalculation mode. Once the task is created, open its settings dialog and use the command to 'Read from active
PC-3000 Utility'. Please keep in mind that data will be transferred using SCT2with intermediate conversion to PCHS and
data access in sector-by-sector mode3. Therefore, data reading will be considerably slower than in UDMA mode!
Once the task configuration detailed above is specified, you can proceed to data restoration following the guidelines in
Data Extractor documentation describing the translator recalculation mode.
Attention! Some FW versions return incorrect data while reading in factory mode. In particular, the last 32 bytes of
each sector may be garbled.
5.5.4. Manual translator restoration
This method requires knowledge of some peculiarities in the operation of translator in Seagate F3 drives.
As we have noted above, during ECC calculation for sector data the drive uses the number of the LBA that it is
working with. Therefore, beginning with the translator "fork" point the drive will detect reading errors. On the ATA
command level it will return then the UNC error informing about unrecoverable data. The drive itself can discern in
such case translation errors and situations when it cannot recover incorrectly read data. Unfortunately, no methods are
known at present that could be used to obtain from a drive the LBA number that has been used to record such data4.
1To do that, you have to start the procedure and configure it to continue from the LBA already mapped to its original
location.
2SCT (SMART Command Transfer) implies transfer of additional commands via the data sectors of standard ATA
commands for operations with SMART logs (for details please refer to the ATA specification).
3Reading specifics in case of a corrupted translator means that each sector will be read separately and an error status
(translation disruption) will be returned after that.
4While reading a sector producing errors, the drive firmware outputs to the terminal messages with the codes:
03110081 – actual UNC sector; 04090082 – addressing error (translator "mismatch"). No information is output
about the LBA used to write the sector.

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
1001101010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110101010110110101010
11
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
1101110110110011
0111011110
111101
011
11
1
PC-3000 EXPRESS / UDMA / PORTABLE  Seagate
ACE Lab F3 architecture
Technical support: [e-mail]
Phone: [phone]
ts.acelaboratory.com 19
Thus during translator restoration indirect methods have to be used to identify the type of the fork to hide. It can be
both a "left" or a "right" fork. To understand the types please keep in mind that hiding of post-processing defects occurs
in several passes. Different passes may reveal defects before or after the previously hidden ones. Besides, during each
recovery step you may discover "forks" added during the current test cycle, i.e. a "left fork" when the area hidden at the
factory is readable because it was written to these addresses but immediately followed by unreadable data, because the
LBA where it was supposed to be written will match the starting LBA of the "left" branch. Therefore, a "left" fork
should be hidden in the direction of LBA number decrease UNTIL THE UNC OCCURRENCE LOCATION.
Testing may also reveal "forks" hidden during earlier scanning steps. These forks have been written before hiding with
larger LBA number than they occupy at the moment. In this situation reading of user data terminates abruptly with a
UNC error followed by the hidden area, then user data continue. Please keep in mind in this connection that post-
processing testing used to be based on recording of a plain pattern – the entire sector was filled with a single byte.
Initially drives were tested using sector filling with byte 0x77, then manufacturer started filling the sectors with zeroes.
While in the first case it is quite easy to recognize the 0x77 code pattern (the probability that user data will match it and
occur in the "fork" location is rather low), filling with zeroes causes ambiguity – before sale the entire drive surface is
filled with zeroes and there is no way to discern by sector content a sector written and hidden during surface tests from
a sector in the user space of the HDD. The difference can only be noticed if non-zero user data are present in the area in
question. Following from the above, you can examine the "fork" area and make assumptions about the position and size
of the hidden area based on the data placement. While you can read the data preceding the LBA with UNC error using
a regular ATA command, reading the LBA with UNC error and the following sectors requires the extended
functionality of the utility. To do that, use the sector editor from the Tools menu. To access the data in the UNC area,
you have to switch the reading mode to reading via the utility. The utility will display a prompt asking whether data
should be returned in case of a real reading error (UNC). To identify translation problems, you should respond 'No'
(responding 'Yes' will allow you to obtain the uncorrected data in case of a corrupted sector, but the mode is unusable
for the purpose of translator restoration).
Fig. 5.8

01010101100110101010110011010101011001101010101100110101010110011010101011001101010101100110
10011010
1010110011010101011001101010101100110101010110011010101011001101010101100110101010110011010101011011010101011
10101010110011010101011011010101001101010100110101101101101010100101
1011010101100110011010101011010101111010111
11010101101101010100111110
110111
0110110011
0111011110
111101
011
11
1
Seagate PC-3000 EXPRESS / UDMA / PORTABLE 
F3 architecture ACE Lab
Technical support: [e-mail]
Phone: [phone]
20 ts.acelaboratory.com
Once the position of the hidden area relatively to UNC is identified, you should add the information about that area to
the translator using the defects editor of the utility.
Create in the list a defect record with the corresponding starting point and length, then invoke the 'Hide to Slip-List'
command from the shortcut menu (Fig. 5.9). When the operation completes, user data up to the next "fork" will become
accessible for reading provided the hidden area has been selected correctly.
Fig. 5.9
The actual searching for the "fork" should be performed using the logical scanning test of the utility with verification
enabled ('Tests → Logical test'). The maximum number of defects to be revealed before the test is stopped should be set
in the test options to 1. Thus the test will stop immediately at the supposed fork location enabling creation of a defects
list pointing to that LBA.
Attention! Please keep in mind while analyzing the test results that apart from the translation "forks" the drive may
contain real bad blocks.
The case of "extra" defects is worth mentioning separately. Essentially, the problem is as follows. For some reason a
drive may have added to P-List or Non Resident G-List1additional defect records disrupting translation. Automatic
translator recovery procedure (both methods) additionally hides sectors in the process and thus obviously cannot "fix"
an area already containing sectors, which have been hidden in error. In that case you should try locating and removing
the extra records using both the data from surface obtained with regular reading and reading via the utility. The utility
provides the following opportunities for that purpose:
♦P-List editing. The editor allows to extract from a drive the list of defects stored in P-List, and then use the
data from surface and the flags of defect records (in particular, records with the G-List -> P-List flag are
suspicious) to identify and remove the records disrupting translation. Please keep in mind that a single
defect record may describe a chain of sectors, some of which may belong to a correct list while the rest are
1Meaning the records with the flag other than 0 (most frequently, 0x20), as the records with the 0 flag are removed
during translator recalculation based on P-List.