Date: 14 Feb 2003 17:27:33 -0800 From: Arun Sharma <arun.sharma@intel.com> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-ia64@FreeBSD.ORG Subject: Re: FreeBSD ia64 install problems WAS: install on Dell Precision Work Station 730 Message-ID: <ulm0i1gfu.fsf@unix-os.sc.intel.com> In-Reply-To: <20030214024721.GB1573@athlon.pn.xcllnt.net> References: <03781128C7B74B4DBC27C55859C9D7380B9DDB5D@es06snlnt.sandia.gov> <20030210203522.GA543@athlon.pn.xcllnt.net> <ur8ab1u5l.fsf@unix-os.sc.intel.com> <20030214024721.GB1573@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar <marcel@xcllnt.net> writes:
> >
> > What's the recommended tool to set the GPT partition type ?
>
> That depends. If you're running Linux, use diskpart. If you only
> have EFI, get Intel's EFI tool. When running FreeBSD, use gpt(8).
Linux uses GNU parted or a distribution specific tool. GNU parted
doesn't know about the FreeBSD GUID type nor does it allow entering
the guid type manually. It maps filesystem types to GUID types (by
design).
After I hacked GNU parted to map "hp-ufs" filesystem type to FreeBSD
GUID i.e. 516e7cb4-6ecf-11d6-8ff8-00022d09712b, I see:
Minor Start End Filesystem Name Flags
1 0.017 203.938 fat32 boot
2 203.938 10447.875 fat32
< other partitions snipped>
1 -> EFI partition
2 -> FreeBSD partition (parted shows fat32, but the guid is correct)
# od -x /dev/sda
shows the following
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0000700 0001 feee ffff 0001 0000 0b03 0224 0000
0000720 0000 0000 0000 0000 0000 0000 0000 0000
*
0000760 0000 0000 0000 0000 0000 0000 0000 aa55
0001000 4645 2049 4150 5452 0200 0001 005c 0000
0001020 793a 6b75 0000 0000 0001 0000 0000 0000
0001040 0b03 0224 0000 0000 0022 0000 0000 0000
0001060 0ae2 0224 0000 0000 9654 3892 b140 473c
0001100 ffbc b53a efc0 8220 0002 0000 0000 0000
0001120 0080 0000 0080 0000 3f55 f673 0000 0000
0001140 0000 0000 0000 0000 0000 0000 0000 0000
*
0002000 7328 c12a f81f 11d2 4bba a000 3ec9 3bc9
0002020 b13b 8578 1666 414a cb97 b159 d30a d2e0
0002040 0022 0000 0000 0000 5f81 0006 0000 0000
0002060 0000 0000 0000 0000 0000 ffff ffff ffff
0002100 ffff ffff ffff ffff ffff ffff ffff ffff
*
0002200 7cb4 516e 6ecf 11d6 f88f 0200 092d 2b71 <-- FreeBSD GUID
0002220 8bac b89e 1624 40ad b29c 6052 1595 d45c
0002240 5f82 0006 0000 0000 7f00 0146 0000 0000
0002260 0000 0000 0000 0000 0000 ffff ffff ffff
0002300 ffff ffff ffff ffff ffff ffff ffff ffff
When I installed FreeBSD over this partition, the instalation went ok,
but when I reboot, EFI couldn't find fs0 any more. On further
investigation, I found that the FreeBSD installer had written the
partitioning info to MBR. Normally MBR contains a fake EFI
partition. After the FreeBSD installation, Linux fdisk showed that
/dev/sda1 (0xee) EFI GPT had been deleted and replaced by
/dev/sda2 (0xa5) FreeBSD with the start and end corresponding to
the GPT partition I'd created for FreeBSD.
I went back and restored the MBR to it's original form, so that EFI
could look into the GPT. Now when I try to boot FreeBSD, it can't
find "ufs:da0s2a".
So my question is, what do I need to do to the GPT to get FreeBSD
recognize it properly ? Have I screwed up on the endianness of the GUID ?
I'd like to see an octal dump of a working GPT, if possible.
-Arun
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?ulm0i1gfu.fsf>