[aviko]

Gradius2, on Jan 19 2009, 11:19 PM, said:

kadolf, on Jan 19 2009, 03:09 PM, said:

I tried the 0 LBA fix (HDD is recognized by BIOS, but as 0MB), but it doesn't seem to work:
When I input "m0 2,2,0,0,0,0,22" it takes a few seconds until the first line ("Max Wr Retries"...) shows up completly but then appears the following error message:

Error 1008 DETSEC 0000500D
User Partition Format Failed - Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 00000084, File Error 00001002
Blk Addr 01080001, Blk Addr Type D0, Cyl 01590000, Hd 00

Anyone experienced the same or can help?
EDIT: Interface is a modified Sagem data-cable with SP232AET-chipset (equal to MAX232), but this interface seems to work as it gets an answer.

This might be caused for something more severe problem on drive.

The drive just went into 0 LBA error after a reboot? After that, you didn't tried anything else (like trying to upgrade the firmware, etc) ?

F3 T>m0,2,2,0,0,0,0,22

m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertifyTrkRewrites],[ValidKey]

Partition: 0
FormatOpts: 2
DefectListOpts: 2
MaxWrRetryCnt: 0
MaxRdRetryCnt: 0
MaxEccTLevel: 0
MaxCertifyTrkRewrites: 0
ValidKey: 22

Try this:
F3 T>m0,1,1,0,0,0,0,22

If no good, try:
F3 T>m0,1,1,2,2,0,0,22

If success, try this again:
F3 T>m0,2,2,0,0,0,0,22

It can takes as slow as 30 to 120 secs to get something on terminal.

Gradius

I am seriously terrified. Your irresponsibility and incompetence has no end. You recommend him try these command, did you ever know what it means? Kadolf was extremely lucky, his terminal wasnt work correctly and these commands wasnt executed.

Just look what it does:

F3 T>m0,1,1,2,2,0,0,22					  
Max Wr Retries = 02, Max Rd Retries = 02, Max ECC T-Level = 00, Max Certify Rewr																				
ite Retries = 0000				  
User Partition Format   0% complete, Zone 00, Pass 00, LBA 001061F7, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 002120B3, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 0031DF6F, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00429E2B, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00536553, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00642C7B, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 0074E2CB, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 0085A9F3, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 009668AF, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00A7276B, ErrCode C40
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00B7E627, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00C8AD4F, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00D97477, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00EA3B9F, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 00FB02C7, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 010BC183, ErrCode 000
User Partition Format   0% complete, Zone 00, Pass 00, LBA 011C803F, ErrCode 000
User Partition Format   1% complete, Zone 00, Pass 00, LBA 012D4767, ErrCode 000
User Partition Format   1% complete, Zone 00, Pass 00, LBA 013E16FB, ErrCode 000
User Partition Format   1% complete, Zone 00, Pass 00, LBA 014ED5B7, ErrCode C40

process was cancelled....

it lasted 120 seconds, data from 0-120000000 sectors was irreversibly destroyed, more after breaking format both defect lists are destroyed and unusable so you cannot recalculate proper translator anymore.

Dear Mr Gradius2, please dont make a specialist from yourself. Your advices could be catastrofic for someone. Dont test commands on innocent people who came here for help with their losted data.

You invented nothing, just copy and paste someones hard work and research. I can proove this many many times. For example this user tryed to enter improper command which he found here and which was with SAME error on source page. I mean "m0 2,2,0,0,0,0,22" space instead of comma, coincidence?

I promised myself that I will not make war against you but after saw your experiments on innocent users I just cant leave it.

[aviko]

alexx86, on Feb 3 2009, 11:33 AM, said:

aviko, on Feb 3 2009, 11:25 AM, said:

first of all, check terminal with shorting tx and rx together you should see what you type. i posted this information few times. and not only me.
tell model f/w and p/nof your disk.
do you have any older series of seagate disks? pcb from it is enough, if yes, connect it as in photo few pages ago and set terminal to 9600, then you will be 100% sure that everything is in place and working

I have fw SD1A and the model is 3500320AS. Okey I will try shortcircuit RX and TX, why 9600, in the main post it says 38400?

9600 was for for older series, 7200.7 .8 .9 .10 , 38400 is for .11

If you have any old seagate set terminal to 9600 and try with older one. There wasnt any issues with terminal so if you can communicate with old one, you will be sure that terminal is working, of course to work with .11 you have to set baud back to 38400

[htpc]

aviko, on Feb 2 2009, 04:37 PM, said:

htpc, on Feb 2 2009, 10:31 PM, said:

aviko, from your experience is it safe to swap pcbs and run the firmware for those of us who are not good with electronics/coding?

