Jump to content

basicguy

Member
  • Posts

    14
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by basicguy

  1. I was about to ask the same question. Aviko, since you are the expert here please

    any ideas on where is this incorrect test machine pattern and if it can be changed?

    Since the event log is said to be directly related to S.M.A.R.T operations I put my 2

    cents that the count (ie. 320 or 320 + any multiple of 256) can be affected/exploited

    by running short self-tests or off-line data collection.

    I made a very simple procedure (using smartmontools 5.39) for almost complete S.M.A.R.T

    dump (including some vendor logs 0xa1, 0xa2, etc) except drive serial# at every shutdown

    for anyone keeping affected drive under old firmware (AD14, SD15, SD16, MX15, etc) and

    interested in a small failure analysis research. Once the drive bricks again and is fixed the

    information may help to develop a simple workaround that predicts or avoid drive failure.

    Dumping some information at the terminal before fixing a bricked drive may also help.

    Level T (/T):
    V4 (dump G-List)
    Level 1 (/1):
    N5 (dump SMART attributes)
    N6 (dump SMART thresholds)
    N7 (dump G-List)
    N8 (dump critical event log)

    Just a thought. Has anyone who recovered their disk from the BSY state and not upgraded the firmware experienced this problem again?

    If the problem is related to data being left by the test machine, and the solution presented here zeros the SMART log area, does this solution mitigate the original problem? Is it wiping the affected areas?

    I have 10 MX15 disks that are sitting in a bag waiting to be re-installed in a machine. It's a fingers crossed type of wait as I have no idea if any or all of them will come back up, but the reports I'm seeing on the SD/MX1A firmware appear to have other "issues" with sleep times and timeouts, while the MX15 has been ok for me. I was wondering if a pre-emptive wipe of the areas required to recover from the BSY state might prevent it from actually occurring ?

    how about downgrade it to AD15 ? when you connect to terminal you have only pcb or disk with pcb ?

    ---sorry for the delayed reply - had to earn some money - does anyone know where I can download a copy of the AD15 firmware? I've scoured the seegate site without success.

  2. and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

    I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

    you can communicate with the drive via diagnostics ? the seagate iso ?

    Negative. My BIOS finds the drive intermitently - 1 in 5 reboots and always with LB0 - and when I tested the Firmware update disk made from the "MooseDT-SD1A-3D4D-16-32MB.ISO" it displays the current firmware as SD1A... so I'm assuming that the update went through at some point. He told me that he'd tried it several times!

    I still cannot make any kind of connection with the hard disk via TTL - despite following the instructions to the letter. I have tried 2 TTL Convertors and 1 Nokia Cable (3210) with the same negative results. The only on-screen response has been that arrow. (Not the '>' cursor)

    how about downgrade it to AD15 ? when you connect to terminal you have only pcb or disk with pcb ?

    I have tried - PCB totally detached, PCB Raised from motor contacts using non-conductive card & PCB attached.

    I'll try and find a copy of the AD15 firmware. At this point, I am not holding out much hope. Could be other things that he's tried that I've not been told.

  3. and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

    I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

    you can communicate with the drive via diagnostics ? the seagate iso ?

    Negative. My BIOS finds the drive intermitently - 1 in 5 reboots and always with LB0 - and when I tested the Firmware update disk made from the "MooseDT-SD1A-3D4D-16-32MB.ISO" it displays the current firmware as SD1A... so I'm assuming that the update went through at some point. He told me that he'd tried it several times!

    I still cannot make any kind of connection with the hard disk via TTL - despite following the instructions to the letter. I have tried 2 TTL Convertors and 1 Nokia Cable (3210) with the same negative results. The only on-screen response has been that arrow. (Not the '>' cursor)

  4. connect wire from pin 3 in terminal socket to gnd of rs232ttl board. next time read carefully what i suggest. I'm wonder when Gradius will fix his tutorial and add this 3rd wire. come on guys this is so boring explaining it all time. noone listens if its not on 1st post

    I'm getting the same arrow -> and would like a bit of confirmation if possible, please.

    Where you say 'pin 3 in terminal socket' - do you mean pin 3 on the seagate PCB?

    Pin 3 on the PCB needs to be grounded. I just used the ground from the RS232 TTL power source (3.3v) and made a third jumper wire to go to the third pin on the PCB.

    Then per Aviko, I then with the power supply off to the computer plugged in the power from the PS to the HDA with PCB attached like normal but no SATA cable and turned the power on to the computer PS.

    Then I put the battery to the 3.3v into the holder to power the RS232 TTL with everything hooked up to my computer serial port and hit connect in hyper termial.

    I went from the farking arrow to the actual text.

    Once I did that, I knew I had the right setup and everything was talking.

    Then turned off hyper terminal, turned off the computer PS (CPS) and pulled out the battery from the TTL board.

    THEN I removed the PCB and put thick paper under BOTH the contacts and then replaced most of the screws except for the one that goes to the motor and the PCB board to HDA.

    Then I restarted the CPS and then put the battery back in and restarted hyper terminal and then followed the instructions to fix the BSY HDA problems.

    Then I felt whole again because this saved my arse big time!

    I tried this...

    setup.jpg

    and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

    I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

  5. connect wire from pin 3 in terminal socket to gnd of rs232ttl board. next time read carefully what i suggest. I'm wonder when Gradius will fix his tutorial and add this 3rd wire. come on guys this is so boring explaining it all time. noone listens if its not on 1st post

    I'm getting the same arrow -> and would like a bit of confirmation if possible, please.

    Where you say 'pin 3 in terminal socket' - do you mean pin 3 on the seagate PCB?

  6. Can anyone provide me with the following info about the Nokia 3210 cable:

    1. The NKI 3210 cable has 4 pins - anyone know which is RX/TX?

    2. Anyone know where I can get the drivers for this cable (if they are, in fact required)?

    Thanks in advance.

    http://pinouts.ru/CellularPhones-Nokia/nok...10_pinout.shtml

    Perhaps I'm being an fool but I can't seem to see how this applies to the cable I have. It's has a DB9 connector on one end and the following on the other:

    nokia3210.jpg

    Anyone also know what the M - F switch does?

  7. BASICGUY

    Hmmm not too sure, And you will need some more bits of cables etc.

    This will definately work and the delivery is quick, and the guy there Rob is really helpfull (in an Electronics type way).

    http://cgi.ebay.co.uk/RS232-to-3-3-Volt-TT...A1%7C240%3A1318

    And its at least £10 cheaper.

    A nokia 3210 fbus data cable is still the cheapest an easiest option, at around 2 quid and only needing the rx and tx connecting (no gnd or power)

    Thanks for the reply...

    How about a DCU-65 cable? - I'm sorta' on a time limit for this...

    ...anyway, the RS232-TTL adaptor turned out to be dead but I did manage to find a nokia 3210 fbus data cable. Couple of questions:

    1. The Nokia cable has 4 pins - which are TX/RX - or how can I determine this?

    2. Do I need the drivers for the nokia 3210 fbus data cable?

    Thanks in advance.

  8. BASICGUY

    Hmmm not too sure, And you will need some more bits of cables etc.

    This will definately work and the delivery is quick, and the guy there Rob is really helpfull (in an Electronics type way).

    http://cgi.ebay.co.uk/RS232-to-3-3-Volt-TT...A1%7C240%3A1318

    And its at least £10 cheaper.

    A nokia 3210 fbus data cable is still the cheapest an easiest option, at around 2 quid and only needing the rx and tx connecting (no gnd or power)

    Thanks for the reply...

    The above adaptor arrived yesterday... have tried for the last few hours to make a connection with the Drive. Have quadruple checked all of the connections but still get a blank terminal screen. The only sign of life from my RS232-TTL adaptor is a solid red light... anyone an idea what this means? (If anything..)

    Note that I have set up the connections EXACTLY like those shown on the first page of this topic... and nothing, nada, sod all, bugger all, nowt! and zilch.

    Any help appreciated... specifically in testing the RS232-TTL...

  9. BASICGUY

    Hmmm not too sure, And you will need some more bits of cables etc.

    This will definately work and the delivery is quick, and the guy there Rob is really helpfull (in an Electronics type way).

    http://cgi.ebay.co.uk/RS232-to-3-3-Volt-TT...A1%7C240%3A1318

    And its at least £10 cheaper.

    A nokia 3210 fbus data cable is still the cheapest an easiest option, at around 2 quid and only needing the rx and tx connecting (no gnd or power)

    Thanks for the reply...

    How about a DCU-65 cable? - I'm sorta' on a time limit for this...



×
×
  • Create New...