blob: c5ccb36dd49fb2acc1b66ae3b4835a3abb80bc0a (
plain)
1 CAUTION:
2
3 I would like to point that relates to an unfinished image.
4
5 In any event, anything less than a 100% recovery will leave portions on
6 the target image/drive that have not been written to by ddrescue.
7
8 If copying to a brand new hard drive, those areas are (hopefully) likely
9 to be zeros. But in any other case, those areas will contain whatever data
10 was there previously. For someone that uses their system for data recovery
11 on a regular basis, and is using image files or reusing hard drives, those
12 areas could contain data from a previous recovery! This could be a privacy
13 issue in some cases, but also could cause an issue with running any other
14 sort of repair/file recovery tools on the recovered image/drive.
15
16 The unrecovered parts could contain "garbage" data that could affect
17 accurate recovery. In these cases I would recommend using the fill mode
18 of ddrescue to fill any unfinished/untried areas with zeros.
19
20 Example command:
21
22 ddrescue --fill-mode=?/*- /dev/zero recovered_image logfile
23
24 This would write zeros to any portion of the recovery that was not
25 successfully read from the source.
26
27 Reference:
28 https://lists.gnu.org/archive/html/bug-ddrescue/2013-11/msg00011.html
|
