ST9500325AS not appear in Windows or DOS tools

[frica]

Dear all:

I conect this 2.5” HDD to my Win10 home PC, using an SATA/USB Adapter device, and power on using a PC Power Supply.
The SATA/USB adapter and the Power Supply were used wih other HDD and there was no problem.

I have this HDD with not critical data.

My HDD:

Seagate Mmentus 5400.6
ST9500325AS de 50 GB
SN : 5VEKPHNN
PN = 9HH134 – 567
FW : 0002BSM1


This HDD is not recoganaized by Windows 10 Home:

- No sound of Windows when I connect the HDD on USB Port
- No appears HDD icon in Internet explorer
- No appears HDD device in Disk Managemenet
- No appears HDD in Device Management

I attached internally this HDD in a laptop vía SATA port and booted it from a Hirens Boot Live CD. Using the DOS Programs no tools detected the HDD. Tools used:

• Test Hard Disk Drive 1.1
• Hard Disk Sentinel
• HDAT2
• DRevitalize 1.2
• Victoria
• Seagate Seetools
• MHDD: the automatic detection was not enabled.

No clics in HDD. Touching with my fingers and closing my ear, HDD víbrate and sound indicanding the disc is spinning up.

Are there any possibility to came back to life this HDD? No critical data stored.

Thanks!

[pcimage]

Sorry to say, but if you don’t need the data then scrap it.

[frica]

Thank you pcimage for your message.
I will scrap it. But it is possible know the cause of the problem?

[pcimage]

Possibly it’s had a knock at some point, or some other reason for media degradation/damage. Or maybe just “old age”

[frica]

Thank you pcimage.

I have a USB to TTL tool and I have used it to autotest that it is works junping the Rx and Tx of this tool. I would like much to learn how can I use this tool to diagnostic the problem in a HDD.

Can I obtain the reason of the fault conecting the HDD to this USB to TTL tool?

[fzabkar]

Can I obtain the reason of the fault conecting the HDD to this USB to TTL tool?

Yes. It doesn't cost much to try, especially if your data are not critical.

[frica]

I have used my USB 2.0 a TTL tool. I tested it using a terminal program (Termite 3.34) and connecting Rx and Tx pins using a wire. The tool tested ok.

Then I connect the Rx pin of the tool with the Tx pin of the HDD. And Tx pin of the tool with Rx pin of the HDD. The HDD was powered on using a SATA conection from a PC Power Supply.

Since the conection was started, binary characters starts to appears in the terminal windows of Termite program and don't stop to appear until I close the conection.

What am I doing bad??

Attachments

Binary character in the terminal windows.

[fzabkar]

Wrong baud rate? Missing ground wire?

[frica]

Dear fzabkar:

Thank you for your reponse! I have just tested with differents baud rate (from very low to very high). No change. The binary characters start to appear when I conect the SATA power cable from POwer Source to HDD (before I power on the Power Source - jumping PS-ON pin to gound).

I have tested conecting GND wire beetween the TTL tool and HDD. No change. The binary character continue appearing.

[HddDonorMarket]

Kinda similar issue. I have at least 7 drive in my stock. Terminal shows strange characters. couldnt understand why and couldnt find a solution yet

ST332060AS
ST3250410AS
ST9500420AS
ST9120822AS
ST3160811AS
ST9200827AS
ST3200827AS 9BD 13E 522

[fzabkar]

What voltages do you measure on the Tx/Rx pins? Are you using a 3.3V LVTTL adapter?

[eaxi]

Simple method to calculate baud-rate on unknown UART:
1. Connect TX to any logic analyzer
2. Set big buffer and big sampling rate in LA
3. Turn on the drive
4. Short terminal transfer appears on disks' TX (green frame)
5. Magnify this transfer and select any fragment with dense transfer - it's one bit (red frame)
6. Magnify this one bit further and measure time - you have your baud-rate
7. Set up UART with this baud-rate in logic analyzer on received transfer, in my example you can see decoded text "Serial Debugger V.1.0 ENG>"
8. Or you can just connect to disk with standard COM terminal, using calculated baud-rate

Attachments

[fzabkar]

Are you using 8N1 as your word format?

[eaxi]

Yeah, it's the most common setting

[HaQue]

make sure you use a gnd.
just try each baud rate, there are not that many.
also maybe try a different ttl adapter

which one are you using?

there was a thread around quite a long time ago that went into the nitty gritty of serial adapters