Gradius2

You can try Tera Term since you're using Vista.

Original: http://www.memtest86.com Better: http://www.memtest.org

Rev stands for Revision. I would say no problem [DataPattern] doesn't looks mandatory, just a comma (,) after 22 will do (example: 22,).

Yep.

Are you using this one: http://support.seagate.com/firmware/MooseD...D-8-16-32MB.ISO ?! If not, use it.

A nice review here: http://www.overclock3d.net/reviews.php?typ...aste_comparison Coollaboratory sells Liquid MetalPad now: http://www.coollaboratory.com/en/product_metalpad.shtml

Even so, did you tried to install? To me it installed w/o any "hack" on .inf

Very nice arguments, this recalls my old days on CBBS/BBS age back in 1985. Seagate boot-of-death analysis - nothing but overhyped FUD Of course that statement above is a BIG bad joke from Seagate or whatever the source is. To put the things simple to everyone the best proof is looking how many viewers we got on topics here related to Seagate's problems (aka 7200.11 syndrome). Now lets just do a simple google search, by entering: "Seagate 7200.11 failing": I got 72,100 links "Seagate 7200.11 fail": 98,100 links "Seagate 7200.11-failing": 371,000 links The bad thing is I don't know how many those links might be related to the same site, so I'll take everything divided by 4: If we take at least four drives are necessary for someone to write about this issue on the web (hence divided by 4), and at least 10 people will read that (because they have the same issue), and they all will have an average of 2 drives with problems, then we would have: 72,100/4*10*2 = 360,500 defective drives, until 371,000/4*10*2 = 1,855,000 drives (in rough math). Now, lets looks to those who knows the issues those drives are reporting: "Seagate 7200.11 bsy+error": 11,100 links "Seagate 7200.11 0+lba": 4,980 links 16,080 links, unfortunately we cannot apply the same "math" as above, since this is a bit different, few people would know relatively well the problem, and will try to fix the thing themselfs, I would estimate as low as 1% of them. So in best case scenario (for Seagate) they're just by x10 factor, and worst, by x100 factor. So 16,080 * 10 = 160,800 until 16,080 * 100 = 1,608,000. In both cases, it ultrapasses 1 million mark, coincidence? overhyped FUD they said? LAUGH!

Double check if the cable are good, w/o any short circuit, and correctly connected. For USB to Serial, you'll need a GOOD driver, I used this one: http://www.prolific.com.tw/eng/downloads.asp?ID=31 Uninstall the old driver first and try prolific driver. After installed, go to Device Manager, under Ports (COM & LPT), confirm your serial is there and config the port to 115200 8 N 1 (no flow control), and press OK. After all that, double check the cables and run hyperterminal (use NO echo) and try now with 38400 8 N 1 (create a new connection), after couple seconds, press CTRL+Z. About terminal you can use VT100, VT102, ANSI, etc.

Glad to see you managed to revive your drive. About the cache, yes that was discussed a lot, it seems Seagate used a very confuse scheme to manage 32MB. For 32MB they did, 0xFFFF + 1 * 512 = 33,554,432 = 32,768 (32MB). 0xFFFF + 1 should be 0x10000, but since they use 16-bit registry only, it goes back to 0x0000, this is why a LOT softwares will report those drives as 0 (zero) cache. Yes, $eagate did a very poor job here. So far the only program I know it will report the right cache size is Everest Ultimate Edition Cheers!

So far the new firmwares are "safe". But even if it rebricks your drive again, you can always unbricks using the method available here.

LOL, that's actually a pretty fat squirrel But i guess we'll never receive any feedback on the true numbers. I would estimate at least 1/3 of them will not bother at all and will just return the drives and getting replaced by another brand at first opportunity. Those will never post a thing or do a research about the problem. Real capacity is 1.81TB (formatted and ready for use). ATM they are very hard to find.

As you can see: "Then open Bootable_1.44M.img file with Power ISO, or Magic ISO, or Ultra ISO, similar, and extract SD1A3D4D.ZIP file inside."

"We will respond, promptly, to your email request with appropriate instructions." Big laugh at that ! I never got an answer from them, except that "automated" one. To me was 50%. 2 out of 4 failed on same day. They make ~10 millions HDD per month, the problem started around June until January 11. In other words, 7 months ! 10mil x 7 = 70 millions HDDs, lets say the half them are 7200.11, so we have 35 millions, if we keeps 50% defective (another half) = 17,5 millions. Now, let's estimate just 10% of 17,5 millions are unlucky and will have this problem so we have 1,75 millions HDDs, in other words, almost 2 millions worldwide I might said. 20,000 is too optimist in my opinion. This problem just wasn't bigger, because that "320 thing" is based by "luck".

