Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4759 replies to this topic

#4751
KlingKlang

KlingKlang

    Newbie

  • Member
  • 46 posts
  • Joined 06-July 09

Hey Jaclaz!

 

 If someone still has problem with failing drives and need a serial-to-TTL i found this little puppy!

This would have saved me some cash at least.

It seems like that the regular Usb-to-RS232 (serial) is at first TTL and then converted to serial signals with the Max213.

By solder some wires to these tiny tiny pins, you can get the TTL-signal before converted.

Hacking the Usb-to-serial is here: http://yd0nxx.wordpr...serial-adapter/

Datasheet for the Max213 is here: http://www.alldatash...MAX213ECAI.html

This is for the Profilic Usb-to-serial-adapter, but it is maybe the same for different manufacturer, or at least same concept?

If possible, you maybe can move this to the beginning of the thread?


Edited by KlingKlang, 16 October 2014 - 12:07 PM.



How to remove advertisement from MSFN

#4752
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,656 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Hey Jaclaz!

 

 If someone still has problem with failing drives and need a serial-to-TTL i found this little puppy!

This would have saved me some cash at least.

It seems like that the regular Usb-to-RS232 (serial) is at first TTL and then converted to serial signals with the Max213.

By solder some wires to these tiny tiny pins, you can get the TTL-signal before converted.

Hacking the Usb-to-serial is here: http://yd0nxx.wordpr...serial-adapter/

Datasheet for the Max213 is here: http://www.alldatash...MAX213ECAI.html

This is for the Profilic Usb-to-serial-adapter, but it is maybe the same for different manufacturer, or at least same concept?

If possible, you maybe can move this to the beginning of the thread?

I wouldn't be so sure/I don't know. :unsure:

 

The point is that the TTL level in the given link is given as 5V TTL (seemingly the "wrong" one or TTL/CMOS), you possibly missed the READ-ME-FIRST:

http://www.msfn.org/...-read-me-first/

 

particularly point 6 and the visual representation (original page is down now, but till viewable through Wayback Machine):

https://web.archive...._threshold.html

AND point 10.

 

This might also possibly clear the matter:

http://www.msfn.org/...72004/?p=972251

the difference between SHOUTED ENGLISH and whispered English easier to grasp ;).

 

So, while it is well possible that the Author of the "hacking adapter" is "wrong" :w00t: (and the actual TTL level between the Prolific chip and the Max213 is the "right" one at 3.3V) I would need some definite report of this hack (or of a similar one) working with one of these stupid 7200.11's before being convinced that it could represent a viable solution.

 

jaclaz



#4753
maqic

maqic
  • Member
  • 1 posts
  • Joined 20-October 14
  • OS:Server 2008R2
  • Country: Country Flag

Hello Everyone,

 

Apparently my drive seems also bricked too. I am getting "Incorrect Function" when I try to initialize the disk via Disk manager on windows 2008.

 

Manufacturer : Seagate

Model : ST3500320AS

Barracuda 500 GB 7200.11

 

I ordered the necessary cable and going to follow the process soon,

 

Can you please check the screenshot, is it the reason when LBA0 happen to a disk... I beleive its not BSY because I am able to see it on windows...

 

Thanks,

 

M.G.

Attached Files


Edited by maqic, 20 October 2014 - 09:08 AM.


#4754
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,656 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Yep, but do check also how the BIOS sees it.

A BSY disk won't be detected at all.

A LBA0 will be detected but with 0 size.

 

jaclaz



#4755
swc2008

swc2008
  • Member
  • 1 posts
  • Joined 08-September 14
  • OS:Windows 7 x86
  • Country: Country Flag

I've just managed to recover my Stupid Barracuda 7200.11 HDD.  I used the USB to RS232 TTL converter I bought from the following ebay link.

 

http://www.ebay.com/...=STRK:MEBIDX:IT

 

It costs only US$1.72, but took about 7 weeks to be shipped from Hong Kong to Singapore.

 

The cable works perfectly when I did the loop test by shorting the green and white color cable.

 

To connect to the HDD, I need to remove the black casing at the end of the cables, and covered it with insulative tapes individually.  After that I followed the instructions and connect it to the HDD.  Initially, it cannot communicate -> no respond after entering CTRL-z at the hyperterminal.  Then, I swapped the green and white cable, also did not respond.  I noticed the metal end of the cable could be too loose to have a good contact with the HDD pins.  I then used a plier to make the metal sleeve narrower to ensure good contact when plug in.  After this, it responded when I type CTRL-z.

 

I used the Avico procedures but without the optional codes initially.  After the last instruction (m0,2,2,0,0,0,0,22), there was no message return after waiting for more than 10 minutes. 

 

I then, power off the HDD. and repeat the procedures from the beginning (including removing the screws and re-inserting an anti-static plastic in between the PCB and heads connector).  This time, I used the optional part and after typing the last instruction, it immediately return the Max Wr Retires = 00, Max Rd .......... message.  Great !

 

I am now able to get back all the data and will update the Firmware.

 

Thanks to all the contributors in this forum !


Edited by swc2008, 28 October 2014 - 08:27 AM.


#4756
kaptsae

kaptsae
  • Member
  • 1 posts
  • Joined 30-October 14
  • OS:Windows 8.1 x64
  • Country: Country Flag

Hey guys!

 

After attempting to fix my drive, it shows up in bios and windows with the correct capacity. Unfortunately it doesn't respond when I try to open up my drive in Windows. It also takes about 15 min to boot up windows. When I doubleclick my computer, it doesn't respond unless I detach my drive from the computer. I attached the hd internally.

 

ST3750330AS is my hd with firmware SD35

 