If you mean 7200.11/ES.2/Diamondmax22 series it will not work. Connect only pcb without hda to pc and recognize it in bios or any other software. there will be capacity 0mb but serial number should be visible. What is that mean? It means that individual for any single hdd data are stored on its own pcb. Unless you do some work (sorry i cant tell you in simple words how exactly you need to do) it will not work. Use your brain/google/help someone and consider do you really have experience and proper tools to do that.

@edit:

as I underestand you mean swap pcb from another hdd right? Or by swapping you mean removing its own and put back together due all above steps in solution.

avico,

Sorry I was not clear at all. I will try again.
I have two drives ST31000340AS, lets call them A + B.
A is good and updated to firmware SD1A.
B has SD15 but cannot be seen in BIOS, hd light is constantly on.

Can I take pcb from B put it on A, flash the drive to SD1A, then put the pcb back to B.
Will this work without damage to both hardware and data?

[mikesw]

Now that everyone is getting pretty good at fixing Seagate drives.
Seagate will have a 2TB drive in the 3rd quarter of 2009. (this could need fixing too! )

see,

http://www.techrepor...ussions.x/16343

seagate press release.
http://www.seagate.com/ww/v/index.jsp?loca...000f5ee0a0aRCRD

Here's a reviewers comment on it which they supplied before they were asked!

Quote

To establish prior art for this joke - 'I know why it's named Constellation, I was so mad when my drive died I saw stars .'

Here's a comment on that review site that I didn't know about and perhaps others didn't either.

Quote

The MBR is limited to a maximum partition size of 2TB, and while the GPT removes that limitation it isn't implemented in BIOS but rather in EFI. I'm sure a hack is forthcoming once single drives exceed 2TB, a la the previous limit.

Thus, should the drive manufacturers make drives bigger than 2TB, one will have to split the drive into partitions
that don't exceed 2TB each.

GUID Partition Table (GPT) per Msoft site when one searches it for "GPT drive".
http://www.microsoft...GPT-on-x64.mspx

Quote

Because the x64 and x86 architectures do not provide support for an EFI boot partition, you cannot use a GPT drive to boot an x64-based computer or an x86-based computer with a legacy BIOS. Therefore, computers running these operating systems must be equipped with more than one physical driver to allow the use of the GPT disk format.

Looks like windowx X64 can do this but not x32. Can someone confirm this since I don't have x64 OS. and VISTA.
Windows 7?????

http://www.microsoft...ge/GPT_FAQ.mspx

Extensible Firmware Interface (EFI). where's the firmware? Intel has the spec on this.
4. Where can I find the specification for GPT disk partitioning?
Chapter 16 of the Extensible Firmware Interface (EFI) specification defines the GPT format.
This document is available at http://www.Intel.com/technology/efi/

More from the GPT FAQS.

Quote

13. Can Windows XP x64 read, write, and boot from GPT disks?
Windows XP x64 edition can use GPT disks for data only. Only Windows for Itanium-based systems can boot from GPT partitions.

14. Can the 32-bit version of Windows XP read, write, and boot from GPT disks?
No. The 32-bit version will see only the Protective MBR. The EE partition will not be mounted or otherwise exposed to application software.

15. Can the 32-bit versions of Windows Server 2003 read, write, and boot from GPT disks?
All versions of Windows 2003 since Server Pack 1 can use GPT partitioned disks for data. Booting is only supported for Itanium-based systems.

16. Can Windows Vista and Windows Server 2008 read, write, and boot from GPT disks?
Yes, all versions can use GPT partitioned disks for data. Booting is only supported for EFI-based systems.

17. Can Windows 2000, Windows NT 4, or Windows 95/98 read, write, and boot from GPT?
No. Again, legacy software will see only the Protective MBR.

18. What about mixing and matching GPT and MBR disks on the same system?
GPT and MBR disks can be mixed on systems that support GPT, as described earlier the following restrictions apply:

• Systems that support EFI require that the boot partition must reside on a GPT disk. Other hard disks can be either MBR or GPT.

• Both MBR and GPT disks can be present in a single dynamic disk group. Volume sets can span both MBR and GPT disks. However, the MBR cylinder alignment restriction might cause some difficulties mirroring or striping MBR and GPT disks.


19. What about removable media?
Removable media must be MBR or "superfloppy."

What about Virtual Disks that are formatted with GPT and Virtual OS'?

More UEFI aka EFI at,
www.uefi.org
tiianocore.org

Here is a link from intel to MSOFT UEFI tools.
http://www.intel.com...il_overview.htm

The following Disk Utilities are available:

Diskpart EFI GPT Disk Partitioning Tool
Efichk EFI Check Disk Utility
Efifmt EFI Format Utility



Darn...

This post has been edited by mikesw: 03 February 2009 - 09:46 AM

[my77stang]

aviko,

If you are so unhappy with the guide that was originally laid out PLEASE give us a list of commands you recommend to safely fix our drives. I have the BSY error, and should be getting my cell phone cable any day. I want to make sure I do not loose all my data.

