Hearns, John wrote:
--- Ug... I would rather have it die and try again -- sometimes a reread will work... if you have to copy a known bad disk, then what you suggest is reasonable, but on disks with no known problems...???
On the subject of using 'dd' to read from a disk which has known bad sectors, Have a look at the 'ddrescue' utility which will retry reads: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
Good idea. If you have a bad disk, you should use a special tool for it. Somehow this topic seems to have migrated from how to do disk to disk copy w/o using command line (and so many of us try to tell him the command line is by far the best for something this simple), to dealing with bad sector in a source disk... which fortunately for me, is a rare situation. But seriously dd is your most reliable be. A gui won't have the decades of use behind it. dd if=/dev/sda of=/dev/sdb bs=64M iflag=direct oflag=direct & pid=$! ^ ^ output file (destination) ^^ says to not waste time w/extra mem copies -input file (source disk) the & on the end puts it in background, and the pid=$! stores the process number of it then "kill -USR1 $pid" every once in a while and it will print out how much it has done: 18335302+0 records in 18335302+0 records out 9387674624 bytes (9.4 GB) copied, 34.6279 seconds, 271 MB/s Note, for the bs, above, adjust it to the size of the cache memory on your destination disk and be sure write-caching is enabled. That way when you write to it, it goes into the write cache FAST, and dd, can start reading the next block size while the destination disk is flushing it's buffer to disk... I.e. you'll get much better performance in doing the copy. But it's not a GUI...so it doesn't really answer your question...but I'd strongly recommend against using an arbitrary GUI product for something this simple.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org