Windows 8.1 x64

 

Does anybody have any suggestions as what to do next?



#4757
toptenandrew

toptenandrew
  • Member
  • 2 posts
  • Joined 04-November 14
  • OS:Windows 7 x64
  • Country: Country Flag

Ok so slightly different topic here....I have used this method to fix numerous drives for myself and others....now I have a Seagate SAS drive that is having issues.  I tried using my connector that I used for the SATA drives but when I pull up PuTTY, I am not getting any response in the terminal.  I know the connector I have still functions because I am able to use it with SATA drives still just fine.  Does anyone know if the Pin-Out for Tx-Rx is different for the Barracuda SAS drives, or is there a different set of variables in PuTTY that I need to use?  Or is there some other solution altogether?  Or is it just not possible?

 

I have looked online everywhere, and no one seems to have a straight answer for this.  The drive is out of warranty and I just want to know if getting it back online is even possible or if this is going to be a straight data recovery center issue.  If the good folks here can tell me if this can even be done for this type of drive or not, I would greatly appreciate it.  Thanks.



#4758
AquaFire

AquaFire

    Newbie

  • Member
  • 12 posts
  • Joined 30-August 09

Hello,

 

I am using a modified DKU-5 cable with correctly marked RX,TX and GND pins. I have used this cable earlier for my hard disk recoveries for seagate ST31000xxxAS 7200.11 (1TB).

 

The disk is now showing the same behavior of having clicking noise immediately after power up. The heads move to the platters and park back. I guess this is the famous BSY error.

 

I have performed recoveries of the similar sort with the same cable, but somehow this time it is not working. I have carefully followed all the steps mentioned in different guides everywhere and especially on this forum.

 

1. I am covering the motor head contacts (3 pins) with card stack paper.

2. I have checked the DKU-5 cable drivers on Windows XP (USB to UART).

3. The hyperterminal connection starts with the connection rate baud settings.

4. Any characters typed in the hyperterminal window do not appear , unless i connect the Rx ad Tx wires which ensures working connection and loopback test.

5. When i connect the cable to the correct pins on the harddisk, the loopback does not work, in a power down state, which means that the cables pins are not touching each other.

6. Whenever I power on the drive (using an external sata disk enclosure by Sarotech), the disk powers on and stays quite because i have isolated the motor contacts.

7. However after waiting for around 10-15 sec when I open the hyperterminal session and send the Ctrl+Z command , I always see a right hand side arrow symbol being show in the window. It is the symbol for ctrl+z (which means undo I guess). Hence the actual F3T/> prompt never comes.

8. If i power off the drive, then I cannot see the right arrow symbol.

9. Based on this behavior I feel that the maybe the PCB is shorted, since when power up , it only connects the cable Tx and Rx pins.

10. Finding an exact replacement PCB is a herculean task, plus I assume that it simply does not work by swapping the PCB.,

11. I dont have and cannot afford expensive recovery services. I only have once service provider in sight, who has the Atola or PC-3000 appratus for recoveries. Is it possible to extract data from such a driver using the PC-3000.

12. Is it possible to try it out with another cable and power supply, maybe the power supplied to the PCB isnt enough, although on visual inspection it does not look fried or having any over voltage damages done to it.

 

 

Am i correct in my diagnosis , any further ray of hope and guidance would be highly thanked for.

 

Thanks.

Can Someone Please tell me what is the exact position of the TX , RX pins on the HDD.

 

The photos in the original first post of this thread are removed and deleted

 

Reading these two websites, the RX TX pins are marked oppositey : which is the correct one ?

 

https://docs.google....DJJT19rMDQ/edit

https://sites.google...ite/seagatefix/

 

Although i did try every possible way of fixing the connectors, all I get I a right hand side arrow in the hyperterminal window, which means maybe the PCB is shorted, no success  :-( and no luck till now.



#4759
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,656 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Can Someone Please tell me what is the exact position of the TX , RX pins on the HDD.
 
The photos in the original first post of this thread are removed and deleted
 
Reading these two websites, the RX TX pins are marked oppositey : which is the correct one ?
 
https://docs.google....DJJT19rMDQ/edit
https://sites.google...ite/seagatefix/

Sure we can tell you :), though it won't really help you since most probably you don't know which one is the Tx and which one is the Rx on the DKU-5 cable, and even if you know, you have anyway a 50% probability of having them wrong, as the marking of Tx and Rx can be interpreted (and may have been applied) in both ways :w00t:.

However the suggested guide is this one:
http://www.msfn.org/...seagate-drives/

(that does contain a correct picture with the ID of the terminals)
Get the attached PDF, as the original guide page is now defunct.

BTW the same guide is ALSO attached to FGA topic:
http://www.msfn.org/...-720011-drives/

and the trick is always, if it doesn't work, to try reverting the Tx and Rx.


jaclaz

Edited by jaclaz, 09 November 2014 - 11:56 AM.


#4760
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,656 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

After attempting to fix my drive, it shows up in bios and windows with the correct capacity. Unfortunately it doesn't respond when I try to open up my drive in Windows.
...
Does anybody have any suggestions as what to do next?

Start a new thread, you are likely in a situation similar to this one:
http://www.msfn.org/...-after-bsy-fix/
and there is the need to fix/recreate the MBR partition table or however attempt to recover the data from it, though it is as well possible that there is an underlying physical issue as in here:
http://www.msfn.org/...11-malediction/
that cannot be fixed DIY.
(in any case the drive is NOT anymore "bricked" and it does NOT anymore belong to this thread).

jaclaz




11 user(s) are reading this topic

0 members, 11 guests, 0 anonymous users