ufbafigawe

Thanks again for the help! DMDE is indeed able to recover the filenames too. Unfortunately most of the data is empty zeros of course. Yeah I'm afraid I already knew that this is a bigger issue. Don't have a clue on how that happened though... Is there no way to achieve something via rs232 interface or even read it byte by byte? Or change the PCB and just grad everything left on the discs? I opened a thread at hhd oracle but it's not reviewed yet. man what a bummer to loose one's data because of a buffer overflow in the hdd firmware... I know it's my fault though that I didn't have any backups as I didn't consider it critical data. thanks and best regards

Hello everyone, I got the BSY error with my Barracuda drive, one day it would simply not show up in the BIOS anymore. I performed the fix like described in the sticky thread. It seemed to me that everything worked fine, as the drive got recognized again. But somehow the drive is seriously "broken" now as I don't see my partition and the drive "crashes" if software wants to access certain sectors. More on that later. As jaclaz suggested (thanks for the help!!) I tried to read the data via "dd" command as Linux was able to at least access the drive on a low level. The first 95938272 sectors (49,1 GB) copied just fine but as soon as any software (also ddrescue) wants to access the next sector or anything beyond it'll return some generic I/O error and after that the drive is not able to communicate any longer. Even the sectors I was able to read before are not accessible afterwards. If I power cycle the drive I'm able to access those first GBs again, but simply nothing beyond. Any ideas on what that means? BTW: The tool "photorec" is able to recover my media files from the 49GB chunk of data. Looks good to me so far even 1GB big video files seem to be undamaged so I think the actual content on the disk is ok. I had no luck with "testdisk" so far though which would keep the filenames. Any chance to access the rest of the drive? thanks in advance & best regards!

ahh that's a cool idea, thanks for your help! dd worked just fine. could well possibly be that the hdd was formatted with linux though. hex dumps attached first2100.hex first100.hex edit: ahh ok you mean first 100 sectors not bytes. how do i find out how many bytes my sectors are? edit2: ahh got it! 512bytes right? edit3: files are to big for the forum: https://drive.google.com/open?id=1bKQdiCrdc7UvYPH6JMlIK0X3Wv4MLGUO, https://drive.google.com/open?id=1iXABssls1_DvSygI9Ow2aTzagxQobRC1

Hello everyone, my drive is a ST3500320AS with SD15 firmware which had the busy state issue and was someday not recognized by the BIOS anymore. I found this thread and was quite confident that this would be an easy fix. I hooked the drive up to my 3.3V TTL to USB cable and executed the commands. Everything worked fine as far as I could tell and the drive returned: The only thing I found odd is that it prompted this line almost instantly as I expected it to take a minute or so. After the procedure the drive is again recognized by the BIOS but other than that every software I tried to access or communicate with this drive behave like this is some kind of alien device. They hang or do weird stuff. The best info about the drive I get is from Ubuntu: But that's it, there is no way I can access the content. Every recovery program I tried on Windows crashes or hangs when trying to access the drive. I also tried to use Seagate's firmware update ISO but it just prompts: Error: Specific model not found. ST3500320AS expected. even though BIOS and Ubuntu recognize the drive. Any ideas? I tried a lot now and just don't know what else to do. thanks in advance! Alex