Probably will not works, when you turn on the HDD, the firmware will read some bytes on service area and then report an error or not. It doesn't matter if HDD is attached to a PC or not, its a firmware thing. This is why when you disconnect the spin motor, you won't get an error (this happens on BSY errors) at start, so you just skip this stage by disconnecting the motor, and re-connecting after couple commands.

Nice to know you managed to fix it and is working perfectly now. Thanks for donating, it will helps with my hosting expenses, believe it or not, it will be the 1st one so far.

Are you sure you're using a RS232 to TTL adapter ?

Los comandos sirven para todos los discos Seagate de la familia 7200.11

Here: http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931

.exe is inside .ZIP file from .img !

Found the original post: About firmware, I'll just post here. They finally released a different (fixed?) firmware today for those drives: STD Firmware Updates Barracuda 7200.11 SD1A 3 and 4 Disc Models (750GB and 1000GB) Distribution tabs ST3750330AS 9BX156 ST3750630AS 9BX146 ST31000340AS 9BX158 Generic Disty/STD-OEM, 16MB and 32MB, SATA Configurations, Moose SHA1 comparing NEW with old firmware: c:Seagate>sha1sum SD1A3D4D.LOD SD1AMOOS.LOD b07e3a9ccf49185bc681f858c6ce568b45dd0ae5 SD1A3D4D.LOD (new) 268c6931e85936cfac3871c5baaee0c327186233 SD1AMOOS.LOD (old) This is what flash.bat does: fdl462b -m Moose -f SD1A3D4D.LOD -i ST3750330AS -s -x -b -v -a 20 fdl462b -m Moose -f SD1A3D4D.LOD -i ST3750630AS -s -x -b -v -a 20 fdl462b -m Moose -f SD1A3D4D.LOD -i ST31000340AS -s -x -b -v -a 20 I flashed all my 4x750GB, however 3 of them were with SD1AMOOS.LOD already installed, and I still don't know if it really re-flashed with new one. How to boot Seagate firmware from a pendrive. You'll just need a bootable pendrive (of course), with MS-DOS 6.22, or similar DOS. How to extract Seagate ISO: Open ISO with 7zip, extract the Bootable_1.44M.img file inside [bOOT] folder (inside the ISO). Then open Bootable_1.44M.img file with Power ISO, or Magic ISO, or Ultra ISO, similar, and extract SD1A3D4D.ZIP file inside. You only need to copy those files (unziped) to your bootable pendrive, and you're done to boot with pendrive. At prompt just type flash (flash.bat) and it will do the rest.

So you speak portuguese, gradius2??? Nice!!! Could you please take a look at my cables? The nokia dku-5 end has 3 wires. From trial and error, I found out that "blue" and "red" are TX and RX (by pressing some keys on hyperterminal), but I wonder what orange is for? When I linked orange with either of the other cables, nothing happened. I'm affraid that the two wires also might be touching each other on the seagate side, since sometimes I see the "invalid command" error (as if I were typing anything on the keyboard). -------------- Então você fala português? Que legal! Você poderia dar uma olhada nesta foto? Meu cabo nokia dku-5 tem três fios. Mas somente quando eu ligava o azul e o vermelho é que eu obtinha alguma resposta no hyperterminal (ao ficar pressionando uma tecla no teclado). Mas ainda não sei qual é a utilidade do cabo alaranjado. E os cabos do dku-5 são realmente bastante finos. Também acho que talvez os cabos estejam relando um no outro dentro do hd, pois às vezes eu recebo o erro "comando inválido". --------------- Many thanks for your kind help (muito obrigado pela ajuda). Well yes, english, spanish, portuguese and a little bit of japanese (sugoi!). Vc deve tomar muito cuidado, pois poderá provocar um curto-circuito e queimar os terminais do Seagate! Será necessário isolar os cabos da melhor maneira possível, se vc não tem nenhum pino fêmea, a melhor forma será soldando os cabos (com muito cuidado), no Seagate, e quando o problema estiver solucionado, basta desoldá-los.

Hola, Si el disco no te reconoce más en la BIOS, tiene el problema de BSY. Si el disco te aparece como 0MB entonces tiene el problema de 0 LBA. BSY quiere dicer BUSY (de pego), en este estado no hay ninguna respuesta del disco duro (ni en la BIOS). 0 LBA quiere dicer cuando el disco es reconocido pero como disco duro de 0MB !

Is just a simple terminal build-in on Seagate (not a modem).

Well, to setup the speed is simple: At level T: F3 T>Bnn Where nn is: - 1152 (for 115200) - 384 (38400) - 192 (19200) - 96 (9600) - 48 (4800) So for 9600 it would be: F3 T>B96 (enter) There are other speeds, but it will be dangerous since it would make the drive not accessible anymore (rare speeds on PC).