gogeta

I can't use at 100% ddrescue because i don't have another hdd of same/bigger size. In fact i have done a manual backup with TestDisk of most important data on another hdd. Now i may format or whatever to do to fix. What can you suggest? Thank you!

Hi, i have restored an ST3500320AS from BSY status (or at least I think), now is recognized by bios but not Windows. Explorer still search for the partition, then nothing. I can see the content of the HDD only with Linux Xubuntu through the software TestDisk, but not always on the first attempt. It also happen that when i try to make a backup (with TestDisk) to another drive, sometimes give me a read error (can't read the partition) and i must retry the copy. What can i do for fix this problem? I haven't updated the firmware. I could fix it on this way? I am available to do any test! Thanks and sorry for the poor english

Ok i will open another thread for my specific issue, thanks!

On my netbook with xubuntu i can use "fdisk -l" correctly, only for about one minutes... after the drive will not see anymore until restart the unit. this is the response of the command Disk /dev/sdf: 500.1 GB, 500107862016 bytes48 heads, 46 sectors/track, 442379 cylinders, total 976773168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0xda688281 Device Boot Start End Blocks Id System/dev/sdf1 * 2048 976771071 488384512 7 HPFS/NTFS/exFATI presume to have the same issue like this thread: http://www.msfn.org/board/topic/170881-seagate-720011-malediction/ Edit: with TestDisk in Xubuntu i recognize the NTFS partition and the files that there are in the HDD! I have write the partition table but still not recognized by Windows... We are one step closer to the solution! Edit 2: for safe i still trying to copy important files to another hdd. But sometimes the drive hang up and no partition were found! After a while the partition reappear and i can continue

What do you mean "not recognized by windows"? I.e. is the DISK device seen in Disk Manager BUT NO DRIVE letter appears in Explorer? The actual original issue may have been: 1) a BSY the disk is NOT seen/detected by the BIOS 2) a LBA0 the disk is seen/detected by the BIOS Is the disk now seen by the BIOS? If yes, it should also be detected in Disk Manager and this means that it is not "bricked" anymore (i.e. the fix was successful ). Still it is possible that further steps are needed to recover the pre-existing partition(s) or, should this fail, only the recoverable data, see: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1078040 (for the record , not hidden a zillion pages back in the megathread, it is last post before your original one) jaclaz I ear the sound that the device is connected in windows, appear unit "F:" but still in this issue. Now the unit is detected by the bios. Device manager is in "waiting" condition like before this operation for restoring the unit. In the attached image in red i sign: Device manager and "This PC" in waiting condition - "F:" unit partially recognized. I ear also the unit that sometimes work (tipical sound of hdd that read/write) Ps: vedo che hai la bandierina italiana, possiamo parlare in italiano? Grazie

I have successfully send all the commands! F3 T>/2 F3 2>Z Spin Down CompleteElapsed Time 0.154 msecsF3 2>USpin Up CompleteElapsed Time 6.399 secsF3 2>/1F3 1>N1F3 1>/TF3 T>i4,1,22F3 T>F3 T>EchoInterfaceCmds: OnEchoInterfaceCmds: Offm0,2,2,,,,,22Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8User Partition Format Successful - Elapsed Time 0 mins 00 secsF3 T>But still not recognized by windows! What to do now? Thank you for your patience!

NO, if a virtual COM port is created and the loopback test works then the driver is fine.Have you checked ALL the points I listed in my previous posts? Have you double-checked them? Have you also double checked the speed/parity/etc? JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer. There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial). jaclaz Yes i have checked all the points on the previous post, many times. Now i have completely remove the PCB, swapped the TX-RX and i can finally enter in the terminal!! Now another problem. When i put this commands the terminal give me these codes: F3 T>/2F3 2>ZLED:000000CE FAddr:00280569LED:000000CE FAddr:00280569 Last row is repeated about every minute. I have isolated only the contact on the lower side of the PCB, that is listed on the guide. I will wait your info, thanks!

i have tried with PCB removed, with only isolation for the contact with a stripe of paper, but same situation... Driver problem for the TTL adapter? Hyperterminal is correctly configured. OS: Windows 8.1 and Windows 7.

I have tried hit CTRl+z (not uppercase), swapped TX RX. I have bought a pl2303hx adapter, i think that is good for this job. I thought that even without removing the PCB, something appeared on the screen, just for test. Today i buy the Torx screwdriver and i will try to remove the PCB. I hope that will work! Thanks for now!

Hi, i have recently bought a USB-->TTL adapter for fix my ST3500320AS. I have installed the driver on 2 pc: 1 on Windows 8.1 x64 and another with Windows 7 x32. The adapter works fine if i put together the TX-RX connector (i see loopback on hyperterminal), but when i connect the hdd there are nothing on the screen, only blink cursor. Now i cannot tried to remove the PCB because i don't have a Torx T6. there is a possibility that work if i try to remove the PCB? Or is possible to a driver problem? The HDD was visible in bios, before the issue, but now isn't.