[zabx2]

deleted

This post has been edited by zabx2: 08 May 2012 - 03:01 AM

[jaclaz]

zabx2, on 05 May 2012 - 04:39 AM, said:

there are tens of posts and 2 hundred pages. you could just help a newbie by PM)

I could, were I not a grumpy heartless bastard , compare with:
http://www.msfn.org/.../page__st__4144

JFYI, this thread has two hundred pages because tens of people, just like you, did not READ the READ-ME-FIRST, and asked AGAIN, and AGAIN and AGAIN, always the SAME questions, which are ALREADY (I hope clearly ) explained in the READ-ME-FIRST and/or in the FGA's and/or in n previous posts.
You might understand how the Read-me-first, the FGA's and, more generally all the help, support, advice and answers given on this thread (BTW extensively contributed by yours truly) was provided in order to easen life of BOTH the "newbies" AND of the "experts", by giving useful info to the former and to let the latter need NOT to repeat, over, and over and over again the SAME things.

It is frustrating how this effort not only is not appreciated, but from time to time a "newbie", just like you, comes here:

• hinting - not so subtly - that I am not as friendly as I should
  
• asking questions already asked again and again (and duly replied to over and over again)
  
• demanding personal assistance for issues already talked over and over n times

jaclaz

[Kelsenellenelvian]

Quote

you could just help a newbie by PM

We are ALSO NOT in the delivery business.

[duk]

Since this topic is so old then i'm not sure how many of you still remember the details of solving the issue, but wanted still to share my problems and maybe someone can give some input as to what is going on.

So, the drives head contacts are blocked, I'm connected to terminal and turn on the drive, it will spin up normally. After 30 sec, it will spin down and start giving error in terminal LED:000000CC FAddr:0025BF67 After this error there is no way to further input anything in the terminal.

Anyway, hence i have 30 secs from switching on the power to input the Crtl+z, /2 and Z because after that the terminal will be blocked. Even though some people in this thread have suggested waiting for 30-60 seconds after turning on the power to enter any commands - don't know how this could be possible if after 30 seconds it will already block the terminal with the error.

Nevertheless i've tried to enter these three commands i don't know how many times in different timing possibilities(i.e. waiting for 10, 15, 20, 30 secs before issuing the Ctrl+z or Z command).
And it will always give an another error LED:000000CE FAddr:00280569 and block the terminal. Some people have received this error when entering lowercase z or not entering slash before 2, or being to fast, but i'm not doing that.

In addition I tried these 3 commands with just motor connection blocked and the PCB completely removed - everything gives same result - LED:000000CE FAddr:00280569 right after Z command or if no commands are given, 10-30 sec after power-up (depending on what contacts are blocked) it will give LED:000000CC FAddr:0025BF67.


Out of ideas completely.

[jaclaz]

duk, on 08 May 2012 - 11:20 AM, said:

Since this topic is so old then i'm not sure how many of you still remember the details of solving the issue, but wanted still to share my problems and maybe someone can give some input as to what is going on.

First thing that comes to mind is that the command is Ctrl+Z, not Ctrl+z.

Is it not - by any chance - and ES2 drive?
http://www.msfn.org/...000000cc-state/

You may want to try with all THREE different approaches:

• Head contacts insulated
  
• Motor contact insulated
  
• PCB completely detached

You may also want to try with a a N1, see:
http://www.facebook....152456431478526

jaclaz

[duk]

jaclaz, on 09 May 2012 - 02:08 AM, said:

You may also want to try with a a N1, see:
http://www.facebook....152456431478526

jaclaz

Hey jaclaz, thanks for the answer!

The drive is not ES.2. It's Maxtor DiamondMax 22.

I'm not sure what you mean by trying with N1? The FB link seems to describe the standard solution.


But otherwise, the possibilities you suggested, unfortunately they have all been tried already.

Ctrl+z or Ctrl+Z does not seem to make any difference, they both bring up the terminal F3 T> but it gets locked with LED:000000CC FAddr:0025BF67 after 30 sec. Tried entering both Ctrl+z and Ctrl+Z after that in all PCB configurations and the terminal will not unlock.
And i have tried all different timings when entering the commands - also with all different PCB configurations(head blocked, motor blocked, pcb off).

I mean it's just rediculous how my drive is in such exceptional situation even though the symptoms are exactly correct with the defect described.

[BlouBul]

duk, on 09 May 2012 - 05:59 AM, said:

Ctrl+z or Ctrl+Z does not seem to make any difference, they both bring up the terminal F3 T> but it gets locked with LED:000000CC FAddr:0025BF67 after 30 sec. Tried entering both Ctrl+z and Ctrl+Z after that in all PCB configurations and the terminal will not unlock.
And i have tried all different timings when entering the commands - also with all different PCB configurations(head blocked, motor blocked, pcb off).

I mean it's just rediculous how my drive is in such exceptional situation even though the symptoms are exactly correct with the defect described.

