ssl666

Inner ramblings pt. 2: If you're determined to spend the rest of your days off trying to fix this stupid thing, you better make technology work for you, or your fingers will end up sore because of all the times you un/plugged the freaking SATA power cable:

Just thinking aloud here, posting for future reference: It seems that what I'm doing is something like "DDOSing" the LED error. The recovery software is reading so fast that the LED error just keeps waiting, until it happens. Then I have to power cycle. To accomplish that in DMDE I reduced the buffer size to 128 and set the sector skip on error to 2000. The result is that it's of course disgustingly slow when encountering errors, but I can (relatively) safely let it do its thing and FINALLY go get some sleep!

Hey there jaclaz, thanks for replying! It seems that I'm somewhat unlucky: With all these errors the process has slowed down dramatically. The tools you linked sure seem strong alternatives, I'll give them a go if DMDE fails. I already tried scanning the drive with R-Studio, and it went well, but once it hit this damaged area it pretty much gave up. Add the LED crap on top of that, and you can guess what happened next Let's hope that DMDE will manage to finish the copy, even with errors. You're right about the $MFT though, I did stumble upon it with R-Studio. Unfortunately the files in the disk are big so it doesn't really make a difference if I know where they are Thanks again for your time man, cheers.

Hi guys, any ideas regarding my little screwup? https://www.msfn.org/board/index.php?showtopic=177263

Hello! Yesterday my old trusty ST2000DL003 suddenly disappeared and nothing I did mattered. Eventually I stumbled upon all this serial console info and decided to give it a go. Fortunately, after some soldering, fidgeting and cursing I managed to get the F3 T> prompt, where I entered the commands given in this tutorial. Everything seemed ok, the drive even got detected by windows once or twice between the restarts. Then this m0,2,2,0,0,0,0,22 command screwed everything up. And, of course, I did read all about it afterwards, how you shouldn't really mess with that and all that stuff. That's what I get for rushing things ike an id*** before actually reading the instructions. Now I'm just trying to copy the failed disk to a new one so that I can recover the data. R-Studio and DMDE do detect the partition and the files. However, while copying the disk at random intervals just outputs the dreaded LED:000000BD FAddr:00008A23. As a result, the copying stops and I have to power off and on the drive so that the copying can be continued. That is of course a very arduous process, and I was wondering if there is a way to stop that from happening, so that the copy isn't interrupted. Any ideas? pics