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

Community Reputation

0 Neutral

About Chilli

  1. Jaclaz, how can you tell? I did not find any match in this forum neither in google for "process effect list". Furthermore Jamesblond stated he has a LBA0 error. Is it necesarry to spin down in this case at all? At least Gradius description for LBA0 starts immediately with partitioning. Until now my understanding was that spind down is necessary to break the infinite loop of bsy drives (however since mine always failed busy, I have no expericene with LBA0). I had some private conversation with JamesBlond in german language and it seems to me that his dirve has a problem whenever it really needs to access the platters. This might be a physical problem either in mechanics or electronic hardware, or wrong calibration values if the data recovery people made some changes for fun. If one of the latter is correct the role of the data recovery company is very doubtfull (considering the quote versus actual costs for recovery of a drive with physically defect mechanics). Regards Chilli
  2. Thanks for the link, I'll look at it when I'm at home. As I said I gave up searching. So maybe I can sell the drive for some bugs or use it as back up drive if I can update the firmware. I don't want to argue with you about the difference of a minimum timespan and an average, it will lead to nowhere ;-). I think I stumbled somewhere about an explanation that there are more than one failure mode of the harddrive caused by the SW (eg. there was a Segate ICT or EOL test pattern dependend issue and some other stuff). Based on my usage (the PC is not booted daily) and the short (almost every time decreasing) MTTF of my drive I would say the normal counter overflow theory is no explanation for the failure of my drive. The drive is what some called "locked in", that means I have to power up with heads & motor attached and than quickliy unattach the heads after first reponse from the drive on the serial line. -Maybe this makes a difference. Still instead of using some plastic cards, I first loosen all PCB screws (to avoid bending/stress on PCB) and than quickly unscrew the screw above the head connector at the right time. But I also won't argue if it is more likely to damage the PCB with a plastic card or to damage the heads because of paritial head connector contact during too slow screwing ;-). -Can just say my drive survived the proceduer, and also survived 5V TTL (thanks to the serial reaistors in the serial line on HDD PCB).. Regards Chilli
  3. I can not agree with this. Just unbricked my drive last week for the 4th time. I undbricked it the last time two months ago. However, since I did not solve the Fujitsu Siemens firmware issue (and to be honest I'm not interrested to look further in this topic anymore), I have a replacement drive at home since Tuesday, that just waits until I figured out how to solve the 4kByte sector alignement issue, before I send my seagate drive into rent. And, ofcourse, the replacement drive is no seagate drive. Regards Chilli
  4. Sucessfully recovered my Segate from locked state for the third time. Eventually i will spend some more hours to find out how to overwrite Fujitsu Siemens firmware, but very likely I will just buy another harddisk, mirrow the data, activate windows..., thrash the seagate and never buy seagate again... Regards Chilli
  5. I had some IT guys that stored my drive in a fridge in the hope to restore some data. Infact they could not restore a single byte. I got the "piece of trash" home and found out that somehow the partition table was corrupted. I could restore almost all the data (ofcourse I invested quit some time to find the right tools). The difficult thing on IT guys is that you need to know how really knows something and how is just talking. -Well i guess that's not only true for IT guys . Regards Chilli
  6. @dragon65: The whole procedure described here is specific for the seagate firmware bug. Maybe others in this forum can help you. But the work around of this thread will not work for you and also, if you look at the topic of the thread, this is not the correct place for your question . Nevertheless: Good luck.
  7. I think that the black cable is not necessary in most cases. 1) If you have potential separation in your serial adapter cable (that's what good adapters do...) it's sufficient to connect the GND on the HD side of the serial adapter cable to the serial GND at the HD serial connetor (no black cable necessary). 2) If you do not have potential seperation and connect the serial cable GND to the HD serial GND (on the HD serial connector) you "short cut" it to the computer GND anyway (no black cable necessary). ad 2) I did not check if serial GND on HD has a protection resistor like Rx and Tx, but if not, a break of the power GND would drive the whole HDD current over the serial GND in that case (what it is not intended for). So black cable or missing potential separation of serial adapter might even have draw backs. The only thing you must not do is use 20year old power supplies that do not have potential separation from the power line... In this case, if you apply the black cable, the smoke on the black cable or the popping noise of the electrolytic capacitors in the power supply might prevent you from destroying your HD ;-). Regards Chilli
  8. Hello all, A just wanted to drop a note that since I could not update the firmware of my drive (fujitsu siemens OEM) after revocery in January, the drive failed again with boot of death within 4-5 months. I just folloew the same procedure as last time to recover it again. Now, that I have sufficient resources backup the whole drive I might try potential destructive fimrware reprogramming methods, if I find tim to play around. @PC995 If you do not write a diploma work, what is the question good for? If seatool works, don't mess around with serial communication. If your drive is looked unlock it with serial communication and make whatever you want in addition with official tools via SATA. The serial connection is for serive purpose. If you do not exactly know what you are doing (and you question impliees this) you can screw up your drive easily. Regards Chilli
  9. At least they could. At data recovery service it is not unusual if you except the electronics to be broken to exchange it with a working one. That would not work on our desktop because the new electronic does not have the correct drive parameters. But a skilled service guy has probably a patented "One - Button - Drive Calibration" software ;-). BTW: Seatools for windows can finish non of the tests on my laptop hdd. This is rather a sign of bad tool and not of bad drive... (seatool does not give a usefull error message either). Regards Chilli
  10. Last time I needed low level format must have been about 15years ago... So I would not be surprised if the command is obsolete (or legacy ;-) ). Regards Chilli
  11. Very strange. You might have another problem too, that boots log entry count. I flew over the diagnostic commands and astonishingly (is this word english?) I did not find a command for low level format. I did not find a way to erase the data via command inteface. Regards Chilli
  12. NOP. Don't have much time either. Seems that interresting stuff is "hidden" in bootblock for each, seagate flash tool and FSC flash utility. Don't have an utility installed yet to view boot block content. Btw. I took a look what flash utility did on the USB stick: it made a 100MB Ext3 partition and used 14 MB of it (excluding boot blcok). So I don't know what FSC ment with 1,7GB free space on stick... It's funny enough that you have to download a utility with about 340MB to get 14MB on the stick... However with static library you're always on safe side ;-). Regards Chilli
  13. @bill4d:As Jaclaz is also writing between the lines: If the drive is bricked as soon as you hook it into you computer, than it was not sucessfully unbricked before. We us the term unbricked for drives that are accessible by the computer again. As long as is it not accessible by the computer it is as much as a brick. Whether you can communicate per seral interface or not has nothing to do with unbricked or not. Regards Chilli
  14. "Card trick" on the head connector and short cutting ist the same. The short cut also only "wipes out" the heads. For many drives the cardboard trick for either the head connector or the motor connector works. But there are some reffered to as "locked in" that do not communicat anymore as soon as you power them with a cardboard on either of the connectors. For these there was the short cut invented, which has to be applied at a certain time. However if you manage to disonnect the head connector at this certain time it does the same. Regards Chilli
  15. For my ES:2 I disconnected the heads at the moment you described. I could accomplish this by loosing all screws around the head connector (at unpoweerd disc), tightending the head connector screw a bit, so that it gets contact again, making procedure like you described and instead of short cutting just quick opening the connector screw. After spin down you can tighten the screw again. Maybe better for people that have no solder equipemnt or another PCB revision. Also the motor connector can be "disconnected" by unscrewing, if needed. Regards Stephan