Try at level 8
http://pictatrove.co...harddrives.html

Quote

2009-Feb-16: Seagate has a problem with its new 1.5TB drive freezing for 30 seconds at a time. ...
At this point things worked up to issuing the "Z" command to spin down the drive. For me as soon as I issued that command the drive would enter the busy error state. The command sequence looked like:

F3 T>/2
F3 2>Z
LED:000000CC FAddr:0025BF67LED:000000CC FAddr:0025BF67
In the end I reviewed the various drive commands (a list is listed here) and noted that the "Z" command was also available at other "levels", so I gave level 8 a try and this worked. The output from my command session looked like:
F3 T>/8
F3 8>Z
Spin Down Complete
Elapsed Time 0.161 msecs
F3 8>
F3 8>U
Spin Up Complete
Elapsed Time 9.250 secs
F3 8>/1
F3 1>N1
F3 1>/T
F3 T>
F3 T>i4,1,22
F3 T>m0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8User Partition Format 5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 000User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 10 secsUser Partition Format Successful - Elapsed Time 0 mins 10 secs
F3 T>After I had done this I was able to remove the drive, test it and confirm that it was working fine.

This post has been edited by BlouBul: 09 May 2012 - 07:24 AM

[jaclaz]

Sorry, my bad , posted the "wrong" link, Bloubul posted the right one , that's exactly what I meant.
(getting old, and forgetful.... )

jaclaz

[duk]

Thank you both, here is the latest update then.

So the problem was actually in the SATA data cable. Since i have it as one plug together with the SATA power i had to have the data also connected. Even though the other side of data was not connected to PC it was still for some reason blocking the terminal.
But i was eventually able to find a separate SATA power cable and run through the steps. And obviously since everything that can go wrong is going wrong then I also had the DETSEC error which i was able to overcome by cleaning the PCB head contacts - TWICE.

Now after running thru all the steps successfully, i connect the drive to PC over USB and the PC reaaaally slowly recognizes it as a local disk - but it doesn't recognize it as Maxtor, neither does Seatools. I did the same process some time ago with another disk and in that case it recognized the connected disk as Maxtor.
Once it recognizes it as disk it will start Autoplay which does some ambiguous scanning, but the drive eventually comes up as 0 bytes under my computer. For the other disc i had i saw autoplay actually go thru the directories on the disk and then the files became available.

OK, then i thought it might be the 0 LBA issue then. Start terminal again, and run the m0... command to fix the 0 LBA. But when i connect again over USB, it's still 0 bytes.
I've seen some people suggest just trying it again and again but don't know if that would eventually be of any help.

Edit: Actually it recognizes the disk only the first time i plug it in over USB after doing the fix and it does actually show in device maneger as Maxtor disk with correct model with file system RAW. The second time i plug it in it is unrecognized device, no matter which USB port i use. And if i plug it in to a different PC then it's also unrecognized device.
And another interesting point, the second disk i fixed some time ago behaves the same, the files are no longer accessible and it's either 0 bytes or unrecognized device.

Do you have any additional ideas on this?

This post has been edited by duk: 09 May 2012 - 03:34 PM

[BlouBul]

duk, on 09 May 2012 - 02:02 PM, said:

i connect the drive to PC over USB and the PC reaaaally slowly recognizes it as a local disk
...
And another interesting point, the second disk i fixed some time ago behaves the same, the files are no longer accessible and it's either 0 bytes or unrecognized device.

Did you check your external USB enclosure/ Port? What happens if you connect it straight in your PC (not through USB)?

This post has been edited by BlouBul: 10 May 2012 - 01:24 AM

[jaclaz]

duk, on 09 May 2012 - 02:02 PM, said:

Do you have any additional ideas on this?

As Bloubul said try connecting it directly, additionally, and in any case, DISABLE autoplay for the USB.


Basically, the "recovery" procedure in most cases renders the disk as it was before (usually when the "reason" why it was bricked was actually the original "firmaware log at position 320") but in many case, for a numebr of reasons, once "unbricked", partitions and/or filesystem on it may not be anymore recognizable.
In this case (and IF this is the case, it means that you MUST have a non 0 result in BIOS when the dik is connected directly to the motherboard, i.e. the disk is not still - or has reverted to - LBA0 state) the next steps are:

• imaging the RAW disk
  
• recover the partition(s), filesystem(s) and if this cannot be done, attempt recovering the files

(the above is fully "software" and not anymore "hardware")

jaclaz

[Jimbolino]

Somewhere in the first post is mentioned: "(yellow is +12V so don't use it)"

Without the 12v i didnt got my console up and running.

After i connected both 5v AND 12v, console was working fine, and everything worked like it was supposed to.

Just wanted to share my experience, cheers!

[BlouBul]

Jimbolino, on 10 May 2012 - 10:21 PM, said:

Somewhere in the first post is mentioned: "(yellow is +12V so don't use it)"

