Re: failing HDD, ddrescue says remaning time is 7104d
ppr [2022-08-31 15:25:36] wrote:
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: FAILED!
> Drive failure expected in less than 24 hours. SAVE ALL DATA.
> Failed Attributes:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
> 2 Throughput_Performance 0x0005 037 037 054 Pre-fail Offline
> FAILING_NOW 3774
> 5 Reallocated_Sector_Ct 0x0033 001 001 005 Pre-fail Always
> FAILING_NOW 2004
> ---
Not looking very good, eh?
> I did not try to mount the HDD. I plugged an external HDD (ext4) and
> launched ddrescue. After two days it has recovered 33GB of 1TB but the speed
> are now so slow it will take 7104 days to complete.
>
> # ddrescue -n /dev/sdb
> /media/sara/2274a2da-1f02-4afd-a5c5-e8dcb1c02195/recup_HDD_sara/image_HDD1.img
> /media/sara/2274a2da-1f02-4afd-a5c5-e8dcb1c02195/recup_HDD_sara/recup.log
> GNU ddrescue 1.23
> Press Ctrl-C to interrupt
> ipos: 33992 MB, non-trimmed: 0 B, current rate: 636 B/s
> opos: 33992 MB, non-scraped: 0 B, average rate: 188 kB/s
> non-tried: 966212 MB, bad-sector: 0 B, error rate: 0 B/s
> rescued: 33992 MB, bad areas: 0, run time: 2d 2h 6m
> pct rescued: 3.39%, read errors: 0, remaining time: 7104d 20h
> time since last successful read: 0s
> Copying non-tried blocks... Pass 1 (forwards)^C
Hmm... I have no idea what's going on with your disk, but: I had a 2TB
2½" drive that failed with somewhat similar symptoms: the `dmesg` and
`smartctl` messages did not look anything like your drive, but just like
you show, `ddrescue` was able to read the drive without errors, just at
a dreadfully slow pace (tho I think it was more around 50kB/s).
While playing around with it, I ended up noticing that the performance
of `ddrescue` would sometimes briefly jump up to "several MB/s" and that
those jumps were somewhat(!?) linked to my running `lvscan`.
In the end, I ran a "while loop" that did `lvscan` repeatedly, and that
sped up `ddrescue` to an average of ~1MB/s which was sufficient for me
to copy the few partitions that actually mattered, within a tolerable
time. I also mounted a few other partitions to copy over some
specific subdirectories.
FWIW, I still have the drive, and last time I tried, it still
(mis)behaves the same. According to my web searches my problem was
probably linked to overheating which apparently can change the shape of
the platters enough that the head's positioning always fails-at-first
bringing access speed down to a crawl.
> Should I wait hoping for a speeding?
I'd prioritize the parts of the drive that matter.
> Should I pass different option to ddrescue or use another tool?
That did not seem to make any difference in my case, but obviously YMMV.
Stefan
Reply to: