7200.14 terminal parameters?

[int0x13]

Hello, i have a Seagate ST3000DM001-9YN166 with sectors problems, i try to access terminal but it does not work. What paramater to connecter to the serial prompt?
I try 38400 8-1-none-none and i have unreadable output. It seems that CTRL+C is working, so sending seems working but not receiving. My cable and settings are working perfectly with another seagate drive but a 7200.9

[warnerr]

Respectfully suggest you clone that drive while you can and forgo trying to access it via terminal. After your data is safe perhaps you might start a selfscan.... but do you think this drive will really be worth trusting with your data?

[irs]

hi,

What paramater to connecter to the serial prompt?

the parameters are the same as all other F3 but something changed on Lombard family.
you can see that you get no errors and looks like some commands work, so you will have "unlock" all serial commands
bye
Luca

[int0x13]

hi,

What paramater to connecter to the serial prompt?

the parameters are the same as all other F3 but something changed on Lombard family.
you can see that you get no errors and looks like some commands work, so you will have "unlock" all serial commands
bye
Luca

And which are the parameters for F3 family? You dont like to give the answer at first ask i see:)

[irs]

you didn't read my post... the settings are the same for all F3, as you told 38400 8 N 1 .
if you read carefully my post you will see that the problem is not on com port settings...

[int0x13]

Sure i've read. But it seems you didnt read mine also.
You dont explain me why i cant get terminal output, i should at least see the output log. In my case i dont see anything just gibberish chars just like when you have not good connection. I think i've discovered why its not working, its not same voltage on 7200.14. You probably know it and didnt tell me for some reason. Knowledge retention i call it.

[irs]

I think i've discovered why its not working, its not same voltage on 7200.14

AFAIK voltage didn't change simply use tx rx and gnd on a TTL comport ...
i don't know which tool you are using for testing the drive, i'm sure that if you can run selftest on F3 drives you're experienced enough to understand how to connect a com port and which part of the firmware can be locking the serial port and so which commands can solve it .
Anyway i never had problems on lombard family to access terminal, it's odd you get garbage on output, try with a older drive belonging to F3 arch to check your tool, the com port settings are the same.
bye
Luca

[fzabkar]

I think i've discovered why its not working, its not same voltage on 7200.14

:shock: AFAIK voltage didn't change simply use tx rx and gnd on a TTL comport ...

Apparently you haven't measured the voltage.

For recent models, Vio = 1.8V

On earlier models it was 2.5V, AFAIK.

Some serial LVTTL adapters may work at these lower voltages while others may not. My recommendation would be to invest in a new adapter based on the CP2104 bridge. Then add switchable 1.8V and 2.5V LDO regulators to reliably and safely support the latest drives.

[int0x13]

That's correct.
I find it funny that irs is the pro who discover this information that amateur discovered
By the way irs, i've never talked about self scan f3 at all. I dont know the magic sequence to unlock full T shell. And i guess you wont tell me. So i will have to go figure myself.

[int0x13]

I know can get complete bootlog. I just cannot get T> prompt. CTRL+Z is not working.
I guess there a special magic sequence to get prompt on this lombard family as irs said.

[ghandi]

int0x13, any luck getting to the prompt?

I have a Prolific PL-2303H bridge. Having the same issue connecting to a 7200.14 ST2000DM001 HDD - can't get to prompt.

Getting from the drive:
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

CTRL-z has no effect. Tested my connection with RX&TX shorted and on an old 7200.11 (there, RX and TX are vice versa!), works perfectly. No idea why I can not get to the F3 prompt on this 7200.14. Help / ideas would be appreciated.

[arztt]

PL-2303H does not work with some 7200.14 drives due to lower voltage.
Buy an adapter with a CP2104 chip.
Maybe a CP2102 will do it too, but I have not yet tested that.

[ghandi]

Success! With a 1.8V TTL adapter I have no issues accessing the F3 command prompt via CTRL-Z.

Drive does not respond any error codes. Here is the terminal output:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

ASCII Diag mode

F3 T>

Now the big question: What to type on the F3 command line for a 7200.14 Barracuda? As I have understood from reading this forum, known parameter sets are only available for 7200.11 or 7200.12 models. Any help would be greatly appreciated.

As the drive spins up completely normal and does not make any sounds, could it be that the bad sector table is full and the drive can not get ready?

[arztt]

Do you want to recover data or just try to use the drive again?

[ghandi]

I would like to recover the data, I would never use a drive that gave me such problems again...

I started a new thread collecting all information I have: viewtopic.php?f=1&t=29535

Freue mich über jeden Kommentar

[int0x13]

int0x13, any luck getting to the prompt?

I have a Prolific PL-2303H bridge. Having the same issue connecting to a 7200.14 ST2000DM001 HDD - can't get to prompt.

Getting from the drive:
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

CTRL-z has no effect. Tested my connection with RX&TX shorted and on an old 7200.11 (there, RX and TX are vice versa!), works perfectly. No idea why I can not get to the F3 prompt on this 7200.14. Help / ideas would be appreciated.

No I've never found the magic command to unlock the shell. As iris said I guess the pro company's know it since long time but they will try to keep it secret the longest time it can be...until some bad sheep will disclose it! Like always security through obscurity is just a matter of time and people willingness.

[int0x13]

Update: With a 1.8v TTL adapter it's working flawlessly and i can have access with my new 7200.14 HDD that seagate RMA me. I dont know what is the difference between my old faulty drive and the new one, but with the new one i have full shell access. Maybe the faulty drive has locked shell and we could be accessed only by shorting RW channel points on the PCB? Im not sure but i heard even that wouldnt work because there are some 7200.14 that are "locked" in factory to not have an accessible T Shell. In those cases, and i think i had this case with my first hand drive, which is the solution to unlock the shell? maybe rewriting the ROM chip?

Here is a sample command with my new drive:

Code:

F3 T>
Prod Desc: GrenadaBP1.5 LuxorPlus2 4K, GPG1 clone DFW
Package Version: GPX17D.CCD2.DC0CAL.CC29
Serial #: W1F2BX55
Changelist: 00610906
Model #: ST3000DM001-1CH166
ID: 100


Update: I noticed the new RMA drive is FW CC29 while the original was CC4H