1 |
On Tuesday, 18 December 2018 17:11:28 GMT Jack wrote: |
2 |
> On 2018.12.18 04:43, Peter Humphrey wrote: |
3 |
> > On Monday, 17 December 2018 23:19:39 GMT Jack wrote: |
4 |
> >> At this point, I think I've forgotten the details, but using the |
5 |
> >> example of a 300G drive with 100G empty and then a 200G partition, |
6 |
> >> when I moved the partition to the beginning of the disk (using |
7 |
> >> gparted, as I remember) once it moved more than the first 100G of |
8 |
> >> the partition, it overwrote the beginning of the original partition, |
9 |
> >> and once it overwrote any of the directory structure it still needed |
10 |
> >> to know where stuff was, game over. |
11 |
> > |
12 |
> > Gparted can handle that without difficulty - I do it often - so I |
13 |
> > think you must be mistaken in the tool you used. |
14 |
> |
15 |
> No, not mistaken in which tool, but likely mistaken in my memory of the |
16 |
> exact course of events. It's possible the gparted move operation was |
17 |
> interrupted. Could have been an accidental Ctl-C or a power failure. |
18 |
> However, at this point, I'd need a better crystal ball looking |
19 |
> backwards to know for sure. |
20 |
> |
21 |
> > Sorry not to be more helpful... |
22 |
> |
23 |
> I have more responses for elsewhere in the thread, but I think any |
24 |
> further serious attempts at recovery are going to have to wait until I |
25 |
> buy a new disk or two, so I can do everything internal on the desktop, |
26 |
> and not on the laptop with USB. |
27 |
> |
28 |
> > -- |
29 |
> > Regards, |
30 |
> > Peter. |
31 |
> |
32 |
> Jack |
33 |
|
34 |
I know others have commented on the reliability of recovering data from drives |
35 |
connected via USB caddy, but I have had satisfactory results on a number of |
36 |
cases. |
37 |
|
38 |
The last time I tried to recover data from a failing disk, which had SMART |
39 |
End-to-End errors increasing continuously and read errors with ddrescue going |
40 |
up each time I ran it. |
41 |
|
42 |
I cloned the whole drive having run ddrescue backwards and forwards a couple |
43 |
of times. c/f/gdisk would see all partitions, but when I tried to mount the |
44 |
cloned /dev/sdb4 (NTFS) with ntfs-3g it complained there was no device found |
45 |
(/dev/sdb4). I got the same error with the failing drive. |
46 |
|
47 |
So, I used losetup with --offset on the failing drive itself over USB 2.0 and |
48 |
was able to mount and recover all the NTFS files. |
49 |
|
50 |
Over the years I've used clonezilla, ddrescue, testdisk, photorec and losetup |
51 |
to recover files. On a couple of times where data on the disk had been |
52 |
overwritten by subsequent operations, I was not able to recover the affected |
53 |
files. So, if when moving the partition data was overwritten I suspect it |
54 |
will be very difficult to recover this with conventional software tools. |
55 |
However, it doesn't hurt to try. :-) |
56 |
|
57 |
-- |
58 |
Regards, |
59 |
Mick |