In ddrescue, should the target drive be formatted the same way as the damaged drive?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Friends: I have 3 brief questions about ddrescue. This is the operation that I want to run:
sudo ddrescue -f -n -v -v -v -v /dev/sdi /dev/sdh RescueHD10.log
For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In other words, if the input drive is NTFS, should the output also be formatted NTFS?)
The output drive, "/dev/sdh", has to be mounted, correct?
The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
Thank you all for your help!!
hard-disk data-recovery corruption ddrescue
asked Jul 4 at 20:17
user584936
92
add a comment |Â
up vote
1
down vote
favorite
Friends: I have 3 brief questions about ddrescue. This is the operation that I want to run:
sudo ddrescue -f -n -v -v -v -v /dev/sdi /dev/sdh RescueHD10.log
For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In other words, if the input drive is NTFS, should the output also be formatted NTFS?)
The output drive, "/dev/sdh", has to be mounted, correct?
The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
Thank you all for your help!!
hard-disk data-recovery corruption ddrescue
asked Jul 4 at 20:17
user584936
92
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Friends: I have 3 brief questions about ddrescue. This is the operation that I want to run:
sudo ddrescue -f -n -v -v -v -v /dev/sdi /dev/sdh RescueHD10.log
For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In other words, if the input drive is NTFS, should the output also be formatted NTFS?)
The output drive, "/dev/sdh", has to be mounted, correct?
The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
Thank you all for your help!!
hard-disk data-recovery corruption ddrescue
asked Jul 4 at 20:17
user584936
92
Friends: I have 3 brief questions about ddrescue. This is the operation that I want to run:
sudo ddrescue -f -n -v -v -v -v /dev/sdi /dev/sdh RescueHD10.log
For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In other words, if the input drive is NTFS, should the output also be formatted NTFS?)
The output drive, "/dev/sdh", has to be mounted, correct?
The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
Thank you all for your help!!
hard-disk data-recovery corruption ddrescue
asked Jul 4 at 20:17
user584936
92
asked Jul 4 at 20:17
user584936
92
asked Jul 4 at 20:17
user584936
92
asked Jul 4 at 20:17
user584936
92
92
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
- For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In
other words, if the input drive is NTFS, should the output also be
formatted NTFS?)
No, the cloning process will overwrite whatever is on the target drive anyway.
But the target drive must have at least the same size as the source drive, not one single byte less for the cloning to be successful. This is enough with an MSDOS partition table.
If there is a GUID partition table, GPT, and the target drive is bigger, you must also repair the backup partition table at the tail end of the drive. You can do it with gdisk.
- The output drive, "/dev/sdh", has to be mounted, correct?
No, if there are partitions on the target drive, they should not be mounted, when cloning. The same holds for the source drive: No partition should be mounted.
- The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
I am not sure, but info ddrescue talks about further -v's so use that syntax.
answered Jul 4 at 20:51
sudodus
47615
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscriptgpt-fix, which will select suitable commands forgdisk:v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.
– sudodus
Jul 5 at 5:12
add a comment |Â
up vote
1
down vote
The tool is a block copy. You're copying the entire drive so the partition table, filesystem structures and everything will be copied from the source to the destination.
No. Emphatically no. You're about to overwrite it at the block level. If you have a mounted filesystem there you may well introduce unintended corruption. Ensure that the source disk is also unmounted. Neither must be in use.
That depends on the particular command, and unfortunately it's not possible to generalise.
You may want to increase the read/write chunk size; the default is 512 byte chunks which is very small. Try 128KB or even bigger.
answered Jul 4 at 20:48
roaima
39.2k544105
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
- For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In
other words, if the input drive is NTFS, should the output also be
formatted NTFS?)
No, the cloning process will overwrite whatever is on the target drive anyway.
But the target drive must have at least the same size as the source drive, not one single byte less for the cloning to be successful. This is enough with an MSDOS partition table.
If there is a GUID partition table, GPT, and the target drive is bigger, you must also repair the backup partition table at the tail end of the drive. You can do it with gdisk.
- The output drive, "/dev/sdh", has to be mounted, correct?
No, if there are partitions on the target drive, they should not be mounted, when cloning. The same holds for the source drive: No partition should be mounted.
- The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
I am not sure, but info ddrescue talks about further -v's so use that syntax.
answered Jul 4 at 20:51
sudodus
47615
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscriptgpt-fix, which will select suitable commands forgdisk:v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.
– sudodus
Jul 5 at 5:12
add a comment |Â
up vote
2
down vote
- For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In
other words, if the input drive is NTFS, should the output also be
formatted NTFS?)
No, the cloning process will overwrite whatever is on the target drive anyway.
But the target drive must have at least the same size as the source drive, not one single byte less for the cloning to be successful. This is enough with an MSDOS partition table.
If there is a GUID partition table, GPT, and the target drive is bigger, you must also repair the backup partition table at the tail end of the drive. You can do it with gdisk.
- The output drive, "/dev/sdh", has to be mounted, correct?
No, if there are partitions on the target drive, they should not be mounted, when cloning. The same holds for the source drive: No partition should be mounted.
- The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
I am not sure, but info ddrescue talks about further -v's so use that syntax.
answered Jul 4 at 20:51
sudodus
47615
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscriptgpt-fix, which will select suitable commands forgdisk:v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.
– sudodus
Jul 5 at 5:12
add a comment |Â
up vote
2
down vote
up vote
2
down vote
- For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In
other words, if the input drive is NTFS, should the output also be
formatted NTFS?)
No, the cloning process will overwrite whatever is on the target drive anyway.
But the target drive must have at least the same size as the source drive, not one single byte less for the cloning to be successful. This is enough with an MSDOS partition table.
If there is a GUID partition table, GPT, and the target drive is bigger, you must also repair the backup partition table at the tail end of the drive. You can do it with gdisk.
- The output drive, "/dev/sdh", has to be mounted, correct?
No, if there are partitions on the target drive, they should not be mounted, when cloning. The same holds for the source drive: No partition should be mounted.
- The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
I am not sure, but info ddrescue talks about further -v's so use that syntax.
answered Jul 4 at 20:51
sudodus
47615
- For me, the output drive "/dev/sdh", is brand new. Does it have to be formatted the same way as the input (i.e., damaged) drive? (In
other words, if the input drive is NTFS, should the output also be
formatted NTFS?)
No, the cloning process will overwrite whatever is on the target drive anyway.
But the target drive must have at least the same size as the source drive, not one single byte less for the cloning to be successful. This is enough with an MSDOS partition table.
If there is a GUID partition table, GPT, and the target drive is bigger, you must also repair the backup partition table at the tail end of the drive. You can do it with gdisk.
- The output drive, "/dev/sdh", has to be mounted, correct?
No, if there are partitions on the target drive, they should not be mounted, when cloning. The same holds for the source drive: No partition should be mounted.
- The "-v" signifies verbose. Does it make a difference if it's "-v -v -v -v" versus "-vvvv"?
I am not sure, but info ddrescue talks about further -v's so use that syntax.
answered Jul 4 at 20:51
sudodus
47615
answered Jul 4 at 20:51
sudodus
47615
answered Jul 4 at 20:51
sudodus
47615
answered Jul 4 at 20:51
sudodus
47615
47615
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscriptgpt-fix, which will select suitable commands forgdisk:v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.
– sudodus
Jul 5 at 5:12
add a comment |Â
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscriptgpt-fix, which will select suitable commands forgdisk:v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.
– sudodus
Jul 5 at 5:12
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
So if the target device (/dev/sdh) in the example above is larger than the input/damaged device (/dev/sdi), I have to repair the backup partition table? I do that with "sudo gdisk /dev/sdh", press "p" to print, "w" to write and "q" to quit? Would it be better/easier to just format a partition on the target device that is the same size as the input/damaged device? Thanks! And pardon my ignorance!
– user584936
Jul 5 at 3:57
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscript
gpt-fix, which will select suitable commands for gdisk: v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.– sudodus
Jul 5 at 5:12
@user584936, Please notice that this is only relevant for GPT. If you want guidance, you can use the shellscript
gpt-fix, which will select suitable commands for gdisk: v, x, e, r, d, w, y, as you can see, if you look at it in a text viewer or editor.– sudodus
Jul 5 at 5:12
add a comment |Â
up vote
1
down vote
The tool is a block copy. You're copying the entire drive so the partition table, filesystem structures and everything will be copied from the source to the destination.
No. Emphatically no. You're about to overwrite it at the block level. If you have a mounted filesystem there you may well introduce unintended corruption. Ensure that the source disk is also unmounted. Neither must be in use.
That depends on the particular command, and unfortunately it's not possible to generalise.
You may want to increase the read/write chunk size; the default is 512 byte chunks which is very small. Try 128KB or even bigger.
answered Jul 4 at 20:48
roaima
39.2k544105
add a comment |Â
up vote
1
down vote
The tool is a block copy. You're copying the entire drive so the partition table, filesystem structures and everything will be copied from the source to the destination.
No. Emphatically no. You're about to overwrite it at the block level. If you have a mounted filesystem there you may well introduce unintended corruption. Ensure that the source disk is also unmounted. Neither must be in use.
That depends on the particular command, and unfortunately it's not possible to generalise.
You may want to increase the read/write chunk size; the default is 512 byte chunks which is very small. Try 128KB or even bigger.
answered Jul 4 at 20:48
roaima
39.2k544105
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The tool is a block copy. You're copying the entire drive so the partition table, filesystem structures and everything will be copied from the source to the destination.
No. Emphatically no. You're about to overwrite it at the block level. If you have a mounted filesystem there you may well introduce unintended corruption. Ensure that the source disk is also unmounted. Neither must be in use.
That depends on the particular command, and unfortunately it's not possible to generalise.
You may want to increase the read/write chunk size; the default is 512 byte chunks which is very small. Try 128KB or even bigger.
answered Jul 4 at 20:48
roaima
39.2k544105
The tool is a block copy. You're copying the entire drive so the partition table, filesystem structures and everything will be copied from the source to the destination.
No. Emphatically no. You're about to overwrite it at the block level. If you have a mounted filesystem there you may well introduce unintended corruption. Ensure that the source disk is also unmounted. Neither must be in use.
That depends on the particular command, and unfortunately it's not possible to generalise.
You may want to increase the read/write chunk size; the default is 512 byte chunks which is very small. Try 128KB or even bigger.
answered Jul 4 at 20:48
roaima
39.2k544105
answered Jul 4 at 20:48
roaima
39.2k544105
answered Jul 4 at 20:48
roaima
39.2k544105
answered Jul 4 at 20:48
roaima
39.2k544105
39.2k544105
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453490%2fin-ddrescue-should-the-target-drive-be-formatted-the-same-way-as-the-damaged-dr%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password