| 1 |
This help? Should be plain text. |
| 2 |
|
| 3 |
Dale |
| 4 |
|
| 5 |
:-) :-) |
| 6 |
|
| 7 |
Stroller wrote: |
| 8 |
> Would love to comment on this. Is it possible you could resend this |
| 9 |
> post in plain text format? |
| 10 |
> |
| 11 |
> Stroller. |
| 12 |
> |
| 13 |
> |
| 14 |
> On 10 Jan 2010, at 02:08, Valmor de Almeida wrote: |
| 15 |
> |
| 16 |
>> |
| 17 |
>> Indeed I am using GNU ddrescue and the -n flag is supposed to |
| 18 |
>> expedite the recovery of data as posted in |
| 19 |
>> http://www.cgsecurity.org/wiki/Damaged_Hard_Disk |
| 20 |
>> |
| 21 |
>> "The best solution - both faster and more efficient - seems to be |
| 22 |
>> Antonio Diaz's 'ddrescue' (ddrescue |
| 23 |
>> <http://savannah.gnu.org/projects/ddrescue/>)" |
| 24 |
>> |
| 25 |
>> # first, grab most of the error-free areas in a hurry: |
| 26 |
>> ./ddrescue -n /dev/old_disk /dev/new_disk rescued.log |
| 27 |
>> # then try to recover as much of the dicy areas as possible: |
| 28 |
>> ./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log |
| 29 |
>> |
| 30 |
>> |
| 31 |
>> |
| 32 |
>> expectation, not a reasoned one. I think the best thing he can do |
| 33 |
>> is hold his breath, wait until its finished and see how if the |
| 34 |
>> results are readable, after running `fsck` on the mounted filesystem. |
| 35 |
>> |
| 36 |
>> |
| 37 |
>> The first step above finished; don't know how long it took but it was |
| 38 |
>> a long time (maybe 20 hours or more?) and the screen output was |
| 39 |
>> |
| 40 |
>> Press Ctrl-C to interrupt |
| 41 |
>> Initial status (read from logfile) |
| 42 |
>> rescued: 0 B, errsize: 0 B, errors: 0 |
| 43 |
>> Current status |
| 44 |
>> rescued: 58811 MB, errsize: 48909 kB, current rate: 83 B/s |
| 45 |
>> ipos: 58860 MB, errors: 95, average rate: 1365 kB/s |
| 46 |
>> opos: 58860 MB, time from last successful read: 0 s |
| 47 |
>> Copying non-tried blocks... |
| 48 |
>> ddrescue: write error: Input/output error |
| 49 |
>> |
| 50 |
> |
Archives