[ultimatescar]

BruceWayne, on 26 May 2012 - 12:06 AM, said:

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

I've been trying to follow every piece of information that i could find i've had that one you forwarded as my bookmark from before. rather than googing you could have shown the adresses.. as i've come to almost every site with almost same response which didnt work for me.
but thanx anyway

[jaclaz]

ultimatescar, on 26 May 2012 - 06:19 AM, said:

I've been trying to follow every piece of information that i could find i've had that one you forwarded as my bookmark from before. rather than googing you could have shown the adresses.. as i've come to almost every site with almost same response which didnt work for me.

There is probably *something* that you are "doing wrong" .
Please do the following:

• FORGET (temporarily) whatever you have read on the topic
  
• ONLY read the Read-me-.first and FGA's:
  http://www.msfn.org/...-read-me-first/
  http://www.msfn.org/...-720011-drives/
  
• Then try following (to the T) the suggested guide here:
  http://www.mapleleaf...agatebrick.html

VERIFY that your RS232 to TTL converter is using the compatible "lower" TTL level, make sure about both power (power to the PCB board) to be "stable" and make sure of proper GROUNDING.

Report.

jaclaz

[ultimatescar]

jaclaz, on 26 May 2012 - 06:40 AM, said:

ultimatescar, on 26 May 2012 - 06:19 AM, said:

I've been trying to follow every piece of information that i could find i've had that one you forwarded as my bookmark from before. rather than googing you could have shown the adresses.. as i've come to almost every site with almost same response which didnt work for me.

There is probably *something* that you are "doing wrong" .
Please do the following:

• FORGET (temporarily) whatever you have read on the topic
  
• ONLY read the Read-me-.first and FGA's:
  http://www.msfn.org/...-read-me-first/
  http://www.msfn.org/...-720011-drives/
  
• Then try following (to the T) the suggested guide here:
  http://www.mapleleaf...agatebrick.html

VERIFY that your RS232 to TTL converter is using the compatible "lower" TTL level, make sure about both power (power to the PCB board) to be "stable" and make sure of proper GROUNDING.

Report.

jaclaz

I read each and every word.... im still stuck with the look i cant manage to get F3.... could it be my ttl converter's problem?
i'm using this on http://www.dealextre...r-101467?item=2 or should i make one from nokia ca-42 cable-

[jaclaz]

ultimatescar, on 26 May 2012 - 08:47 AM, said:

I read each and every word.... im still stuck with the look i cant manage to get F3.... could it be my ttl converter's problem?
i'm using this on http://www.dealextre...r-101467?item=2 or should i make one from nokia ca-42 cable-

Sure , but you do not report whether you are actually following what you have read in the given links.
Have you provided grounding?
How EXACTLY are you powering the adapter?
Are you trying insulating the head or motor contacts?
Have you successfully performed a loopback test?
etc., etc.

About the adapter you are using, there is NO specific info on that page about the kind of TTL level that adapter uses. (unless the "working voltage" means TTL level)
The photo *seems* like having a "323x" chip (which should mean that it is of the "right" kind) but cannot say for sure.
But yes, trying another adapter (not necessarily a CA-42 one) is your next step, it is very possible you have a DOA one or however one that is not suited.
About CA-42, please DO READ point #10 of the read-me-first (you know, it is written for a reason ) and FGA #6, then:
http://www.imdb.com/...es?qt=qt0362962


jaclaz

[ultimatescar]

Edit Edit..


Nevermind.. Thanx mr Jaclas... I'm forever grateful to you.... I dont know what seem to be the problem is but i fixed it by using my laptops serial port so basically there was something wrong with my serial-usb converter.. Thanx Again
UltimateScar Bows down to Jaclas.

I'm copying my old pics to the new hard drive right now.. should i format it later and use the brink's iso firmware or should i just throw it Jacles.?

This post has been edited by ultimatescar: 26 May 2012 - 09:27 AM

[jaclaz]

ultimatescar, on 26 May 2012 - 09:21 AM, said:

I'm copying my old pics to the new hard drive right now.. should i format it later and use the brink's iso firmware or should i just throw it Jacles.?

