On Wed, Jun 24, 2009 at 11:11:21PM +0100, krad wrote:
Personally id stay away from dd. Create the partitions and file systems
manually, and install the boot loader, then rsync the data across. It will
be a lot faster in most cases, as unlike dd you wont be copying unused
space. Something like
I wound up using kraduk's suggestion except for using a snapshot instead of a
live file system. Because the source disk had suffered DMA errors and a few
files lost to SOFT UPDATE errors, I built a full system first and then let
rsync merge the two.
mount -u -o snapshot /snapshot/snap1 /
/** / /mnt
I'm assuming you weren't migrating due to a bad disk
-Original Message-
From: owner-freebsd-hack...@freebsd.org
[mailto:owner-freebsd-hack...@freebsd.org] On Behalf Of Jim Flowers
Sent: 23 June 2009 05:55
To: freebsd-hackers@freebsd.org
Subject: dd copy of FreeBSD-7.2 won't boot
I have
On Tue, 23 Jun 2009, Jim Flowers wrote:
I have a remote server that was dd copied from one hard drive to
another - essentially the same size. The disk device name (ad4) is
the same but the geometry for the new drive has a CHS of 969021/16/63
On booting it hangs at:
F1FreeBSD
Boot:
I have a remote server that was dd copied from one hard drive to another -
essentially the same size. The disk device name (ad4) is the same but the
geometry for the new drive has a CHS of 969021/16/63
On booting it hangs at:
F1FreeBSD
Boot: F1
I copied the MBR with 'boot0cfg -B
On Tue, 23 Jun 2009, Wojciech Puchar wrote:
Any help on direction to solve this?
try fdisk -B /dev/ad0
but even better next time don't make slices, only disklabel. It just
make life simpler. I still don't understand why sysinstall by default
create them. It should be only used when windoze
I have a remote server that was dd copied from one hard drive to another -
essentially the same size. The disk device name (ad4) is the same but the
geometry for the new drive has a CHS of 969021/16/63
On booting it hangs at:
F1FreeBSD
Boot: F1
I copied the MBR with 'boot0cfg -B
7 matches
Mail list logo
