Date: Mon, 01 Aug 2005 08:21:15 -0700 From: garys@opusnet.com (Gary W. Swearingen) To: alexandre.delay@free.fr Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, freebsd-questions@freebsd.org Subject: Re: Migrate primary disk (duplicate) Message-ID: <xtslxt4r9w.lxt@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 > ... > > the disk doesn't boot. So "fdisk -B ad3" shouldn't work if you don't have a valid partition table which also has the correct fdisk partition marked "active" (or "bootable", which I'm fairly sure is the same thing, despite what the fdisk manual implies). But is seem that "fdisk -I ad3" should work if you have a "s1" correctly configured and populated. But after using it, I'd run "fdisk ad3" and verify that your "s1" is marked "(active)". It sound like /boot/mbr behaves like an IBM/MSFT MBR, while /boot/boot0 is the standard FreeBSD MBR configured by "boot0cfg".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xtslxt4r9w.lxt>