recover data from bad hdd

ok thanks i will give it a try

what happened when you ran chkdsk /f ?   any messages, or errors?

For future - never run CHKDSK on such partitions before you try data recovery tool or before you take a sector per sector image of this partition.
As mentioned above - GetDataBack tool from www.runtime.org should be able to see the content of this drive. If it is possible at all. Run it and report back. Do you know when and how went it bad?

If testdisk didn't work, it is very unlikely that any other product, even getdataback or photorec will work. Send the disk to a professional recovery agency, like Gilware:

https://gillware.com/

Testdisk only does very basic recovery things like finding lost partition boundaries and fixing filesystems by using the backup blocks. The other recovery tools like photorec are trying to read the drive sector by sector and analyzing the bit patterns to recognize filetypes. Get data back does try to interpret all the remainings of the filesystem on the disk it can find not just looking at the backup blocks. Frequently I was able to recover files with photorec and get data back when testdisk failed.

So its worth a try. BUT if your files are really important and it would be fatal to lose them you should really consider to consult a professional recovery lab, one mistake on recovery procedure might destroy the data on the disk and then professional labs also might be unable to recover files.

I tryed get back data there were a lot of I/Q errors  eroorr 23 , 55

Photorec freezes at Disk idenification

Then the drive is bad. If the data is critical then let professional services care about it.

Just send it to a recovery agency like I already suggested. Any further stress you let the disk experience reduces your chances for recovery.

Besides, since there is no backup, the data can't be important, and trying to recover the data a waste of your time and money for your customer. If on the other hand the data is important, and the customer could afford to not make any backups of it, he can also afford to pay the professional recovery agency.

All though i did not recover the data Andreas info was good

so was the other's info!!!

You can use FTK imagers as a tool for triage to try and get the data back.  It will mount the physical layer of the drive so your chances are good.  It is free and I would look for version 1.81 I think as the older version is a bit more user friendly.

IO errord indicate bad sectors, that means physical damage to the drive. If data is really important its time to stop any exteriments and send to a recovery lab.

If no money should be spent for recovery, you may try to make an image with dd_rescue (that skips the broken sektors) and then let get data back work on the image file.
Creating the partition image with dd_rescue may take a long time depending on how many sectors are defective. the stress of trying to read the hdd from begin to end to make the image may even break the entire disk totally.

Ioerrors does not indicate bad sectors necessarily. It can b simply a bad logical controller or even the heads are failing to go to requested area.

yes thats correct but MOSTLY its defective sectors especially if its only parts of the disk. controller erros usually make all IO operations error out.
Head positioning issues are also possible. but these are also usually increase when stressing the drive.

Positioning error sometimes can be made better when the drive is operated at different orientations. e.g. vertical instead of horizontal or upside down.