Original post from "Ben" (2020-12-11):
I am trying to rescue a 4TB harddrive to another 4TB drive on Windows OS using DDrescue GUI. The settings are set to best recovery.
Pass 1 went smoothly over 2 days and recovered about 2TB of data with ~2000 read errors. I woke up today to see that it has went on to pass 2 and the time remaining was over 4000 days. It seems to have stucked somehow and I aborted it to let the computer and disks to cool down before restarting with the logfile. I have a temperature monitor open at all times and nothing is overheating with a fan pointing at it.
https://imgur.com/W4dgCEZ
Is this normal?
(2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal? Topic is solved
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "hamishmb" (2020-12-11):
Hi Ben,
Unfortunately, this is quite normal - often failing disks are very slow to read, and very slow to fail read operations. Chances are it will speed up again soon after getting through a rough patch.
Glad to hear you're keeping an eye on the temperatures.
You may be able to speed it up with these things (try a few different combinations, some may work better than others depending on your drive):
- Select fastest recovery instead to get past the bad areas quicker, then make another pass with best recovery afterwards.
- Enable the "Read backwards" option to try to read from the end of the damaged drive first, which might be in better condition than what it's trying to read right now.
Hope this helps,
Hamish
Hi Ben,
Unfortunately, this is quite normal - often failing disks are very slow to read, and very slow to fail read operations. Chances are it will speed up again soon after getting through a rough patch.
Glad to hear you're keeping an eye on the temperatures.
You may be able to speed it up with these things (try a few different combinations, some may work better than others depending on your drive):
- Select fastest recovery instead to get past the bad areas quicker, then make another pass with best recovery afterwards.
- Enable the "Read backwards" option to try to read from the end of the damaged drive first, which might be in better condition than what it's trying to read right now.
Hope this helps,
Hamish
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "Ben" (2020-12-11):
Interestingly though, I switched off my computer and allowed the drives to cool down completely before restarting the operation. It was able to progress to 1841 GB (from 1835 GB) with 317 read errors before crawling to a halt again at 1000 B/S read speed with 22000 days of completion.
I will try your suggestions and update you on the progress! Thank you so much!
Interestingly though, I switched off my computer and allowed the drives to cool down completely before restarting the operation. It was able to progress to 1841 GB (from 1835 GB) with 317 read errors before crawling to a halt again at 1000 B/S read speed with 22000 days of completion.
I will try your suggestions and update you on the progress! Thank you so much!
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "Ben" (2020-12-11):
Also, does it matter if the image sources are exactly the same as the logfile? For example if the logfile source was /dev/sdf and destination was /dev/sdg, could I start it again with the drive names swapped (The physical drives are still correct). My computer seems to switch the drive names randomly
Also, does it matter if the image sources are exactly the same as the logfile? For example if the logfile source was /dev/sdf and destination was /dev/sdg, could I start it again with the drive names swapped (The physical drives are still correct). My computer seems to switch the drive names randomly
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "hamishmb" (2020-12-12):
If the drive names swap that's okay, just as long as you're sure that the source and destination are still correct.
I wonder if it slow down after a certain number of read errors, that's kind of interesting. Does it feel really hot to the touch when it slows down?
If the drive names swap that's okay, just as long as you're sure that the source and destination are still correct.
I wonder if it slow down after a certain number of read errors, that's kind of interesting. Does it feel really hot to the touch when it slows down?
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "Ben" (2020-12-13):
It does feel a little warm when it slows down. It recently stopped automatically and said that the source file wasn't available, had to restart it a couple of times.
It does feel a little warm when it slows down. It recently stopped automatically and said that the source file wasn't available, had to restart it a couple of times.
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
Reply from "hamishmb" (2020-12-13):
Yeah, you may have an overheating problem then, that does happen with drives sometimes where they disconnect when they overheat.
If it keeps disconnecting, it may also be worth trying DDRescue-GUI with Linux or a Mac if you have one, but hopefully that won't be necessary. Sometimes Linux copes better with disk read errors than Windows does.
Yeah, you may have an overheating problem then, that does happen with drives sometimes where they disconnect when they overheat.
If it keeps disconnecting, it may also be worth trying DDRescue-GUI with Linux or a Mac if you have one, but hopefully that won't be necessary. Sometimes Linux copes better with disk read errors than Windows does.
Re: (2020-12-11) Copying non-tried blocks Pass 2 - 4000 days, is this normal?
(there was never another reply)