Hi, I have a suspicious hard disk (suspicion of failure), and I have cloned it to a new one. Exact same model and version. I did it this way: Andor:~/Mantenimientos/migracion_disco_C_2T_2020 # time ddrescue --force --ask --retry-passes=3 /dev/sdc /dev/sdd ddrescue.mapfile --log-events=ddrescue.logfile --log-rates=ddrescue.logrates GNU ddrescue 1.23 About to copy 4000 GBytes from '/dev/sdc' [UNKNOWN] (4000787030016) to '/dev/sdd' [UNKNOWN] (4000787030016) Proceed (y/N)? y Press Ctrl-C to interrupt ipos: 4000 GB, non-trimmed: 0 B, current rate: 47996 kB/s opos: 4000 GB, non-scraped: 0 B, average rate: 75418 kB/s non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s rescued: 4000 GB, bad areas: 0, run time: 14h 44m 7s pct rescued: 100.00%, read errors: 0, remaining time: n/a time since last successful read: n/a Finished real 884m53.976s user 0m28.480s sys 41m34.528s Andor:~/Mantenimientos/migracion_disco_C_2T_2020 # That is, 14,73 hours. A lot, for a disk with no errors found. ddrescue said initially (yesterday night) that it would take 5:45 hours. This morning it was still running: it said 7 minutes remaining, it took about 14. The thing is, I could see in gkrellm that ddrescue was alternating reading from one disk and writing on the other, instead of doing it simultaneously. Why? :-o I would understand that when it finds a read error it drops to alternating the operations, but when there is no problem, why? If a disk is prone to failure, the longer it takes, the danger increases, right? -- Cheers, Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org