Date: Fri, 24 Mar 2006 13:12:31 -0500 From: Mike Meyer <mwm-keyword-freebsdhackers.102a7e@mired.org> To: vd@freebsd.org Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Khaled Hussain <khaled@ipbill.com>, Dirk GOUDERS <gouders@et.bocholt.fh-ge.de> Subject: Re: cloning a FreeBSD HDD Message-ID: <17444.13967.998120.314837@bhuda.mired.org> In-Reply-To: <20060324174235.GA58111@qlovarnika.bg.datamax> References: <HCEOIFALKKLBLJPENPNOMEMNCAAA.khaled@ipbill.com> <200603241719.k2OHJDbh012213@sora.hank.home> <20060324174235.GA58111@qlovarnika.bg.datamax>
next in thread | previous in thread | raw e-mail | index | archive | help
In <20060324174235.GA58111@qlovarnika.bg.datamax>, Vasil Dimov <vd@freebsd.org> typed: > On Fri, Mar 24, 2006 at 06:19:13PM +0100, Dirk GOUDERS wrote: > Without reading it, I would first try this, it's quite straightforward > > * boot into single user mode (enter "boot -s" at loader prompt) > * make sure filesystems are mounted readonly (mount) > dd if=/dev/ad0 of=/dev/ad1 bs=1m > (where ad0 is your disk with data and ad1 is your new disk, make sure > you do not swap them :) Doesn't really matter in single user mode - you'll just copy the swap over. But yeah, this procedure works fine for me in the past. One thing: 1m is a bit small for modern systems. Or for not-so-modern systems. Since nothing else is running, you might as well use all the memory you've got, or as big as you can get a process to be. 128m or more is perfectly reasonable. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17444.13967.998120.314837>