breadbin

Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About breadbin

Contact Methods

  • Website URL
    http://
  1. don't know if this thread will help you, its specifically to do with a busy error on some drives with a certain version of firmware. i have a drive too thats not recognised in the bios but even though its the same as these drives in here its a different problem to the "busy" error. i don't know how to determine it the drive is busy or not so try and find that out first. or see if there are other problems with your model on the net.
  2. pm'ed you - great video btw and love the music in it. Should i be able to hear my hard disk if i have the busy error? I held it to my ear and couldn't hear or feel any vibration when i powered on the computer. also one of the chips on the pcb got very very hot is that normal? the seatools for DOS didn't detect the drive either. but there is definitely no noise coming from it:(
  3. does anyone know is the SD35 firmware dodgy too? i searched this thread and no definite answer, i'm assuming not seeing as they would have had time to fix the problems since SD15 but not sure. my drive is not recognised by bios and is ST3750330AS 750Gb SD35. just wondering if it could have the busy error or something else. seagate link says no - not affected but still not seen by bios.
  4. There are a lot of misunderstandings going on on this topic, your question may be the occasion to attempt clearing some of them. This thread and the nice page by CarterinCanada: http://www.msfn.org/board/index.php?showto...807&st=1232 http://www.mapleleafmountain.com/seagatebrick.html and various similar hints/guides linked to or various information posted on the present thread, are aimed to recover or "debrick" a specific Seagate series drive suffering from the problem initially explained in this same thread (links given in this post): http://www.msfn.org/board/index.php?showto...807&st=1589 THIS problem may appear with two different symptoms: 0 LBA or BSY state. There may be tens or maybe hundreds of different problems leading to the same symptoms. Moreover several people with a failed or failing drive come here thinking this represents a miracle cure for any desease. (even if Symptoms are different) It is NOT. There are NO reports of drives suffering from THIS problem, to which THESE remedies were PROPERLY applied, using PROPER interfaces/cabling/power supplies, PROPERLY connected, which were not fully and integrally recovered. There is NO rational reason to presume that once THIS problem has been resolved and the PROPER firmware upgrade has been applied, the drive is not anymore dependable: it is EXACTLY as DEPENDABLE as any other Seagate Hard disk of the same series that was NOT affected by the problem. Whether this particular series of drive is more or less dependable than series X of manufacturer Y is higly debatable, there are NO publicly available extensive studies in this direction, and anyway by the time (exception made for early failures) the data would be available, a new (or more than one) series will be available and common, both from Seagate and from manufacturer Y. Borrowing the words Peter Gutmann used to describe the misunderstandings about his reknown paper: http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html this thread and the info within it has been sometimes interpreted/used more as: If the problem is THIS one, the "cure" does work, if the problem is not exactly THIS one, who knows? jaclaz so is there a surefire way of finding out if this is my problem. it seems sort of suss that my hd just happens to be same firmware and drive model, serial no's as everybody else here. i tried victoria, did a pci scan and clicked on the drive and got an error. don't think the busy light was on though:( what i am wondering though should i be able to hear or feel the hard disk working when i plug it in? even for a few seconds? just gonna read some of them links you posted to see if anything new pops up.
  5. so what about mine? i can get the loopback test working perfectly so its not a question of the setup but when i press ctrl-z i get the little arrow. someone else mentioned this might be cos of wires touching off each other but if i press other keys it doesn't appear on the terminal? i have tried with and wothout grounding, swapping rx and tx etc but never get the F3 T> i'm using power straight from the psu and a dku-5 cable connected to same pc. i've tried it with pcb removed and installed. still nothing. i think mine is f***ed:(
  6. hiya can't get the F3 T> have the loopback test working ok and when i press ctrl-z i get the little arrow - is this to do with wires connecting that shouldn't be? using victoria my drive doesn't get a busy light but an error i.e. - unknown error [ATA protocol] DRQ!!! Press RESET or restart HDD! Get drive passport: drive error! I tried this cos i couldn't get the F3 T> prompt when i hooked my dku-5 cable to it. I can do the loopback test no problem. also i can't hear anything when i connect the drive to power - should i be able to? i've read all 89 pages of this thread and to be so close and yet so far away is crap. i'll keep trying though. anyone help me?