Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 04 Feb 2003 14:34:15 -0600
From:      Juan E Navarro <jnavarro@cs.rice.edu>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        "freebsd-ia64@FreeBSD.ORG" <freebsd-ia64@FreeBSD.ORG>
Subject:   Re: MBR/GPT mess :-) [was: Re: Problems with fxp driver]
Message-ID:  <3E4023C7.657B8CD5@cs.rice.edu>
References:  <3E35E4A9.3C8A4845@cs.rice.edu> <20030128021356.GA1228@athlon.pn.xcllnt.net> <3E38AC98.E8C6FF17@cs.rice.edu> <20030130045351.GB1574@athlon.pn.xcllnt.net> <3E38B494.7250D2AE@cs.rice.edu> <20030130055100.GA1717@athlon.pn.xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote:
>
> Ok. The "bogus map" error is an indication that you have both an
> MBR partition and a GPT partition that overlap. Now the really
> bad news: you cannot fix this easily, because we have a new disk
> partitioning framework that tries to be helpful. It's designed
> to be a pain in the ass :-(

I guess the easy fix is to wipe the entire disk, repartition and
reinstall. Diskpart doesn't work because it complains that the disk is
an MBR disk. I might do that with one of the two machines I'm playing
with.

The other machine has 2 disks. One is a sane GPT disk with an EFI and a
Windows partition. The other disk has the MBR/GPT problem (due to a
previous Linux installation?). For now I'm unsing the EFI partition of
the sane disk to boot FreeBSD: if I mount that partition in /boot and
add
vfs.root.mountfrom="ufs:da0s1a" to /boot/loader.conf, then I can
recompile the kernel and enjoy unattended reboots. I suppose that as
long as nobody tries to use the GPT partitions of the FreeBSD disk then
I'm OK. Is that a safe assumption?

-- 
++*Juan--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E4023C7.657B8CD5>