These may help you (or completely fail to ) in doing the right thing :
http://www.msfn.org/...259#entry985259
http://www.msfn.org/...258#entry932258
(basically IF the issue with your drive was the original log entry issue, your drive is likely to live with no firmware update and a reset every three to nine months time, die instantly on a failed firmware upgrade, or live happily *ever after* a successful firmware upgrade)
BTW, good to have another happy bunny in the basket :
http://www.msfn.org/...ic=128727&st=10

jaclaz

[Airkey]

Please I need some help! Just one little step and I'll succeed.

I've got everything working....cable, wires, driver, hyperterminal.
But when I put down the power for a few seconds before going further to the last step, hyperterminal STOPS or breaks the connection with the harddrive!!!

And I have to start all over. How can you put the power down without breaking the connection with hyperterminal?

I don't read anything about this problem.

Power OFF/ON the drive (very important!)

Wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:

Partition regeneration:

F3 T>m0,2,2,,,,,22 (enter)

This post has been edited by Airkey: 02 June 2012 - 03:24 AM

[jaclaz]

Airkey, on 02 June 2012 - 03:24 AM, said:

Please I need some help! Just one little step and I'll succeed.

I've got everything working....cable, wires, driver, hyperterminal.
But when I put down the power for a few seconds before going further to the last step, hyperterminal STOPS or breaks the connection with the harddrive!!!

And I have to start all over. How can you put the power down without breaking the connection with hyperterminal?

I don't read anything about this problem.

Power OFF/ON the drive (very important!)

Wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:

Partition regeneration:

F3 T>m0,2,2,,,,,22 (enter)

I am not sure to be follwing you. (actually I am quite sure that I am not following you ).
WHO told you that Hyperterminal needs to remain connected when you power off? (it is a logical impossibility, the device is powered down, so you NEED to re-connect)

FORGET anything you have read till now.
Simply follow the suggested guide (and NOT any other one) "to the T":
http://www.mapleleaf...agatebrick.html

BTW ten seconds sound like a bit too little, the cited suggested guide says 60 seconds, but it also say that you can try WITHOUT disconnecting power (BUT in this case you NEED to change level to /T)

jaclaz

[smandurlo]

@AirKey, follow this guide: http://www.msfn.org/...post__p__832863

You don't need to power off the drive in any moment and it is safier. Btw it is logic that the hyperterminal is disconnected if you power off the drive.............. If u call someone and this person hang off the conversation, are u still connected/speaking with him/her?

[Airkey]

Thank you all for your help!! I followed the instructions and it worked.......it's unbricked.
And it's showing the drive (letter) in "my computer" again. But....I still can't open my files.

Maybe the disk also has a hardwareproblem..

Frustrating after all these months.

Anyway, thnx guys

This post has been edited by Airkey: 03 June 2012 - 12:07 PM

[jaclaz]

Airkey, on 03 June 2012 - 12:06 PM, said:

Thank you all for your help!! I followed the instructions and it worked.......it's unbricked.

Good , though the questions "WHICH instructions?" (since you were suggested TWO different ones) comes to mind.

Airkey, on 03 June 2012 - 12:06 PM, said:

And it's showing the drive (letter) in "my computer" again. But....I still can't open my files.

Maybe the disk also has a hardwareproblem..

Naaah, it happens quite often that a few sectors are anyway "bad" (or were part of the G-list you have possibly cleared).
Now you need to recover your data.
Please - should you need help for this - start a new thread and do not post on this one.

To have an idea of possible paths, do check these threads:
http://www.msfn.org/...-after-bsy-fix/
http://www.msfn.org/...as-please-help/
http://www.msfn.org/...srebuild-fat32/

jaclaz

This post has been edited by jaclaz: 03 June 2012 - 01:00 PM

[goldrocket]

I am connected, I can set up hyper terminal, but When the terminal is open, I can't type in it. I can actually not perform any kind of input. I thought it was due to a wireless keyboard, but no luck with a USB either. I have used hyper terminal and Tera Term. What's the trick? Sorry for the NooB question, but this is the first time I've used this equipment/software.

Windows 7 x64, 6core AMD Vision, 12G ram, in case it matters.

This post has been edited by goldrocket: 11 June 2012 - 03:00 PM

