Jump to content

BlouBul

Member
  • Posts

    409
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    South Africa

Everything posted by BlouBul

  1. Can you see it in BIOS (and is it working) if you connect it directly to your computer via SATA?
  2. I actually agree with you (except for the part where you are saying that you are disagreeing with me) What I meant (maybe it did not quite came out that way) was: meaning it is not necessarily a problem, but when it is a problem, then it is usually when someone did not power down (probably due to the rheumatic fever case (BTW good explanation), where I think it is needed.).
  3. That is because you did not do the optional power down. It can take up to a couple of hours (or forever) if you do not do that Anyway, glad you managed to fix it
  4. Good find (guess that is why your title is The Finder) That also got me confused originally...
  5. Ok, maybe I'll settle for the long lost (adopted?) child of the 7200.12 series, totally confused (he hasn't been told of his recently discovered heritage and therefore the identity crisis) and thus still happily spinning at 5900 RPM, but still giving the impression (only due to the long lost family ties discovered and published by the marketing people) of belonging to the 7200.12 family But I still think Eurgene should rather try the fix for the LP series... ???
  6. I am not convinced Maybe some 3rd party part suppliers market their PC boards as "Seagate Barracuda 7200.12 ST31500541AS", but it is stated very clearly (from your last link for one) So AFAICU, the two are mutually exclusive. The 7200.12 spins at 7200 RPM, while the LP spins at the reduced spindle speed of 5900 RPM.
  7. From the little I know, it is a 5900 Rpm drive http://www.seagate.com/docs/pdf/datasheet/disc/ds_barracuda_lp.pdf See if anything here helps:
  8. Where did you connect BOTH 5V and 12V to? 12V will definitely fry your hdd connected through your converter at TTL, but you need to power your hdd with the normal full spectrum of power cables.
  9. Did you check your external USB enclosure/ Port? What happens if you connect it straight in your PC (not through USB)?
  10. Try at level 8 http://pictatrove.co...harddrives.html
  11. First things first. Did you do a loopback test? See the FGA for more info. (especially no. 4)
  12. _TK_here (August 10, 2010) had exactly same problem as you on an ES.2, which was solved by the shorting trick, so there is hope, we just have to find the right answer for your problem. Maybe start a new thread and we can see if we can find more info on that problem for your drive.
  13. Well, if you have no important data on the disk of which you have no backup of, and can afford a new hdd, that is certainly a good way to get rid of your frustration Otherwise, let us see if we can find a solution to your problem. On further searching, I found a couple of very similar symptoms on the 7200.11's (but no solution yet ), so it might be caused by "something else". I will look some more and hopefully find something helpful.
  14. Ok, at least you can see your hdd. Now your first priority is to recover any data that you do not have a backup of. Try putting that hdd as a secondary hdd, boot from the good hdd and see if you can see your data and copy that to a safe location. Once your data is safe, you can worry why the disk is not bootable.
  15. Well, since this method is for 7200.11 Drives and NOT for Seagate LP Green drives and your Drive are neither in the BSY, nor 0LBA state, the short answer is NO (and you are in the wrong thread ). However, IIRC , there has been some reports where a failed fix resulted in a wrongly displayed model, which has been resolved by doing the fix again (on a 7200.11). So, since this is like a "general reset" the method might work, if you can get it to work in Hyperterminal (which has been a problem for LP Green drives ). See if anything here helps http://www.msfn.org/...-ceases-to-tal/
  16. The only other thing I can think of that might work is to try the optional commands given by Aviko here All HP firmware before HP26 suffer from the same symptoms (and uses the same fix)
  17. Glad you managed to fix it , BUT... You could have saved yourself a lot of trouble if you read the instructions first. The colours of the wires are NOT important as it differ between manufacturers/ days of manufacturing and whatever colour was available during manufacturing. An easy way to identify them is given in the link in FGA #6. http://www.msfn.org/board/topic/147532-fga-for-the-seagate-720011-drives/page__pid__945647#entry945647 and http://buffalo.nas-central.org/wiki/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation
  18. I agree with the using/suggesting part, but about mentioning, since it is already out there in the public domain: forewarned is forearmed. It is better if people know beforehand NOT to use it. Good question. That depends on what your definition (and degree) of dead is. Like I said earlier, my theory (I might be wrong) is : The drive might not necessarily be dead in the strictest sense of the word, but the symptoms is not caused by the BSY bug, since everything has been reset to defaults and error codes cleared, but the symptoms still persists. It might be something simple like a SATA data connection that doesn't make contact for some reason or something more serious that cause the drive not to be recognised by BIOS.
  19. It is the M0,1,... command that wipes the disk. See here http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page__st__3680__p__962051#entry962051
  20. That is strange . The User Partition Format Successful normally means the disk is reset to defaults and the BSY error is fixed. I wonder if your disk does not suffer from *something else* that cause it not to be recognised by BIOS.
  21. If you used the original driver cd that came with the cable, it should be the right driver, otherwise your guess would be as good as mine. Check in Device Manager if your cable is seen, that should mean you have the right driver installed. If driver is right, unplug/replug cable and see if it is better. Also restart HyperTerminal.
  22. Great, that should work better Use the previous given link to identify Rx and Tx. And I wish you all the luck you need to fix it (and some more)
×
×
  • Create New...