Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by dskbrk

  1. I hope you removed the isolation before giving U command...
  2. Hello I have 2 drives bricked : one 7200.11 and one ES.2 I tried to contact seagate for 10 days, and got anything but professional responses (I have a ton of seagates drives, those guys just don't want to keep their customers, one day they will pay for that). I've read all the stuff on that topic. The 2 solutions are nearly identical, but the differences are not only the ones you list : one isolates the heads, one the motor, and that is pretty much a difference. I just need a working solution, period. The aviko one, taking in account only the commands, seems to be less disruptive, but I really don't know which part should be isolated, motor or heads. It's impossible to get the truth between 2 people whose words to each other are insults and "you are all wrong". Why do they fight like that ? The only result of all this will be in people's mind : "DO NOT TRUST DATA RECOVERY COMPANIES, THEY'LL TRY TO FOOL YOU IN SAYING THAT THE COMPETITOR IS LYING". Right, i forgot that. I'm not a data recover professional, like all the people there, except Aviko who seems to be the only who work in data recovery field (for what I know). I only realized that seems there's more tecnology in hard drives than in Formula 1 cars. about isolating... This is all we know till now about that. You can do trial and errors, or ask for someone else opinion. you need the truth...well, just remember that this is a DIY solution on a public and not-professional forum. There's almost no fails still now but, of course, noone will take warranty of your drives. If you don't want accept any risk you have to go to professionals. period. Anyway, there're no data recovery companies in competition here.
  3. I think there's always voltage in it once the drivers are properly installed...but: It seems there are 2 type of nokia cables. One is self-powered thru USB, one needs an external 3.3v power to work. Usually, the latter has more wires (tx, rx, data gnd, 3.3v in, 3.3v gnd, and maybe other stuff). So, maybe you just need to connect a 3v battery to it. There is a great guide here that show you how identify and check your Nokia cable. I already posted this link so many times, I hope this would be the last one. Please take a look at older posts or do some searches, most of the common problems are already covered in this thread. Here're my own 2 general little advices: 1. Always double check your terminal connection before plug any wire to the Seagate drive. I see many people here connecting random wires from random cables they found in their drawers. Connecting a standard straight USB cable to your HD is not a good idea. 2. If you get strange characters in the terminal window after connecting the drive, be careful at what you type in it! In my first attemp to recover my drive I got only random characters because I didn't connected the ground wire on the drive third pin, but actually, what I was typing were sent to the drive. I tested it: I was able to spin off the motor (/2 & Z) even without see nothing readable in the terminal window... Be patient and good luck with the fix! I follow this soap opera since the first early posts at the original 7200.11 Falling down thread on seagate forums. So, chronologically: Till 16 January 2009 we were all lost and confused and angry and many other things, then Shuky posted this on elektroda.pl forum: http://www.elektroda.pl/rtvforum/viewtopic...6012404#6012404 As you can see there Nirvanowiec give him a link to: http://yura.projektas.lt/files/seagate/720011_ES2.html where, for the first time, were given a solution for fix the 7200.11 CC and BSY errors, by Yura. In that page (in Polish) there's no date, I think it was up since early January 2009. Then, one day later, 17 January 2009, Shuky alias Gsustek, posted the first solution in english, based on Yura's page above, in the hddguru forum. The thread was deleted and reposted two days later. In the google cache there's still the original one: I posted myself in that thread, as well as Aviko. (who also contacted me with a Pm for give help, I never answered him back, there was a bad mood there in that forum and many people were trying to misinform about those info. Still now some of them are doing that. Now I'm very sorry about it, Aviko, I was wrong. Thank you for that pm) So we arrived at 18 January 2009, when Gradius posted his solution on this thread (based on the Shuky (gsustek)' one posted the day before) also adding that aesthetically pleasant graphic with TX and RX legend instead of ugly ascii art (the pic with the drive and tx/rx arrows insted was first posted by fatlip in the previous '7200.11 Troubles' thread) and original credit links to Yura and Shuky post, now removed. So this are the fact by my point of view. Personally, I don't give a thing about donations or other stuff like that (actually, Gradius was and is very helpfull with many people and in many circumstances in this thread), I only think that should be right to give credit to people who saved us all. A noticeable thing is that, now, Gradius and Aviko solutions are quite the same. Don't be confused, the only difference is that Aviko removed the command i4,1,22 because, as he explained, it isn't essential and it can damage data on the drive in some cases. He also added other commands for testing purposes only (F712,F,,22). As you can see, this was a very long story. I really wish that there'll be a happy end now. We recovered out data, other people will recover their drive with this thread and this is really beautiful. So, make love not war Happy fixing!
  4. Yura was the one who gave us the solution we're talking about in this thread. period. come on, pichi and fatlip...you already did it, but some people seem to not understand, tell them who is the one who save our data. He deserves it.
  5. I have to agree at some part. Yura was the first and only one who revealed the top secret command we were all hard looking for fix out our dead drives, the (now) well known m0,2,2,,,,,22. Yep, he is the HERO! And don't misunderstand me, please. Then Shuky, as gsustek, re-posted the solution on the hddguru forum, and I remember I was more happy to see some people there going on business panic than to found finally a solution for my data lost. (If their business was built on a secret command, how trust them as professional people who do critical/important data recovery?) After, Gradius2 made this thread with his well written tutorial. Top Kudos go to Fatlip and pichi for their hard work, since their early posts at seagate forums (yeah, before censorships and bans), top kudos go to Gradius for his great translation work and his help here in the forum, and kudos go to everyone helped in any way to solve this. It's a long story and it's a beautiful story after all. We came here angry and so restless for our data. Then, post after post, we figured it out. We win. Seagate people admitted their fault (and now they have to deal with it). We had our data back and now we're helping people to solve problems that were our problem till yesterday. So, I see an happy end here. Yep, this is my point of view of the whole story.
  6. People, as I said before, you all should always do a sanity check on your connection before connect any wire to the Seagate hard drive! Actually, trying connecting random cables you found in your drawers may damage permanently your USB port or your hard drive! So be safe! By now, as I can remember, the right phone cables used for the fix were Nokia DKU-5, CA-42 and CA-45. I remember Shuky also used a cable for Siemens 35 series but I don't know the exact model. Usually, phone cables with built-in serial converter have a longer USB plug. Other than phone cables, there's a plenty of adapters of any kind here that will work for the fix. Just read carefully this thread, I'm sure almost all the info you need are already here.
  7. oh well, i didn't noticed that.. CA-53. If you checked one of the links in my previous post above you'ld already know that: Now I just wonder how your system can't recognize a straight, generic usb data cable...
  8. You should install the drivers that come with it. Note that for most clone cables there'are no Vista drivers. Your previously quote from other forum were about some linux commands, but yep, right pop-port pin are 6 (RX), 7 (TX) e 8 (GND, if you need to use it). You all should always check your connection before connect any wire to the seagate drive. Be safe!
  9. no one knows, colors are not standard. A continuity tester/voltmeter and this link will help you. Good info about indentifing wires and checking the connection is here. If you don't have a continuity tester/voltemeter i posted a very rogh test for indentify each wire here. Be careful and use at your own risk! good luck! PS: for all the people who feel uncomfortable with wires, volts and terminal windows, always remember that seagate seems to offer free data recovery for 7200.11.
  10. Tokuro, you're right too. 3.3v is already in RX/GND and TX/GND. With a little help of a volt meter you can find the ground: connecting the negative pole to the ground wire and the positive to RX or TX you will see that 3.3 voltage in the meter. Once you set up your terminal session, by typing some random chars in the terminal you'll see in the meter that voltage slighty go up or down in the TX line, the other one should stay fixed on 3.3v. With this you can find RX and TX wire too and then you're done, connect TX and RX to the HD and if you don't share a common ground (if you use your notebook for the usb plug and another PSU for powering the HD) connect the ground wire on the HD pin 2 as showed on one of my previous posts. My cable had 6 wires and the right ones were white (GND), yellow (TX) and blue (RX) but sadly there're no standard colors. If you don't have a volt meter, you can also do a very rough test. Set up your terminal session and slightly let touch 2 wires at once. If you see come up strange characters in your terminal window, then you have in your hands RX and GND wires. Then, type random characters in your terminal and do the same with the other wire and when you'll see what you type come back in your terminal window it just means you connected RX and TX togheter (a loopback connection!!). Do some trial and error and don't be hurry! Good luck! It's the same -nameless- brand i bought! The only thing is that mine was CA-42, this is CA-45. I cannot be sure, but I think the only difference is in the phone plug model, the long usb connector seems to be the same as mine. Inside it there's a chinese USB to Serial Arkmicron chip. Note that for those chips there're no Vista drivers, XP only. You may also check on pinouts.ru website for be sure it has TX/RX/3.3v. Well, I've just chopped it off. And it has 3 cables: Black, Red and White. You were right: it installs as "Arkmicro USB to SERIAL" in my XP notebook. You were also right: my vista PC won't install it. (no drivers) You were right too: It is a long USB connector identical as the one seen in the CA-42 and DKU-5 pictures on the net. But... are you sure I've to check if one of the 3 cables is 3.3V???? I was assuming that the 3 cables were for TX, RX and GROUND. Am I wrong??? Greets, ToKuRo.
  11. It's the same -nameless- brand i bought! The only thing is that mine was CA-42, this is CA-45. I cannot be sure, but I think the only difference is in the phone plug model, the long usb connector seems to be the same as mine. Inside it there's a chinese USB to Serial Arkmicron chip. Note that for those chips there're no Vista drivers, XP only. You may also check on pinouts.ru website for be sure it has TX/RX/3.3v.
  12. hello guys, I'm just writing from my ex-bsy-death 7200.11!!! (i'm gonna cry, i missed my data so much! ) I used a cheap CA-42 data cable clone for Nokia phones, bought on ebay (4€). I think it's the best deal because it's already self-powered by the USB and uses a nice 3.3 voltage (i tested it with a volt meter). You can find very useful info about pins and terminal checks here. I had only one problem: after connecting TX and RX cables i got only a few garbage characters in my terminal window. I figured out connecting a third wire to the HD, the ground! In this way: [ 1 2 3 4 ] [sata] [power] -> [1=none] [2=GND from USB cable] [3=TX from USB] [4=RX from USB] I think i needed that because my usb cable was plugged in my netbook while the power plug was from the main computer PSU. I don't know exactly but, anyway, it worked flawless! Hope this can help someone! many thanks to everyone who contribuited to make that possible, except Seagate peremptorily censorship and some (very kindly and professional, you should say) people at hddguru forum. i have to go, it's backup time now!!
  13. SO, is there anyone who successfull recovered a drive that had more than one partition? My busy drive is divided into 3 NFTS partitions and i'm a bit worried about doing the fix right now. Most of the important data is in the extended third one.
  14. Question: when you say 'POWER OFF/ON' you mean to unplug and replug the ALI molex from the HD PCB? or turn off the pc? Should be the molex already on the HD PCB when you connect to the HD via terminal?
  15. look at the traslated chinese page, there are interesting things! They say that the terminal connection is only needed to unlock BSY state, while for the 0gb LBA problem can be fixed using only the sata connection. It says to connect the drive thought a IDE->SATA adaptor, maybe for bypass some locks, there are also two parameters (170,376) wich I can't understand. But this let me think that the 0GB LBA issue can be solved by sending ATA commands to the drive. In the 7200.11 spec docs from Seagate website there's a list of supported ATA commands (see section 4.3): http://www.seagate.com/staticfiles/support.../100507013c.pdf
  16. What do you think if I'll put a good 7200.11 into sleep in Windows, after the boot. Then swap the pcb on the faulty one and wake up it again? (the second question is: am I becoming delirious? )
  17. Can anyone give a confirmation on the validity of these commands? Pichi perhaps? Seems to be just a list of diagnostic commands for Seagate drives, like the ones located here: http://files.hddguru.com/download/Datashee...0RS-232%20Port/ (already posted many posts ago, i think) The problem is still to know exactly which of these commands will unlock the drives from 0gb LBA.
  18. Seagate to lay off 10 percent and replace CEO Bill Watkins
  19. I agree. What about to open a blog on the issue? While users here work to find a technical solution, we can make a page (or a post) with the dead list and people will be able to add their hd info by comments. Also, a website entirely focused on the issue may receive more media attention. If anyone is interested in this, feel free to PM me.
  20. i'm updating my info with my country (Italy) and disk type (OEM). I have other 3 500gb Seagate 7200.11 SD15, i'm going to throw them in the WC. One of the worst investments i made. A big loss of data, time and money. As Blichev said, try to create links to this thread on blogs, other forums, everywhere. This will help to spread the problem and improve visibility on google searches. Also, if you use social sites like delicious or digg, add a link there too. This may help too. No Seagate lawyer can stop this. LIST UPDATED. Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User ==================================================================================================== ========== 01:9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:OEM:poolcarpet:Malaysia 02:9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:-:DaftMule:United Kingdom 03:9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:-:DerSnoezie:Netherlands (no detect in bios) 04:9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:OEM:dskbrk:Italy (no detect in bios) 05:9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:OEM:ToKuRo:Chile (no detect in bios) 06:9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:-:jeroen__online:Netherlands 07:9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:-:quattro150:Malaysia 08:9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:-:Nichev 09:9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:-:PrOdiGy1:UK 10:9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:-:AVINNC:USA 11:9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:-:Ruddrage:UK 12:9QM6354J:ST3500820AS:9BX134-505:SD15:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:-:rainshower:Germany 13:9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:-:fabio.cillo:Italy 14:9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:-:Death_Angel:Malaysia 15:9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:-:Taiketo 16:5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:-:Styleman 17:9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:-:roadstarter:Philippines 18:9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:-:labraticmp3:USA 19:9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:-:eli2k 20:9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:-:poim76 21:9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:-:caba212:Spain 22:9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:-:GrayGhost:USA 23:9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09:-:timha 24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:-:viniciusferrao:Brazil 25:9QM60864:ST3500320AS:9BX154-303:SD15:09076:KRATSG:31 October 2008:Dec 2008:-:RiderZen:Australia (BSY) 26:9QJ0W41R:ST31000340AS:9BX158-335:SD15:08457 (16/May/2008):KRATSG:Jul2008:20Dec2008:-:Macprk:USA 27:9QM5V5HQ:ST3500320AS:9BX154-303:SD15:09071:KRATSG:(04/Nov/08):(09/Jan/09):-:BigSilverHotdog:USA 28:9QM2C4LT:ST3500320AS:9BX154-303:SD15:08382(??):KRATSG:Aug2008:1Jan2009:-:Keddar:USA 29:5QM1EYCG:ST3500320AS:9BX154-303:SD15:08383:WUXISG:jUL2008:02Jan2009:-:waly2k1:Argentina (no detect in bios). 30:9QM5RCNT:ST3500320AS:9BX154-303:SD15:09063:KRATSG:JUL2008:25DEC2008:-:criverock:Italy (no detect in bios). 31:9QM*****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:Oct2008:20Dec2008:-:sarahcoco:France 32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104 (10/Oct/2008):KRATSG:3Jan2009:-:artpav:Canada 33:9QM*****:ST3500320AS:9BX154-303:SD15:08371 (15/Mar/2008):KRATSG:7May2008:29Dec2008:-:KillerB :Korea (no detect in bios) 34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:WUXISG:CHINA:August2008:Dec24th08:-:Fuzzy_3D:Canada
  21. Ironically, i read Speedfan values (and ran an in-depth online analisys too) just a few days before my 7200.11 died. Every value was ok. The angriest part in this story is that those drives may leave you randomly between one boot and another. With no early symptom. For those who still have a Seagate 7200.11 running I strongly suggest to place your data somewhere safe as soon as you can. Seriously, even if your drive is running fast and fine.
  22. here's mine, bought in late August and broken down in early November 2008. Product of Thailand. 9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146:KRATSG:Oct2008:24Dec2008:poolcarpet 9QM6X90B:ST3500320AS:9BX154-303:SD15:09115:KRATSG:Oct2008:28Dec2008:DaftMule 9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie 9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503:KRATSG:Aug2008:Nov2008:dskbrk
  23. Hi all, please check also the barracuda 7200.11 spec docs from seagate. Take a look at page 32, it says: "This command controls the implementation of various features that the drive supports. When the drive receives this command, it sets BSY, checks the contents of the Features register, clears BSY and generates an interrupt." It talks about the hd "supported ATA commands". No idea of what ata commands are and if this can help. I just hope so.
  24. As other members, i got deleted my posts from the closed thread on seagate forum. Now i'm here too. while hoping to find a solution, i'ld suggest to save the closed thread on delicious and other bookmark service, tagging it with something like shame on seagate.
  • Create New...