HDD crashed and bad sectors appeared. How to hide bad sectors?

Question

Hard disks

Hdd fell from a small height and hit slightly, was disabled.
The speed of work slowed down and slow and broken sectors appeared. Data already written is read with large pauses but mostly read. And the new recorded large files with errors.
The data is read but with big delays. For example, 300 MB is read, then a delay and again 300 MB.
The files are copied to disk. But copying is suspended and after a pause it continues again. But when copying them back, an error occurs.
1 What could go wrong?
Looks like the disc surface is damaged.
Could the head be damaged or something else?
During operation, when it cannot count, rustling, weak tapping is heard. Then, as it were, it stops, a sharp, as it were, electromagnetic crackle or rustling, it seems that it stops.
2 How can I hide bad sectors?
There is no important data on the disk, but I would not want to throw it away, it is suitable for storing unnecessary data. But writing and reading sometimes occurs with errors.
Drives should automatically hide bad sectors, but it doesn't seem to do that.
Programs don't seem to be able to remap.
Victoria can't do a remap because the drive works via usb. And when booting from a flash drive, it does not see the disk.
Mhdd does not see the disk.
Hdd regenerator scanned for a long time, scanned 2% of the disk in 6 hours. He saw slow sectors but does not see broken ones. The scan has been aborted. Nothing has changed since then.
On the Internet they write that the Current Pending Sector should disappear but did not disappear after the programs were running. The programs did not scan the entire disk, but in some places, because it took too long. Scans were launched in different places on the disk, but there were no changes there. There is no point in scanning completely?
3 HDD has 3 disks, 6 surfaces. How to determine if all surfaces (or heads) are damaged or not? Can you disable some of them? On the Internet, writing on disks occurs simultaneously on all surfaces. But the blow was weak and it is generally strange that the entire disk fell off.

Here is the result of a quick scan, but the actual number of broken cells is higher. The fact is that normal scanning is too slow.
It may be that only one surface was damaged, but the errors are all over the disk, as the recording occurs simultaneously on everything? It's just too strange that the whole disk could fall off at once with a slight fall.

Answer 1

1 What could go wrong?
Looks like the disc surface is damaged.
Could the head be damaged or something else?
During operation, when it cannot count, rustling, weak tapping is heard. Then, as it were, it stops, a sharp, as it were, electromagnetic crackle or rustling, it seems that it stops.

You have correctly diagnosed yourself. The "spindle" of the reading rod could loosen from the impact, thereby the head began to scratch the disk. Don't torture him with tests. Copy all important files and let it go with flying colors.

2 How can I hide bad sectors?
There is no important data on the disk, but I would not want to throw it away, it is suitable for storing unnecessary data. But writing and reading sometimes occurs with errors.

Software erroneous sectors can still be restored, and then these are continuous "dances with a tambourine" and if there is mechanical damage, write wasted.
I'll say it again. Copy what is a pity to lose and let him go in peace. His fate is sealed and finished.

Answer 2

Hdd fell from a small height and hit slightly, was disabled.
The speed of work slowed down and slow and broken sectors appeared. Data already written is read with large pauses but mostly read.

Do not finish the disk with reading tests! Copy (while you can!) the most important data, then the rest. Then take the drive out of service.
Generally speaking, you are lucky enough - play the lottery or vice versa, do not play (because luck has gone here).
The heads are probably damaged ("weakened") and most likely, gradually degrade completely. With a certain probability, they can also cut the surface.
The text of the question is large, but remap and so on are not for your case. These are mechanisms for hiding minimal defects caused by wear or imperfections in the manufacturing process. You have physical damage.
Zelenka cannot cure a fracture and concussion.
Heads can be turned off, but, depending on the disc, this requires at least basic skills and specials. software, then hardware and software systems, experience in data recovery, reverse engineering, etc. begin to appear in the requirements.
Yes, the recording goes to all heads, otherwise it is unreasonable, at least in terms of speed.
In addition, the block of heads is a rigid structure ( as a hard disk is arranged ). For the same reason, the damage can be extensive - if one head was displaced due to mechanical action, then the law of conservation of momentum affected the neighboring ones to the same extent.
And in any case, do not use this profanity. How much data (originally salvageable) was irretrievably destroyed along with the disks, thanks to its developer's tales of "hysteresis loops"!
If you need to test a disk (not this one, another one), use R.tester instead - its functions are focused primarily on diagnostics (safe).