Dear Roberto,
On 07.10.2011 18:28, [email protected] wrote:
I mean that those drives hangs linux too.
Basically, skipping the BIOS would help a lot.
I have not had a drive fail that badly yet, but wouldn't it just work
(or at least skip the bios / any
boot-time-magic-detection-read-access-on-broken-sectors) to connect it
after Linux has booted?
Hot-Plugging works quite well for my s-ata drives. I'm using some cheap
IcyDock backplane I had lying around for this and have it connected to
my onboard controller (Intel something in AHCI mode).
I've run a windows tool that allows to run direclty in reverse mode.
Yes, it is slower, but it read straightly over 75% of the drive.
If all you need is copying in reverse mode you could also just use
dd_rescue in reverse-mode for that - it's a lot more basic than
ddrescue, but I don't think that the hdd / image you recover to will
care anything about which of the two tools you use to copy the data.
Personally I consider ddrescues approach to be quite nice, especially
with the new min-read-speed parameter. As far as I understood the
documentation the second pass over the HD will attempt to read backwards
anyway, so you could also just mark the entire drive to be trimmed
(replace ? by *) to achieve the desired behavior?
Kind Regards
Felix
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