Thanks

[enrolb]

I would like to say thanks to Gradius2 and I know there were others that first decided and then provided a solution to "debrick" our drives. Seagate has been more arragont than anyone on this forum, as they knew about the issue, knew who could have the problem (if one registered), knew how it could be stopped until solution (leave drive running), and been a lot more understanding of those who had a "bricked" drive.

In defence of Gradius2 and others who, if they hadn't pursued the simple solution to this problem, we might never have known how really simple the problem is to solve. Instead we all would have had to pay big dollars to data recovery companies for something they could fix in 15 minutes. I for one was quoted a cost of $500 for fixing my drive and I know some probably would have had to pay a lot more.

Its interesting how the "data recovery people" are jumping into the forums since a solution has been posted. Why did't they try to help from the start!

Anyway I don't want to start a flame war again. Now I do see merit in what Aviko is saying about powering down/up PCB during the fix that issues could occur. I concur with a previous post that Aviko, if you have a better safer solution to fixing these drives then post your solution in full and let the users decide which one they want to use... Then there can be Kudos to both!

[aviko]

enrolb, on Feb 3 2009, 03:27 PM, said:

I would like to say thanks to Gradius2 and I know there were others that first decided and then provided a solution to "debrick" our drives. Seagate has been more arragont than anyone on this forum, as they knew about the issue, knew who could have the problem (if one registered), knew how it could be stopped until solution (leave drive running), and been a lot more understanding of those who had a "bricked" drive.

In defence of Gradius2 and others who, if they hadn't pursued the simple solution to this problem, we might never have known how really simple the problem is to solve. Instead we all would have had to pay big dollars to data recovery companies for something they could fix in 15 minutes. I for one was quoted a cost of $500 for fixing my drive and I know some probably would have had to pay a lot more.

Its interesting how the "data recovery people" are jumping into the forums since a solution has been posted. Why did't they try to help from the start!

Anyway I don't want to start a flame war again. Now I do see merit in what Aviko is saying about powering down/up PCB during the fix that issues could occur. I concur with a previous post that Aviko, if you have a better safer solution to fixing these drives then post your solution in full and let the users decide which one they want to use... Then there can be Kudos to both!

you are wrong. Gradius2 didnt provide anything.

ok, as you wish

Drive is busy example, not solution: drive ST3500320AS SD15

remove 3 screws nearest heads connector, motor connected, put something between pcb and hda to lift pcb and prevent contact.

power on, wait until drive stops motor


(ctrl+z)

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.146 msecs 

[color="#FF0000"]ADDED: Now its time to put pcb back to hdd and install it.[/color]

F3 2>U

Spin Up Complete
Elapsed Time 6.864 secs 

this part is not necessary, use when firts try fails

F3 2>/

F3 T>F712
Byte:0712:	   RealTimeUpdatedFlags = 00 00
Byte:0712:		   Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712:		   Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712:		   Bit:2, DCO_SET_ACTIVE = 0
Byte:0712:		   Bit:3, CONGEN_READ_FROM_MEDIA = 0	   <- configuration not loaded from surface

F3 T>F,,22
 
Drive Configuration restored to defaults.

F3 T>F712
Byte:0712:	   RealTimeUpdatedFlags = 08 00
Byte:0712:		   Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712:		   Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712:		   Bit:2, DCO_SET_ACTIVE = 0
Byte:0712:		   Bit:3, CONGEN_READ_FROM_MEDIA = 1	   <- done

(end of part to skip at first attempt)

F3 T>/1

F3 1>N1

F3 1>/

F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs		
User Partition Format Successful - Elapsed Time 0 mins 05 secs		

F3 T>	  

(finished, power off)

happy now?



@edit: added missed step to install pcb back on drive.

This post has been edited by aviko: 04 February 2009 - 10:54 PM

[aviko]

htpc, on Feb 3 2009, 01:42 PM, said:

Sorry I was not clear at all. I will try again.
I have two drives ST31000340AS, lets call them A + B.
A is good and updated to firmware SD1A.
B has SD15 but cannot be seen in BIOS, hd light is constantly on.

Can I take pcb from B put it on A, flash the drive to SD1A, then put the pcb back to B.
Will this work without damage to both hardware and data?

it makes no sense,
1. update firmware is not only on pcb
2. drive A will not work with pcb from B
3. firmware update will not fix bsy and cap. 0 problem

why cant you fix drive B ?

[puma34]

Hi

I rescued my data

My priceless thanks ($30 ) go to Gradius2 and all the people who made his tutorial possible


Now mister aviko

Do you think you have contributed anything useful up till now?

Personally I wouldn't dare to follow any of your instructions

Besides I comprehend only half of what you are saying


Is there any moderator who can rescue this thread by showing 'someone' the door - give him his own thread or something

