aviko

sure, just follow this link: (that link was posted by Gradius2) http://www.elektroda.pl/rtvforum/viewtopic.php?p=6012404

ok here is proof #1: http://www.msfn.org/board/index.php?showto...st&p=828590 look at the command: "m0 2,2,0,0,0,0,22" its a mistype there is SPACE intead of COMMA this is command which was initialy posted by Gradius2 and users got that errors, he fixed it already, thats why you dont see this mistype in first post. Wanna know how it happens? ok here is link to original text (in Polish): http://yura.projektas.lt/files/seagate/720011_ES21.html where command is correct but when you use google translate: http://translate.google.com/translate?prev...l=en&swap=1 site was changed since that day, it looks different after translation but ADDITIONAL SPACE still remains. proof #2: http://www.msfn.org/board/index.php?showto...mp;#entry828180 these credits was on this topic to but he removed them, haha he forgot about second copy where it is. Do you need more proof? I will find.

F3 T3>/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, connect disk to pc and check your data) fixed. "User Partition Format" its recalculate of translator that part of disk where user have his data. If you dont erased G-list data is untouched during this. clear enough?

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

bye

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 ?

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.

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

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.

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

driver to cable is properly installed? did you try to "loopback test" ? short RX and TX in your cable and try type something. are you sure that you choose 38400, n , 1 and no flow control? I saw something like you described but then also cpu consumpition was always 100% and the only way to stop it was to pull off cable from usb port. i tryed on another pc and it worked fine. Is it original nokia's CA-42 or clone? What you see in COM ports in device manager? Tell more details then someone will help ya

To dear mr Gradius2: I really dont want start an flamewar. When someone comming here and reads your first post, everything looks as you are autor of this solution. To be honest did you underestand what are you doing? No, you just grabbed all infos from Yura site and called him a thief. I cant forgive you that. How dare you? You make terrible mistakes when translating that site by google and you dont want to listen when we tryed to tell you what is wrong in "your tutorial". There are rare cases when problems can occur, but it happens. I sent PM to you, you ignored that. Its your choice. But people have right to know that you dont have any idea how this really works. Anyway there are many drives where terminal locks up. It will happen after do a power cycle, which was totally unnecessary at that moment and dangerous for drive. All these steps can be done without any power cycle between steps, but its necessary to do additional checks. Without, it can be a lottery and noone wants to gamble with own (or worse customers) data. What can i say? If anyone feels that I helped and want to make a donation? Sure, but not for me, send money to unicef, caritas or any other organization who really needs it. I dont want anyones money for helping here. I like my job and it makes me fun when I can help someone without any interest in it. As your tutorial is on first page, I really suggest you mr Gradius2 to review all steps and correct what is wrong with it. First, there is no any reason to clear G-list if it not contain errors, moreover it will destroy all content in sectors which was remapped. It will not visible just by checking content of directories and check few files for consistence. Second: power cycles are no need and are potentialy dangerous. Third: Touching any single screw on drive is not necessary too. Yes you dont need to take off pcb to do all steps. So ppl dont need torx screwdriver that you wanted to sell in kit. 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. When you read posts from yesterday you (maybe) will find out what else are wrong.

unless you connect sata connectors to mainboard/sata controller the only way where ground both psu meets is in your adapter connected to terminal. i think its not worth a risk. sure you can power it from pc psu. byt there is danger when you do power cycle power surge can turn off other disks in your pc for just a sec. it happens to me when i have much drives connected on same cable when I power on one of them, rest make a power reset too.

read PM

both. there is ground on pin 3 in terminal connector: You can solder a ground wire into back of jumper and put it as limit to 1,5gbits

it would be good if u will connect ground of adapter too, pin next to rx and tx. just for safety you should connect ground of both power suppiles together (black wire)

