Recovering data is taking too long!

[Moizevitch]

Hello everybody.

I joined this forum precisely because I have a big problem and a related question.
I have a 1TB HDD and to make matters worse, it presented errors, and it seems to me that it "died".
It doesn't even appear in Windows Explorer.
The only way to try to recover my data, I guess, is through Easeus Recovery Technician (it's the only one that recognizes the problematic HDD).
But it takes horrors!
A little more than two days passed and it was only 7%!!!
Gee, like that, how many years until 100%?
My question is: if I format the HDD, and then try to recover the data, will I be able to do it faster this way?
I did it on a flash drive once, and it was pretty quick.
But it stands to reason that, both technology and size greatly influenced the speed at which the data was obtained.
However, this tactic stuck in my head and I imagine myself trying this tactic on this HDD.
I would like to rely on the experience of colleagues and see if the idea is good or bad.
My Windows is 10, the HDD is the second on my laptop, the main one is perfect.
I greatly appreciate any advice that helps me resolve this issue.
Thanks.

[northwind]

It is a very, very, very, very bad idea. It could be also catastrophic if your drive is SMR or has TRIM active.

There is a reason why your drive is slow. It could be bad head(s), some firmware glitch/feature or anything else.

For starters, check your drives SMART: Download Smartmontool or CrystalDiskInfo and see what it says.

Oh, and tell us the drive model.

[Moizevitch]

Thank you for your attention and time in helping me @Northwind. I also appreciate the program tip to test on my HDD. This Smartmontool is for Linux. I even downloaded it and installed it on my Windows, but it has no icons, it's just via command line. I didn't find videos showing its use on Windows either. So I installed and I'm using GSmartControl. The image I'm sending is from him. And, the test done with it also failed! There may even be some workaround for this problem, but I can't see it at the moment.

[Moizevitch]

I forgot the image.

Attachments

[pepe]

Hello,

that's a WD plamer family drive, can be both heads and fw problem, you will most likely kill it in some way by torturing it with Easeus.

The only way to try to recover my data, I guess, is through Easeus Recovery Technician

wrong guess here, it will most likely kill it for good.
The cause of the problem needs to be determined and treated, then clone it on specialist hw with appropriate settings.

pepe

[Moizevitch]

Hey @Pepe, I appreciate your help and advice regarding my problem. However, its solution requires the intervention of a specialist. I have neither the money nor the intention to go for this solution. I've done it in the past, and the experience was totally negative. So I'll try to solve it myself. Thanks.

[DRUG]

Hey @Pepe, I appreciate your help and advice regarding my problem. However, its solution requires the intervention of a specialist. I have neither the money nor the intention to go for this solution. I've done it in the past, and the experience was totally negative. So I'll try to solve it myself. Thanks.

Good luck and let's us know how it went.

[Moizevitch]

Hey @Pepe, I appreciate your help and advice regarding my problem. However, its solution requires the intervention of a specialist. I have neither the money nor the intention to go for this solution. I've done it in the past, and the experience was totally negative. So I'll try to solve it myself. Thanks.

Good luck and let's us know how it went.

OK.

[rec]

The picture ist pretty useless. Just naming the drive would have been sufficient.

Read here and post your logfile:
https://forum.cgsecurity.org/phpBB3/vie ... =5&t=10910

[Moizevitch]

The picture ist pretty useless. Just naming the drive would have been sufficient.

Read here and post your logfile:
https://forum.cgsecurity.org/phpBB3/vie ... =5&t=10910

I can extract information from drive a (main), however, from drive b (the problem drive), I can't.
I'm not an expert in DOS or Linux. Maybe there is some command that allows me to access it. But I don't know.

Thanks for the link.

[rec]

I am not using NVM drives but I suspect you of leaving out important information. I don't think that the full log ends at that line starting with "3 -".
Doing so as opposed to the detailed instructions in the linked article I have to assume that self-repair even on a software level is not suitable for you.

[rec]

I am not using NVM drives but I suspect you of leaving out important information. I don't think that the full log ends at that line starting with "3 -".
With you doing so as opposed to the detailed instructions in the linked article I have to assume that self-repair even on a logical level is not suitable for you.

[Moizevitch]

I am not using NVM drives but I suspect you of leaving out important information. I don't think that the full log ends at that line starting with "3 -".
With you doing so as opposed to the detailed instructions in the linked article I have to assume that self-repair even on a logical level is not suitable for you.

@rec, If you had looked at the image a little more closely (and read the message as well), you would have noticed that the clipped information you noticed, is the DRIVE A information. This drive is the main one and it's ok! The problem is in DRIVE B! This drive I am not able to access it. That's why there is no information on it. I tested several command letters (-a, --all, -scan, etc), and it only worked on Drive A. But on Drive B nothing happened. There is no reason to inform one drive if the problem is in another. Don't you agree?

[rec]

I never thought somebody would post a log file from a healthy drive, sorry!
You have to change the device name, not the command parameters to access drive sdb.