Seagate F3 Terminal Command Set
Here's a consolidated version of all the Seagate terminal commands collected so far. It's not intended to be an exhaustive list, but rather a collection of commands useful in data recovery. If you have more info to share please post it and I'll add it to the list:
The Very Basics:
TTL Default Settings:
Bits per second - 38400
Data Bits - 8
Parity - None
Stop Bits - 1
Flow Control - None
Ctrl + z (initiates the terminal connection and should prompt with level T>)
Ctrl + a (displays drive info, Package Version, Serial #, Model # (useful for missing label), Servo FW, etc.
Ctrl + l (displays drive info, # heads, serial, preamp type, family ID, etc.)
Ctrl + c (tells some drives to spin down, can be used immediately after CTL + z)
Ctrl + x (displays log of history commands)
/X (used to change levels, replace X with level 2, 3, 4,... 7, T, etc.)
2>Z (puts drive to sleep)
2>U (spins drive up)
7>X (test read/write head resistance)
T>V1 (returns slip defect list - confirm translator loading)
T>V2 (checks T-List)
T>V4 (checks G-List entries)
T>V10 (checks P-List)
T>V40 (checks for non-resident G-list entries)
1>G6A (clear P-List - Not Recommended!)
T> i2,2,22 (clear T-List - Non Recommended!)
C>Q (returns list of all available commands, sometimes just says "No Help Available" on all of them)
1>N1 (clears S.M.A.R.T)
1>N5 (returns SMART values in terminal window)
T>i4,1,22 (clears G-List)
7>m100 (clears DOS config tables)
Seagate Preamp Pulled From ROM (Requests)
So I've now devised a method that allows me to extract the preamp from
the ROM code of many Seagate models very quickly. No need for modifying
head maps and comparing using PC-3000 or anything like that. For those
who have access to the secrets section, I've posted my methods there for
you to enjoy.
For anyone else who needs to know the preamp of a
particular drive, just post the ROM code here and we can tell you what
the preamp is. It only takes a few seconds to determine it for most
families now.
Seagate Grenada Preamp Tracking
OK, I'm creating this sticky to just keep track of which preamp type is
in which of these drives. Given how many head swaps we are doing on
these, I think it'd be nice to get it down to a little better science,
so perhaps we can more loosely match these when the exact part number
isn't available. So I'm just going to be taking every healthy drive I
get in here and posting the specs along with the PreampType listed when
you press Ctl + L in terminal.
I'll be listing them all in the following format:
- Model
- Part #
- First three of serial
- FW
- Date
- Site
Followed by the Preamp Type
Seagate Maximum Baud Rates for Reading / Writing ROM
I don't know if anyone has ever kept track of this (I know I haven't
until now) but I think I'm going to do a running list of the maximum
baud rate that different Seagate families can use to read/write ROM via
boot ROM code.
Grenada: 921000 (some will read at 921600)
Kahuna: 921000
Bogart: 460800
Anak: 921600
Yarrah_5400: 460800
V9: 921600
MantaRay: 460800
If
you've got any that you know off hand, please feel free to add below so
I can update the list. I know it's not terribly important but it
certainly does speed things up not always having to read at the default
38400 speed.
Seagate DM Headswap Experiences
As we all seem to be having difficulties head swapping these, I though
it'd be nice to have a thread to share our DM head swap experiences.
Here's mine from today:
Patient
ST30000DM001
PN: 9YN166-570
FW CC9F
Date: 13044
Site: TK
Serial: Z1F0Y...
Donor
ST30000DM001
PN: 9YN166-570
FW: CC9E
Date: 12433
Site: TK
Serial: Z1F0K...
As
you can see, I matched model, site, PN, and first four of serial. The
drive initially ID'd showed correct capacity and allowed sector access.
Resources were backed up and imaging started. A few heads actually read
relatively quickly, others were slow but steady with only a few bad
sectors. After about 10 minutes, drive hit a bad sector, began clicking
and failed to ID after power cycling it. 
Now it just clicks and spins down. But at least I know the heads were compatible, and I didn't kill them in the swap.
0 Comments