i am on a ST3500320AS with firmware SD1A (it is already updated, since it is my experimenting-drive, on which i try all out to see if it works BEFORE i use it on my RAID drive..... i typed only F .......... (removed) Close log which you pasted in [codebox] log put here [/codebox] if my drive is 'visible' for BIOS but with SIZE 0MB, then only the command 'm0,2,2,0,0,0,0,22' (Enter) is needed, right? no other command before this would be needed. i type this in T level (= F3 T>)? it should be enough. @edit I never tested that fixed firmware, it seems code is slight different. Only time can show us is these patches really works.

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.

I should be done. You can try spin down and spinup drive (from level 2>Z and then U) after it spins go back to T ( with /) then type F3 T>F712 i tried this on my TESTING DRIVE, since i will do all of this on my RAID drive after all possible 'pitfalls' are excluded. if i type: 'F712' i get this: =============================================================================== Byte:05A1: Expansion = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 '' F3 T> ============================================================================= which was the mistake in your last command? so would this be all ok? may i use the the 'path' of commands AS I WROTE in my last posting?? it seems that you testing on ES.2 (probably SN05) drive not on 7200.11, try just F without any numbers just 2 things: connect to terminal before you power up drive. second: - N1 (Enter) - / <- you need to go back into T> (you are on 1>) level before sending next command - m0,2,2,,,,,22 (Enter) >>>>>>>>>>>>>> User Partition Format Successful that should be all. If you have critical/sensitive/important data on your raid you really should consider visit in a professional DR company. Poland is not so far from you You were warned.

I should be done. You can try spin down and spinup drive (from level 2>Z and then U) after it spins go back to T ( with /) then type F3 T>F712 (as I remember its was 712 in 500g) it should be 4 parameters last one CONGEN READ FROM MEDIA, 1 means drive reads properly parameters from platters and its really good. If its 0 send command F3 T>/2 and then F3 2>x1 and paste results here if you not see CONGEN in F712 type F list will be long and CONGEN should be at position 716 @edit: I dont have any drive from this family here at this moment to check on myself these commands, so everything I told was from my head. Sometimes I could be wrong. I did a mistake in last command but Yura noticed me that. Now its fixed. I see many people reading this thread now. I have to say everyone case is a little different and have to be studied separatelly. I really dont have time to help all of you. If you decide to repeat steps that I wrote to all above, please dont be mad if it will not work for you. Thats why I really think it will be hard to develop universal solution which will work in ANY case.

It seems that you burned motor ic, Im almost sure that you connect motor when pcb was not stopped and gives voltage to motor. Thats why I told its was really stupid to disconnect it, you will not know when motor is powered and when not. Does drive making any sounds? (it can be really silent, just put ear on it and power on). Does drive says anything on terminal? Maybe something like this: Buzz Buzz Buzz if yes, it means that microprogram is trying to start motor but could not. Let me know.

I am working in well known data recovery company in Poland since last 6 years. I have no idea about Gradius2 profession. Who you will believe?

I am glad to be helpful. But the real credits belongs to okzo aka Yura, because everything I know about these drives, I know from him. And now? Who's real hero?

ok aviko, i am aware of this fact. but i guess only few of us with this problem understand native polish language..... therefore we follow(ed) Gradius2's version/solution. but now is seems that there are main differences, for example, u say to skip the 'i4,1,22' command, also the POWER OFF, waiting 10secs and then POWER ON of the drive, which Gradiu2 says wouls be 'very important'...... since most of us are newbies, who are not familiar with all these commands and their function, we are somewhat confused..... thanks cmburns because Gradius2 lost in translation information about it was only example how other tools work. this will be funny (Polish version of Yura's guide): Popatrzmy jak to robi pc3k -> which literally means: Let's look how pc3k doing this -> I hope everything is clear now.

ok lets start from scratch, try this: put some isolation under connector to heads (paper plastic etc.) motor have to be connected. power up drive. enter terminal, press ctrl+z. and this i am not sure, i havent any 7200.11 here to check, you have to try first try: wait until motor stops itself. then enter /2 and Z if you got message spin down completed remove isolation from pcb and mha connector (mha - magnetic heads assembly) screw on pcb to hdd. if you still dont get CC or CE its really good. now wake up drive with command U motor should be started and you should not get any error messages, otherwise you have to start again from begin. when drive spins up, go to level T (just enter /) now type F,,22 should appear message about restoring to defaults. then F3 t>/1 then F3 1>N1 if drive goes back to prompt ask for further instructions. (dont power off yet) ufff, I hope it will work