TiVo Community Forums Archives - Is there a way to stop a DD copy?

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

Is there a way to stop a DD copy?
(Click here to view the original thread with full colors/images)

Posted by: David Platt

I'm sure this has been asked before, but it's pretty hard to search for topics on DD since it's less than three letters. I couldn't find it.

I'm DDing a 160GB Series 2 DirecTiVo drive to another 160GB drive. DMA is enabled, and they're on different IDE channels. The last time I did this, it finished in under three hours. This time, it's been going for over eight hours and is still not completed.

Is there a safe way to abort the DD without harming the source drive?

Posted by: weaknees

Ctrl-z or Ctrl-c should do it. If not, you may have crashed.

Michael

Posted by: Deja-vue

I copied 2 identical Hard drives, both 160 Gigs.

One of them in my hot-swap Raid-controller, the other one using the good old DD-Command

The Raid finished after 12 hours, the DD command finished after 16 hours.
be patient!

look at the tiny little LED's on the Hard drive controllers, if there is still something going on. ( flasing)
good luck!
;)

Posted by: c3

With DMA and block size of 1MB, it's 30-40GB per hour for me. What block size (bs=) did you use?

When you stop "dd", it tells you the number of blocks it has copied. You can continue dd with iseek/skip and oseek/seek parameters.

Posted by: David Platt

quote:
Originally posted by c3
With DMA and block size of 1MB, it's 30-40GB per hour for me. What block size (bs=) did you use?

When you stop "dd", it tells you the number of blocks it has copied. You can continue dd with iseek/skip and oseek/seek parameters.

My block size was 32. I'm going to run some diagnostics on the destination drive today; I have a suspicion it might be bad.

Posted by: c3

quote:
Originally posted by David Platt
My block size was 32.

If you used "bs=32", that means 32 bytes. If that's really the case, it will take forever. If there are bad sectors, you should see error messages on the screen.

Posted by: David Platt

quote:
Originally posted by c3
If you used "bs=32", that means 32 bytes. If that's really the case, it will take forever. If there are bad sectors, you should see error messages on the screen.

Sorry; I should have been clearer about that. My blocksize was 32k.