puma34

[aviko]

puma34, on Feb 3 2009, 04:06 PM, said:

Hi

I rescued my data

My priceless thanks ($30 ) go to Gradius2 and all the people who made his tutorial possible


Now mister aviko

Do you think you have contributed anything useful up till now?

Personally I wouldn't dare to follow any of your instructions

Besides I comprehend only half of what you are saying


Is there any moderator who can rescue this thread by showing 'someone' the door - give him his own thread or something

puma34

bye

[Gradius2]

aviko, on Feb 2 2009, 11:28 PM, said:

Fourth: making unnecessary double signal conversion is a potentialy source of problems: from USB (which is +5V) to RS232 levels (which are -12V to +12V) and back to TTL levels (+5V) which btw is a little too much but noone fried his drive due that.

I'll only talk about this part, is the only one "interesting".

Valid signals are plus or minus 3 to 15 volts for RS232.

From wiki:
A common deviation from the standard was to drive the signals at a reduced voltage: the standard requires the transmitter to use +12V and -12V, but requires the receiver to distinguish voltages as low as +3V and -3V. Some manufacturers therefore built transmitters that supplied +5V and -5V and labeled them as "RS-232 compatible."

Many adapters also includes an Optocoupler inside on IC or component.

This is my last reply for aviko, if you want to continue this flamewar, go to a place like youtube and start putting comments on any video there, I bet you'll get a lot more fun there.

[spankerer]

Hi all,

I finally managed to revive my HDD with the Nokia CA-42/DKU-5 cable.

To whomever it was who came up with the steps to recover the HDD, you have my heartfelt gratitude, whether it be gradius or the dudes at Ace Labs or the HDD Doctor dudes. Without the instructions, I would not have been able to revive the HDD, without gradius I'd still be searching (and waiting) for a working solution.

Thank you, my data was worth far more than a crummy Seagate HDD

[Gradius2]

Well guys, I have bad news for those who just did an update from (for example) SD15 to SD1A, when the drive didn't showed any 0 LBA or BSY symptom.

I'll open a new topic talking about it.

Edit: ok here is: http://www.msfn.org/...howtopic=129459

This post has been edited by Gradius2: 03 February 2009 - 10:36 AM

[my77stang]

im so confused, i dont know which procedure to use

[alexx86]

Hi again,

Now i've tried the loopback test so my setup is correct.
I dont get any response from the terminal, I dont get "F3 T>", but i can type..

I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?

Anyone that can help me? Over msn maybe?

I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.

[Gradius2]

yura's_friend, on Feb 3 2009, 02:03 PM, said:

@my77stang:
Yura is well known data recovery researcher, aviko works in data recovery company and posted yura's solution. The original solution was given into public domain in Polish, gradius is from Chile - do you think he understand Polish better then aviko? I don't think so. He used translator to make his 'help topic' - just for profit as we see now (gradius registerd puma34 account just to force people to pay more and discredit aviko - which is even more unfair than stealing somebody's work).

Me? for profit? registered puma34? LOL !!!

You guys are too funny.

Nice try aviko's clone.

This post has been edited by Gradius2: 03 February 2009 - 11:36 AM

[Gradius2]

alexx86, on Feb 3 2009, 02:14 PM, said:

Hi again,

Now i've tried the loopback test so my setup is correct.
I dont get any response from the terminal, I dont get "F3 T>", but i can type..

I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?

Anyone that can help me? Over msn maybe?

I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.

Turn off all, remove the PCB from HDA, power on, then try CTRL+Z.

[aviko]

my77stang, on Feb 3 2009, 05:48 PM, said:

im so confused, i dont know which procedure to use

dont be confused, method is same, i just removed all steps which is potentialy dangerous for data.

[Laz]

yura's_friend, on Feb 3 2009, 12:03 PM, said:

@my77stang:
Yura is well known data recovery researcher, aviko works in data recovery company and posted yura's solution. The original solution was given into public domain in Polish, gradius is from Chile - do you think he understand Polish better then aviko? I don't think so. He used translator to make his 'help topic' - just for profit as we see now (gradius registerd puma34 account just to force people to pay more and discredit aviko - which is even more unfair than stealing somebody's work).
Use aviko's step-by-step solution. We know what we're talking about - we fix these drives on a daily basis.

One thing there; you seem intent on flaming the fellow who helped us here. The 1st post here was by gradius2 who detailed the items required and proceedure that I used to bring my hdd back. Where were you ? I come back here to say thanks and perhaps see if there are any people who may need some help and find half your posts flaming the one fellow who helped here. That is not very nice. Stop your war, you are too late. I am sure your friends will have enough business to fill their pockets many times over because of the issue with the seagate 7200.11 hard drives. Perhaps you could start your own thread here detailling your way of helping people, because you seem to be cluttering up the thread here. OK ? bye.