Without the 12v i didnt got my console up and running.

After i connected both 5v AND 12v, console was working fine, and everything worked like it was supposed to.

Just wanted to share my experience, cheers!

Where did you connect BOTH 5V and 12V to? 12V will definitely fry your hdd connected through your converter at TTL, but you need to power your hdd with the normal full spectrum of power cables.

[jaclaz]

Jimbolino, on 10 May 2012 - 10:21 PM, said:

Somewhere in the first post is mentioned: "(yellow is +12V so don't use it)"

At the very beginning of the first post there is printed in BIG LETTERS:

Quote

Please make sure you've READ the Read-Me-First Sticky FIRST!

Now, had you actually READ it, you might have seen how (point #3) the RECOMMENDED method to be followed is:
http://www.msfn.org/...seagate-drives/
http://www.mapleleaf...agatebrick.html

WHY would we be RECOMMENDING that guide and not first post of this thread?
BECAUSE it is CLEARer, it is step-by-step, has detailed images (including those of connections), and more generally, unlike the first post of this thread it includes a number of "tricks" and suggestions that were found out after the first thread was initiated.

In any case even in first post, the reference to the "yellow" cable is in the context of "how to power the USB/TTL or Serial/TTL converter" and has NOTHING to do with powering the HD.
Try re-reading the whole part in this highlighted version:

Quote

Connect TX and RX ports with RS232 to TLL adapter, you'll need something like jumpers in order to do that, or soldering directly to the PCB board. Connect GND and +5V to PC power supply, or similar. Keep in mind those are direct from Seagate sides, so you'll need to connect in this way:

- From PC (TX) to >>> RX (on Seagate)
- From PC (RX) to >>> TX (on Seagate)

You can use RED wire (+5V) from PC power supply. Blacks are GNDs (yellow is +12V so don't use it).

If you don't want to mess with power supply, just use a CR2032 (3V) battery:

The idea was to prevent people from frying the adapter by supplying it 12V instead of the 3 or 5 V required by it (depending on adapter model)

jaclaz

[Gradius2]

Just to let you guys to know... yes, I'm alive and well.

Specially since I decided to change HDD manufacture. ;-)

[jaclaz]

Gradius2, on 11 May 2012 - 04:33 PM, said:

Just to let you guys to know... yes, I'm alive and well.

Specially since I decided to change HDD manufacture. ;-)

Good to see you around and know everything is fine.
But don't be too proud about hard disk manufacturer change, though the 7200.11 (and to some extents the 7200.12) have been total crap, we do have the deskstar/deathstar preceding issue:
http://en.wikipedia....itachi_Deskstar
so I won't bet against the possibility that sooner or later another disk manufacturer will fall in a similar issue.

jaclaz

[Bumangero]

My second hardrive stopped working about two years ago, I then bought a new one but I had data on the old drive that I wanted to recover so I didn't throw the drive away. I read about how to try to get it working again but it took me very long time to actually try it out. Today I finally did it and it worked!!! but I had big trouble to succeed with it and that I want to share.

By coincidence I used the converter board with a known exception (sparkfun) that is mentioned in the sticky. I powered it with an external supply at 3 V and grounded it with the drive. I followed the instructions in the first post except that I placed a paper between the pcb and the connectors instead of removing the pcb completely. It connected to the drive with the "ctrl+z" in the terminal window, but I always got the error "LED:000000CC FAddr:0025BF67" or "LED: 000000CC FAddr: 0024A051". I tried it many times with different timings but always with the same result. I then took away the pcb completely with the same result. I was then willing to give up and thought the drive was beyond salvation. When the clock was 3 in the morning I went to sleep.

Today in the afternoon I gave it another try with another approach. I powered the converter board with two 1.5 batteries in series because I suspected some interference/grounding problem. To my surprise it now worked exactly as the instruction in the first post.

Conclusion: Never ever give up!

Thanks for this thread it made my day!

[BruceWayne]

Duds and dudesses , thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
got back 500GB of data

After few weeks i tried to connect handmade tool i actually bought one pre assembled, but it worked and i have all my data backkkkkkkkkk

MOST IMPORTANT THING type commands exactly like its on first page

[ultimatescar]

well so may it be me reviving the thread. i've tried to read all but i got stuck on the first page. i dont got anywhere from endless loop of

Rst 0x20M
(P) SATA Reset
LED:000000CC FAddr:0024CDC9
Rst 0x20M
(P) SATA Reset

and when i block contact of moterhead i get Rst0x20 ? i didnt find solution anywhere care to help guys.. my hd is seagate ST31000333AS and i'm using ttl to rs232 converter.
thankx.

Attached File(s)

•  ttl.jpg (93.33K)
  Number of downloads: 18

[BruceWayne]

seems to be your case

http://forums.seagat...ssue/td-p/45408

you can google for "(P) SATA Reset loop " and find more info from other users