Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Proper Cloning

December 28th, 2010, 14:18

It took forever, but I rescued everything from a corrupt drive onto a brand new one with ddrescue.

I would now like to clone my healthy drive to have a 2nd copy of everything. I was told this is the syntax to use:

dd if=/dev/src of=/dev/dst bs=512000 count=2000000

Just wanted to double check if that's correct? ... would hate to do anything to jeopardize the data on this new drive.

Re: Proper Cloning

December 28th, 2010, 14:51

No need for count if you are cloning the entire drive

Re: Proper Cloning

January 2nd, 2011, 5:32

i ran my command: dd if=/dev/sdb of=/dev/sda bs=512000
(making double sure the source and destination drives were right)

but now dd just sort of hangs, there's a flashing cursor, but no other output.
is that normal?

i know for sure linux could see both drives, it showed them both to me in /dev/ ...
* the 'source' new drive that has my recovered data was listed as sdb, sdb1, sdb5, sdb6 (same partition layout as the old failed drive that was previously ddrescued onto it)
* the 2nd brand new drive was listed as sda.
* there were no other sd_ entries shown, nor any other drives connected to motherboard.

Re: Proper Cloning

January 2nd, 2011, 12:51

Yep

Re: Proper Cloning

January 2nd, 2011, 17:26

'bs' switch states: read and write BYTES bytes at a time
So if you change default 512 to 512000 dd can hang sometimes ;)
And for checking what is going on with dd you have to use kill command:
kill -USR1 [dd PID]

Re: Proper Cloning

January 2nd, 2011, 20:57

Thanks for the info. I didn't realize when I ran it that dd is just kind of silent when it runs. But I believe it finished the clone job correctly.
Post a reply