From owner-freebsd-hackers  Sun Oct  5 04:38:07 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id EAA14014
          for hackers-outgoing; Sun, 5 Oct 1997 04:38:07 -0700 (PDT)
Received: from bubble.didi.com (sjx-ca25-27.ix.netcom.com [204.30.65.219])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA14005
          for <hackers@freebsd.org>; Sun, 5 Oct 1997 04:38:03 -0700 (PDT)
Received: (from asami@localhost)
	by bubble.didi.com (8.8.7/8.8.5) id EAA00727;
	Sun, 5 Oct 1997 04:38:31 -0700 (PDT)
Date: Sun, 5 Oct 1997 04:38:31 -0700 (PDT)
Message-Id: <199710051138.EAA00727@bubble.didi.com>
To: kyle@heathers2.stdio.com
CC: hackers@freebsd.org
In-reply-to: <Pine.SUN.3.91.971004155906.18214A-100000@heathers2.stdio.com> (message from Kyle McPeek on Sat, 4 Oct 1997 16:02:48 -0400 (EDT))
Subject: Re: Replacing a drive in a ccd array...
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * I have thought about using dd to copy the data from the old drive to the 
 * new one, will this work ok?  If so, which device(s) should I copy from/to?

Well, that will probably work, assuming the old drive can survive
that.  Try something like

dd if=/dev/rsdXX of=/dev/rsdYY bs=2k

where "XX" and "YY" are the numbers of corresponding drives.

BTW, the above assumes the drives are identical models and thus you
can just copy the whole thing bit-by-bit.  If not, you will need to
create a disklabel on the new drive and do a copy of the appropriate
partitions (e.g., "/dev/rsd0g").

Satoshi