Jump to content

ctblack

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Posts posted by ctblack

  1. Hello.

    I am a "happy owner" of a 500 GB 7200.11 Seagate drive affected with the firmware issue, the BSY one and maybe the LBA0 too... After a intensive search I founded the way to fix my drive and recover all my info. But when I try the method I have a little problem: I do not obtain the prompt in hyperterminal. Let me explain what i've done:

    I have the rs232 to ttl converter powered by a molex from the PC at 5 Volts. I've tested it conecting rx and tx and typing in hyperterminal and works fine.

    Then, I remove completly the pcb from the HD and connect RX and TX wires to the TX and RX of the converter (shifting connections do nothing in hyperterminal). The next step is power the converter, open hyperterminal and configure it (38400,8,N,1,N) and power the HD board. The problem arrives now:

    I press CRTL+z but I do not get the prompt. The only thing that appears on hyperterminal screen are spaces and black squares. As I said previosly, changing the conections do nothing on screen.

    I've changed hyperterminal config as suggested in other post to "windows key" and the problem persists.

    What I'm doing incorrectly???

    Thanks in advance and excuses for my bad english.

    PD: he estado siguiendo los posts de Pichi en el hilo en castellano hasta que lo cerraron. Si algun consejo fuera en castellano lo entendería mejor :blushing: :blushing:

    When I tried using 5 volt from the power supply to power the rs-232 convertor, I also gotten nothing. I then used 2 'D' cell batteries to power the convertor and connecting all the negatives together to make it work.

  2. Im a Mac user, does the solution apply to mac ox system?

    As for the terminal software, I only found a mac system terminal software, does it work as well?

    The solution is not OS dependent, any terminal software should work. The tricky part is if all you have access to is USB ports and no DB9(or DB25) serial ports, then you'll need to find or make the right cable.

  3. Anyone has any idea why replacing the PCB doesn't work in this case? I purchased 4 x 1TB drives and only one had problems (not recognized anywhere). While I am waiting for the connector I ordered I thought about this second option (replacing the PCB) but it seems that it doesn't work. The "good" PCB is from a disk with exactly the same model number and firmware.

    I did remember reading from earlier post, there were someone swaped the PCB from a "bad" drive into a working drive and did the firmware update on the "bad" PCB, and then swap it back to make the "bad' drive work again, but then they were complaining about some unusual noise the drive now makes.

  4. A 500 g is back to life .

    But i have another one seagate 1 T and have problems to make to work

    when the drive power on make a noise and after about 20 sec stop

    F3 T/2

    F3 2>Z

    IT GIVES :

    LED 000000CE FAdr00280569

    LED 000000CE FAdr00280569

    the same gives and with pcb alone

    When i gave the U

    ERROR 1009 DETSEC0006008

    SPIN ERROR

    ........

    This is exactly what happened to me when I tried, then I used a level 3 spin down command instead:

    F3 T>/3

    F3 3>Z

    with

    F3 T>/3

    F3 3>Z

    again

    LED 000000CE FAdr00280569

    LED 000000CE FAdr00280569

    something else to try?

    Did you try the level 3 command with the PCB alone or still mounted on the drive? All I can tell you is, I tried that with the PCB mouted on the drive and it worked for me. There might be other level spin down commands, you can look in the earlier posts of this thread for a complete list of all the commands.

  5. A 500 g is back to life .

    But i have another one seagate 1 T and have problems to make to work

    when the drive power on make a noise and after about 20 sec stop

    F3 T/2

    F3 2>Z

    IT GIVES :

    LED 000000CE FAdr00280569

    LED 000000CE FAdr00280569

    the same gives and with pcb alone

    When i gave the U

    ERROR 1009 DETSEC0006008

    SPIN ERROR

    ........

    This is exactly what happened to me when I tried, then I used a level 3 spin down command instead:

    F3 T>/3

    F3 3>Z

  6. Hi,

    Greetings from Vancouver BC Canada, My 500 GB seagate 7200.11 harrddrive also suddenly cannot be detected by the bios. Good thing I found this forum. I am planning to get the DKU-5 or CA-45 cables. My question is those pins at the back of the hardrive is sooo small ! how did everyone connect the wire to there ? I dont have any soldering equipment and I am a newbie to electronics. I can strip wires and connect two wires together and put electric tape around it but thats the most I have done and not at this small scale. Can anyone tell/show me how do I connect the wires from my usb data cable to the HD pins ? Or can I find something at "Circuit city/the source" to connect to the hd pin ?

    thanks,

    Elman

    I took the curcuit board out and flipped around to solder some "wire wrap" wires to the back of the pins. You can try to use those plastic connectors like a video card fan power connector and break them open so only the metal pin is show, I tried that but found it to be too closed together and can short each other easily when it is pushed into the HD's pin, especially if you tries to connect all three (TX/RX/GND).

  7. I have successfully unbricked my drive using Gradius2's instructions! Thank you very much Gradius!! A few things I found that might already been encountered by others, as I didnt read all of the postings (39 pages and still growing!!). I just wanted to share them as they might be helpfull:

    1. I started the procedure using the PC's power supply (+5V) to power the convertor and found it does not work! I needed to use 2 'D' cells batteries in series to provide the 3V power to the convertor inorder for the convertor to be able to convert the hard drive's data to RS-232 back to the PC.

    2. I keep getting the "LED:000000CE FAddr:00280569" error after I issue the level 2 'Z' spin down command. After checking my connections many times and retried many times. I then used a level 3 'Z' spin down command and it woked!

    3. I did'nt have any of the those hard drive pin connectors to the TX/RX/GND pins, so I used some very fine wire to solder to them, got the terminal session working, but all my lower case characters sending to the hard drive would end up corrupted returning as extened ascii characters. I then used the 'B9600' command to change my connection speed to 9600 baud (since the command is in upper case), and everything else worked from that point on.

×
×
  • Create New...