sergserg

I set up everything again and just applied the last command, it was instantly successful this time (0 seconds). All the files and partitions are intact. Thank you very much everybody for your help

Thanks. After waiting about 3 hours, I terminated the communication and restarted, switched off main pc and hard drive, turned on again, I read that there was a small chance that the drive was actually fixed, so I plugged it to the pc via USB. Windows automatically started to install suitable drivers for the specific model of hard disk (something new because the drive couldn't be seen or recognized at all before). But the drive doesn't show up on the "My Computer" folder (where one can see all other disks and drives installed listed), I launched the Device Manager to see if I could find the drive listed there, and I got the following message: I don't know what to do. How can I know if the disk has been fixed but a few more steps are needed for complete recovery (like restoring partition tables or testdisk), or if I should start the process from start?

I started again following each step but I get the same results every time. I can hear the drive spinning up after the F3 2>U command, and I can feel it spinning the whole time, but no matter how long I wait, no confirmation message is displayed. Edit: I finally got the spin up complete message, but now I'm stuck on the last step (F3 T>m0,2,2,0,0,0,0,22). I've read that the time this last step can take varies from a few seconds to up to 10 minutes. More than 30 minutes have passed and there's still no final message. I'm afraid to stop the process, I don't know what should I do if everything stays like this.

Hi. I'm currently in the process of fixing a hard drive with firmware hp24. I could apply the first commands, but after removing isolation between board and hard drive, reattaching it and doing F3 2>U, I can hear the drive spinning up, but the terminal hangs up there, no message is returned, not even error, and trying to close and start a new session doesn't work because there's still an ongoing communication. Does anyone know what could be the problem? Thanks.