From owner-freebsd-questions Sun Feb 10 8:55:31 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fedde.littleton.co.us (cfedde.dsl.frii.net [216.17.139.141]) by hub.freebsd.org (Postfix) with ESMTP id 15E7A37B402; Sun, 10 Feb 2002 08:55:29 -0800 (PST) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) by fedde.littleton.co.us (8.12.2/8.12.2) with ESMTP id g1AGtSD4014807; Sun, 10 Feb 2002 09:55:28 -0700 (MST) Message-Id: <200202101655.g1AGtSD4014807@fedde.littleton.co.us> To: jacks@sage-american.com Cc: Giorgos Keramidas , freebsd-questions@FreeBSD.ORG Subject: Re: Using dd to clone HD In-Reply-To: <3.0.5.32.20020210075653.0195ca18@mail.sage-american.com> From: Chris Fedde Date: Sun, 10 Feb 2002 09:55:27 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Feb 2002 07:56:53 -0600 jacks@sage-american.com wrote: +------------------ | Thanks for the reply. I went ahead and tried the 'dd' approach using two | identical 10GB HDs on an experimental box where I wasn't concerned about | the result just to see what would happen. After more than two hours of | copying, I decided to abort the process because 10GB is a pretty small HD | and it would be a very long process to use on the bigger HDs. | | Of course the abort trashed the 2nd HD but fixed it with FDISK. Back to the | drawing board, perhaps with some of your other suggestions. I already use | tar.... +------------------ using DD to clone disk drives has the advantage that it does not depend on the drive archetecture. It has the disadvantage that it copys every byte on the disk. An approach that combines disklabel, newfs and dump can work well. -- Chris Fedde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message