[jaclaz]

goldrocket, on 11 June 2012 - 02:59 PM, said:

I am connected, I can set up hyper terminal, but When the terminal is open, I can't type in it.

I am not sure to understand the issue.

Have you tried a loopback test (as you should have)?

Check first the Read-me-first (ALL of it, but particularly point #8):
http://www.msfn.org/...-read-me-first/
and the FGA's (ALL of them but psrticularly #4 and #5):
http://www.msfn.org/...-720011-drives/

jaclaz

[smandurlo]

So, I have another unlucky Seagate... 500GB SD15.

It was detected by the bios, but not in windows. It was not LBA 0 since, for example, testdisk doesn't see it at all and any other recovery software the same. It was something in between the bsy and the the lba 0.

I decided to attempt a bsy solution from avico and now it is detected by the bios and by windows. The last cmd (m0,2,2,0,0,0,0,22) exited with 1 partition formatted. BUT! They are 2!

The user, in fact, formatted it in 2 dynamic partitions. I made a full dd image and inspected it with recovery softwares.

Only the first one, 100GB is visible and I can recovery everything inside. The second partition is something like blank. Nothing inside. No file system, no files, nothing. Photorec doesn't find any files. Not even 1 small file.

I tried another LBA 0 fix. The same: just one partition formatted and again I can see everything inside the first one, nothing on the second one.

Any idea? The files I need to recovery are, obviously, into the second partition...

[jaclaz]

smandurlo, on 15 June 2012 - 01:33 AM, said:

The last cmd (m0,2,2,0,0,0,0,22) exited with 1 partition formatted. BUT! They are 2!

No .
Meaning that at the "level" it is very unlikely that the disk firmware knows anything about "partitions" (as defined in the partition table in the MBR).
I suspect that the "User partition" message you saw on the screen is not related to a partition like you are used to (software partition).
To the disk firmware there are two partitions, Firmware partition and User partition, or, if you prefer, "Reserved Area" and "User accessible area".
The partitions you make via software are inside the "User accessible area" or "User partition".
I wouldn't give any relevance to the message (in the sense that it seem to me like UNrelated to the actual issue).

smandurlo, on 15 June 2012 - 01:33 AM, said:

The user, in fact, formatted it in 2 dynamic partitions. I made a full dd image and inspected it with recovery softwares.
Only the first one, 100GB is visible and I can recovery everything inside.

Dynamic partitions are "tricky" .
There are several ways how the user may have made them :

• simple volumes
  
• spanned volumes
  
• striped volumes
  
• mirrored volumes
  
• RAID-5 volumes

once set aside simple volumes (and probably the first partition you found is of such a type) and mirrored volumes, all the other types are VERY complex to recover and very few softwares can deal with them properly.
A tool known to be able to deal with those is File Scavenger (Commercial):
http://www.quetek.com/RAID.htm

smandurlo, on 15 June 2012 - 01:33 AM, said:

The second partition is something like blank. Nothing inside. No file system, no files, nothing. Photorec doesn't find any files. Not even 1 small file.

Are actual sectors blank (00 filled)?
If yes, there is nothing you can do .
If no, there are maybe some possibilities .

jaclaz

[smandurlo]

jaclaz, on 15 June 2012 - 02:37 AM, said:

Meaning that at the "level" it is very unlikely that the disk firmware knows anything about "partitions" (as defined in the partition table in the MBR).
I suspect that the "User partition" message you saw on the screen is not related to a partition like you are used to (software partition).
To the disk firmware there are two partitions, Firmware partition and User partition, or, if you prefer, "Reserved Area" and "User accessible area".
The partitions you make via software are inside the "User accessible area" or "User partition".
I wouldn't give any relevance to the message (in the sense that it seem to me like UNrelated to the actual issue).

I can agree with u, but I saw many of these HDD giving me 2 or even 3 formatted partitions after the cmd m0,2,2,0,0,0,0,22 and they were according with the logical partitions they were divided. That is why I assumed they should be related.

jaclaz said:

Are actual sectors blank (00 filled)?
If yes, there is nothing you can do .
If no, there are maybe some possibilities .

jaclaz

How can I inspect the single sector? I didn't check them, just realized there is nothing to recover.

Anyway, I checked it with Seatools in windows (I will on DOS too in few hours) and it gives me an error while checking the internal diameter...

This post has been edited by smandurlo: 15 June 2012 - 02:52 AM

[jaclaz]

smandurlo, on 15 June 2012 - 02:50 AM, said:

How can I inspect the single sector? I didn't check them, just realized there is nothing to recover.

With *any* hex/disk editor.
The one I normally use and suggest is Tiny Hexer:
http://reboot.pro/8734/

Another very good tool (though not strictly a hex/disk editor) is dmde (which is IMHO an exceptionally good "advanced" recovery software):
http://softdm.com/
It does have "sector level" access:
http://softdm.com/ma...diskeditor.html

jaclaz

[smandurlo]

jaclaz, on 15 June 2012 - 03:16 AM, said:

Another very good tool (though not strictly a hex/disk editor) is dmde (which is IMHO an exceptionally good "advanced" recovery software):
http://softdm.com/
It does have "sector level" access:
http://softdm.com/ma...diskeditor.html

Ok, is it the correct view? https://dl.dropbox.c...6462486/boh.jpg

If yes, all the sectors from this one (it should be the first of the problematic partition) are not blank, there is something written. Correct?

And if they are not blank. why nothing inside?

[jaclaz]

smandurlo, on 15 June 2012 - 07:53 AM, said:

Ok, is it the correct view? https://dl.dropbox.c...6462486/boh.jpg

Yep, that is a view of LBA sector 202213012.

smandurlo, on 15 June 2012 - 07:53 AM, said:

And if they are not blank. why nothing inside?

This is going to be a loong thread (and it does not belong here, this is becoming "generic data recovery" and NOT 7200.11 specific), please start a new thread for it.

Basically *any* software tries to interpret "RAW" data (which is stored in the HD sectors).
If even a teeny-tiny byte is "wrong" some software may be unable to interpret the data (just as an example removing/altering the 55AA Magic Bytes makes from the MBR *any* Windows built-in tool to fail interpreting a whole disk).
Recovery software tries to detect the sectors or bytes missing/altered/whatever and tries to correct them and/or hints you about where to manually correct them.
Most recovery software is aimed to "basic disks" and not to "dynamic disks" (thus they can find "nothing inside").
You need a dedicated tool AND a more than basic knowledge of the layout.
From the screenshot it seems like DMDE finds that partition allright, but you need to study and learn BOTH about how a Dynamic disk is made AND about the specific tool usage, we are well beyond the "click-here-and-I-will-automagically-recover-all-files-approach" a number of "end user" recovery tools tend to adopt.

jaclaz

[Gradius2]

jaclaz, on 12 May 2012 - 04:15 AM, said:

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

The real option is backup, and you also need to check backup time after time.

I went for WD not Hitachi. Looks like Samsung is also a good (cheap) alternative.

Btw, the Seagate list with FW problem is:
Barracuda 7200.11
ST31000340AS
ST3750330AS
ST3750630AS
ST3640330AS
ST3640530AS
ST3500320AS
ST3500620AS
ST3500820AS
ST31500341AS
ST31000333AS
ST3640323AS
ST3640623AS
ST3320613AS
ST3320813AS
ST3160813AS

Barracuda ES.2 SATA
ST31000340NS
ST3750330NS
ST3500320NS
ST3250310NS
STM3320614AS
STM3160813AS

DiamondMax 22
STM31000340AS
STM3750330AS
STM31000334AS
STM3500320AS

SV35
ST31000340SV
ST3750330SV
ST3500320SV
ST3320410SV

I got a lot more apart of how/what HDD companies works/do, and I can tell you is a total prehistoric business.

They should unite and create an UNIVERSAL and up-to-date standard for HDD's firmwares. Just the algorithm would continue to be unique, but the way to access the drive and allows us a much easier way to recovery, diagnostic, etc any HDD would hundred fold (or even more).

S.M.A.R.T. is way too limited and not completely reliable.

Is time to change, specially when many of us know the real future is indeed SSD drivers, when they fail you can still easily read all the stuff there, just cannot write/erase/format anymore. The same will never happen with HDDs.