Date: Mon, 01 Aug 2005 07:58:56 -0700 From: garys@opusnet.com (Gary W. Swearingen) To: alexandre.delay@free.fr Cc: freebsd-questions@freebsd.org Subject: Re: Migrate primary disk (duplicate) Message-ID: <s1zms14sb3.ms1@mail.opusnet.com> In-Reply-To: <1122889913.42edf0b9cc43e@imp6-q.free.fr> (alexandre delay's message of "Mon, 01 Aug 2005 11:51:53 %2B0200") References: <1122880808.42edcd280f5fd@imp6-q.free.fr> <20050801094151.GA16934@beatrix.daedalusnetworks.priv> <1122889913.42edf0b9cc43e@imp6-q.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
alexandre.delay@free.fr writes: > I tried every combination: > fdisk -I ad3 && fdisk -B -b /boot/mbr ad3 > fdisk -I ad3 && fdisk -B -b /boot/boot0 ad3 > fdisk -B -b /boot/mbr -I ad3 Assuming that you've got the rest of the file systems configured and populated properly, as I think you said, and you really only need to get the MBR right... I'd try using "boot0cfg", which has always worked for me. BTW, you don't need "-b /boot/mbr" because that's the default. Just based on my manpage reading: It sounds like "-I" and "-B" do quite different things and using them together is problematical. With -I, it sets up the partition table to support only "ad3s1". With -B, it probably doesn't touch the partition table, and only changes the boot code in the first 446 bytes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?s1zms14sb3.ms1>