1 |
On Sun, Jan 10, 2010 at 9:39 PM, Stroller |
2 |
<stroller@××××××××××××××××××.uk> wrote: |
3 |
> |
4 |
[snip] |
5 |
> |
6 |
> I just reread the above ("from within systemrescuecd"), which implies you |
7 |
> may be stuck without another working system. |
8 |
|
9 |
Yes. |
10 |
I am afraid the text below will be confusing but will send anyway. |
11 |
Will be happy to send clarifications if needed. This is a resend (in |
12 |
plain text) of another e-mail I sent with information on the LVM |
13 |
partition on the broken drive. |
14 |
|
15 |
>On Sat, Jan 9, 2010 at 11:10 AM, Stroller <stroller@××××××××××××××××××.uk> >wrote: |
16 |
[snip] |
17 |
> I think Valmor is using GNU ddrescue, with which one makes the multiple >passes manually. The "-n" flag on the command line that Valmor posted >(`ddrescue -n /dev/sda /dev/sdc rescued.log`) relates to the examples given >in the GNU manual page [1]. I believe that GNU ddrescue is the better version >- it was inspired by garloff's original work, and makes improvements, but it >operates differently. |
18 |
|
19 |
|
20 |
Indeed I am using GNU ddrescue and the -n flag is supposed to expedite |
21 |
the recovery of data as posted in |
22 |
http://www.cgsecurity.org/wiki/Damaged_Hard_Disk |
23 |
|
24 |
"The best solution - both faster and more efficient - seems to be |
25 |
Antonio Diaz's 'ddrescue' (ddrescue)" |
26 |
|
27 |
# first, grab most of the error-free areas in a hurry: |
28 |
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log |
29 |
# then try to recover as much of the dicy areas as possible: |
30 |
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log |
31 |
|
32 |
|
33 |
> expectation, not a reasoned one. I think the best thing he can do is hold >his breath, wait until its finished and see how if the results are readable, after >running `fsck` on the mounted filesystem. |
34 |
|
35 |
|
36 |
The first step above finished; don't know how long it took but it was |
37 |
a long time (maybe 20 hours or more?) and the screen output was |
38 |
|
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 |
|
51 |
Comparing with the screen output at the time of my first post, |
52 |
|
53 |
Current status rescued went from 58656 MB to 58811 MB, errsize went |
54 |
from 4408 kB to 48909 kB. |
55 |
|
56 |
Don't know how the write error: Input/output error message affect the |
57 |
data in the new drive copied to. Not sure whether I should do the next |
58 |
step with option -r 1. |
59 |
|
60 |
This failed drive is still bootable and the corruption is in the |
61 |
partitions /var (which I do not care) and /home; these cannot be |
62 |
mounted. I would like to attempt to get a couple of files from /home |
63 |
that were not in the most recent backup. Maybe I should try to rescue |
64 |
only the partition /home. However this partition is under LVM. |
65 |
Specifically, /dev/sda4 is a linux LVM partition. The volume group is |
66 |
vfda and the logical volume of interest is /dev/vfda/home which has |
67 |
reiserfs file system. Is it possible to rescue data only from this |
68 |
partition when under LVM? |
69 |
|
70 |
> Valmor: when I ran the `ddrescue -dr3` stage I had no success at all, >however the system was fine after a reboot & a `chkdsk`. Better than it had >been, in fact, on the old hard-drive. You might have more luck getting *some* >of the blocks showing as failed when you run it on your drive, but don't be >too disheartened if you don't. |
71 |
|
72 |
> Stroller. |
73 |
|
74 |
Stroller, you mean your rescue.log showed no problematic entries? I |
75 |
got over 400 lines in my rescue.log file. |
76 |
|
77 |
root@sysresccd /root % head rescued.log |
78 |
# Rescue Logfile. Created by GNU ddrescue version 1.11 |
79 |
# current_pos current_status |
80 |
0xDB45D9000 ? |
81 |
# pos size status |
82 |
0x00000000 0x9CE341000 + |
83 |
0x9CE341000 0x00000200 - |
84 |
0x9CE341200 0x0001F000 * |
85 |
0x9CE360200 0x00000200 - |
86 |
0x9CE360400 0x00020000 * |
87 |
0x9CE380400 0x3BD63AC00 + |
88 |
|
89 |
|
90 |
|
91 |
Thanks for inputs. |
92 |
|
93 |
-- |
94 |
Valmor |